How to Increase the Deployment Timeout for Offline Hosted Virtual Machines

Version 6

    Purpose

     

    This document includes instructions on how to increase the deployment timeout for offline hosted virtual machines.  Performing the steps in this document will be required when a deployment to an offline hosted virtual machine requires more than 120 minutes to complete.  The typical cause would include a deployment of a large number of patches to a single machine.

    Symptoms

     

    You will see the following error message in the Deployment Tracker approximately 2 hours into the deployment process.

    A subsequent scan of the target offline hosted virtual machine will show fewer patches missing indicating some of the patches installed within that 120 time-frame.

     

    Resolution

     

    Manually increase the deployment timeout by editing the STEnvironment.config.

     

    1.  Close Protect or Patch for Windows Server (PWS).

    2.  Stop the Shavlik or Ivanti Console Service.

    3.  Navigate to the installation folder. (C:\Program Files\LANDesk\Shavlik Protect by default)

    4.  Make a backup STEnvironment.config.

    5.  Edit the STEnvironment.config.

    This value is in days, so setting the value to 1 is a timeout of 1 day.

    6. Locate tempReportsDirectory="C:\ProgramData\LANDESK\Shavlik Protect\Console\TempReports\"

    7. Add the following on the line below it:

    virtualDeploymentTimeout="1"

     

    This is what it will look like after your change:

    tempReportsDirectory="C:\ProgramData\LANDESK\Shavlik Protect\Console\TempReports\"

    virtualDeploymentTimeout="1">

    8. Close and save the STEnvironment.config file.

    9. Start the Shavlik or Ivanti Console Service.

    10. Launch the console and test.

    Affected Products

     

    Shavlik Protect 9.2.x

    Ivanti Patch for Windows Servers 9.3.x