Repeating Updates

“As we begin to install the Ivanti EPM suite in some of our smaller environments, the need arose to provide support / insight in regards to patching methodologies.”

posted Jan 3, 2018, 10:33

When diagnosing potential update issues u may encounter situations where the update is in a repetitive state (installing / prompting for restart).  This can be due to the following:

• 2359302 - This means the update is already installed.

• 2149842967 - This means the update is not applicable.

• Unexpected error in custom script source. See agent log for details - Indicative of a client side issue such as PowerShell, security settings or group policy.  In the example below we see that PowerShell failed on execution.  PowerShell is used as a means of detection in some cases.  So if it cant start or encounters issues then the process will fail but show DETECTED as noted in (https://community.ivanti.com/docs/DOC-62086 / In all cases where we cannot get a proper detection from our scripts Ivanti errs on the side of caution and will throw a DETECTED and will try and install the patch just to be safe.)

Error 2 is typically a path issue.

A review of the detection process reveals that Powershell is being used:

Copying the Detection Script and executing on the client can also assist with identification of the problem.

Updating WinRM (more to come) allowed this client to proceed without error.  I suspect it is path related.  A re-scan of the client with the Current group will now show the log without error as shown below.

Compared to

Note - Incorrectly assigned product version - This will require a clone of the original and creation of a custom definition to address the incorrect assignment.