Patch Remedy caused slow internet at client.

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: 2432
Joined: Tue Dec 29, 2015 7:57 pm
8
Contact:

Patch Remedy caused slow internet at client.

Post by Cubert »

You maybe overloading the network during business hours.


Patch Remedy has 3 switches at the top of the plugin. If you turn off “Auto Update” then Patch Remedy will only scan agents for WUA versions and will not attempt to update systems (which sounds like your issue) Setting the scan interval to 24 will also prevent scans or updates during normal business hours but will also tend to miss agents that are otherwise offline. So we suggest at least setting intervals to 12 so Patch Remedy gets 2 attempts to get data needed from all agents enabled.

That is how you control update pushes and scans ( although scans are only 2 lines of script code and will have zero impact on an agent when run, it’s the updates that will sink a network.)

Now that your under control, have a look at the 2nd tab, WUA updates and see how many agents are reporting out of date. If this number is really high then if you turn on updating you may load up client networks. We suggest a controlled approach to first updates so if you have really lacking clients you do not over load networks with patch downloads all at once.

Our process is:

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 if you only show a few issue per client. If you see whole clients in your update list then use the manual push on a few agents at a time and reboot them before going on to the next set. Clear out the bulk over a couple of days if needed before turning on auto updates. Auto Update will now maintain the agents for you without overloads.

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”