Get Quote Free Trial
System Update Center

ManageEngine ADManager Plus Service Packs

Access the latest enhancements, security patches, and feature upgrades for your ADManager Plus deployment. Ensure your Active Directory management remains secure and compliant.

View Downloads
Server Update Process

Available ADManager Plus Service Packs

Find your current build number and verify the correct PPM file before executing your environment upgrade.

If your build number is Update to build number SHA256 checksum hash value
8002 through 8036 Download Update to 8040 e2d80a81eab9a21a50c0b9a3941442b5edd882e4c99ecef754488ac43961a760
7222 through 8001 Download Update to 8002 be11d4a23045b78b739b84cb9232bd7adfb346765977f052794f6206927a673a
7203 through 7221 Download Update to 7222 b7de07c6d0e623f1f7235c0b4ba75dd2b9f251e9923aed51605667210f1f010f
7102 through 7202 Download Update to 7203 dfd47a275d9759a8b229db28100d043a6155ee88934a569b6de12247c91d9869
7000 through 7101 Download Update to 7102 4763c9e1e5a0fafe10b0d921ed238b9c91d64a19356363596b176f98040c6894

Service Pack Installation Steps

1. Stop the ADManager Plus Service

If the product runs as an application: Navigate to Start → All Programs → ADManager Plus → Stop ADManager Plus.

If the product runs as a Windows service: Go to Start → Run, type services.msc, locate ManageEngine ADManager Plus, and safely halt the service.

Execute the stopDB.bat file located in your <ADManagerPlusHome>in directory.

2. Complete a System Backup

Secure your current implementation by zipping the entire contents of the <ADManagerPlusHome> directory. If operating in a virtualized realm, create a complete snapshot of the VM.

Note: If utilizing Microsoft SQL Server as the backend database, manually connect to that precise node and initialize a full remote database backup too.

3. Execute the Update Manager Tool

Open your Command Prompt under explicit Run as Administrator privileges (vital for UAC environments) and navigate to the <ADManagerPlusHome>in framework director. From there, execute the localized UpdateManager.bat script.

4. Process Your Service Pack (PPM File)

From the Update Manager UI, click Browse and trace the local path to the recently downloaded PPM file explicitly mapped to your build trajectory. Click Install to execute the injection.

Because active backend metadata transformation occurs at this stage, the installer may take heavy allocation time depending on the environmental complexity. Never arbitrarily terminate the migration cycle prematurely.

For installations targeting build 7222 and later: If the system presents a "Signature does not match" condition, verify your repository dependencies by importing a valid updated ManageEngine system certificate prior to finalizing installation steps.

5. Reinitialize and Launch

Following successful confirmation on-screen, properly invoke the Close → Exit logic to decouple the wizard. Once free, you may safely reboot the underlying application or Windows master service parameters to resume normal processing functionality.

How to update ADManager Plus when High Availability (HA) is enabled?

1. Stop ADManager Plus

Stop ADManager Plus in both the primary and secondary servers.

In the secondary server, navigate to services.msc. Make sure the ADManager Plus service is stopped and the Startup Type is changed to disabled.

Ensure that the instance in the secondary server is accessible from the primary server. To verify the access rights, follow these steps:

  • Log on to your secondary server.
  • Navigate to the installation directory of ADManager Plus.
  • Right-click the ADManager Plus folder and go to Properties > Sharing. Check if ManageEngineADManagerPlus is listed below Network Path.
  • If yes, go to the Security tab and verify if the service account configured to run the ADManager Plus service has Full control permission over the ADManager Plus installation folder.
  • If not, click Share, add the service account to the list, and grant Read/Write permission. Once done, go to Advanced Sharing > Add, enter ManageEngineADManagerPlus in the Share name field, and click Apply.

2. Back up ADManager Plus' folder and database

In both primary and secondary servers, back up ADManager Plus by zipping the contents of the <ADManagerPlusHome> directory or, if it's a VM, by taking a snapshot of the server.

Note: If you are using Microsoft SQL as ADManager Plus' backend database, connect to that server and back that up as well.

3. Apply service pack in the primary server

In the primary server, start Command Prompt as an administrator, navigate to the <ADManagerPlusHome>\bin directory, and execute the UpdateManager.bat file.

Next, browse and select the PPM file (service pack file). Click Install.

Note: Applying the service pack in the primary server will automatically update the ADManager Plus version in the secondary server as well.

4. Start ADManager Plus

Once the service pack installation is successful, start ADManager Plus in the primary server first, and then after a few minutes, in the secondary server.

In the secondary server, navigate to services.msc and change the Startup Type to automatic.

How do I update ADManager Plus when Load Balancing is enabled?

1. Stop ADManager Plus

Stop ADManager Plus in both the primary and secondary nodes.

2. Back up the ADManager Plus folder and database

In both the primary and secondary nodes, back up ADManager Plus by zipping the contents of the <ADManagerPlusHome> directory or, if it's a VM, by taking a snapshot of the node.

Note: If you are using Microsoft SQL as ADManager Plus' back-end database, connect to that node and back it up as well.

3. Apply the service pack in the primary node

Apply the service pack in the primary node. After successfully applying it in the primary node, do not start the ADManager Plus service. Continue applying the service pack in all the secondary nodes one by one.

4. Start ADManager Plus

Once the service pack installation is successful across all nodes, start ADManager Plus in the primary node first, and then after a few minutes, in each of the secondary nodes.