asked on Can't install Exchange 2016 on prem.
Back ground - Exchange On prem. Exchg. 2010 and 2016 already in the org. our US servers are on 2010 and overseas ones on 2016. we are looking to install new 2016 servers and migrate our US users over. Now comes the fun.
Can't install Exchange 2016 on prem. install errors out saying the install account doesn't have permissions, but it is in the proper permission groups. verified several times.
My service account is a member in both the Enterprise Admins and the Organization Management groups as well as the local administrators group for the server.
We have verified the Schema is at the correct level and the Domain level is 2012R2.
Error listed below. Any help would be appreciated.
__________________________
Error:
You must be a member of the 'Organization Management' role group or a member of the 'Enterprise Admins' group to continue.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.GlobalServerInstall.aspx
Error:
You must use an account that's a member of the Organization Management role group to install or upgrade the first Mailbox server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedBridgeheadFirstInstall.aspx
Error:
You must use an account that's a member of the Organization Management role group to install the first Client Access server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedCafeFirstInstall.aspx
Error:
You must use an account that's a member of the Organization Management role group to install the first Client Access server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedFrontendTransportFirstInstall.aspx
Error:
You must use an account that's a member of the Organization Management role group to install or upgrade the first Mailbox server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedMailboxFirstInstall.aspx
Error:
You must use an account that's a member of the Organization Management role group to install or upgrade the first Client Access server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedClientAccessFirstInstall.aspx
Error:
You must use an account that's a member of the Organization Management role group to install the first Mailbox server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedUnifiedMessagingFirstInstall.aspx
Error:
Setup encountered a problem while validating the state of Active Directory: No domain controllers for the domain belcan and the site AW-Common-Global are available. See the Exchange setup log for more information on this error.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.AdInitErrorRule.aspx
Error:
Either Active Directory doesn't exist, or it can't be contacted.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.CannotAccessAD.aspx
Can't install Exchange 2016 on prem. install errors out saying the install account doesn't have permissions, but it is in the proper permission groups. verified several times.
My service account is a member in both the Enterprise Admins and the Organization Management groups as well as the local administrators group for the server.
We have verified the Schema is at the correct level and the Domain level is 2012R2.
Error listed below. Any help would be appreciated.
__________________________
Error:
You must be a member of the 'Organization Management' role group or a member of the 'Enterprise Admins' group to continue.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.GlobalServerInstall.aspx
Error:
You must use an account that's a member of the Organization Management role group to install or upgrade the first Mailbox server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedBridgeheadFirstInstall.aspx
Error:
You must use an account that's a member of the Organization Management role group to install the first Client Access server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedCafeFirstInstall.aspx
Error:
You must use an account that's a member of the Organization Management role group to install the first Client Access server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedFrontendTransportFirstInstall.aspx
Error:
You must use an account that's a member of the Organization Management role group to install or upgrade the first Mailbox server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedMailboxFirstInstall.aspx
Error:
You must use an account that's a member of the Organization Management role group to install or upgrade the first Client Access server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedClientAccessFirstInstall.aspx
Error:
You must use an account that's a member of the Organization Management role group to install the first Mailbox server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedUnifiedMessagingFirstInstall.aspx
Error:
Setup encountered a problem while validating the state of Active Directory: No domain controllers for the domain belcan and the site AW-Common-Global are available. See the Exchange setup log for more information on this error.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.AdInitErrorRule.aspx
Error:
Either Active Directory doesn't exist, or it can't be contacted.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.CannotAccessAD.aspx
ExchangeInstallationActive Directory
Last Comment
cdshreve
ASKER CERTIFIED SOLUTION
Log in or sign up to see answer
Become an EE member today7-DAY FREE TRIAL
Members can start a 7-Day Free trial then enjoy unlimited access to the platform
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
Not exactly the question you had in mind?
Sign up for an EE membership and get your own personalized solution. With an EE membership, you can ask unlimited troubleshooting, research, or opinion questions.
ask a question
1. Both servers on US and overseas are updated?
2. what is the schema and domain functional lvls on each site
3. are both sites connected over vpn?
4. Use administrator to run the installation (domain\administrator)
5. Check replication between AD on one site and the other (cross-site replication).
2. what is the schema and domain functional lvls on each site
3. are both sites connected over vpn?
4. Use administrator to run the installation (domain\administrator)
5. Check replication between AD on one site and the other (cross-site replication).
Hi
Does the same error happen with another Admin that has Org, schema, enterprise and domain admin rights?
Is this one forest stretched across by VPN? Any Read only domain controllers (RODC)?
Does the same error happen with another Admin that has Org, schema, enterprise and domain admin rights?
Is this one forest stretched across by VPN? Any Read only domain controllers (RODC)?
I started with Experts Exchange in 2004 and it's been a mainstay of my professional computing life since. It helped me launch a career as a programmer / Oracle data analyst
William Peck
Exchange 2016 version that you are installing making some changes to schema it seems..
Add the user account into schema admins group and run the installation again.
Add the user account into schema admins group and run the installation again.
ASKER
We had all of the permissions correct. Unfortunately another project going on had moved the network segment we were on to another AD Site! GRRRRRR. and I did not know that. Once this was resolved the install went as planned. I had a discussion with their managers and highlighted the change process and that it has a purpose!
Thanks so much for the responses!!
Thanks so much for the responses!!
and netdom query dc lists all of my DC's