Direct Inward Dialing: +1 408 916 9393
Important: We strongly recommend you to take backups before applying the service pack. This helps prevent accidental loss of data. Steps to update builds
If High Availability (HA) is enabled, proceed with these steps after applying the service pack.
Alternatively, if Load Balancer (LB) is enabled, follow these steps.
Service Pack install order for build
| Steps | SHA256 Checksum hash value |
|---|
| If your build number is | Update to build number | SHA256 Checksum hash value |
|---|---|---|
| 8002 through 8042 | ||
| 7222 through 8001 | ||
| 7203 through 7221 | ||
| 7102 through 7202 | ||
| 7000 through 7101 | ||
| Builds older than 7000 | ||
If the product runs as an application, click Start > All Programs > ADManager Plus > Stop ADManager Plus.
If the product runs as a Windows service, click Start > Run. Type services.msc and stop ManageEngine ADManager Plus.
<ADManagerPlusHome>\bin to stop the database.When using the built-in PostgreSQL database:
Run the initPgsql.bat file located in <ADManagerPlusHome>\bin from the Command Prompt using the privileges of a domain or local admin account.
Run the backupDB.bat file located in <ADManagerPlusHome>\bin directory.
Back up ADManager Plus by zipping the contents of the <ADManagerPlusHome> directory.
Note:
Open the Command Prompt and execute the UpdateManager.bat file under the <ADManagerPlusHome>\bin directory.
Click Browse and select the service pack file that you have downloaded.
Click Install. Depending on the amount of data to be migrated, the installation procedure may take a few minutes. Please do not terminate this process prematurely.
Having problems? Troubleshoot here
Once the service pack is installed, click Close and then Exit to quit the Update Manager.
If the product runs as an application, click Start > All Programs > ADManager Plus > Start ADManager Plus.
If the product runs as a Windows service, click Start > Run. Type services.msc, and in the window that opens, Start ManageEngine 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 the steps provided below.
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 whether ManageEngineADManagerPlus appears under 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.
In both primary and secondary servers, back up ADManager Plus by zipping the contents of the <ADManagerPlusHome> directory. If ADManager Plus is running on a virtual machine, you can take a snapshot of the VM instead.
Start Command Prompt as an administrator, navigate to the <ADManagerPlusHome>\bin directory and execute the UpdateManager.bat file.
Click Browse and select the service pack file that you have downloaded.
Click Install.
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. If ADManager Plus is running on a virtual machine, you can take a snapshot of the VM instead.
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.
Once the service pack installation is successful, start ADManager Plus in the primary node first, and then after a few minutes, in each of the secondary nodes.
Reason: The server is running a significantly older version of ADManager Plus. Your installation will need updates installed during a few subsequent (major) versions of the product before it will be ready for the latest version.
Fix: Download and install every major version of ADManager Plus until the latest one.
Steps:
So, for instance, if you are running version 6013, update to version 6100, then to version 6200, and then finally to version 6207 (the latest build). You can find these patches on the ManageEngine site.
Reason: The server is running an older version of ADManager Plus (before version 6201) and cannot connect to the ManageEngine site (blocked port, firewall restrictions, no internet connection, etc). The Update Manager automatically imports the certificate when it is able to connect to the ManageEngine site. However, when it cannot do so, you will need to import the certificate manually.
Fix: Import the certificate manually.
Steps:
Run the UpdateManager.bat file located in <ADManagerPlusHome>\bin (by default: C:\Program Files\ManageEngine\ADManager Plus\bin) from the Command Prompt using the privileges of a domain or local admin account (refer to the requirements for running the initPgsql.bat file mentioned above).
Click Browse and select the service pack file ManageEngine_ADManager_Plus_x_x_SP-x_x_x.ppm that you have downloaded.
Log in to the ADManager Plus web client, and click the "License" link in the top pane.
You will find the build number mentioned below the version number. This indicates the currently installed build of ADManager Plus.
