Try me first! I might solve your issues here.

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.
Post Reply
User avatar
Cubert
Posts: 2430
Joined: Tue Dec 29, 2015 7:57 pm
8
Contact:

Try me first! I might solve your issues here.

Post by Cubert »

Here is a quick post on how to recover or replace a Patch Remedy install that your unsure is working or setup correctly.

Patch Remedy is a very easy to replace plugin. There is no data or settings that can not be quickly reproduced after a clean install.

So first question is do you see more than one Patch Remedy listed in the tools menus? If so you have a duplicates issue , here is why and here is how to look for and fix that issue.
viewtopic.php?f=55&t=5521


Next,
You should go into SQL is able and remove all Patch Remedy tables from SQL using SQLYog. Look for tables in SQL starting with “plugin_sw_patchremedy_xxx”. There should be 5 or 6 tables there. Just drop them so we get a nice clean install. Follow that by searching your scripts folder for Patch Remedy Maintenance script and remove that.

Next,
Remove the old plugin from the plugin manager, Disable it, then delete it. Restart the DBagent and log out and back into LT console.

Next,
Download the latest Patch Remedy at https://delivery.shopifyapps.com/-/924f ... 58508aad63 and unzip it. Using plugin manager install plugin as new and restart the dbagent again. Log out and back into LT console.

Next,
Launch the Patch Remedy plugin, Set the scan interval on settings tab to 8 or 12, enable your clients then turn on the master switch at top. This will allow Patch remedy to scan the agents in enabled clients 2 to 3 times a day or every 8 to 12 hours as scan interval is set.

Wait 24 hours for data. (2 to 3 scan cycles to make sure we got all agents reporting back)

Review data and see what you actually have. Turn on the Auto update switch to start pushing updates to out of date agents.

Below are links to our 3 most used forum posts. These help explain how Patch Remedy works and what the MSP needs to pay attention to, to get things functional in their environments.

Want to upgrade Windows 10 agents from 1709 to 1803 or 1809 through automation?
viewtopic.php?f=7&t=5462

Patch Remedy documentation project
viewtopic.php?f=7&t=5434

Patch Remedy WUA updates Explained.
viewtopic.php?f=7&t=5302


As for WUA updates, the big take away you should get is (Reboot, Reboot, Reboot). Having a really good “Search + Group + Script” setup for reboots will take you a long way in making the most from Patch Remedy. So after all the setup and data collections get don and you ready to start updating agents make sure to craft a search that looks for agents with the pending reboot flag set. When the search finds them have them join a reboot group that reboots agents nightly after hours or when maintenance cycles are available. What will happen is that the agents as they need reboots will join group , get rebooted, no long qualify for group and leaves group until next time when reboot flag is again set.

This will allow you to automate reboots as needed keeping agents fully up to date and stable in the environments.

Post Reply

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