Hybrid AD Manager: Installation Guide
Hybrid AD Manager is a web console for Active Directory and Entra ID that replaces the RSAT snap-ins with one browser page. It runs as a Windows service on a domain controller or any member server, and admins use it from any browser. This guide takes a new installation from the download to the first sign-in. The User Guide covers day-to-day use.
1. Before you start
Server. Windows Server 2019 or later (Server Core is fine). 2 CPU cores and 2 GB of RAM are plenty; the console keeps no database. One server serves any number of admins.
Network. The server must reach a domain controller of every domain it will manage over LDAPS (TCP 636)
or LDAP with StartTLS (TCP 389). Admins reach the console on TCP 5080 (HTTPS; see
HTTPS). For Entra ID, the server needs outbound HTTPS to login.microsoftonline.com
and graph.microsoft.com.
Domain controllers must offer TLS. A DC with a certificate from an enterprise CA already does. A lab DC without one needs a certificate in its computer store; the console refuses to send a password over a cleartext connection.
Accounts. Admins sign in with their own Active Directory accounts and the console acts as them, so no service account is needed for them. A service account is only used for sessions that have no directory password of their own: Entra ID sign-in and API tokens. Read-only rights are enough for it.
Browser. Any current Edge, Chrome, Firefox or Safari. Phones and tablets get a search-first layout.
2. Install on Windows
Copy
HybridAdManager-<version>.msito the server.From an elevated PowerShell:
msiexec /i C:\Temp\HybridAdManager-1.0.53.msiFor an unattended install add
/qn /norestart. Deployment tools can use the same command.The installer registers the HybridAdManager service (runs as Local Service, starts automatically, restarts on failure), opens TCP 5080 in Windows Firewall, and creates
C:\ProgramData\HybridAdfor settings, keys, licence and audit logs. Program files go toC:\Program Files\HybridAd.Read the one-time setup token: Start Menu, Hybrid AD Manager setup token, or
Get-Content C:\ProgramData\HybridAd\setup-token.txt
The service listens on every interface from the first start, so the wizard can be opened from another machine; Server Core has no browser of its own.
3. First-run wizard
Open https://<server>:5080 and accept the certificate warning (the console made itself a certificate; see HTTPS). The wizard runs once and has five steps; each is saved as you go, so you can
close the browser and come back.
Setup token. Paste the token from step 2 or 3. It proves you are the person who installed the software and is discarded when setup completes.
Administrator. Create the local console account. It maintains the console itself (Settings, Licence, Sessions, Audit) and never sees the directory, so it does not use a licence seat. Passwords need 12 characters with mixed case, digits and a symbol; the page says which rule is unmet.
Directory. On a domain-joined server the console finds its own domain controller and fills in the name and port; confirm it. Otherwise enter the DC's DNS name. Untick certificate validation only for a lab DC with a self-signed certificate. "Test" tries the connection, optionally with your own account; nothing typed there is stored. The service account is optional (see section 1).
Entra ID (optional). Nothing is needed here: the first time a console administrator chooses Connect Entra ID in the console, it does this step for you. To do it now instead, press Set up automatically, check the console's address (the one administrators' browsers use, filled in for you), and have a Global Administrator sign in to Microsoft in the window that opens. Microsoft returns them to a short page on the TideReach site that shows your console's address; they press Continue and the window closes. (If the window can't reach the console, it shows a one-time code to paste back instead.) The console then registers itself in your tenant: its own app registration, a certificate made on this server whose private key never leaves it, its address for sign-ins, and the delegated permissions it needs, with consent. Nobody copies an ID or uploads a file, and the one-time setup app is removed from your tenant afterwards. Run it again at any time to bring the registration up to date.
The application holds no permissions of its own: each administrator connects with their own Microsoft sign-in, usually without a click (see the User Guide), and can never do more through the console than in the Entra admin centre.
If you prefer to register it yourself, or a policy blocks the setup app, use Set up manually instead: an app registration with Web redirect URIs
<console address>/signin-entra-graphand<console address>/signin-oidc, the certificate (a thumbprint in LocalMachine\My, or PEM files) under Certificates & secrets, and Microsoft Graph Delegated permissionsUser.ReadWrite.All,Group.ReadWrite.All,User-PasswordProfile.ReadWrite.AllandUser.Readwith admin consent; no Application permissions. Enter the tenant ID, application ID and certificate, and Test checks they belong together.Sign-in and roles. Which sign-in methods to allow and which groups map to the three console roles: Administrator (everything, including permissions), Operator (day-to-day changes), Reader (browse only). Group names or distinguished names;
*under Readers admits any signed-in domain user.
Finish, then sign in with Active Directory and your own account.
4. Licence
A fresh install runs the free edition: every tool, read-only, one signed-in user, and lists capped at 15 items. Under the user menu, Licence, the page shows this server's Installation ID and the Domain SID of the domain it manages. Both go with your order (the page's Buy Licence button opens the order site with them filled in); the key you receive is issued for that installation and domain and will not install anywhere else. To try the full product first, Start a 30-day trial on the same page emails a free trial key for this server: the Standard edition for 30 days, after which the console goes back to the free edition by itself, with no grace period. There is one trial per domain. Paste the key on the same page. The key states the edition, number of concurrent signed-in users (seats), number of domains and tenants, and which tools it includes. Keys are verified offline; no internet access is needed.
A licence runs for 12 months from the date it is issued and does not renew by itself. For the last 30 days of the term the console's title bar shows how many days remain; order a new key from the vendor's site (the Licence page links to it) and paste it over the old one. If the key lapses there is a 30-day grace period during which writes still work, after which the console is read-only until a key is installed.
The Installation ID comes from the server's Windows machine identity, so reinstalling the application or restoring the data folder on the same server keeps it. A new or rebuilt server has a new ID and needs a replacement key; contact the vendor with the new ID.
5. Adding domains
Settings, Directory, More domains. Add a domain controller for each further domain, within the licence's domain count. Admins sign in once with the account of any configured domain; the Domain picker in the menu bar switches the console between domains. Reads and changes in another domain run with the signed-in account, so a trust is needed and the account must hold rights there.
6. HTTPS for the console
The console listens on HTTPS from the first start. Until you install a certificate it uses one it generated
for itself (valid for the server's host name and localhost), so browsers show a certificate warning that
you accept once; the connection is still encrypted. To replace it: sign in as a console administrator, open
Settings, Listener, and either upload a PFX (a web server certificate for the server's name with its
private key, from your enterprise CA or a public CA) or pick a certificate already in the server's Local
Computer, Personal store. The change applies at once with no restart. To terminate TLS on a reverse proxy
instead, set Listener.PlainHttp to true in settings.json and restart the service.
7. Upgrading
Run the newer installer over the existing one. On Windows:
msiexec /i C:\Temp\HybridAdManager-<newer>.msi /qn /norestart
Settings, keys, licence, audit logs, API tokens and sessions are kept. The version shows in the title bar and under Help, About; a higher number is always newer. To roll back, install the previous package the same way.
8. Uninstalling
Apps and Features, or msiexec /x <msi>. Data in C:\ProgramData\HybridAd is kept; delete it by hand
for a clean slate.
9. If something goes wrong
- "Could not read the directory" after setup: the DC certificate is not trusted (tick or untick validation to match your DC), or the account used has no directory role. Settings, Directory, Test shows the exact reason.
- Cannot reach the console from another machine: check the firewall rule for TCP 5080 exists, and that
Listener.AllInterfacesis true insettings.json. - "Licence limit reached" at sign-in: every seat is in use. A console administrator can see who holds them under Sessions and disconnect one.
- Logs: on Windows the service writes to the Application event log; the audit trail is in
<data>\audit\<date>.jsonl, one JSON line per action.