Overview of the Custom Patch XML Process

Show Me!   

To view a video tutorial on this topic, click the video icon on the left.

CAUTION! Creating and using custom patch XML files should only be attempted by experienced administrators. Creating and deploying inaccurate custom patches may have seriously adverse affects on the performance of the programs in use at your organization.

Shavlik Protect provides the ability to scan for and deploy patches not supported in the primary XML patch data file (hf7b.xml). It does this by allowing you to create your own custom patch XML files that contain the information about the additional patches and products you want to support. Shavlik Protect will then combine your custom XML files with the primary XML patch data file and use that modified file when performing scans and deployments.

Within each custom XML file you can define multiple custom products, bulletins, and patches.

One major difference between a regular patch and a custom patch is that you cannot download a custom patch to the patch download directory in advance of a deployment. Rather, you must make the patch available by manually copying the patch to all expected locations (typically to the console as well as any distribution servers).

If you are using agents to deploy custom patches, be certain you enable the Use Server by IP Range check box on the deployment template used by the agents. Custom patches cannot be downloaded from a vendor and the agents must therefore be able to download the custom patches from one or more distribution servers. See Deployment Template: Distribution Servers Tab for more information.