Patch Remedy Version 4 Beta

Support and question forum for Patch Remedy 4 WUA plugin for LabTech. This plugin was retired on 06/01/2022. All new Patch Remedy 5 is now the current plugin. This forum is for retaining the old posts for Patch Remedy 4.
User avatar
Cubert
Posts: 2457
Joined: Tue Dec 29, 2015 7:57 pm
8
Contact:

Patch Remedy Version 4 Beta

Post by Cubert »

We have a new Patch Remedy version starting, build 1.0.4.x will not start changing out the old charts with DEVExpress charts and we are now incorporating the first automated Windows 10 Version Upgrade feature.

If you want to try beta, make sure to check back here regularly for updates.

You must have an active subscription to Patch Remedy. Patch Remedy is now out of beta and available at https://www.plugins4labtech.com/products/patch-remedy


Re-Read this top post if you are upgrading from any version lower than 1.0.4.10 We have all new setups and configurations to make it easier for you to get going.
First off, if you are upgrading from 1.0.3.94 or earlier you should install plugin and execute the following in SQLYog before restarting the DBAgent.
DROP TABLE plugin_sw_patch_remedy_win10upgrades; DROP TABLE plugin_sw_patch_remedy_win10deferred;DROP TABLE plugin_sw_patch_remedy_wua;
This will cause a few tables to be recreated that Patch Remedy will need moving forward.

We are changing out all the charts. The first one is the main WUA versions bar graph

Capture.PNG
Capture.PNG (214.09 KiB) Viewed 18902 times


We already upgrade the different build inside each Windows 10 Version, Now we upgrade older versions of Windows 10 to the latest version 16299. Select 1 or more agents from the Windows 10 list and enable updates. If they are already up to date. The script will note this in the database and the agent will not be re-updated.

Updates will query for logged in consoles and if user is on console will present a inquiry to user to allow update. The user can refuse and the update will be halted and noted in the database. The update process requires a that the MSP first download and create a Windows 10 64bit ISO and to make that ISO available either on web or via LTShare (depending on desired function.)


Capture1.PNG
Capture1.PNG (230.72 KiB) Viewed 18902 times


The first agent to start a install will download the ISO to the "Location Drive" location set for the location of a given client. All other agents will check here first to see if file exists. If not it will attempt to download and place file here. You must have a network share set or script will bail out. Downloading 4+ GB for 50 Windows 10 agents will cause major headaches for the bandwidth at the location so caching the download is extremely important.


Capture2.PNG
Capture2.PNG (42.34 KiB) Viewed 19207 times


For more information on the setup process visit http://lp.plugins4automate.com/helpfile ... roject.pdf (page 10 or so)


To configure the ISO download via URL or LTShare use tool to configure the settings needed.


Capture2.PNG
Capture2.PNG (195.29 KiB) Viewed 19068 times


Configure A WEB URL if you do not want to use the LTShare. By default if no Web URL exists then script will switch to LTShare instead. The ISO file name is the name of the file to download from the Web or via LTShare. If using LTShare the ISO file must be placed in the following directory [\\LTShare\Transfer\Software\Windows10\]


Capture11.PNG
Capture11.PNG (49.61 KiB) Viewed 18959 times


ISO Web URL allows you to disable the use of the [LTShare] and instead retrieve all ISO files directly from the Internet. This is the preferred way when not all Clients or Locations can reach the LTShare on the LTHost.

32/64bit ISO file tells Patch Remedy what files need to be downloaded based on OS type. If you are updating both 32 and 64 bit systems you will need both ISOs.

The User Message Image allows you to place a custom logo inplace of our default Patch Remedy logo when an user is logged in and an upgrade is pushed.

The User Message allows you to set a HTML message for any logged in user that may be using the system during a upgrade process. The user will be asked if upgrade can continue and then afterwards this message will pop up letting them know upgrade is in progress.


What to consider when supporting plugin and using the media creation tool to create the ISO:
https://www.microsoft.com/en-us/softwar ... windows10/

64-bit or 32-bit processor (CPU). You’ll create either a 64-bit or 32-bit version of Windows 10. To check this on your PC, go to PC info in PC settings or System in Control Panel, and look for System type.

System requirements. Make sure the PC meets the system requirements for Windows 10. We also recommend going to the PC manufacturer's website for additional info about updated drivers and hardware compatibility.

Language in Windows. You'll need to choose the same language when you install Windows 10. To see what language you're currently using, go to Time and language in PC settings or Region in Control Panel.

Edition of Windows. You should also choose the same edition of Windows. To check what edition you're currently running, go to PC info in PC settings or System in Control Panel, and look for Windows edition. Windows 10 Enterprise isn’t available in the media creation tool. :? For more info, go to the Volume Licensing Service Center.

User avatar
Cubert
Posts: 2457
Joined: Tue Dec 29, 2015 7:57 pm
8
Contact:

Re: Patch Remedy Version 4 Beta

Post by Cubert »

To successfully complete Windows 10 Version upgrades there is a few prereq’s needed. If any prereq is not met, then that information will show up in the install logs of any agent that has attempted an upgrade. Use log view to reset an agent.

#1 Visit https://www.microsoft.com/en-us/softwar ... windows10/ to see how to create a Windows10 ISO for Windows 10

#2 Name the new ISO file created

#3 Place the new ISO on the Automate Server in the \\LTShare\Transfers\Software\Windows10\Windows10.iso if the Windows 10 agents are able to access this share from the agent.

#4 Select the GEAR on the Defer tab to edit the file name and locations of ISO so agents can find the files you are committing.

#5 The Patch Remedy Maintenance script will cache the 4+ GB ISO file to the locations share drive. You must have each Location’s “Drive” populated with a share capable of saving the 4+ GB ISO file. Once the first agent downloads the ISO it will be placed here, all other agents will look here for ISO first. If ISO is missing they will attempt to download it and place it here. This will prevent large groups of downloads from attempting to download ISO and drowning out the bandwidth connection.

The ”Location Drive” is located here:
LocationDrive.png
LocationDrive.png (52.19 KiB) Viewed 19174 times

You can use the menu in the Defer Windows 10 View to view install logs and to reset an agent if a install failed at any step.
deferrWin10View.png
deferrWin10View.png (23.92 KiB) Viewed 19174 times

User avatar
Cubert
Posts: 2457
Joined: Tue Dec 29, 2015 7:57 pm
8
Contact:

Re: Patch Remedy Version 4 Beta

Post by Cubert »

If your patch remedy fails to open or opens like so, you maybe missing some of the DevExpress Libs. We have pulled the libs from our LT Control Center which includes chart libs. If your missing one or more of the following files then the zip file here has the libs you need. Just copy them to the LTclient install directory.

image001.jpg
image001.jpg (32.54 KiB) Viewed 19162 times

Files that should be there but may not be.
Capture21.PNG
Capture21.PNG (87.44 KiB) Viewed 19162 times
The Libs you need are here -> https://lp.plugins4labtech.com/files/De ... s_LIBS.zip

ben_
Posts: 17
Joined: Wed Dec 28, 2016 2:22 pm
7

Re: Patch Remedy Version 4 Beta

Post by ben_ »

Cubert,

First, thanks for this, this has been a thorn in my side for some time now that Microsoft is giving my clients prompts when they come in to work in the morning saying that the update is NEEDED and their OS wont be SUPPORTED anymore, as you can imagine they get anxious! I can finally see all of them in one place and handle this in a more AUTOMATEd way ;)
Image


I have installed and followed your pre-reqs. Here are some notes/questions.

- When downloaded Win10 via the Microsoft Media Creator Tool, It only has the option for 'Windows 10 x64, and nothing else. Am I missing something here? I created the said ISO with just the 'Windows 10 x64' and proceeded anyway to try and test.

Image

- I enabled the auto upgrade on one of my client's computers, and noticed that the maintenance script immediately made a registry change but I was wondering how can I force this upgrade to go now? Forcing an 'Attempt Repair' on the Hotfix Issues tab does not kick of this upgrade. Your documentation states ' the next cycle '. I am not sure what that is. I want to force some tests before I deploy to multiple clients.

User avatar
Cubert
Posts: 2457
Joined: Tue Dec 29, 2015 7:57 pm
8
Contact:

Re: Patch Remedy Version 4 Beta

Post by Cubert »

We are adding a "Upgrade Now" menu item today. So watch the forum for an update.

ben_
Posts: 17
Joined: Wed Dec 28, 2016 2:22 pm
7

Re: Patch Remedy Version 4 Beta

Post by ben_ »

Cubert wrote: Thu Mar 22, 2018 1:46 pm We are adding a "Upgrade Now" menu item today. So watch the forum for an update.
Thanks for this. I cant make heads or tails of why the upgrade did not go off last night automagically on my test laptop that is running version 14393.

Here is the Patch Remedy Maintenance Script Log. It shows successful, but there is no ISO on the share location that I set or attempt on the node to do any installs.

Code: Select all

The Script(6110) was successful in the Then section.

Script: S6110 - Starting at Server Time: Thursday, March 22, 2018 9:04:09 AM
IF F5 ValueOne (P1): MYCMD   Comparer (P2): 8   ValueTwo (P3): SCANWUA T: 0.6049994
L2 F235  T: 0.6109986
L3 F21 Seconds (P1): 3 T: 9.2069988
L4 F235  T: 12.2119989
L5 F21 Seconds (P1): 3 T: 19.2409983
L6 F235  T: 22.2459995
L7 F70 Value (P1): WUA   Comparer (P2): 4   To (P3): 10.0.14393.0
    Jump (P4): 1 T: 25.2609992
L8 F70 Value (P1): WUA   Comparer (P2): 7   To (P3): 10.0.14393.0
    Jump (P4): 1 T: 25.2619989
L10 F20 SetType(P1):1   Parameter(P2):Microsoft Windows 10 Pro x64   VariableName(P3):OSTYPE T: 25.2619989
L12 F20 SetType(P1):0   Parameter(P2):'HKEY_LOCAL_MACHINE\SOFTWARE\Mi...'   VariableName(P3):OPTMICRO T: 25.2629988
L13 F70 Value (P1): OPTMICRO   Comparer (P2): 0   To (P3):    Jump (P4): :EXISTS T: 39.8870004
L16 F139 Note (P1): :EXISTS T: 39.8969992
L17 F20 SetType(P1):1   Parameter(P2):1   VariableName(P3):OPTMICRO T: 39.8969992
L18 F70 Value (P1): WUA   Comparer (P2): 1   To (P3):    Jump (P4):  T: 39.8969992
L19 F70 Value (P1): OSTYPE   Comparer (P2): 1   To (P3):    Jump (P4):  T: 39.8979989
L20 F70 Value (P1): WUA   Comparer (P2): 2   To (P3): OK   Jump (P4):  T: 39.8979989
L21 F70 Value (P1): OSTYPE   Comparer (P2): 2   To (P3): OK   Jump (P4):  T: 39.8979989
L22 F70 Value (P1): OSTYPE   Comparer (P2): 8   To (P3): script failed   Jump (P4):  T: 39.8989987
L23 F70 Value (P1): WUA   Comparer (P2): 2   To (P3):    Jump (P4):  T: 39.8989987
L24 F70 Value (P1): WUA   Comparer (P2): 8   To (P3): script failed   Jump (P4):  T: 39.8989987
L25 F70 Value (P1): OSTYPE   Comparer (P2): 8   To (P3): error   Jump (P4):  T: 39.8989987
L26 F70 Value (P1): OSTYPE   Comparer (P2): 2   To (P3):    Jump (P4):  T: 39.9019984
L27 F70 Value (P1): VERSIONNUMBER   Comparer (P2): 8   To (P3): Get-Item   Jump (P4): 2 T: 39.9019984
L28 F70 Value (P1): VERSIONNUMBER   Comparer (P2): 8   To (P3): error   Jump (P4): 1 T: 39.9029984
L29 F20 SetType(P1):1   Parameter(P2):'Microsoft Windows 10 Pro x64 1...'   VariableName(P3):OSTYPE T: 39.9029984
L30 F139 Note (P1): :RUNSQL T: 39.9029984
L32 F20 SetType(P1):1   Parameter(P2):'INSERT INTO plugin_sw_patch_re...'   VariableName(P3):SQLCMD T: 39.9029984
L33 F29 Message (P1): 'INSERT INTO plugin_sw_patch_remedy_wua (ComputerID,ClientID,WUAVersion,OS,MicrosoftUpdates...' T: 39.9029984
L34 F67 Sql (P1): 'INSERT INTO plugin_sw_patch_remedy_wua (ComputerID,ClientID,WUAVersion,OS,MicrosoftUpdates...' T: 39.9049997
L35 F21 Seconds (P1): 5 T: 39.9079993
L36 F67 Sql (P1): 'UPDATE  plugin_sw_patch_remedy_wua SET WUAVersion = REPLACE(WUAVersion, '\n', ''),OS = REP...' T: 44.918999
L37 F172 SqlStatement (P1): 'SELECT count(*) from  properties where `Name` = 'PatchRemedyFix80240025Error' and `Value` ...' T: 44.9389992
L38 F70 Value (P1): sqlresult   Comparer (P2): 2   To (P3): 0   Jump (P4): 4 T: 44.9389992
L43 F20 SetType(P1):0   Parameter(P2):'HKEY_LOCAL_MACHINE\SOFTWARE\Mi...'   VariableName(P3):MyKeyValue T: 44.9389992
L44 F70 Value (P1): MyKeyValue   Comparer (P2): 2   To (P3): 1   Jump (P4): :UPDATEDEFERRED T: 49.0169981
L45 F139 Note (P1): :RUNUPDATEDEFERREDSQL T: 49.0229979
L46 F67 Sql (P1): 'REPLACE INTO `plugin_sw_patch_remedy_win10deferred` (ComputerID,ComputerName,ClientID,Clie...' T: 49.0239979
L47 F129 Jump (P1):  T: 49.0259981

User avatar
Cubert
Posts: 2457
Joined: Tue Dec 29, 2015 7:57 pm
8
Contact:

Re: Patch Remedy Version 4 Beta

Post by Cubert »

We posted 1.0.4.5 this morning,

We forgot to disable the plugin updater so it keeps reverting back to the production version of Patch remedy (1.0.3.94). We have disabled that in the beta now until it moves to production.

We also added new feature to windows 10 menu, Attempt Upgrade OS Now will start the upgrade process on a agent now. You monitor the script logs or occasionally open the log viewer to see progress.

ben_
Posts: 17
Joined: Wed Dec 28, 2016 2:22 pm
7

Re: Patch Remedy Version 4 Beta

Post by ben_ »

Thanks! Gonna try it out now.

ben_
Posts: 17
Joined: Wed Dec 28, 2016 2:22 pm
7

Re: Patch Remedy Version 4 Beta

Post by ben_ »

It might be worth noting in the documentation that to be able to create the directory in the 'drive', the folder that you've entered needs to have NTFS Security Permissions (Full). Just having share permissions/network access is not enough.

Update: How can I edit the script to allow it to also skip the popup message if the console is LOCKED and not just LOGGED OUT? Alot of my userbase just locks their computers at night and I notice the script fails if there is no response because it does a logged in check.

User avatar
Cubert
Posts: 2457
Joined: Tue Dec 29, 2015 7:57 pm
8
Contact:

Re: Patch Remedy Version 4 Beta

Post by Cubert »

ben_ wrote: Thu Mar 22, 2018 3:55 pm It might be worth noting in the documentation that to be able to create the directory in the 'drive', the folder that you've entered needs to have NTFS Security Permissions (Full). Just having share permissions/network access is not enough.

Update: How can I edit the script to allow it to also skip the popup message if the console is LOCKED and not just LOGGED OUT? Alot of my userbase just locks their computers at night and I notice the script fails if there is no response because it does a logged in check.
That's a great observation! The local share will work if the share is on workgroups computers or drive permissions are set to allow everyone full control.

Post Reply

Return to “Patch Remedy for LabTech (Patch Remedy 4) Retired”