Access the latest enhancements, security patches, and feature upgrades for your ADManager Plus deployment. Ensure your Active Directory management remains secure and compliant.
Find your current build number and verify the correct PPM file before executing your environment upgrade.
| Current build | Upgrade path to the latest build | SHA256 Value |
|---|---|---|
| 8002 through 8042 | - Install the service pack to move to build 8043. | 8c87c8a9bdfa46babdb9bf1c65dff87274dd82c6c73f671f85e71233dc239503 |
| 7222 through 8001 | - Install the service pack to move to build 8002. | be11d4a23045b78b739b84cb9232bd7adfb346765977f052794f6206927a673a |
| 7203 through 7221 | - Install the service pack to move to build 7222. | b7de07c6d0e623f1f7235c0b4ba75dd2b9f251e9923aed51605667210f1f010f |
| 7102 through 7202 | - Install the service pack to move to build 7203. | dfd47a275d9759a8b229db28100d043a6155ee88934a569b6de12247c91d9869 |
| 7000 through 7101 | - Install the service pack to move to build 7102. | 4763c9e1e5a0fafe10b0d921ed238b9c91d64a19356363596b176f98040c6894 |
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.
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.
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.
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.
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.
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:
ManageEngineADManagerPlus is listed below Network Path.ManageEngineADManagerPlus in the Share name field, and click Apply.
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.
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.
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.
Stop ADManager Plus in both the primary and secondary nodes.
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.
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.
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.