How To Manually Execute A Deployment

Version 6



    This document will outline how to manually execute a deployment.


    The reason you may want or need to do this is if you do not schedule deployments. The resolution outlined in this document is typically only applicable if you set the deployment to, "Copy files to selected machine(s) but do not install" in the Deployment Configuration:

    Copy Files.PNG





    The way deployments work in Shavlik Protect 9.2 and Ivanti Patch for Windows Server 9.3.x has changed since Protect 9.1/9.0. In order to manually execute a deployment, you will need to do the following:

    1. Browse to C:\Windows\ProPatches on the target machine.
    2. When deployment files are copied to the target machine, they are placed in the C:\Windows\ProPatches\Staged folder.
    3. All deployment files will stay in the Staged folder until they are deployed. If you have not scheduled a deployment and have only copied the files over, all the necessary files will be in Staged.
    4. Within the Staged folder, each deployment will have it's own folder. It will be based on the date of the deployment. It typically is named YY-MM-DD-T-HH-MM-SS.
    5. Within the deployment folder you will see a Windows Batch File named, "InstallPatches-###" and this is the file you will want to right click and Run as administrator.
    6. A Command prompt will open and then close but the deployment will begin and the deployment files in the Staged folder will now move to the C:\Windows\ProPatches\Installation folder.
    7. Once the deployment begins, you will be able to track it in the Deployment Tracker on the Shavlik console if you have the option checked in the Deployment Template.

    Affected Product(s)


    Shavlik Protect 9.2

    Ivanti Patch for Windows Server 9.3.x