One of the hurdles most MSPs have is identifying and updating Windows 7 and Server 2008 R2 systems and Patch Remedy helps to fill that void. Patch Remedy is now taking it one step further with the release of build 184.108.40.206. Windows 7 SP1 is not by any means a new patch but is often overlooked when MSPs are trying to get their patch score above 50%. In 2017 you would think by now all Windows 7 systems would be on SP1. That's just not so. Many MSPs have agents that are pre WUA version 7.6.7601.17514 which means you are not yet on SP1.
Windows 7 SP1 Gets Applied First
If Windows 7 was post SP1, then, Patch Remedy would elevate the system to the latest WUA updates through a progression of updates applied through automation. This process worked very well but had little effect on agents reporting pre Windows 7 SP1 agents. This changes with Patch Remedy's build 220.127.116.11
When Patch Remedy comes across a Pre Windows 7 SP1 it will first apply the Service Pack 1.
This is a multiple reboot update that will not require any direct user intervention. The user will activate the console and will be halted from logging in until the update completes. The first step in the update is done with a /NoRestart flag set so you can safely apply the service pack across clients without fear of mass reboots. When the reboot does finally happen, users will see the image above until completed and the Windows system will reboot itself during this second stage.
Service Pack Has Been Applied
After the Service Pack is applied and has completed install the user will be presented with this dialog box confirming the updates.
Onward and Upward
Once Patch Remedy has updated the Windows 7 agent to Service Pack 1 it will continue to apply updates, as needed, and bring the agent up to current within a short period. Each update(4), gets applied separately until the Windows 7 agent is fully patched with the latest WUA versions.