Install, Uninstall, and Upgrade Endpoint Privilege Management for Windows

Requirements

For more information about the installation requirements, see Endpoint Privilege Management Release Notes.

Frequently Asked Questions

Can I Install the 32-bit Client on a 64-bit Endpoint?

No. The 32-bit client can only be installed on 32-bit endpoints.

Can I Install the 32-bit Endpoint Privilege Management Policy Editor on a 64-bit Endpoint?

Yes. The 32-bit Endpoint Privilege Management Policy Editor can be installed on 64-bit endpoints if required.

Do I Need to Install the Endpoint Privilege Management for Windows and the Endpoint Privilege Management Policy Editor Together?

For standalone installations, you must install both Endpoint Privilege Management for Windows and the Endpoint Privilege Management Policy Editor. We also recommend that Endpoint Privilege Management for Windows and the Endpoint Privilege Management Policy Editor be installed together during evaluation, to simplify the evaluation process.

For larger deployments, there is no requirement to install the Endpoint Privilege Management Policy Editor on endpoints.

What Distribution Mechanisms Do You Support?

Endpoint Privilege Management for Windows can be deployed using any third party software which supports the deployment of MSI and/or Executable files, such as Microsoft Active Directory, Microsoft SMS/SCCM, and McAfee ePolicy Orchestrator (ePO).

For silent installations and advanced installations (such as CERT_MODE and EPOMODE), the third party deployment software must also support the use of command line options.

What is the Update Priority for Endpoint Privilege Management GPO Edition?

The update priority for Endpoint Privilege Management GPO edition is as follows:

  1. Event Collector
  2. Reporting Database
  3. Client
  4. Management Console
  5. Policy

Can Different Versions of the Agent Coexist?

Yes. In some estates, a range of different agent versions can exist together. Here are a couple of scenarios where this might occur:

  • An older version of the agent might be needed for an older OS. For example, agent version 22.5 does not support Windows 7, so an earlier version is required.
  • A company might create a pilot group to run a newer version for agent testing while the rest of the estate runs the older version.

We always retain backwards compatibility for the policies when adding new features. This allows you to configure and use new features in your policies and use them with newer agents. On any older agents in your estate the new features will be ignored and will not affect the function of the agents.