Any input in that, I have done POC for Ivanti Patch for Windows and Microsoft SCCM both, I found Ivanti as light,sleek and easy to use. Any Pro's and Con's will be helpful.

Description

During setup of a patch deployment within Protect you will eventually get to the "Deployment Configuration" screen (Figure 1). The deployment templates that you already have configured can be modified while you are at this screen. However, it is important to know the difference between using the "Edit" button vs. the "Change" button.

• The "Edit" button on the upper right will make permanent changes to the chosen template. You will not be able to modify built-in templates from this option.
• The "Change" button on the lower right will make temporary changes to the chosen template. The temporary template will only be used for this deployment. You will also see "(Temporary)" in the name of the chose template.

Figure 1: Deployment Configuration Screen showing a Temporary template currently chosen.

Affected Product(s)

Shavlik Protect 9.x

Purpose

The purpose of this document is to explain what causes deployments to stay at the status of 'Files Copied' but never install any patches after all files are copied to the target machines.

Symptoms

Deployment tracker will show both the machine status and the patch status as Files Copied.

Cause

The deployment was configured to be a copy only operation. When configuring the deployment, the 'Execute deployment package' option was selected as 'Do not schedule execution'.

This is further validated by looking at the View Deploy Rules in the deployment tracker. This will show the deployment type as 'Copy files only and do no execute deployment'.

Resolution

To ensure that the deployment installs the patches, make sure to select the Install the patch(es) option and configure the deployment to either install the patches 'Immediately after staging' or scheduled for a later time or next reboot.

Additional Information

How To: Schedule and Configure a Deployment in Patch for Windows Servers 9.3

Affected Product

Ivanti Patch for Windows Servers 9.3

Symptoms

Protect is detecting a Patch that should not be detected as missing.

Resolution

NOTE: Before performing the following, please update to the latest XML data by going to Help > Refresh Files, close and reopen Shavlik Protect and then perform another scan against the machine(s) using a Security Patch or WUScan Template. The root cause of the issue may stem from custom filtering in a Scan Template or could already be fixed in a later XML release.

From The Protect Console:

1. Click on Results tab.

2. Choose the most recent scan containing the specific patch.

3. Click on the machine containing the specific patch.

4. Click on the specific patch.

5. View why Protect detects the patch as missing (Patch Information Tab).

6. Click on the linked Qnumber to be taking to documentation regarding this patch. Most of the time this will include the detection logic.

7. Browse to the location referenced in step 5 to verify the information found in step 5 and 6.

See below for more information:

Also note the Downloaded File name.

On the Target:

Browse to C:\Windows\ProPatches\Patches and find the specific patch. If you have previously deployed this patch and it failed, manually try to run the patch.

Take any screenshots of any errors such as the one below.

Information to Send to Support

If you experience these errors, please create a support case at support.shavlik.com or by calling into support.

NOTE: If you choose to call into support, please gather this information before calling in: Obtaining Support

Gather the following information:

1. Before doing the following, please download the latest XML data by going to Help > Refresh Files.
2. The Bulletin ID & Qnumber of the patch in question. This information can be found in Step 4 above.
3. Clear your logs, and do a rescan and/or deployment.then gather the log. Please do this by following this guide for console logs: How To: Collect Shavlik Protect - Ivanti Patch for Windows Servers console, patch deployment and agent logs
   
4. A DPDTrace gives more information on how Protect detects certain patches. Please gather a DPD trace on the target machine by following this guide: DPDTrace command line logging tool used for patch detection issues
5. Screenshots from Step 5 from the console, Step 7 from the target and if applicable, the error when the patch is manually installed.

Include the following registry exports from the same target machine that ran the DPDTrace.  This will not only save time, it will also greatly increase our chances of determining the root cause of the detection issue and correcting it:

NOTE: This document has a batch file that retrieves the needed registry keys: Batch File for Obtaining Registry Exports for Detection Related Issues

• HKLM\SOFTWARE\WOW6432\Microsoft\Windows\CurrentVersion\Uninstall

• HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall

• HKLM\SOFTWARE\Classes\Installer\Products

• HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages

• HKLM\SOFTWARE\Classes\Installer\Patches

Please zip all files into one archive file before emailing or attaching them to the case.

NOTE: You will not be able to email the registry keys to the case as .reg files. They must be either uploaded to the case through the support portal or changed into .txt files.

Affected Product(s)

Shavlik Protect 9.x

Purpose

This document explains how to transfer data and patch files manually from a Shavlik Protect Console on a Internet facing network, to a Protect Console on a Secure network with no internet connection using Write Once/Read Only Media .  This procedure is used when data from re-writable media is not allowed to be copied to machines in a secure zone.

Procedure

Setup a separate Distribution Share for Internet Connected and Offline Protect Consoles as a data file and patch repository

• Setup a separate shared folder for each security zone for the Internet Connected and offline facing consoles that is accessible from the console to be used as the path for Distribution Server configuration.
• Make sure that patch definitions downloads are scheduled so that current patch definitions are synced to the Distribution Server share
• Configure a Distribution Server on each console using the document, Configuring Authenticated SMB Distribution Servers
  
• Configure the Distribution Server on the Connected Protect Console to Sync All engines, definitions, and patch downloads.
• Under Tools > Operations > Downloads on the Secure Network Protect Console, select the Specific Distribution Server for the "Definition download source" and the "Patch and Service Pack" download source.

Copy files to a DVD to be delivered to the Protect Console on the Secure Network 

• Sync data files and patches to the Distribution Server share manually using information the document How To: Manually Synchronize Distribution Servers
• Burn contents of the Distribution Server Share from the Internet Connected Console to a write one DVD-R
• Walk the DVD-R to the Secure non-internet facing network and copy the contents to the Distribution Share on the Secure Network Protect Console

Using the copied files

After the data files and patches have been downloaded to the Secure Network Protect Console Distribution share, data files will be transferred to the correct folder when files are refreshed automatically during a scan or manually using Help > Refresh files.  Patch downloads will go to the Downloads folder when the console requests a patch download during deployment.

Additional Information

This Procedure is simplified by using the existing Download folder as specified under Tools > Operations > Downloads as the Distribution Share for the internet console.  This eliminates the need to sync the Patch downloads.  You would only need to sync the Core engines/definitions and Threat engines/definitions if you are using agents.

Affected Product(s)

Protect 9.X

Hi everyone, we have recently implemented PWS 2018 and deployed agents to the end user laptops. A lot of the end users are now complaining that their laptops are freezing before the welcome screen, after the welcome screen and after windows loaded at desktop screen. We have disabled Asset Scan on the agent, and Patch Scan is scheduled to be on Fridays. Because of the freezing, we have to uninstall the agents from the users' laptops. Just wondering if anybody in the community have encountered similar situation. The end user's os are win 10 and win 7.

I am having an issue with schedules kicking off a week early.  See screenshot.  My schedule is set to 3rd Tuesday but it ran last night and it scheduled to run again next week.

This is the second occurrence this has happened that i have noticed.  It may have been happening before but I only noticed it once I started running check-reboot scripts in tandem.  Last time was when the 1st of the month was Thursday and it affected my (3rd Tuesday + 2 Day) schedules.

Overview

This document provides a list of required URL addresses for Shavlik Protect and Ivanti Patch for Windows Servers to allow:

• Patch executable download.
• Patch content definition download.
• Online license activation or license refresh.
  
• Home page RSS feed.
  
• Product check for update.
  

URL List

The following URLs may be used to download updates and must allowed through firewalls, proxies and web filters:

Additional Information

• To obtain the IP for vendor sites you can ping the vendor site or contact the vendor to obtain this information. We are unable to provide a list of IP addresses due to the varied dynamic IP addresses being used by the vendors. It may be easier to create an exception for an entire domain rather than entering all specific URLs, you can usually do so by entering the exception in this format:
  • *.domain.com.

Affected Product(s)

Shavlik Protect

Ivanti Patch for Windows Servers

The event logs clearly show the command line execution of patches, but are they being executed from an elevated command prompt?

Reason we are asking is because several of the Exchange Security patches note install failures if this is not done:

"When you try to manually install this security update in "normal mode" (not running the update as an administrator) by double-clicking the update file (.msp), some files are not correctly updated. When this issue occurs, you do not receive an error message or any indication that the security update is not correctly installed. Also, Outlook Web Access (OWA) and the Exchange Control Panel (ECP) may stop working. This issue occurs on servers that are using user account control (UAC). The issue occurs because the security update does not correctly stop certain Exchange-related services. To avoid this issue, run the security update from an elevated command prompt. For more information about how to open an elevated command prompt, visit the following Microsoft webpage: Start a Command Prompt as an Administrator"

-Keith

Hi all,

Just wondering if anyone is aware of a way to Add a Baseline and Exception Patch group to a Scan template.

I have a Number of baselines in play with a customer but also have a few KB's I want to keep off a Machine group. Is there a known way to make this happen or is there a place to request a feature like this.

Apologies if this is in the wrong area, relatively new to Ivanti Forum so will find my way Eventually.

Thanks in advance for any response.

Overview

You receive this error when scanning Error 106 when scanning a Windows 10 machine after upgrading to 1709 or newer version.  Microsoft changed the way Windows 1709+ handles SPN's for CIFS.

Microsoft network server: Server SPN target name validation level

Cause

Starting in Windows 10 build 1709, how Windows handles SPN's for CIFS: Microsoft network server: Server SPN target name validation level

By default this is set to Off in Windows, however customers that have configurations for higher security such as CIS they will experience this issue.

Resolution

Microsoft has released an update addressing that issue: KB4343909An alternate fix would be to change the Microsoft network server: Server SPN target name validation level security policy setting to Off.

Affected Product

Shavlik Protect 9.2.x

Ivanti Patch for Windows Server 9.x

Hi.  I'm looking to complete an Ivanti setup leveraging a Protect Master rollup console access to the internet, console w/o internet access, and a distribution server.

Is there a preference on where the DB needs to reside?  On the rollup console or additional console?

Where in the options do you point, assign, or how does Ivanti distinguish between the two?

Thanks.

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.

I'm after some help please,

All of our RDS and citrix servers failed to patch last night see screenshot below

I've tried checking STDeploy.log but as you can see from the date modified below it hasn't been updated

Any suggestions on where to check please ? Many Thanks

Symptoms

When your deployment options are set to take a pre-deploy snapshot of a hosted VM, the deployment fails with error "Pre-deploy snapshot failed":

Deployment logs show the following error:

HostedVirtualDeployment.cs:555|VMware.Vim.VimException: Current license or ESXi version prohibits execution of the requested operation. ---> System.Web.Services.Protocols.SoapException: Current license or ESXi version prohibits execution of the requested operation.

Cause

All versions of ESXi licensing allow you to take manual snapshots.  However, the free version of ESXi has locked APIs, so with that free version you are unable to initiate that task remotely even though you can take snapshots manually.

Resolution

The only way to unlock the ESXi APIs is to purchase licensing for it.  As of the publication of this doc, any level of paid licensing will unlock the APIs, so any license tier will suffice for this operation.

Affected Products

Shavlik Protect 9.2.x

Ivanti Patch for Windows Servers 9.3.x

Symptoms

• Agents attempting to patch machines fail.
• The agents are unable to find and download the .MSU patch files from HTTP-configured distribution servers.
• On the UI of the target machine in the Patch tab, you see the error:
  
  Cannot download patch

Cause

This issue caused by the IIS MIME type extension for MSU not being configured correctly.

Resolution

To resolve this issue, configure the MIME Type extension for MSU on the IIS Server.

Note: If you are not using the vCenter vProtect Console patch repository, support for configuration of the the HTTP/HTTPS distribution server is not provided by VMware.

• On Windows 2003 server:
  1. On the core server, launch Internet Information Services Manager.
  2. Navigate to the Default Web Site.
  3. Right-click the Default Web Site and select Properties.
  4. Click the HTTP Headers tab, then click MIME Types.
  5. Click New.
  6. Enter MSU for the file extension, and application/octet-stream for the MIME Type.
  7. Restart IIS by clicking Start> Run and entering iisreset.
     
     
• On Windows 2008 Server:
  1. On the core server, Launch Internet Information Services Manager.
  2. Navigate to the Default Web Site and select it.
  3. Double-click MIME Types in the middle panel.
  4. Click Add.
  5. Enter MSU for the file extension, and application/octet-stream for the MIME Type.
  6. Restart IIS by clicking Start> Run and entering iisreset.

Products

Shavlik NetChk Protect

Shavlik NetChk vProtect

Product Versions

Shavlik NetChk Protect 7.8.1340

Shavlik NetChk Protect 7.8.1388

Shavlik NetChk Protect 7.8.1392

Shavlik NetChk vProtect 7.8.1340

Shavlik NetChk vProtect 7.8.1388

Shavlik NetChk vProtect 7.8.1392

Symptoms

When installing the latest version of 7-Zip, vulnerability scans still report that older versions are installed and vulnerable.

Cause

The 7-Zip installer does not actively remove registry keys from older versions.  The vulnerability is a false positive since the executable has been upgraded, but the registry keys from those previous versions trigger the detection.

Resolution

We currently have a request posted on the 7-Zip support forum for the vendor to address this in future installers.  That thread is located here:

https://sourceforge.net/p/sevenzip/discussion/45797/thread/c6f74111/

This doc will be updated as that request reaches a resolution.

I noticed that the automated patch content update mechanism is no longer functioning on our Ivanti PFW server for more then a month.or so.

I tried to find the option to manually run an update of the patch content, but could not find it.

Searching for "how to manually update the patch content" did not pop up any usefull solutions.

I guess that updating the "update database" with the latest available patches should have a manual option to run this.

For now I rebooted the server and noticed that the patch content was now successfully updated.

Guido

Hi All wondering if anyone has came across this issue, (Support case raised)

Ivanti Product Fully Licensed:

Licensed Capabilities

--------------------

Maintenance and Data Subscription expires:  24/06/2019 01:00

## ISSUE ##

This is a New installation of Ivanti Patch for windows,

Once installed I was able to add 2 ESXI Vcenters, populate machine groups with discovered machines.

Came back a week later to add internet proxy details so I could start testing deployment and patching levels of the estate and I am met with:

I then removed one of the hosts and re-added and I get

Credentials have been confirmed to be valid and working,

Successful Connection from Ivanti VM to Host via SSH:

Can Ping the hosts successfully:

Can telnet (443) from Ivanti VM to hosts:

I have also completed a successful Refresh of all files.

Again the Credentials being used have already successfully added these hosts to Ivanti last week, and I can log in with these credentials to full admin level.

I have been unable to find any details of this issue anywhere else which has been successfully resolved.

Thanks Malachy

Hello,

we organized our Workstations based ob departments from our company.  So we basicly created multiple machine groups wich are linked with OUs from our domain.

Now we are facing the followin issure:

We are not able to add systems which are currently offline/powered off.

When we try for example an enerygy status scan we can see the new System in the result list (with the status - system not found).
But when we change the view to the machine groups we notify that the system not added to the group.

So what can we do to add offline/powered off machines to its machine groups without powering on.