Patch Deployment Overview

Shavlik Protect allows local and remote patch deployment via a few simple mouse clicks.  From one management console you can deploy missing patches and service packs to a single machine or to many machines.

Note:  Service packs should be applied before all patches. For this reason Shavlik Protect will not allow you to deploy service packs and patches in the same deployment.

Patch Deployments Are Performed As Background Tasks

All patch deployments are performed as background tasks, regardless of how they are initiated. In other words, the deployment is launched as its own separate Windows task. This means you can initiate a patch deployment and then move on to other concurrent work within Shavlik Protect without having to wait for the deployment to complete. This also means you can have multiple patch deployments active at the same time.

Deployment Considerations

Yes. It is dependent on the CPU and memory size of the console machine. It is also dependent on the number of other tasks currently active (for example, other patch downloads, patch deployments, etc.). While there is no exact answer, you'll know you've reached a practical limit if Shavlik Protect starts responding slowly.

You should avoid concurrent deployments to the same machine. Exactly what will happen is dependent on a number of issues. The second deployment may overwrite the patch files already deployed, it may fail if the files are currently in use by the first deployment, or it may fail if the first deployment reboots the machine while the second deployment is still in progress.

The Operations Monitor will display the status of the patch deployment. From the Shavlik Protect console's perspective, the deployment is complete when all necessary files have been copied to the target machine and the deployment is scheduled.