Jump to content

Search the Community

Showing results for tags 'windows 10'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • MSPGeek
    • Announcements
    • The Geek Cast
  • 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

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 5 results

  1. 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 under the LTsvc\packages folder on each machine. Rather than download 50 x 4GB ISO's for a client, I thought to use the server to then have Automate copy this locally, but I'm struggling. My plan was to create an EDF whereby we can enter at the location level the path to the ISO and then call this in a variable for the Script copy as Admin but it doesn't seem to unpack the variable path and the script fails. Has anybody else had any success upgrading from 1803/1809/1903 using Automate? Any help would be appreciated!
  2. 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 "FlightCommitted"=dword:00000000 "LastToastAction"=dword:00000000 "RestartNotificationsAllowed"=dword:00000001 "UxOption"=dword:00000004 "InsiderProgramEnabled"=dword:00000000 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Notifications\Settings] "Windows.SystemToast.Suggested"=dword:00000000 Thank you,
  3. 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
  4. 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?
  5. 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...