.Loading..Loading.

Installing on the Core and Rollup Core

Because Alternate Data Streams (ADS) may block files on Windows systems, it is recommended that you extract the patch on the machine you are going to install it on.

Steps

1. Disable any services on other machines that interact with the Core Server
2. Double-click on the self-extracting executable and extract it
3. Extract the files for the Core patch
4. From the extracted files, run Setup.exe
5. When Setup completes, reboot the machine if a reboot is required
6. After applying the patch, you may need to re-activate your Core Server using the Core Server Activation Utility
7. Restart any services stopped in Step 1

Note: The installer included with this release writes a detailed log that can be used to help troubleshoot installation problems. After running setup.exe from the patch, the log is located in the \ManagementSuite\log folder.

Installing on Remote Consoles

A Remote Console is any machine that is not the Core Server and has the Ivanti Endpoint Manager Console installed. Console Machines need to be updated to the same version as the core server to be able to connect to the updated Core Server and Database.

Because Alternate Data Streams (ADS) may block files on Windows systems, it is recommended that you extract the patch on the machine you are going to install it on.

Steps

1. Close the Console
2. Double-click on the self-extracting executable and extract it
3. Extract the files for the appropriate patch
4. From the extracted files, run Setup.exe
5. When Setup completes, reboot the machine if a reboot is required

Note: The installer included with this release writes a detailed log that can be used to help troubleshoot installation problems. After running setup.exe from the patch, the log is located in the \ManagementSuite\log folder.

Updating the Agent

The patch should be installed on the Core Server before updating Agents

Use one of the following methods to re-deploy the agent once the patch has been applied to the Core or to apply the patch manually.

Methods of agent deployment

• New with 2022 SU3: The Engine Based Agent (EBA).
  • The Engine Based Agent (EBA) is enabled along side the traditional agent install on Windows using wscfg32.
  • Agent-push uses wscfg32 by default but is configurable using a registry key on the core server.
  • For more information see this Community Article: Ivanti EPM Engine Based Agent Information
• Manual: Map a drive to \\Coreserver\ldlogon and run 'wscfg32.exe -f'
  This is used for single client installs and testing
• Push: Schedule a push of the full agent
• Self-Contained EXE: Create an EXE that can be installed
• Advance Agent: This is a two stage process. The Advance Agent consists of a small MSI and a self-contained EXE. The MSI is deploy to the client and then the MSI downloads and installs the EXE. This allows for bandwidth friendly downloads.

For more information on agent configuration and deployment see Agent Deployment for Ivanti Endpoint Manager and Endpoint Security

Manual installation of the client patch

The client patch is no longer available. For more information see this Community Article:
Ivanti Community Doc - EPM SU Client Patch

Updating the Agent With Patch Manager

Agent updates are no longer supported using Patch Manager. For more information see this Community Article:
Ivanti Community Doc - EPM SU Client Patch