Purpose

This document provides links to other documents addressing custom action, custom patch, and ITScript information and troubleshooting.

Overview

Custom Action

Prerequisites and Process

How To: Perform a Custom Action Complete Tutorial with Custom Actions

Can You Use Custom Actions With Agents?

Custom Action - Using The Null Patch

How to: Scan for the Null Patch using the Custom Actions scan filter

Custom Action - Things to know and watch for

Run a batch file

Custom Action - How to Work with Batch Files

Install programs

Work with custom patches

How To: Run An Executable or MSI With A Custom Action

Using Custom Actions To Deploy MSU/MSI Files

Uninstall programs or remove files

Custom Action - Remove the Remote Scheduler for Protect Version 9

How To Uninstall A Program Using Custom Actions

How To Remove The Propatches Folder Using Custom Actions in Protect 9.1

How To: Uninstall Java using a Custom Actions

Reboot a machine

How To: Reboot Target Machines with Using the Custom Actions Patch Type in a Custom Scan Template

Work with custom patches

Custom Action vs. Custom XML

Custom Patch: Custom .exe File Distribution With Custom Action

Custom Patch

Considerations For Custom Patches And Products

How To: Create a Custom Patch

Custom Patch Deployment .bat File Never Completes.

ITScript

ITScript - Errors Importing Custom ITScripts

ITScripts - Enabled Scripts Not Showing in Run Console ITScripts

Temp Folder Fills Up With Small Files Troubleshooting

Purging Downloaded Patch Install Files From The Protect Console

You Receive "Error: A Command That Prompts the User Failed because the Host Program or the Command Type Does Not Support…

Affected Product(s)

Shavlik Protect 9.x

With the now never-ending required OS changes from Microsoft and the constant re imaging and renaming machines, I am wondering if anyone has developed a workable solution to the 45 day expiration requirement of an Ivanti license seat. While Ivanti has been helpful and provided me with some temporary seats, I can see where future upgrades and replacements of machines will become an issue.

We want to patch a machine as soon as it is on the network, this of course requires it be given a name that hopefully it will keep for some duration, but often is not.  When systems are swapped out, say a workstation for a tablet to the same user, the name changes to reflex the machine type, and using another license.

I am looking for methods to better control this, even if it means retraining techs and changing procedures, but wondered if anyone has had success with a specific process for such a moving target.

Guys,

Is it only me not seeing all fixes regarding Exchange patching mess up mentioned here:

Issue with July Updates for Windows on an Exchange Server – You Had Me At EHLO…

For example I am missing KB 4338816 for Window 2012 (not R2) but can see KB 4345425 listed in Patches View.

Any advise before I start rolling up them to my Exchange boxes?

hi,

the status column in the patch deployment shows scheduled instead of finished, even though the patches were successfully applied and the server rebooted.

Purpose

When updating VMware Tools with, Protect and Patch for Windows Servers, there may be a couple quirks you will come across. Below is a FAQ list to help address questions you may have.

Description

Frequently Asked Questions

Q: Does the version of VMware Tools need to match a specific version of ESXi or vCenter host?

A: No. The VMware Tools versions should be backward compatible with all product supported versions. VMware has to make it backward compatible since there may be mixed hypervisor versions on the same vCenter and DRS can move VMs from one host to another. See the excerpt below from the VMware 5.0 upgrade guide: http://www.vmware.com/files/pdf/techpaper/vSphere-5-Upgrade-Best-Practices-Guide.pdf

"The first step in upgrading virtual machines is to upgrade VMware Tools. vSphere 5.0 supports virtual machines running both VMware Tools version 4.x and 5.0. Running virtual machines with VMware Tools version 5.0 on older ESX/ESXi 4.x hosts is also supported. Therefore, virtual machines running VMware Tools 4.x or higher do not require upgrading following the ESXi host upgrade. However, only the upgraded virtual machines will benefit from the new features and latest performance benefits associated with the most recent version of VMware Tools."

Q: Why does my VMware host show VMware Tools version out of date or missing when Protect shows it is now up-to-date, or Why does Protect show VMware Tools missing when the VMware host shows the version is already up-to-date?

A: VMware Tools assessment in vSphere is comparing against the local version on the hypervisor the VM resides on. The ESXi host or vCenter may need to be updated. Often, it will help if you perform a Hypervisor bulletin scan and deployment to correct these inconsistencies. As long as your patch definitions in Shavlik Protect are up to date the scan information from Protect should be correct in this regard.

More information on how to scan and deploy to ESXi hosts can be found in the following Help articles:

Scanning VMware hosts for bulletins:

http://www.shavlik.com/onlinehelp/Protect90HTMLHelp/How_to_Initiate_a_Scan_of_an_ESXi_Hypervisor.htm

Deploying bulletins to VMware hosts:

http://www.shavlik.com/onlinehelp/Protect90HTMLHelp/Initiating_a_Bulletin_Deployment_to_an_ESXi_Hypervisor.htm

Q: After updating Vmware Tools with Protect I no longer have access to the VMware Tools UI and Settings within a patched VM. Why is this happening?

A: This is a change put into place by VMware. The behavior is intentional. Additional information on this is provided by VMware in a KB article, here:

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2046615

Q: Originally VMware Tools support was added to Protect as a Non-Security Patch. Why was this changed to a Security Patch type?

A: More than anything the decision to change VMware Tools to a 'Security Patch' in Protect's scans is based on the fact that it is a requirement to have the latest version of VMware Tools installed on guest operating systems to be able to use the full functionality of patching hosted VM's using Protect, especially offline VMs or templates. Since this is a requirement for Protect's features to work - we consider these updates important enough to be included in Security patches.

If you do not wish for this to be scanned along with other security patches you can create a custom scan template, and set the Product Filter to 'Skip Selected' for VMware, or you can use other filtering options to exclude VMware Tools updates from the scan.

Q: How can I make a request for a change or addition to any features around patching VMware Tools?

A: Please feel free to submit any feature or change requests at our Shavlik Feature Requests site.

Q: If patching VMware Tools how is it determined that the update is needed?

A: A virtual machine that has a previous version of VMware Tools installed that is in the affected products section of the particular patch being deployed would show the patch as needed. Physical machines will not get the patch as the vendors installer will not install on a physical machine.

Affected Products

Ivanti Patch for Windows Servers 9.x

Shavlik Protect 9.x

I'm using Patch for Windows 9.3.  I created a custom patch to install R Studio on multiple computers rather than installing it individually on them all.  It successfully scans and sees it's not installed, but when it tries to run the installation it fails with a status "Patch is not available for the language selected".  When I've looked up this error everything I find is related to virus scan software.  I don't have any issues installing patches on a regular basis, just installing this software.  Has anyone run into this error not related to virus scan software?

Hi

Created a standard image Win 2016 and scan server all good.

Then added IIS and now it finds the server ( eventually ) and then takes so long to scan that it times out.

After removing IIS all is fine again.

Any thoughts.

Port issue perhaps

Thanks

Steve

Symptoms

• Patch for Windows reports database timeout errors.
• In the ST.Protect.managed.log file, you see may see an error such as the following:

System.Transactions.TransactionAbortedException: The transaction has aborted. ---> System.TimeoutException: Transaction Timeout

     OR

2012-07-17T21:10:46.8328850Z 0001 W ScanSummaryPresenter.IsRecoverable|A SQL Server query operation timed out. Consider increasing the command timeout in the configuration file

Purpose

This article provides steps to increase the database timeout value in Patch for Windows.

Resolution

To increase the database timeout period:

Note: Close the Patch for Windows application before proceeding.

1.Navigate to C:\Program Files\LANDesk\Shavlik Protect.

2.Locate the ST.Data.Config file and open it using a text editor.

3.Change this entry:
st.data commandTimeout="30"
To:
st.data commandTimeout="3600"

This increases the timeout period allotted for transactions with the database. This number is in seconds and you can set the number to a higher value as required. 3600+ is the recommendation value for most timeout issues.

4. Save the changes for the ST.Data.Config file.

5.Re-open your Patch for Windows console, and test to see if the issue is resolved.

Affected Products

Ivanti Patch for Windows

Shavlik Protect 9.x

Hi, I'm after some help please. We have just built some server 2016 templates in vmware and have added them into ivanti.

When I run an OD scan and choose to package and deploy patches afterwards I get an error stating:

I've tried using local admin credentials, no .\ just administrator and known password

Have tried domain admin creds that we use for all vms

Any suggestions please ?

Hi all, I'm after some help please.
Ran a deployment to our SQL servers on Friday the 20th, all of them ran fine but one of them decided to install patches and vmware tools at 15:00 instead of 03:00, which as you can imagine didn't go down too well.

Contend of CSTDeploy.log file on the day shown below:

2018-07-20T02:11:19.7811574Z 4910 S STDeploy.cpp:257 Entering wmain.
2018-07-20T02:11:19.7811574Z 4910 I STDeploy.cpp:262 'C:\Windows\ProPatches\Staged\2018-07-20-T-02-11-13\stdeploy.exe' is starting, version: 9.3.2708.0.
2018-07-20T02:11:19.7811574Z 4910 V DeployContext.cpp:259 STDeploy.exe command line args: 'package="C:\Windows\ProPatches\Staged\2018-07-20-T-02-11-13\deployPackage-70992.zip" "baseDir=C:\Windows\ProPatches" "removeStaging=yes"'
2018-07-20T02:11:19.7811574Z 4910 S DeployExeStates.cpp:344 Entering STDeploy::CExtendedCmdLineHandlingPackageDeploy::ProcessExtendedCmdLineArguments.
2018-07-20T02:11:19.7811574Z 4910 S DeployExeStates.cpp:344 Leaving STDeploy::CExtendedCmdLineHandlingPackageDeploy::ProcessExtendedCmdLineArguments.
2018-07-20T02:11:19.7967837Z 4910 S DeployExeStates.cpp:401 Entering STDeploy::CInitialExecutionPackageDeploy::ServiceDeploymentSandboxes.
2018-07-20T02:11:19.7967837Z 4910 I DeployExeStates.cpp:41 Sandbox service: removing old directory 'C:\Windows\ProPatches\Installation\InstallationSandbox#2018-07-13-T-02-14-18', age '6.997937' days
2018-07-20T02:11:19.8124045Z 4910 V DeployExeStates.cpp:60 Created new deployment sandbox at 'C:\Windows\ProPatches\Installation\InstallationSandbox#2018-07-20-T-02-11-19'
2018-07-20T02:11:19.8124045Z 4910 S DeployExeStates.cpp:401 Leaving STDeploy::CInitialExecutionPackageDeploy::ServiceDeploymentSandboxes.
2018-07-20T02:11:19.8124045Z 4910 V STDeploy.cpp:135 initialLogFilePath='C:\Windows\ProPatches\Staged\2018-07-20-T-02-11-13\STDeploy.log' permanentLogFilePath='C:\Windows\ProPatches\Logs\STDeploy.log' sandboxLogFilePath='C:\Windows\ProPatches\Installation\InstallationSandbox#2018-07-20-T-02-11-19\STDeploy.log'
2018-07-20T02:11:19.8124045Z 4910 I STDeploy.cpp:143 Preparing to Move initial trace logs to the permanent logfile at 'C:\Windows\ProPatches\Logs\STDeploy.log'.
2018-07-20T02:11:19.8280363Z 4910 I STDeploy.cpp:167 Trace logging transferred from 'C:\Windows\ProPatches\Staged\2018-07-20-T-02-11-13\STDeploy.log'.
2018-07-20T02:11:19.8280363Z 4910 V STDeploy.cpp:171 Moved initial trace logs to the logfile at 'C:\Windows\ProPatches\Logs\STDeploy.log'.
2018-07-20T02:11:19.8592866Z 4910 I STDeploy.cpp:331 Relaunching STDeploy.exe to run out of a sandbox at 'C:\Windows\ProPatches\Installation\InstallationSandbox#2018-07-20-T-02-11-19'.
2018-07-20T02:11:20.1256513Z 1b78 S STDeploy.cpp:257 Entering wmain.
2018-07-20T02:11:20.1256513Z 1b78 I STDeploy.cpp:262 'C:\Windows\ProPatches\Installation\InstallationSandbox#2018-07-20-T-02-11-19\stdeploy.exe' is starting, version: 9.3.2708.0.
2018-07-20T02:11:20.1256513Z 1b78 V DeployContext.cpp:259 STDeploy.exe command line args: 'package="C:\Windows\ProPatches\Staged\2018-07-20-T-02-11-13\deployPackage-70992.zip" "baseDir=C:\Windows\ProPatches" "removeStaging=yes"'
2018-07-20T02:11:20.1256513Z 1b78 S DeployExeStates.cpp:344 Entering STDeploy::CExtendedCmdLineHandlingPackageDeploy::ProcessExtendedCmdLineArguments.
2018-07-20T02:11:20.1256513Z 1b78 S DeployExeStates.cpp:344 Leaving STDeploy::CExtendedCmdLineHandlingPackageDeploy::ProcessExtendedCmdLineArguments.
2018-07-20T02:11:20.1415226Z 1b78 I STDeploy.cpp:358 C:\Windows\ProPatches\Installation\InstallationSandbox#2018-07-20-T-02-11-19\stdeploy.exe is now executing out of a sandbox: 'C:\Windows\ProPatches\Installation\InstallationSandbox#2018-07-20-T-02-11-19'.
2018-07-20T02:11:20.1415226Z 1b78 S DeployExeStates.cpp:409 Entering STDeploy::CInitialExecutionPackageDeploy::DoStatefulRemediateActions.
2018-07-20T02:11:20.1415226Z 1b78 V DeployExeStates.cpp:84 Invoking remediation manager processing: userSuppliedFileName='deployPackage-70992.zip', userSuppliedPath='C:\Windows\ProPatches\Staged\2018-07-20-T-02-11-13', patchStorePath='C:\Windows\ProPatches\Patches', deployerCoreLogFilePath='C:\Windows\ProPatches\Logs\STDeployerCore.log', LaunchCount='0', LaunchReason='0', currentDirectory='C:\Windows\ProPatches\Installation\InstallationSandbox#2018-07-20-T-02-11-19', sandboxDirectory='C:\Windows\ProPatches\Installation\InstallationSandbox#2018-07-20-T-02-11-19'
2018-07-20T02:11:20.1415226Z 1b78 I STPackageDeployer.cpp:1589 Moving files from stagingDirectory 'C:\Windows\ProPatches\Staged\2018-07-20-T-02-11-13' to sandbox directory 'C:\Windows\ProPatches\Installation\InstallationSandbox#2018-07-20-T-02-11-19'
2018-07-20T02:11:20.1415226Z 1b78 I DeploymentFileSetBuilder.cpp:107 Moving 'C:\Windows\ProPatches\Staged\2018-07-20-T-02-11-13\3c197e11-9480-484e-815a-1432a898bbe2.tracker' to 'C:\Windows\ProPatches\Installation\InstallationSandbox#2018-07-20-T-02-11-19\3c197e11-9480-484e-815a-1432a898bbe2.tracker'.
2018-07-20T02:11:20.2968008Z 1b78 I DeploymentFileSetBuilder.cpp:107 Moving 'C:\Windows\ProPatches\Staged\2018-07-20-T-02-11-13\7z.dll' to 'C:\Windows\ProPatches\Installation\InstallationSandbox#2018-07-20-T-02-11-19\7z.dll'.
2018-07-20T02:11:20.3280517Z 1b78 I DeploymentFileSetBuilder.cpp:107 Moving 'C:\Windows\ProPatches\Staged\2018-07-20-T-02-11-13\cl5.exe' to 'C:\Windows\ProPatches\Installation\InstallationSandbox#2018-07-20-T-02-11-19\cl5.exe'.
2018-07-20T02:11:20.5060864Z 1b78 I DeploymentFileSetBuilder.cpp:107 Moving 'C:\Windows\ProPatches\Staged\2018-07-20-T-02-11-13\deployPackage-70992.zip' to 'C:\Windows\ProPatches\Installation\InstallationSandbox#2018-07-20-T-02-11-19\deployPackage-70992.zip'.
2018-07-20T02:11:20.5624384Z 1b78 I DeploymentFileSetBuilder.cpp:107 Moving 'C:\Windows\ProPatches\Staged\2018-07-20-T-02-11-13\dplyevts.dll' to 'C:\Windows\ProPatches\Installation\InstallationSandbox#2018-07-20-T-02-11-19\dplyevts.dll'.
2018-07-20T02:11:20.5946217Z 1b78 I DeploymentFileSetBuilder.cpp:107 Moving 'C:\Windows\ProPatches\Staged\2018-07-20-T-02-11-13\InstallPatches-70992.bat' to 'C:\Windows\ProPatches\Installation\InstallationSandbox#2018-07-20-T-02-11-19\InstallPatches-70992.bat'.
2018-07-20T02:11:20.6405564Z 1b78 I DeploymentFileSetBuilder.cpp:107 Moving 'C:\Windows\ProPatches\Staged\2018-07-20-T-02-11-13\safereboot.exe' to 'C:\Windows\ProPatches\Installation\InstallationSandbox#2018-07-20-T-02-11-19\safereboot.exe'.
2018-07-20T02:11:20.6561953Z 1b78 I DeploymentFileSetBuilder.cpp:107 Moving 'C:\Windows\ProPatches\Staged\2018-07-20-T-02-11-13\safereboot64.exe' to 'C:\Windows\ProPatches\Installation\InstallationSandbox#2018-07-20-T-02-11-19\safereboot64.exe'.
2018-07-20T02:11:20.6561953Z 1b78 I DeploymentFileSetBuilder.cpp:107 Moving 'C:\Windows\ProPatches\Staged\2018-07-20-T-02-11-13\STDeploy.log' to 'C:\Windows\ProPatches\Installation\InstallationSandbox#2018-07-20-T-02-11-19\STDeploy.log'.
2018-07-20T02:11:20.6718206Z 1b78 I DeploymentFileSetBuilder.cpp:107 Moving 'C:\Windows\ProPatches\Staged\2018-07-20-T-02-11-13\STDeployerCore.dll' to 'C:\Windows\ProPatches\Installation\InstallationSandbox#2018-07-20-T-02-11-19\STDeployerCore.dll'.
2018-07-20T02:11:20.7030637Z 1b78 I STPackageDeployer.cpp:1595 Deleted staging directory 'C:\Windows\ProPatches\Staged\2018-07-20-T-02-11-13'
2018-07-20T02:11:20.7030637Z 1b78 I STPackageDeployer.cpp:847 Deploy package 'deployPackage-70992.zip' successfully opened unsigned for package IO
2018-07-20T02:11:20.7030637Z 1b78 I STPackageDeployer.cpp:192 All required parts found in the deployment package.
2018-07-20T02:11:20.7030637Z 1b78 I STPackageDeployer.cpp:673 Deploy id ('3c197e11-9480-484e-815a-1432a898bbe2'), machine id ('70992'), deployerCoreVersion ('9.3.2708.0')
2018-07-20T02:11:20.7030637Z 1b78 V SchedClt.cpp:148 CSchedClt(): schedulerType=0, jobCreator=STPackageDeployer, jobName=Scheduled Deployment {3c197e11-9480-484e-815a-1432a898bbe2}, comment=deleting job.
2018-07-20T02:11:20.7030637Z 1b78 V Task.cpp:32 Task connected MS 2.0 scheduler
2018-07-20T02:11:20.7030637Z 1b78 E Scheduler.cpp:767 NativeOS scheduler: Failed to delete jobName=Scheduled Deployment {3c197e11-9480-484e-815a-1432a898bbe2} with the scheduler 2.0 interface installed - will not try AT interface
2018-07-20T02:11:20.7030637Z 1b78 V Task2.cpp:99 Task2 destructor
2018-07-20T02:11:20.7030637Z 1b78 V SchedClt.cpp:148 CSchedClt(): schedulerType=1, jobCreator=STPackageDeployer, jobName=Scheduled Deployment {3c197e11-9480-484e-815a-1432a898bbe2}, comment=deleting job.
2018-07-20T02:11:25.7507669Z 1b78 E SchedClt.cpp:486 ST scheduler: Failed to delete jobName='Scheduled Deployment {3c197e11-9480-484e-815a-1432a898bbe2}'
2018-07-20T02:11:25.7507669Z 1b78 V SchedClt.cpp:148 CSchedClt(): schedulerType=0, jobCreator=STPackageDeployer, jobName=LaunchSTDeployToRetryDownloadsAtBootup (3c197e11-9480-484e-815a-1432a898bbe2), comment=deleting job.
2018-07-20T02:11:25.7507669Z 1b78 V Task.cpp:32 Task connected MS 2.0 scheduler
2018-07-20T02:11:25.7507669Z 1b78 E Scheduler.cpp:767 NativeOS scheduler: Failed to delete jobName=LaunchSTDeployToRetryDownloadsAtBootup (3c197e11-9480-484e-815a-1432a898bbe2) with the scheduler 2.0 interface installed - will not try AT interface
2018-07-20T02:11:25.7507669Z 1b78 V Task2.cpp:99 Task2 destructor
2018-07-20T02:11:25.7507669Z 1b78 V SchedClt.cpp:148 CSchedClt(): schedulerType=1, jobCreator=STPackageDeployer, jobName=LaunchSTDeployToRetryDownloadsAtBootup (3c197e11-9480-484e-815a-1432a898bbe2), comment=deleting job.
2018-07-20T02:11:30.8284260Z 1b78 E SchedClt.cpp:486 ST scheduler: Failed to delete jobName='LaunchSTDeployToRetryDownloadsAtBootup (3c197e11-9480-484e-815a-1432a898bbe2)'
2018-07-20T02:11:30.8284260Z 1b78 V SchedClt.cpp:148 CSchedClt(): schedulerType=0, jobCreator=STPackageDeployer, jobName=LaunchSTDeployToRetryDownloadsAtNextProgressiveTime (3c197e11-9480-484e-815a-1432a898bbe2), comment=deleting job.
2018-07-20T02:11:30.8284260Z 1b78 V Task.cpp:32 Task connected MS 2.0 scheduler
2018-07-20T02:11:30.8284260Z 1b78 E Scheduler.cpp:767 NativeOS scheduler: Failed to delete jobName=LaunchSTDeployToRetryDownloadsAtNextProgressiveTime (3c197e11-9480-484e-815a-1432a898bbe2) with the scheduler 2.0 interface installed - will not try AT interface
2018-07-20T02:11:30.8284260Z 1b78 V Task2.cpp:99 Task2 destructor
2018-07-20T02:11:30.8284260Z 1b78 V SchedClt.cpp:148 CSchedClt(): schedulerType=1, jobCreator=STPackageDeployer, jobName=LaunchSTDeployToRetryDownloadsAtNextProgressiveTime (3c197e11-9480-484e-815a-1432a898bbe2), comment=deleting job.
2018-07-20T02:11:35.9067185Z 1b78 E SchedClt.cpp:486 ST scheduler: Failed to delete jobName='LaunchSTDeployToRetryDownloadsAtNextProgressiveTime (3c197e11-9480-484e-815a-1432a898bbe2)'
2018-07-20T02:11:35.9067185Z 1b78 V SchedClt.cpp:148 CSchedClt(): schedulerType=0, jobCreator=STPackageDeployer, jobName=LaunchSTDeployForDeployAfterPreDeployReboot (3c197e11-9480-484e-815a-1432a898bbe2), comment=deleting job.
2018-07-20T02:11:35.9067185Z 1b78 V Task.cpp:32 Task connected MS 2.0 scheduler
2018-07-20T02:11:35.9067185Z 1b78 E Scheduler.cpp:767 NativeOS scheduler: Failed to delete jobName=LaunchSTDeployForDeployAfterPreDeployReboot (3c197e11-9480-484e-815a-1432a898bbe2) with the scheduler 2.0 interface installed - will not try AT interface
2018-07-20T02:11:35.9067185Z 1b78 V Task2.cpp:99 Task2 destructor
2018-07-20T02:11:35.9067185Z 1b78 V SchedClt.cpp:148 CSchedClt(): schedulerType=1, jobCreator=STPackageDeployer, jobName=LaunchSTDeployForDeployAfterPreDeployReboot (3c197e11-9480-484e-815a-1432a898bbe2), comment=deleting job.
2018-07-20T02:11:40.9850143Z 1b78 E SchedClt.cpp:486 ST scheduler: Failed to delete jobName='LaunchSTDeployForDeployAfterPreDeployReboot (3c197e11-9480-484e-815a-1432a898bbe2)'
2018-07-20T02:11:40.9850143Z 1b78 V SchedClt.cpp:148 CSchedClt(): schedulerType=0, jobCreator=STPackageDeployer, jobName=LaunchSTDeployForOnlineStatusRetry (3c197e11-9480-484e-815a-1432a898bbe2), comment=deleting job.
2018-07-20T02:11:40.9850143Z 1b78 V Task.cpp:32 Task connected MS 2.0 scheduler
2018-07-20T02:11:40.9850143Z 1b78 E Scheduler.cpp:767 NativeOS scheduler: Failed to delete jobName=LaunchSTDeployForOnlineStatusRetry (3c197e11-9480-484e-815a-1432a898bbe2) with the scheduler 2.0 interface installed - will not try AT interface
2018-07-20T02:11:40.9850143Z 1b78 V Task2.cpp:99 Task2 destructor
2018-07-20T02:11:40.9850143Z 1b78 V SchedClt.cpp:148 CSchedClt(): schedulerType=1, jobCreator=STPackageDeployer, jobName=LaunchSTDeployForOnlineStatusRetry (3c197e11-9480-484e-815a-1432a898bbe2), comment=deleting job.
2018-07-20T02:11:46.0633143Z 1b78 E SchedClt.cpp:486 ST scheduler: Failed to delete jobName='LaunchSTDeployForOnlineStatusRetry (3c197e11-9480-484e-815a-1432a898bbe2)'
2018-07-20T02:11:46.0633143Z 1b78 V SchedClt.cpp:148 CSchedClt(): schedulerType=0, jobCreator=STPackageDeployer, jobName=LaunchSTDeployForPostBootActions (3c197e11-9480-484e-815a-1432a898bbe2), comment=deleting job.
2018-07-20T02:11:46.0633143Z 1b78 V Task.cpp:32 Task connected MS 2.0 scheduler
2018-07-20T02:11:46.0633143Z 1b78 E Scheduler.cpp:767 NativeOS scheduler: Failed to delete jobName=LaunchSTDeployForPostBootActions (3c197e11-9480-484e-815a-1432a898bbe2) with the scheduler 2.0 interface installed - will not try AT interface
2018-07-20T02:11:46.0633143Z 1b78 V Task2.cpp:99 Task2 destructor
2018-07-20T02:11:46.0633143Z 1b78 V SchedClt.cpp:148 CSchedClt(): schedulerType=1, jobCreator=STPackageDeployer, jobName=LaunchSTDeployForPostBootActions (3c197e11-9480-484e-815a-1432a898bbe2), comment=deleting job.
2018-07-20T02:11:51.1416136Z 1b78 E SchedClt.cpp:486 ST scheduler: Failed to delete jobName='LaunchSTDeployForPostBootActions (3c197e11-9480-484e-815a-1432a898bbe2)'
2018-07-20T02:11:51.1416136Z 1b78 V SchedClt.cpp:148 CSchedClt(): schedulerType=0, jobCreator=STPackageDeployer, jobName=LaunchSTDeployToRetryFailedPostBootActions (3c197e11-9480-484e-815a-1432a898bbe2), comment=deleting job.
2018-07-20T02:11:51.1416136Z 1b78 V Task.cpp:32 Task connected MS 2.0 scheduler
2018-07-20T02:11:51.1416136Z 1b78 E Scheduler.cpp:767 NativeOS scheduler: Failed to delete jobName=LaunchSTDeployToRetryFailedPostBootActions (3c197e11-9480-484e-815a-1432a898bbe2) with the scheduler 2.0 interface installed - will not try AT interface
2018-07-20T02:11:51.1416136Z 1b78 V Task2.cpp:99 Task2 destructor
2018-07-20T02:11:51.1416136Z 1b78 V SchedClt.cpp:148 CSchedClt(): schedulerType=1, jobCreator=STPackageDeployer, jobName=LaunchSTDeployToRetryFailedPostBootActions (3c197e11-9480-484e-815a-1432a898bbe2), comment=deleting job.
2018-07-20T02:11:56.2199313Z 1b78 E SchedClt.cpp:486 ST scheduler: Failed to delete jobName='LaunchSTDeployToRetryFailedPostBootActions (3c197e11-9480-484e-815a-1432a898bbe2)'
2018-07-20T02:11:56.2199313Z 1b78 V SchedClt.cpp:148 CSchedClt(): schedulerType=0, jobCreator=STPackageDeployer, jobName=LaunchSafeRebootPostDeployment (3c197e11-9480-484e-815a-1432a898bbe2), comment=deleting job.
2018-07-20T02:11:56.2199313Z 1b78 V Task.cpp:32 Task connected MS 2.0 scheduler
2018-07-20T02:11:56.2199313Z 1b78 E Scheduler.cpp:767 NativeOS scheduler: Failed to delete jobName=LaunchSafeRebootPostDeployment (3c197e11-9480-484e-815a-1432a898bbe2) with the scheduler 2.0 interface installed - will not try AT interface
2018-07-20T02:11:56.2199313Z 1b78 V Task2.cpp:99 Task2 destructor
2018-07-20T02:11:56.2199313Z 1b78 V SchedClt.cpp:148 CSchedClt(): schedulerType=1, jobCreator=STPackageDeployer, jobName=LaunchSafeRebootPostDeployment (3c197e11-9480-484e-815a-1432a898bbe2), comment=deleting job.
2018-07-20T02:12:01.2982118Z 1b78 E SchedClt.cpp:486 ST scheduler: Failed to delete jobName='LaunchSafeRebootPostDeployment (3c197e11-9480-484e-815a-1432a898bbe2)'
2018-07-20T02:12:01.2982118Z 1b78 I STPackageDeployer.cpp:207 No support files in the deployment package.
2018-07-20T02:12:01.2982118Z 1b78 V StatusClient.cpp:43 Attempting to load 'C:\Windows\ProPatches\Installation\InstallationSandbox#2018-07-20-T-02-11-19\dplyevts.dll'.
2018-07-20T02:12:01.2982118Z 1b78 I StatusClient.cpp:49 Loaded 'C:\Windows\ProPatches\Installation\InstallationSandbox#2018-07-20-T-02-11-19\dplyevts.dll' (9.3.4510.0).
2018-07-20T02:12:01.2982118Z 1b78 V DeployStatusReporter.cpp:309 Retrying online status reports. DeploymentId='3c197e11-9480-484e-815a-1432a898bbe2'
2018-07-20T02:12:01.2982118Z 1b78 I STPackageDeployer.cpp:269 No vendor patch installers in the deployment package.
2018-07-20T02:12:01.2982118Z 1b78 I STPackageDeployer.cpp:1527 Found the separately pushed 'C:\Windows\ProPatches\Installation\InstallationSandbox#2018-07-20-T-02-11-19\STDeployerCore.dll' file on disk
2018-07-20T02:12:01.3138367Z 1b78 V STPackageDeployer.cpp:763 (patchSpecifiers.xml) StatusId from PatchDesc: patchId='0001e509-0000-0000-0000-000000000000', regionId='1033', instanceName='' => statusId='197745'
2018-07-20T02:12:01.3138367Z 1b78 V STPackageDeployer.cpp:763 (patchSpecifiers.xml) StatusId from PatchDesc: patchId='0001e9c1-0000-0000-0000-000000000000', regionId='1033', instanceName='' => statusId='197746'
2018-07-20T02:12:01.3138367Z 1b78 V STPackageDeployer.cpp:763 (patchSpecifiers.xml) StatusId from PatchDesc: patchId='0001ea1c-0000-0000-0000-000000000000', regionId='1033', instanceName='' => statusId='197747'
2018-07-20T02:12:01.3138367Z 1b78 V STPackageDeployer.cpp:763 (patchSpecifiers.xml) StatusId from PatchDesc: patchId='0001e9bc-0000-0000-0000-000000000000', regionId='1033', instanceName='' => statusId='197748'
2018-07-20T02:12:01.3138367Z 1b78 V STPackageDeployer.cpp:763 (patchSpecifiers.xml) StatusId from PatchDesc: patchId='0001e9bd-0000-0000-0000-000000000000', regionId='1033', instanceName='' => statusId='197749'
2018-07-20T02:12:01.3294641Z 1b78 I DeployerClient.cpp:355 Loaded 'C:\Windows\ProPatches\Installation\InstallationSandbox#2018-07-20-T-02-11-19\STDeployerCore.dll' (9.3.2708.0).
2018-07-20T02:12:01.3450911Z 1b78 I STPackageDeployer.cpp:1780 Created deployer client. If statically linked, tracing to 'C:\Windows\ProPatches\Logs\STDeployerCore.log'. Otherwise, tracing to STDeploy.log.
2018-07-20T02:12:01.3450911Z 1b78 I STPackageDeployer.cpp:1832 Remote dialog request flag: 'false'
2018-07-20T02:12:01.3450911Z 1b78 V STPackageDeployer.cpp:1842 Getting vendor patch download information.
2018-07-20T02:12:01.3450911Z 1b78 I STPackageDeployer.cpp:1036 Not using distribution servers. Not downloading patches
2018-07-20T02:12:01.3450911Z 1b78 V DeployStatusReporter.cpp:128 Queueing online machine status msg. DeploymentId='3c197e11-9480-484e-815a-1432a898bbe2', machineId='70992', status='43', isFinal='false'
2018-07-20T02:12:01.3450911Z 1b78 S StatusClient.cpp:109 Entering STDeployment::CStatusClient::ReportMachineStatusOnline.
2018-07-20T02:12:03.6576700Z 1b78 I STPackageDeployer.cpp:1931 Deploying patches...
2018-07-20T02:12:03.6576700Z 1b78 V STPackageDeployer.cpp:1936 statusId='197745' <= StatusId from PatchDesc: patchId='0001e509-0000-0000-0000-000000000000', regionId='1033', instanceName=''
2018-07-20T02:12:03.6576700Z 1b78 I STPackageDeployer.cpp:307 Deploy arguments: machineName '192.168.11.195', patchId '0001e509-0000-0000-0000-000000000000', isServicePack 'false', regionId '1033'
2018-07-20T02:12:03.6576700Z 1b78 V DeployStatusReporter.cpp:239 Queueing online patch progress msg. DeploymentId='3c197e11-9480-484e-815a-1432a898bbe2', statusId='197745', patchStatus='4', isFinal='false'
2018-07-20T02:12:03.6576700Z 1b78 S StatusClient.cpp:90 Entering STDeployment::CStatusClient::ReportPatchStatusOnline.
2018-07-20T14:12:14.0685379Z 1b78 V DeployStatusReporter.cpp:257 Queueing online patch progress msg. DeploymentId='3c197e11-9480-484e-815a-1432a898bbe2', statusId='197745', cookedResult='1', isFinal='true'
2018-07-20T14:12:14.0685379Z 1b78 S StatusClient.cpp:99 Entering STDeployment::CStatusClient::ReportPatchStatusOnline.
2018-07-20T14:12:16.2248617Z 1b78 I STPackageDeployer.cpp:1235 Patch file 'C:\Windows\ProPatches\Patches\WinSCP-5.13.3-Setup.exe' install operation completed. Cooked result='1'. RebootRequired='false'
2018-07-20T14:12:16.2248617Z 1b78 V STPackageDeployer.cpp:1936 statusId='197748' <= StatusId from PatchDesc: patchId='0001e9bc-0000-0000-0000-000000000000', regionId='1033', instanceName=''
2018-07-20T14:12:16.2248617Z 1b78 I STPackageDeployer.cpp:307 Deploy arguments: machineName '192.168.11.195', patchId '0001e9bc-0000-0000-0000-000000000000', isServicePack 'false', regionId '1033'
2018-07-20T14:12:16.2248617Z 1b78 V DeployStatusReporter.cpp:239 Queueing online patch progress msg. DeploymentId='3c197e11-9480-484e-815a-1432a898bbe2', statusId='197748', patchStatus='4', isFinal='false'
2018-07-20T14:12:16.2248617Z 1b78 S StatusClient.cpp:90 Entering STDeployment::CStatusClient::ReportPatchStatusOnline.
2018-07-20T14:12:24.0845094Z 1b78 V DeployStatusReporter.cpp:257 Queueing online patch progress msg. DeploymentId='3c197e11-9480-484e-815a-1432a898bbe2', statusId='197748', cookedResult='1', isFinal='true'
2018-07-20T14:12:24.0845094Z 1b78 S StatusClient.cpp:99 Entering STDeployment::CStatusClient::ReportPatchStatusOnline.
2018-07-20T14:12:24.1001388Z 1b78 I STPackageDeployer.cpp:1235 Patch file 'C:\Windows\ProPatches\Patches\AspNetWebToolsVS2013-KB4339279.exe' install operation completed. Cooked result='1'. RebootRequired='false'
2018-07-20T14:12:24.1001388Z 1b78 V STPackageDeployer.cpp:1936 statusId='197749' <= StatusId from PatchDesc: patchId='0001e9bd-0000-0000-0000-000000000000', regionId='1033', instanceName=''
2018-07-20T14:12:24.1001388Z 1b78 I STPackageDeployer.cpp:307 Deploy arguments: machineName '192.168.11.195', patchId '0001e9bd-0000-0000-0000-000000000000', isServicePack 'false', regionId '1033'
2018-07-20T14:12:24.1001388Z 1b78 V DeployStatusReporter.cpp:239 Queueing online patch progress msg. DeploymentId='3c197e11-9480-484e-815a-1432a898bbe2', statusId='197749', patchStatus='4', isFinal='false'
2018-07-20T14:12:24.1001388Z 1b78 S StatusClient.cpp:90 Entering STDeployment::CStatusClient::ReportPatchStatusOnline.
2018-07-20T14:12:29.0690552Z 1b78 V DeployStatusReporter.cpp:257 Queueing online patch progress msg. DeploymentId='3c197e11-9480-484e-815a-1432a898bbe2', statusId='197749', cookedResult='1', isFinal='true'
2018-07-20T14:12:29.0690552Z 1b78 S StatusClient.cpp:99 Entering STDeployment::CStatusClient::ReportPatchStatusOnline.
2018-07-20T14:12:29.1159352Z 1b78 I STPackageDeployer.cpp:1235 Patch file 'C:\Windows\ProPatches\Patches\AspNetWebFrameworksToolsVS2013-KB4339279.exe' install operation completed. Cooked result='1'. RebootRequired='false'
2018-07-20T14:12:29.1159352Z 1b78 V STPackageDeployer.cpp:1936 statusId='197746' <= StatusId from PatchDesc: patchId='0001e9c1-0000-0000-0000-000000000000', regionId='1033', instanceName=''
2018-07-20T14:12:29.1159352Z 1b78 I STPackageDeployer.cpp:307 Deploy arguments: machineName '192.168.11.195', patchId '0001e9c1-0000-0000-0000-000000000000', isServicePack 'false', regionId '1033'
2018-07-20T14:12:29.1159352Z 1b78 V DeployStatusReporter.cpp:239 Queueing online patch progress msg. DeploymentId='3c197e11-9480-484e-815a-1432a898bbe2', statusId='197746', patchStatus='4', isFinal='false'
2018-07-20T14:12:29.1159352Z 1b78 S StatusClient.cpp:90 Entering STDeployment::CStatusClient::ReportPatchStatusOnline.
2018-07-20T14:14:15.3148538Z 1b78 V DeployStatusReporter.cpp:257 Queueing online patch progress msg. DeploymentId='3c197e11-9480-484e-815a-1432a898bbe2', statusId='197746', cookedResult='6', isFinal='true'
2018-07-20T14:14:15.3148538Z 1b78 S StatusClient.cpp:99 Entering STDeployment::CStatusClient::ReportPatchStatusOnline.
2018-07-20T14:14:17.4099783Z 1b78 I STPackageDeployer.cpp:1235 Patch file 'C:\Windows\ProPatches\Patches\VMware-tools-10.3.0-8931395-x86_64.exe' install operation completed. Cooked result='6'. RebootRequired='true'
2018-07-20T14:14:17.4099783Z 1b78 V STPackageDeployer.cpp:1936 statusId='197747' <= StatusId from PatchDesc: patchId='0001ea1c-0000-0000-0000-000000000000', regionId='1033', instanceName=''
2018-07-20T14:14:17.4099783Z 1b78 I STPackageDeployer.cpp:307 Deploy arguments: machineName '192.168.11.195', patchId '0001ea1c-0000-0000-0000-000000000000', isServicePack 'false', regionId '1033'
2018-07-20T14:14:17.4099783Z 1b78 V DeployStatusReporter.cpp:239 Queueing online patch progress msg. DeploymentId='3c197e11-9480-484e-815a-1432a898bbe2', statusId='197747', patchStatus='4', isFinal='false'
2018-07-20T14:14:17.4099783Z 1b78 S StatusClient.cpp:90 Entering STDeployment::CStatusClient::ReportPatchStatusOnline.
2018-07-20T14:14:41.1131532Z 1b78 V DeployStatusReporter.cpp:257 Queueing online patch progress msg. DeploymentId='3c197e11-9480-484e-815a-1432a898bbe2', statusId='197747', cookedResult='5', isFinal='true'
2018-07-20T14:14:41.1131532Z 1b78 S StatusClient.cpp:99 Entering STDeployment::CStatusClient::ReportPatchStatusOnline.
2018-07-20T14:14:41.1444398Z 1b78 I STPackageDeployer.cpp:1235 Patch file 'C:\Windows\ProPatches\Patches\Wireshark-win64-2.6.2.exe' install operation completed. Cooked result='5'. RebootRequired='false'
2018-07-20T14:14:41.1444398Z 1b78 I STPackageDeployer.cpp:1963 Done deploying patches...
2018-07-20T14:14:41.1444398Z 1b78 I STPackageDeployer.cpp:1965 Deploying product instances patches...
2018-07-20T14:14:41.1444398Z 1b78 I STPackageDeployer.cpp:2005 Done deploying product instances patches...
2018-07-20T14:14:41.1444398Z 1b78 W SingleInstanceLock.cpp:28 Waiting for another deployment to finish.
2018-07-20T14:14:41.1444398Z 1b78 I SingleInstanceLock.cpp:36 Exclusively continuing deployment.
2018-07-20T14:14:41.1444398Z 1b78 V STPackageDeployer.cpp:85 Initiating patch store servicing.
2018-07-20T14:14:41.1444398Z 1b78 V STPackageDeployer.cpp:106 Patch store servicing complete.
2018-07-20T14:14:41.1600763Z 1b78 I STPackageDeployer.cpp:1378 Scheduling a relaunch of STDeploy.exe at next bootup to perform post-boot actions processing
2018-07-20T14:14:41.1600763Z 1b78 V SchedClt.cpp:148 CSchedClt(): schedulerType=1, jobCreator=STPackageDeployer, jobName=LaunchSTDeployForPostBootActions (3c197e11-9480-484e-815a-1432a898bbe2), comment=Schedule STDeploy.exe to run at next bootup to perform post-boot actions.
2018-07-20T14:14:41.1600763Z 1b78 I STPackageDeployer.cpp:974 'STDeploy.exe package="deployPackage-70992.zip" relaunchSandbox="C:\Windows\ProPatches\Installation\InstallationSandbox#2018-07-20-T-02-11-19" relaunchReason="afterPostDeploymentReboot=1"' scheduled to run on next boot-up.
2018-07-20T14:14:41.1600763Z 1b78 I STPackageDeployer.cpp:422 Reporting pending reboot to status handler.
2018-07-20T14:14:41.1600763Z 1b78 V DeployStatusReporter.cpp:17 CDeployStatusReporter@MakePostBootActionSequence: Loading existing task-xml filename='PostBootTasks.xml'.
2018-07-20T14:14:41.1600763Z 1b78 S PostBootActionSequence.cpp:332 Entering STDeployment::CPostBootActionSequence::Load.
2018-07-20T14:14:41.1600763Z 1b78 S PostBootActionSequence.cpp:347 Entering STDeployment::CPostBootActionSequence::ReadXml.
2018-07-20T14:14:41.1600763Z 1b78 S PostBootActionSequence.cpp:347 Leaving STDeployment::CPostBootActionSequence::ReadXml.
2018-07-20T14:14:41.1600763Z 1b78 S PostBootActionSequence.cpp:332 Leaving STDeployment::CPostBootActionSequence::Load.
2018-07-20T14:14:41.1600763Z 1b78 S PostBootActionSequence.cpp:546 Entering STDeployment::CPostBootActionSequence::Save.
2018-07-20T14:14:41.1600763Z 1b78 S PostBootActionSequence.cpp:390 Entering STDeployment::CPostBootActionSequence::WriteXml.
2018-07-20T14:14:41.1600763Z 1b78 S PostBootActionSequence.cpp:390 Leaving STDeployment::CPostBootActionSequence::WriteXml.
2018-07-20T14:14:41.1600763Z 1b78 S PostBootActionSequence.cpp:546 Leaving STDeployment::CPostBootActionSequence::Save.
2018-07-20T14:14:41.1600763Z 1b78 V DeployStatusReporter.cpp:226 Queued a PostBootTasks.xml action: 'Report machine status finished to the online status handler'. DeploymentId='3c197e11-9480-484e-815a-1432a898bbe2', machineId='70992', machineStatus='34'
2018-07-20T14:14:41.1600763Z 1b78 V DeployStatusReporter.cpp:128 Queueing online machine status msg. DeploymentId='3c197e11-9480-484e-815a-1432a898bbe2', machineId='70992', status='34', isFinal='false'
2018-07-20T14:14:41.1600763Z 1b78 S StatusClient.cpp:109 Entering STDeployment::CStatusClient::ReportMachineStatusOnline.
2018-07-20T14:14:41.1913307Z 1b78 I STPackageDeployer.cpp:478 Launching SafeReboot. deployerSpecifiedRebootRequired=true
2018-07-20T14:14:41.1913307Z 1b78 I STPackageDeployer.cpp:390 SafeReboot command line: '"C:\Windows\ProPatches\Installation\InstallationSandbox#2018-07-20-T-02-11-19\SafeReboot.exe" -o 0 -requestor 1 -s 2 -m 1 -w 60 -n "Safe Reboot" -u "MEARSDOM\admin_cullenp" -power 4'
2018-07-20T14:14:41.2695069Z 1b78 S DeployExeStates.cpp:409 Leaving STDeploy::CInitialExecutionPackageDeploy::DoStatefulRemediateActions.
2018-07-20T14:14:41.2695069Z 1b78 I STDeploy.cpp:365 Current remediation phase completed. Process exit code: 3010.
2018-07-20T14:14:41.2695069Z 1b78 S STDeploy.cpp:257 Leaving wmain.
2018-07-20T14:18:40.6984133Z 08e8 S STDeploy.cpp:257 Entering wmain.
2018-07-20T14:18:40.6984133Z 08e8 I STDeploy.cpp:262 'C:\Windows\ProPatches\Installation\InstallationSandbox#2018-07-20-T-02-11-19\STDeploy.exe' is starting, version: 9.3.2708.0.
2018-07-20T14:18:40.6984133Z 08e8 V DeployContext.cpp:259 STDeploy.exe command line args: 'package="C:\Windows\ProPatches\Installation\InstallationSandbox#2018-07-20-T-02-11-19\deployPackage-70992.zip" "relaunchSandbox=C:\Windows\ProPatches\Installation\InstallationSandbox#2018-07-20-T-02-11-19" "relaunchReason=afterPostDeploymentReboot=1"'
2018-07-20T14:18:40.6984133Z 08e8 S DeployExeStates.cpp:344 Entering STDeploy::CExtendedCmdLineHandlingPackageDeploy::ProcessExtendedCmdLineArguments.
2018-07-20T14:18:40.7140392Z 08e8 S DeployExeStates.cpp:344 Leaving STDeploy::CExtendedCmdLineHandlingPackageDeploy::ProcessExtendedCmdLineArguments.
2018-07-20T14:18:40.7452871Z 08e8 I STDeploy.cpp:358 C:\Windows\ProPatches\Installation\InstallationSandbox#2018-07-20-T-02-11-19\STDeploy.exe is now executing out of a sandbox: 'C:\Windows\ProPatches\Installation\InstallationSandbox#2018-07-20-T-02-11-19'.
2018-07-20T14:18:40.7452871Z 08e8 S DeployExeStates.cpp:418 Entering STDeploy::CRelaunchedExecutionPackageDeploy::DoStatefulRemediateActions.
2018-07-20T14:18:40.7452871Z 08e8 V DeployExeStates.cpp:84 Invoking remediation manager processing: userSuppliedFileName='deployPackage-70992.zip', userSuppliedPath='C:\Windows\ProPatches\Installation\InstallationSandbox#2018-07-20-T-02-11-19', patchStorePath='C:\Windows\ProPatches\Patches', deployerCoreLogFilePath='C:\Windows\ProPatches\Logs\STDeployerCore.log', LaunchCount='1', LaunchReason='5', currentDirectory='C:\Windows\ProPatches\Installation\InstallationSandbox#2018-07-20-T-02-11-19', sandboxDirectory='C:\Windows\ProPatches\Installation\InstallationSandbox#2018-07-20-T-02-11-19'
2018-07-20T14:18:40.7609139Z 08e8 I STPackageDeployer.cpp:847 Deploy package 'deployPackage-70992.zip' successfully opened unsigned for package IO
2018-07-20T14:18:40.7609139Z 08e8 I STPackageDeployer.cpp:192 All required parts found in the deployment package.
2018-07-20T14:18:40.7609139Z 08e8 I STPackageDeployer.cpp:673 Deploy id ('3c197e11-9480-484e-815a-1432a898bbe2'), machine id ('70992'), deployerCoreVersion ('9.3.2708.0')
2018-07-20T14:18:40.7609139Z 08e8 V SchedClt.cpp:148 CSchedClt(): schedulerType=0, jobCreator=STPackageDeployer, jobName=Scheduled Deployment {3c197e11-9480-484e-815a-1432a898bbe2}, comment=deleting job.
2018-07-20T14:18:40.7926497Z 08e8 V Task.cpp:32 Task connected MS 2.0 scheduler
2018-07-20T14:18:40.7926497Z 08e8 E Scheduler.cpp:767 NativeOS scheduler: Failed to delete jobName=Scheduled Deployment {3c197e11-9480-484e-815a-1432a898bbe2} with the scheduler 2.0 interface installed - will not try AT interface
2018-07-20T14:18:40.7926497Z 08e8 V Task2.cpp:99 Task2 destructor
2018-07-20T14:18:40.7926497Z 08e8 V SchedClt.cpp:148 CSchedClt(): schedulerType=1, jobCreator=STPackageDeployer, jobName=Scheduled Deployment {3c197e11-9480-484e-815a-1432a898bbe2}, comment=deleting job.
2018-07-20T14:18:45.8703005Z 08e8 E SchedClt.cpp:486 ST scheduler: Failed to delete jobName='Scheduled Deployment {3c197e11-9480-484e-815a-1432a898bbe2}'
2018-07-20T14:18:45.8703005Z 08e8 V SchedClt.cpp:148 CSchedClt(): schedulerType=0, jobCreator=STPackageDeployer, jobName=LaunchSTDeployToRetryDownloadsAtBootup (3c197e11-9480-484e-815a-1432a898bbe2), comment=deleting job.
2018-07-20T14:18:45.8703005Z 08e8 V Task.cpp:32 Task connected MS 2.0 scheduler
2018-07-20T14:18:45.8703005Z 08e8 E Scheduler.cpp:767 NativeOS scheduler: Failed to delete jobName=LaunchSTDeployToRetryDownloadsAtBootup (3c197e11-9480-484e-815a-1432a898bbe2) with the scheduler 2.0 interface installed - will not try AT interface
2018-07-20T14:18:45.8703005Z 08e8 V Task2.cpp:99 Task2 destructor
2018-07-20T14:18:45.8703005Z 08e8 V SchedClt.cpp:148 CSchedClt(): schedulerType=1, jobCreator=STPackageDeployer, jobName=LaunchSTDeployToRetryDownloadsAtBootup (3c197e11-9480-484e-815a-1432a898bbe2), comment=deleting job.
2018-07-20T14:18:50.9484443Z 08e8 E SchedClt.cpp:486 ST scheduler: Failed to delete jobName='LaunchSTDeployToRetryDownloadsAtBootup (3c197e11-9480-484e-815a-1432a898bbe2)'
2018-07-20T14:18:50.9484443Z 08e8 V SchedClt.cpp:148 CSchedClt(): schedulerType=0, jobCreator=STPackageDeployer, jobName=LaunchSTDeployToRetryDownloadsAtNextProgressiveTime (3c197e11-9480-484e-815a-1432a898bbe2), comment=deleting job.
2018-07-20T14:18:50.9484443Z 08e8 V Task.cpp:32 Task connected MS 2.0 scheduler
2018-07-20T14:18:50.9484443Z 08e8 E Scheduler.cpp:767 NativeOS scheduler: Failed to delete jobName=LaunchSTDeployToRetryDownloadsAtNextProgressiveTime (3c197e11-9480-484e-815a-1432a898bbe2) with the scheduler 2.0 interface installed - will not try AT interface
2018-07-20T14:18:50.9484443Z 08e8 V Task2.cpp:99 Task2 destructor
2018-07-20T14:18:50.9484443Z 08e8 V SchedClt.cpp:148 CSchedClt(): schedulerType=1, jobCreator=STPackageDeployer, jobName=LaunchSTDeployToRetryDownloadsAtNextProgressiveTime (3c197e11-9480-484e-815a-1432a898bbe2), comment=deleting job.
2018-07-20T14:18:56.0265731Z 08e8 E SchedClt.cpp:486 ST scheduler: Failed to delete jobName='LaunchSTDeployToRetryDownloadsAtNextProgressiveTime (3c197e11-9480-484e-815a-1432a898bbe2)'
2018-07-20T14:18:56.0265731Z 08e8 V SchedClt.cpp:148 CSchedClt(): schedulerType=0, jobCreator=STPackageDeployer, jobName=LaunchSTDeployForDeployAfterPreDeployReboot (3c197e11-9480-484e-815a-1432a898bbe2), comment=deleting job.
2018-07-20T14:18:56.0265731Z 08e8 V Task.cpp:32 Task connected MS 2.0 scheduler
2018-07-20T14:18:56.0265731Z 08e8 E Scheduler.cpp:767 NativeOS scheduler: Failed to delete jobName=LaunchSTDeployForDeployAfterPreDeployReboot (3c197e11-9480-484e-815a-1432a898bbe2) with the scheduler 2.0 interface installed - will not try AT interface
2018-07-20T14:18:56.0265731Z 08e8 V Task2.cpp:99 Task2 destructor
2018-07-20T14:18:56.0265731Z 08e8 V SchedClt.cpp:148 CSchedClt(): schedulerType=1, jobCreator=STPackageDeployer, jobName=LaunchSTDeployForDeployAfterPreDeployReboot (3c197e11-9480-484e-815a-1432a898bbe2), comment=deleting job.
2018-07-20T14:19:01.1048893Z 08e8 E SchedClt.cpp:486 ST scheduler: Failed to delete jobName='LaunchSTDeployForDeployAfterPreDeployReboot (3c197e11-9480-484e-815a-1432a898bbe2)'
2018-07-20T14:19:01.1048893Z 08e8 V SchedClt.cpp:148 CSchedClt(): schedulerType=0, jobCreator=STPackageDeployer, jobName=LaunchSTDeployForOnlineStatusRetry (3c197e11-9480-484e-815a-1432a898bbe2), comment=deleting job.
2018-07-20T14:19:01.1048893Z 08e8 V Task.cpp:32 Task connected MS 2.0 scheduler
2018-07-20T14:19:01.1048893Z 08e8 E Scheduler.cpp:767 NativeOS scheduler: Failed to delete jobName=LaunchSTDeployForOnlineStatusRetry (3c197e11-9480-484e-815a-1432a898bbe2) with the scheduler 2.0 interface installed - will not try AT interface
2018-07-20T14:19:01.1048893Z 08e8 V Task2.cpp:99 Task2 destructor
2018-07-20T14:19:01.1048893Z 08e8 V SchedClt.cpp:148 CSchedClt(): schedulerType=1, jobCreator=STPackageDeployer, jobName=LaunchSTDeployForOnlineStatusRetry (3c197e11-9480-484e-815a-1432a898bbe2), comment=deleting job.
2018-07-20T14:19:06.1883248Z 08e8 E SchedClt.cpp:486 ST scheduler: Failed to delete jobName='LaunchSTDeployForOnlineStatusRetry (3c197e11-9480-484e-815a-1432a898bbe2)'
2018-07-20T14:19:06.1883248Z 08e8 V SchedClt.cpp:148 CSchedClt(): schedulerType=0, jobCreator=STPackageDeployer, jobName=LaunchSTDeployForPostBootActions (3c197e11-9480-484e-815a-1432a898bbe2), comment=deleting job.
2018-07-20T14:19:06.1883248Z 08e8 V Task.cpp:32 Task connected MS 2.0 scheduler
2018-07-20T14:19:06.1883248Z 08e8 E Scheduler.cpp:767 NativeOS scheduler: Failed to delete jobName=LaunchSTDeployForPostBootActions (3c197e11-9480-484e-815a-1432a898bbe2) with the scheduler 2.0 interface installed - will not try AT interface
2018-07-20T14:19:06.1883248Z 08e8 V Task2.cpp:99 Task2 destructor
2018-07-20T14:19:06.1883248Z 08e8 V SchedClt.cpp:148 CSchedClt(): schedulerType=1, jobCreator=STPackageDeployer, jobName=LaunchSTDeployForPostBootActions (3c197e11-9480-484e-815a-1432a898bbe2), comment=deleting job.
2018-07-20T14:19:11.2717624Z 08e8 E SchedClt.cpp:486 ST scheduler: Failed to delete jobName='LaunchSTDeployForPostBootActions (3c197e11-9480-484e-815a-1432a898bbe2)'
2018-07-20T14:19:11.2717624Z 08e8 V SchedClt.cpp:148 CSchedClt(): schedulerType=0, jobCreator=STPackageDeployer, jobName=LaunchSTDeployToRetryFailedPostBootActions (3c197e11-9480-484e-815a-1432a898bbe2), comment=deleting job.
2018-07-20T14:19:11.2717624Z 08e8 V Task.cpp:32 Task connected MS 2.0 scheduler
2018-07-20T14:19:11.2717624Z 08e8 E Scheduler.cpp:767 NativeOS scheduler: Failed to delete jobName=LaunchSTDeployToRetryFailedPostBootActions (3c197e11-9480-484e-815a-1432a898bbe2) with the scheduler 2.0 interface installed - will not try AT interface
2018-07-20T14:19:11.2717624Z 08e8 V Task2.cpp:99 Task2 destructor
2018-07-20T14:19:11.2717624Z 08e8 V SchedClt.cpp:148 CSchedClt(): schedulerType=1, jobCreator=STPackageDeployer, jobName=LaunchSTDeployToRetryFailedPostBootActions (3c197e11-9480-484e-815a-1432a898bbe2), comment=deleting job.
2018-07-20T14:19:16.3551976Z 08e8 E SchedClt.cpp:486 ST scheduler: Failed to delete jobName='LaunchSTDeployToRetryFailedPostBootActions (3c197e11-9480-484e-815a-1432a898bbe2)'
2018-07-20T14:19:16.3551976Z 08e8 V SchedClt.cpp:148 CSchedClt(): schedulerType=0, jobCreator=STPackageDeployer, jobName=LaunchSafeRebootPostDeployment (3c197e11-9480-484e-815a-1432a898bbe2), comment=deleting job.
2018-07-20T14:19:16.3551976Z 08e8 V Task.cpp:32 Task connected MS 2.0 scheduler
2018-07-20T14:19:16.3551976Z 08e8 E Scheduler.cpp:767 NativeOS scheduler: Failed to delete jobName=LaunchSafeRebootPostDeployment (3c197e11-9480-484e-815a-1432a898bbe2) with the scheduler 2.0 interface installed - will not try AT interface
2018-07-20T14:19:16.3551976Z 08e8 V Task2.cpp:99 Task2 destructor
2018-07-20T14:19:16.3551976Z 08e8 V SchedClt.cpp:148 CSchedClt(): schedulerType=1, jobCreator=STPackageDeployer, jobName=LaunchSafeRebootPostDeployment (3c197e11-9480-484e-815a-1432a898bbe2), comment=deleting job.
2018-07-20T14:19:21.4386421Z 08e8 E SchedClt.cpp:486 ST scheduler: Failed to delete jobName='LaunchSafeRebootPostDeployment (3c197e11-9480-484e-815a-1432a898bbe2)'
2018-07-20T14:19:21.4386421Z 08e8 I STPackageDeployer.cpp:207 No support files in the deployment package.
2018-07-20T14:19:21.4699191Z 08e8 V StatusClient.cpp:43 Attempting to load 'C:\Windows\ProPatches\Installation\InstallationSandbox#2018-07-20-T-02-11-19\dplyevts.dll'.
2018-07-20T14:19:21.5011979Z 08e8 I StatusClient.cpp:49 Loaded 'C:\Windows\ProPatches\Installation\InstallationSandbox#2018-07-20-T-02-11-19\dplyevts.dll' (9.3.4510.0).
2018-07-20T14:19:21.5011979Z 08e8 V DeployStatusReporter.cpp:309 Retrying online status reports. DeploymentId='3c197e11-9480-484e-815a-1432a898bbe2'
2018-07-20T14:19:21.5168486Z 08e8 I STPackageDeployer.cpp:1527 Found the separately pushed 'C:\Windows\ProPatches\Installation\InstallationSandbox#2018-07-20-T-02-11-19\STDeployerCore.dll' file on disk
2018-07-20T14:19:21.5794041Z 08e8 V STPackageDeployer.cpp:763 (patchSpecifiers.xml) StatusId from PatchDesc: patchId='0001e509-0000-0000-0000-000000000000', regionId='1033', instanceName='' => statusId='197745'
2018-07-20T14:19:21.5794041Z 08e8 V STPackageDeployer.cpp:763 (patchSpecifiers.xml) StatusId from PatchDesc: patchId='0001e9c1-0000-0000-0000-000000000000', regionId='1033', instanceName='' => statusId='197746'
2018-07-20T14:19:21.5794041Z 08e8 V STPackageDeployer.cpp:763 (patchSpecifiers.xml) StatusId from PatchDesc: patchId='0001ea1c-0000-0000-0000-000000000000', regionId='1033', instanceName='' => statusId='197747'
2018-07-20T14:19:21.5794041Z 08e8 V STPackageDeployer.cpp:763 (patchSpecifiers.xml) StatusId from PatchDesc: patchId='0001e9bc-0000-0000-0000-000000000000', regionId='1033', instanceName='' => statusId='197748'
2018-07-20T14:19:21.5794041Z 08e8 V STPackageDeployer.cpp:763 (patchSpecifiers.xml) StatusId from PatchDesc: patchId='0001e9bd-0000-0000-0000-000000000000', regionId='1033', instanceName='' => statusId='197749'
2018-07-20T14:19:21.5794041Z 08e8 I DeployerClient.cpp:355 Loaded 'C:\Windows\ProPatches\Installation\InstallationSandbox#2018-07-20-T-02-11-19\STDeployerCore.dll' (9.3.2708.0).
2018-07-20T14:19:21.5970415Z 08e8 I STPackageDeployer.cpp:1780 Created deployer client. If statically linked, tracing to 'C:\Windows\ProPatches\Logs\STDeployerCore.log'. Otherwise, tracing to STDeploy.log.
2018-07-20T14:19:21.5970415Z 08e8 S PostBootLauncher.cpp:32 Entering STDeploy::CPostBootLauncher::LaunchPostBootActions.
2018-07-20T14:19:21.5970415Z 08e8 S PostBootActionSequence.cpp:332 Entering STDeployment::CPostBootActionSequence::Load.
2018-07-20T14:19:21.6106921Z 08e8 S PostBootActionSequence.cpp:347 Entering STDeployment::CPostBootActionSequence::ReadXml.
2018-07-20T14:19:21.6106921Z 08e8 S PostBootActionSequence.cpp:347 Leaving STDeployment::CPostBootActionSequence::ReadXml.
2018-07-20T14:19:21.6106921Z 08e8 S PostBootActionSequence.cpp:332 Leaving STDeployment::CPostBootActionSequence::Load.
2018-07-20T14:19:21.6106921Z 08e8 S PostBootActionSequence.cpp:415 Entering STDeployment::CPostBootActionSequence::ProcessPostRebootTasksImpl.
2018-07-20T14:19:21.6106921Z 08e8 S PostBootActionSequence.cpp:560 Entering STDeployment::CPostBootActionSequence::DispatchPostRebootTask.
2018-07-20T14:19:21.6106921Z 08e8 S PostBootActionSequence.cpp:89 Entering `anonymous-namespace'::ProcessRegistryBreadCrumbUpdate.
2018-07-20T14:19:21.6106921Z 08e8 I PatchBreadCrumbAccessor.cpp:261 Recording post-reboot registry breadcrumb=Finished for patchId=0001e9c1-0000-0000-0000-000000000000.
2018-07-20T14:19:21.6106921Z 08e8 S PostBootActionSequence.cpp:89 Leaving `anonymous-namespace'::ProcessRegistryBreadCrumbUpdate.
2018-07-20T14:19:21.6106921Z 08e8 S PostBootActionSequence.cpp:560 Leaving STDeployment::CPostBootActionSequence::DispatchPostRebootTask.
2018-07-20T14:19:21.6106921Z 08e8 I PostBootActionSequence.cpp:433 Command RECORD_PATCH_INSTALL_BREADCRUMB_IN_REGISTRY completed
2018-07-20T14:19:21.6106921Z 08e8 S PostBootActionSequence.cpp:560 Entering STDeployment::CPostBootActionSequence::DispatchPostRebootTask.
2018-07-20T14:19:21.6106921Z 08e8 S PostBootActionSequence.cpp:273 Entering `anonymous-namespace'::ProcessStatusReport.
2018-07-20T14:19:21.6106921Z 08e8 V StatusClient.cpp:43 Attempting to load 'C:\Windows\ProPatches\Installation\InstallationSandbox#2018-07-20-T-02-11-19\dplyevts.dll'.
2018-07-20T14:19:21.6106921Z 08e8 I StatusClient.cpp:49 Loaded 'C:\Windows\ProPatches\Installation\InstallationSandbox#2018-07-20-T-02-11-19\dplyevts.dll' (9.3.4510.0).
2018-07-20T14:19:21.6106921Z 08e8 V PostBootActionSequence.cpp:278 Reporting post-reboot status for statusType='OnlineMachineStatus'
2018-07-20T14:19:21.6106921Z 08e8 S PostBootActionSequence.cpp:247 Entering `anonymous-namespace'::COnlineMachineStatusReport::operator ().
2018-07-20T14:19:21.6106921Z 08e8 S StatusClient.cpp:109 Entering STDeployment::CStatusClient::ReportMachineStatusOnline.
2018-07-20T14:19:24.7546146Z 08e8 S PostBootActionSequence.cpp:247 Leaving `anonymous-namespace'::COnlineMachineStatusReport::operator ().
2018-07-20T14:19:24.7546146Z 08e8 S PostBootActionSequence.cpp:273 Leaving `anonymous-namespace'::ProcessStatusReport.
2018-07-20T14:19:24.7546146Z 08e8 S PostBootActionSequence.cpp:560 Leaving STDeployment::CPostBootActionSequence::DispatchPostRebootTask.
2018-07-20T14:19:24.7546146Z 08e8 I PostBootActionSequence.cpp:433 Command STATUS_REPORT completed
2018-07-20T14:19:24.7546146Z 08e8 S PostBootActionSequence.cpp:415 Leaving STDeployment::CPostBootActionSequence::ProcessPostRebootTasksImpl.
2018-07-20T14:19:24.7546146Z 08e8 S PostBootLauncher.cpp:32 Leaving STDeploy::CPostBootLauncher::LaunchPostBootActions.
2018-07-20T14:19:24.7702420Z 08e8 V Sandbox.cpp:66 DoSandboxCleanup: Deleted file='C:\Windows\ProPatches\Patches\WinSCP-5.13.3-Setup.exe'
2018-07-20T14:19:24.7702420Z 08e8 V Sandbox.cpp:66 DoSandboxCleanup: Deleted file='C:\Windows\ProPatches\Patches\AspNetWebToolsVS2013-KB4339279.exe'
2018-07-20T14:19:24.7702420Z 08e8 V Sandbox.cpp:66 DoSandboxCleanup: Deleted file='C:\Windows\ProPatches\Patches\AspNetWebFrameworksToolsVS2013-KB4339279.exe'
2018-07-20T14:19:24.7702420Z 08e8 V Sandbox.cpp:66 DoSandboxCleanup: Deleted file='C:\Windows\ProPatches\Patches\VMware-tools-10.3.0-8931395-x86_64.exe'
2018-07-20T14:19:24.7702420Z 08e8 V Sandbox.cpp:66 DoSandboxCleanup: Deleted file='C:\Windows\ProPatches\Patches\Wireshark-win64-2.6.2.exe'
2018-07-20T14:19:24.7702420Z 08e8 V Sandbox.cpp:66 DoSandboxCleanup: Deleted file='C:\Windows\ProPatches\Installation\InstallationSandbox#2018-07-20-T-02-11-19\3c197e11-9480-484e-815a-1432a898bbe2.sequence.txt'
2018-07-20T14:19:24.7702420Z 08e8 V Sandbox.cpp:66 DoSandboxCleanup: Deleted file='C:\Windows\ProPatches\Installation\InstallationSandbox#2018-07-20-T-02-11-19\3c197e11-9480-484e-815a-1432a898bbe2.tracker'
2018-07-20T14:19:24.7702420Z 08e8 V Sandbox.cpp:66 DoSandboxCleanup: Deleted file='C:\Windows\ProPatches\Installation\InstallationSandbox#2018-07-20-T-02-11-19\7z.dll'
2018-07-20T14:19:24.7702420Z 08e8 V Sandbox.cpp:66 DoSandboxCleanup: Deleted file='C:\Windows\ProPatches\Installation\InstallationSandbox#2018-07-20-T-02-11-19\cl5.exe'
2018-07-20T14:19:24.7702420Z 08e8 V Sandbox.cpp:66 DoSandboxCleanup: Deleted file='C:\Windows\ProPatches\Installation\InstallationSandbox#2018-07-20-T-02-11-19\deployPackage-70992.zip'
2018-07-20T14:19:24.7702420Z 08e8 I Sandbox.cpp:75 DoSandboxCleanup: Cannot delete filename='C:\Windows\ProPatches\Installation\InstallationSandbox#2018-07-20-T-02-11-19\dplyevts.dll', file in use. Scheduled delete at next bootup.
2018-07-20T14:19:24.7702420Z 08e8 V Sandbox.cpp:66 DoSandboxCleanup: Deleted file='C:\Windows\ProPatches\Installation\InstallationSandbox#2018-07-20-T-02-11-19\InstallPatches-70992.bat'
2018-07-20T14:19:24.7702420Z 08e8 V Sandbox.cpp:66 DoSandboxCleanup: Deleted file='C:\Windows\ProPatches\Installation\InstallationSandbox#2018-07-20-T-02-11-19\PostBootTasks.xml'
2018-07-20T14:19:24.7702420Z 08e8 V Sandbox.cpp:66 DoSandboxCleanup: Deleted file='C:\Windows\ProPatches\Installation\InstallationSandbox#2018-07-20-T-02-11-19\safereboot.exe'
2018-07-20T14:19:24.7702420Z 08e8 V Sandbox.cpp:66 DoSandboxCleanup: Deleted file='C:\Windows\ProPatches\Installation\InstallationSandbox#2018-07-20-T-02-11-19\safereboot64.exe'
2018-07-20T14:19:24.7702420Z 08e8 I Sandbox.cpp:75 DoSandboxCleanup: Cannot delete filename='C:\Windows\ProPatches\Installation\InstallationSandbox#2018-07-20-T-02-11-19\stdeploy.exe', file in use. Scheduled delete at next bootup.
2018-07-20T14:19:24.7702420Z 08e8 V Sandbox.cpp:66 DoSandboxCleanup: Deleted file='C:\Windows\ProPatches\Installation\InstallationSandbox#2018-07-20-T-02-11-19\stdeploy.exe.config'
2018-07-20T14:19:24.7858790Z 08e8 I Sandbox.cpp:75 DoSandboxCleanup: Cannot delete filename='C:\Windows\ProPatches\Installation\InstallationSandbox#2018-07-20-T-02-11-19\STDeployerCore.dll', file in use. Scheduled delete at next bootup.
2018-07-20T14:19:24.7858790Z 08e8 V Sandbox.cpp:66 DoSandboxCleanup: Deleted file='C:\Windows\ProPatches\Installation\InstallationSandbox#2018-07-20-T-02-11-19\ToDelete.txt'
2018-07-20T14:19:24.7858790Z 08e8 S DeployExeStates.cpp:418 Leaving STDeploy::CRelaunchedExecutionPackageDeploy::DoStatefulRemediateActions.
2018-07-20T14:19:24.7858790Z 08e8 I STDeploy.cpp:365 Current remediation phase completed. Process exit code: 0.
2018-07-20T14:19:24.7858790Z 08e8 S STDeploy.cpp:257 Leaving wmain.

Symptoms

Your Shavlik Protect/Ivanti Patch for Windows Servers agent performs a scan and finds a service pack missing, but does not attempt to deploy it.  Your logging will show entries like the following:

2018-07-20T17:25:32.1993466Z 3a84 I PatchWorkflowEngine.cpp:717 Found 1 missing service pack and 0 missing patch.

2018-07-20T17:25:32.1993466Z 3a84 I PatchWorkflowEngine.cpp:834 The scan did not find any missing patches or service packs to deploy.

Cause

There are a couple of reasons you may see this:

1. The patch task within your Agent Policy does not allow for the deployment of the missing service pack

A. The patch task does not have "Deploy service packs" checked

B. The patch task has "Deploy service packs" checked, but points to an SP group that does not include the missing service pack

2. The patch task is set up to deploy service packs (including the service pack in question), but the scan finds no missing patches

Resolution

1A - The patch task does not have "Deploy service packs" checked

• Set your patch task to deploy service packs by checking the "Deploy service packs" option

1B - The patch task has "Deploy service packs" checked, but points to an SP group that does not include the missing service pack

• Set your patch task to use either the "All SPs detected as missing" option or a Service Pack Group that contains the missing service pack

2 - The patch task is set up to deploy service packs (including the service pack in question), but the scan finds no missing patches

• As noted above, this is a known defect, but you can work around it by providing the scan with a consistently missing patch by editing the Patch Scan template the patch task uses to include the "Custom Actions" patch property:

Additional Information

How To: Automate Service Pack Deployment with Agents

Affected Product(s)

Shavlik Protect 9.x

Ivanti Patch for Windows Servers 9.3

Due to compliance with regulatory work, I would like to know if there is a way that Bulletin ID's IVA18-001 and MS12-A06 not show up on our scans as missing.

We are very aware of what they do, but we have to mitigate every month because they show up.

I cant do an exception list as I would have to produce that as evidence as well and why its being omitted.

Is there a way we can just not have IVA18-001 and MS12-A06 no show up as Patch Missing?

Thanks

Jerry Wetzel

wetzjj@jea.com

Guys,

Is it only me not seeing all fixes regarding Exchange patching mess up mentioned here:

Issue with July Updates for Windows on an Exchange Server – You Had Me At EHLO…

For example I am missing KB 4338816 for Window 2012 (not R2) but can see KB 4345425 listed in Patches View.

Any advise before I start rolling up them to my Exchange boxes?

I was wondering if it's possible to perform the following during an SCCM Task Sequence:

- Change an agent policy

- Run a patch task and install updates.

Is it as simple as just including command line arguments?

I am using Ivanti Patch for Windows, 9..0 Build 4510.

Thanks,

Today I was getting the message "Connected to a machine with the wrong hostname or domain name."  Turns out the real error was remote registry service not running (it was set to manual).  This was 9.1.0 build 4334 scanning a fresh build of Windows 7 pro.

Purpose

The purpose of this document is to show how to manually set proxy information in the configuration files for advanced issues caused by proxies.

Description

Shavlik Protect has a web service that Agents and the console itself talk to. The console talking to the service is all local traffic. You want to do two things on the Console machine so internal addresses do not run into issues. In your IE connection settings under LAN Settings, proxy settings, check bypass proxy for local addresses or you can add the console to the bypass specific address list under advanced if you do not want to bypass all local addresses. For the services you need to do a manual config file modification.

Resolution

1 - Modified the "ST.ServiceHost.exe.Config" file, adding the following section before the </configuration> tags:

<system.net>

<defaultProxy>

<proxy proxyaddress="http://**PROXY**:**PORT**" bypassonlocal="true" />

<bypasslist>

          <add address="127.0.0.1" />

<add address="**PROTECT_CONSOLE_NAME**" />

</bypasslist>

</defaultProxy>

</system.net>

2 - Modified the "ST.Protect.exe.config" file, adding the following section within the existing "system.net" tags:

<defaultProxy>

<proxy proxyaddress="http://**PROXY**:**PORT**" bypassonlocal="true" />

<bypasslist>

          <add address="127.0.0.1" />

<add address="**PROTECT_CONSOLE_NAME**" />

</bypasslist>

</defaultProxy>

Impact/Risks

Make sure to save a copy of your config file before modifying them - we recommend you to contact the Support to be assisted in that process.

If you edit the information in the config files as mentioned in step three, be aware that you have now hardcoded the information that Protect uses for your proxy. If you make changes on your network you may need to go back and edit these files again at a later date.

Affected Product(s)

Shavlik NetChk vProtect

VMware vCenter Protect

Shavlik Protect

Attachment

A set of configuration files are attached to this article in order to provide an example - having something concrete will help to see what is the outlook of those files after the modification.

We are looking to add another Console server but share the Database, we already have two of them configured this way. Is there a limit how many consoles we can add?

Purpose

This document will help you identify and correct a Patch for SCCM crash caused by missing prerequisite C++ x86 install.

This can be identified by looking in the Application event log:

Application: Microsoft.ConfigurationManagement.exe

Framework Version: v4.0.30319

Description: The process was terminated due to an unhandled exception.

Exception Info: System.DllNotFoundException

   at ST.Engines.NativeMethods.IsDigitallySignedBy(System.String, ST.Engines.Crypto.Signers, Boolean ByRef)

   at ST.Engines.Crypto.SignatureVerifier.IsSignedBy(System.String, ST.Engines.Crypto.Signers)

   at ST.Engines.Catalog.SingleFileDownload.HandleCompletedFile(System.Object, System.ComponentModel.AsyncCompletedEventArgs)

   at ST.Engines.Catalog.SingleFileDownload.ClientDownloadFileCompleted(System.Object, System.ComponentModel.AsyncCompletedEventArgs)

   at System.Net.WebClient.OnDownloadFileCompleted(System.ComponentModel.AsyncCompletedEventArgs)

   at System.Net.WebClient.DownloadFileOperationCompleted(System.Object)

   at System.Threading.QueueUserWorkItemCallback.WaitCallback_Context(System.Object)

   at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)

   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)

   at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()

   at System.Threading.ThreadPoolWorkQueue.Dispatch()

   at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback()

Resolution

Install Microsoft Software C++ 2015 Redistributable (x86) - 14.0.24215.

Affected Products

Patch for SCCM 2.3.x

Patch for SCCM 2.4.x

Overview

Support for Office 365 has been added to Shavlik Protect 9.2 and Ivanti Patch for Windows Servers 9.3.x

By default, Click-to-Run for Office 365 installations are automatically updated, but most administrators change the update source to control which updated builds are deployed and when they are deployed.  Now administrators can scan for and initiate these updates from Shavlik Protect 9.2 and Ivanti Patch for Windows Servers 9.3.x

Caveats

Office 365 patching:  The Office 365 patching process is different than other Microsoft patches.  Office 365 updates are installed by initiating the Microsoft Office 365 Click-to-Run update process which prompts the target machine to download the patch and install itself.

Where the Office 365 updates are downloaded from:  Updates are download from default source Microsoft Content Delivery Network (CDN) which requires a connection to the internet on the target machine.  Administrators who do not want their clients downloading from the internet can set their own download source.

• More information on setting a custom download source: Office Deployment Tool
  

Offline Virtual Machines: Due to the nature of this update, we do not support Office 365 patching on hosted offline virtual machines (VM).

Regarding Current Channel updates:  Most companies won't be using this channel in production due the higher update frequency. These updates interfere with line-of-business applications, add-ins and macros so time to test the updates is required any time there is an updated version of Office 365 ProPlus. Here is what is supported for customers who do use the Current Channel:

• Build 6868.2060 and higher are supported.  (Released on May 4th, 2016)
• Build 6769.2040 and lower are not supported.  (Released April 28th, 2016)
  

Regarding Deferred Channel updates:  This is more common channel customers will be using.  Updates for this channel are less frequent to allow time for testing.

• We support all versions of the deferred channel.

Additional Information

• Overview of Office 365 Channels: Overview of update channels for Office 365 ProPlus
• Build list numbers: https://technet.microsoft.com/en-us/library/mt592918.aspx
• GPO administrative templates for Office: Download Office 2016 Administrative Template files (ADMX/ADML) and Office Customization Tool from Official Microsoft Dow…

Affected Product(s)

Shavlik Protect 9.2

Protect SDK 9.2

Ivanti Patch for Windows Servers 9.3.x

Purpose

The purpose of this document is to outline the process for creating a custom patch, and to provide an example of how to create a custom patch using Patch for Windows.

Description

Create a Custom XML

1. Open the custom patch editor. Tools > Custom patch editor

2. Click on Create a new custom XML file.

Create a Custom Product

In this example, I create a product called X-Zip. You will need to provide a HKEY_LOCAL_MACHINE registry key path for the software as well as the corresponding information.

Create a Custom Bulletin

1. Click insert, then Add Bulletin (or right click Custom Bulletins > Add New Bulletin).

2. Give the bulletin a name. In this example I used HF01-001 because it is a hotfix.

3. Give the bulletin a title which typically this will be a description. In the summary portion provide any important information.

Create a Custom Patch

1. Click on Insert and add a custom patch (or right click Custom Patches > Add New Patch).

2. Give your patch a name. In this example I used the KB as the patch name.

3. Select the bulletin you created in the above steps.

4. Select the type of patch, and the severity.

5. From here you will add the detection information in the Scan Information tab.

6. You can also target a particular application or operation system using the targeting tab. In this case, since this update is only applicable to Windows Server 2008 SP2 and Vista SP2 I selected all corresponding operating systems.

7. On the deployment tab browse to the location of the patch and select it. Protect will automatically fill in the file size. Select any install switches that are required or desired for the patch deployment. In this case since the file is a .msu we need the /quiet switch.

Import/Validate your XML

1. Next you will need to validate your XML. There will be more information in the issue column if the validation fails.

2.  Save your custom XML, and then click the X to close the dialog box. This will prompt for you to import the custom patch.

3. Click import now.

4. When the below dialog box pops up select your Custom XML file and click OK. It goes through a second validation.

5. After validation the Import Patch Definitions process automatically updates the database with the latest definitions, including the newly created custom XML. If you created a custom product you should see it added as well.

Scan and deploy to your machines.

1. Once the definitions are updated proceed to scanning your machines.

2. Deploy the patch and verify it installs properly. You should now also be able to look up and view your custom patch using View > Patches in Protect.

Additional Information

Additional information about custom patch creation and use can be found in the Shavlik Help - Overview of the Custom Patch XML Process.

If the patch detects as missing correctly, but the .bat file never runs on the target system, see our knowledge base related to custom patch .bat file never completing:

Custom Patch Deployment .bat File Never Completes.

You can also find helpful training on this topic here Patch for Windows

Affected Product(s)

Ivanti Patch for Windows Servers

Shavlik Protect 9.x