The following table lists the new features that have
upgrade impact. Before you upgrade the ESM and
Traps to release 4.2, make sure you understand the changes
that will occur in the configuration.
Feature
Upgrade Considerations
ESM Upgrade Considerations
You can upgrade to ESM 4.2 from any ESM
3.4 or any later release.
Traps Upgrade Considerations
Beta participation—If you
participated in the Traps beta program, you cannot upgrade from
the Traps 4.2 beta version to a Traps 4.2 release.
Windows XP, Windows Server 2003, Windows Server 2008,
and Windows Vista—Action rules are not supported to upgrade
the Traps agent on these operating systems. Use GPO, SCCM, or another
alternate method of deploying the Traps software.
Other Windows operating systems—Due to the Digital
Signature requirements for Traps agent 4.2.1 and later releases,
you must first upgrade Traps to Traps 4.1.5 or 4.2.0 before you
can use action rules to upgrade to 4.2.2 or a later release. You
can also use the MSI installer to manually upgrade Traps to Traps
4.2.2 or a later release.
Traps 4.1.5-h1 is a hotfix
release to support macOS 10.14 and does not contain any updates
for Windows agents. To upgrade Windows agents to Traps 4.2.1, you
must first upgrade the Traps agents to the non-hotfix release package ClientUpgradePackage-4.1.5.37365.zip (release
date: 07/28/2018) or to the 4.2.0 release using the upgrade package ClientUpgradePackage-4.2.0.36348.zip (release
date: 06/25/2018).
Mac operating systems—To upgrade Mac agents to Traps
4.2.2 or a later release, you can upgrade from any earlier version
including the Traps 4.1.5 hotfix release package ClientUpgradePackage-4.1.5.37365-h1.zip (release
date: 10/03/2018).
To use Traps on macOS 10.14, you
must install the ESM and Traps versions before upgrading the operating system:
Upgrade the ESM to 4.2.1-h2 or a later release.
Upgrade the Traps agent to Traps 4.2.1-h3 or a later
release using one-time action rules or the deployment method of
your choice.
Upgrade the Mac endpoint to macOS 10.14.
If
you upgraded the operating system or Traps agent in a different
order, you must uninstall and reinstall the Traps agent on the endpoint
either using a third-party deployment tool such as JAMF or manually.
