Purpose
The purpose of this document is to go over an issue with deployments in an offline environment that stay stuck at scheduled following an upgrade of the console from Shavlik Protect 9.2 to Ivanti Patch for Windows Servers 9.3.
Symptoms
- Deployment stays stuck in scheduled.
- The staged folder for the deployment stays in the Staged directory instead of moving to the Installation folder.
- The STDeploy.log inside of the staged deployment folder shows a similar error to the below:
STDeploy.cpp:154 Entering wmain.
STDeploy.cpp:159 'C:\Windows\ProPatches\Staged\2018-06-19-T-19-19-33\stdeploy.exe' is starting, version 9.2.2535.0.
DeployContext.cpp.102 User supplied file path 'package=C:\WINDOWS\ProPatches\Staged\2018-06-19-T-19-19-33\deployPackage-5070.zip' does not exist.
STDeploy.cpp:154 Leaving wmain
Cause
The offline console's data files have not been updated from version 9.2 data files to the new version 9.3 data files. When data files are not updated after upgrading, the deployment package is built using 9.2 files and can not be read by the 9.3 STDeploy.exe deployment engine. This causes the deployment engine to fail to read the deployment package and then start the deployment as expected.
Resolution
1. Download the new data files for version 9.3 by either copying the data from C:\Programdata\Landesk\Shavlik Protect\Console\DataFiles an online 9.3 console OR download the files using our Disconnected Data Download Powershell script found in this document: How To: Download Content Data Files and Patches using the Download PowerShell Script
2. Once new data is downloaded and/or copied to the offline console, go to Help > Refresh Files to ensure the console sees the updated data files.
3. Run the deployment again to confirm the issue is resolved.
Affected Product
Ivanti Patch for Windows Servers 9.3