Direct Inward Dialing: +1 408 916 9890
Ensure that the minimum hardware and software requirements listed below are met before installing ADManager Plus.
Following are the hardware requirements for deploying ADManager Plus:
Hardware | Minimum | Recommended |
Processor | 1.6 GHz or faster | 2.13 GHz or faster |
RAM | 1GB* (1.5GB if it is a virtual machine) | 4GB* (8GB if it is a virtual machine) |
Disk Space | Hard disk space: 4GB* | 10GB* |
* Based on the number of scheduled reports and automations running in parallel, additional space might be needed. Learn more.
The following section outlines the memory and RAM requirements for Active Directory reporting and management.
Following are the memory and RAM requirements for performing Active Directory management tasks using ADManager Plus:
Number of objects created or modified per hour | RAM required (MB) | HDD required (GB) | Bandwidth (Mbps) |
1,000 | 256 | 4 | 10 |
5,000 | 512 | 8 | 10 |
10,000 | 1024 | 30 | 10 |
20,000 | 2048 | 50 | 50 |
50,000 | 8096 | 50 | 50 |
100,000 | 8096 | 50 | 50 |
This section outlines the memory and RAM requirements for Active Directory reporting. These specifications consider all report generation activities, including reports generated on demand, through the scheduler, and by automations, for performing management tasks.
Number of objects in the domain | RAM required (MB) | HDD required (GB) | Bandwidth (Mbps) |
1,000 | 256 | 4 | 10 |
5,000 | 512 | 8 | 10 |
10,000 | 1024 | 30 | 10 |
20,000 | 2048 | 50 | 50 |
50,000 | 8096 | 50 | 50 |
100,000 | 8096 | 50 | 50 |
Following are the software requirements for deploying ADManager Plus:
ADManager Plus can be installed in any one of the following Microsoft Windows operating system versions:
ManageEngine ADManager Plus requires one of the following browsers to be installed on the system.
* Supports IE8 as well
Note:
The following databases are supported by ADManager Plus:
Note: If your ADManager Plus server has MySQL installed, we recommend migrating to PostgreSQL. Click here for database migration steps.
Port Number | Protocol | Purpose |
8080/8443 | HTTP/HTTPS | Necessary to connect to the Tomcat web server |
33306 | TCP | To connect to the product database |
Allow outbound connections to ports on the source server (the ADManager Plus server) and inbound connections to ports on the target servers (i.e., domain controllers).
Port Number | Protocol | Source | Destination | Port Type | Service | Purpose |
389/636 | TCP and UDP | ADManager Plus server | Domain controllers | Static | LDAP | To connect to Active Directory |
135 | TCP | ADManager Plus server | Domain controllers | Static | RPC | To establish data exchange |
445 | TCP and UDP | ADManager Plus server | Domain controllers | Static | SMB | To get access to shared file systems |
88 | TCP | ADManager Plus server | Domain controllers | Static | Kerberos | For authentication when accessing a domain resource |
139 | TCP | ADManager Plus server | Domain controllers | Static | NetBIOS session | Required for communicating within the network |
3268/3269 | TCP | ADManager Plus server | Domain controllers | Static | Global Catalog | Necessary for performing search operations in the Global Catalog |
25 | SMTP | ADManager Plus server | SMTP server | Static | SMTP | To send emails |
80 | HTTP | ADManager Plus server | Domain controllers | Static | Exchange | For connecting to Exchange servers |
80, 443 | HTTP/HTTPS | ADManager Plus server | Microsoft 365 or Google Workspace servers | Static | Microsoft 365 and Google Workspace | Required for communicating with Office 365 and Google Workspace platforms |
49152- 65535 | TCP | ADManager Plus server | RPC randomly allocated high TCP ports | Dynamic | RPC | Used to establish data exchange |