Jump to content

Search the Community

Showing results for tags 'windows 10'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • MSPGeek
    • The Geek Cast
    • Code of Conduct
  • ConnectWise Automate / Labtech
    • ConnectWise Automate / LabTech
    • ConnectWise Automate / LabTech - Development

Categories

  • ConnectWise Automate
    • Scripts
    • Plugins
    • SQL Snippets
    • Role Definitions
    • Automate PowerShell Code
    • Reports
    • Internal Monitors
    • Remote Monitors
  • ConnectWise Manage
    • API Interacting Code

Calendars

There are no results to display.


Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


About Me


Location


Agent Count


INTERESTS


OCCUPATION


ICQ


WEBSITE


WLM


YAHOO


AOL


FACEBOOK


GOOGLEPLUS


SKYPE


TWITTER


YOUTUBE

Found 11 results

  1. Version 2.5.0

    526 downloads

    This script will upgrade copies of Windows to whatever Windows 10 ISO you give it. You will need to upload the Windows 10 ISO to your LTShare/Transfer/ folder(by default in the /ISO/ sub folder). For Windows 7 installs, you must put a copy of 7z.dll and 7z.exe in your LTShare/Transfer/ folder(by default in the \Software\7ZipCLI\ sub folder). This is because it extracts the ISO since Windows 7 can't mount it. I recommend a 32bit copy because they work for both 32 and 64bit. You can download the 7-Zip installer and open it with 7-Zip like a zip file to extract just those files without bothering
  2. THE PROBLEM: Windows Update stops reporting the monthly security Cumulative Update and instead only reports the Feature Update to the latest OS release. Automate relies on Windows Update to report that there are available security updates, so it treats it as "Everything is great, no missing updates!" when in fact the system is missing potentially critical Cumulative Updates. I used PSWindowsUpdate to test and confirm the behavior on a number of computers. As of yet, I have not found a way to get around this wonderful "feature" (presumably it works differently if you are using Enterprise o
  3. I am working to create this type of workflow and wondered if anyone has come across this or would know the best way to set it up. Thanks in advance! I am wanting to create a script in Automate that would essentially e-mail the customer with the computers that are needing to be upgraded to the latest version of Windows 10. Then, once that e-mail is sent, the script then schedules the upgrade script to run on the weekend for those computers listed in the e-mail.
  4. View File Windows 7,8,10 Upgrade Script This script will upgrade copies of Windows to whatever Windows 10 ISO you give it. You will need to upload the Windows 10 ISO to your LTShare/Transfer/ folder(by default in the /ISO/ sub folder). For Windows 7 installs, you must put a copy of 7z.dll and 7z.exe in your LTShare/Transfer/ folder(by default in the \Software\7ZipCLI\ sub folder). This is because it extracts the ISO since Windows 7 can't mount it. I recommend a 32bit copy because they work for both 32 and 64bit. You can download the 7-Zip installer and open it
  5. Hola, Pretty new to Automate. I've been looking around for a script to use for groups/companies not on a domain and need console lock set. Manually, it's a registry edit: HKEYLOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\7516b95f-f776-4464-8c53-06167f40cc99\8EC4B3A5-6868-48c2-BE75-4F3044BE88A7 , change Attributes value to 2. Then using the GUI, change adv power settings, adjust Console lock display off timeout value. I've been trying to use CLI powercfg, but the sub GUID for this setting (console lock) is eluding me. Anyone out there dealt with th
  6. Hi All, After speaking with ConnectWise, I understand there is a script from the Solution Centre called 'Windows 10 - Install Feature Update' which requires you to deploy the latest build of Windows 10 to your LTShare, but that it's only a supported feature on-prem and cloud partners currently don't have support for this.. https://docs.connectwise.com/ConnectWise_Automate/ConnectWise_Automate_Knowledge_Base_Articles/Scripting%3A_Windows_10_Install_Feature_Update_Script As a potential workaround, ConnectWise have told me I can individually place the ISO und
  7. I have been trying to get the attached script to run. It shows in the actual device script monitor and then just disappears. We are a hosted client. I could use some help if someone could tell me what I have wrong. Thanks! Windows 10 1903 update Kiffer.xml
  8. I have tried applying several registry keys to no avail, Half of my endpoints are getting 1709 pop-ups the other half are getting critical security pop-ups. The later only seemed to start since upgrading at Labtech 12. Here is what I have tried: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsUpdate\UX\Settings] "ActiveHoursEnd"=dword:00000012 "ActiveHoursStart"=dword:00000005 "BranchReadinessLevel"=dword:00000010 "DeferFeatureUpdatesPeriodInDays"=dword:0000016d "DeferQualityUpdatesPeriodInDays"=dword:00000000 "ExcludeWUDriversInQualityUpdate"=dword:00000000 "FlightCom
  9. I am having issues updating my PC running Windows 10 and Deslock+ Full disk encryption. The error message in the attachment. Has anyone come across this problem? Deslock - Win 10.docx
  10. Hey, I have a batch of Windows 10 systems that aren't updating to the latest and greatest OS build (16299.x). Several are still at 14393 or 15063. The updates are approved in the Patch Manager. Any ideas or suggestions other that manually patching one system at a time?
  11. Plugins4Automate.com has released a new build of Patch Remedy that now handles Windows 10 version 1709. Read our blog for information of what was added to this plugin at https://www.plugins4labtech.com/blogs/blog/patch-remedy-makes-way-for-windows-10-version-1709
×
×
  • Create New...