none
Unable to install Exchange 2013 on Server 2012 server.

    Question

  • I am getting the follwing errors when trying to install exchange 2013 on server 2013. I have already cleared some of the errors reported but the below i seem to be having issues with.

    The logon account is the domain administrator and is a member of schema admins, enterprise admins and organization managment.

    I have dropped the server off the domain and back on to see if this fixes it but to no avail.

    Error:

    The Active Directory schema isn't up-to-date, and this user account isn't a member of the 'Schema Admins' and/or 'Enterprise Admins' groups.

    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.SchemaUpdateRequired.aspx

    Error:

    Global updates need to be made to Active Directory, and this user account isn't a member of the 'Enterprise Admins' group.

    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.GlobalUpdateRequired.aspx

    Error:

    The local domain needs to be updated. You must be a member of the 'Domain Admins' group and 'Organization Management' role group, or 'Enterprise Admins' group to continue.

    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.LocalDomainPrep.aspx

    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: Exchange organization-level objects have not been created, and setup cannot create them because the local computer is not in the same domain and site as the schema master.  Run setup with the /prepareAD parameter on a computer in the domain landlinc and site Hertford, and wait for replication to complete.

    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.AdInitErrorRule.aspx

    Error:

    The forest functional level of the current Active Directory forest is not Windows Server 2003 native or later. To install Exchange Server 2013, the forest functional level must be at least Windows Server 2003 native.

    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.ForestLevelNotWin2003Native.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

    Warning:

    Setup will prepare the organization for Exchange 2013 by using 'Setup /PrepareAD'. No Exchange 2010 server roles have been detected in this topology. After this operation, you will not be able to install any Exchange 2010 servers.

    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.NoE14ServerWarning.aspx

     

    Tuesday, October 22, 2013 2:02 PM

All replies

  • Hi

    Is DNS working correctly on the Exchange server?  If you ping yourdomain.local does it return the IP address of one of you DCs?

    Steve

    Tuesday, October 22, 2013 2:19 PM
  • try opening a command prompt as administrator and running setup from there

    regards

    Nick

    Tuesday, October 22, 2013 3:41 PM
  • Tuesday, October 22, 2013 3:49 PM
  • Yes it replies with the local LAN IP address of one of the DC's
    Wednesday, October 23, 2013 8:33 AM
  • Done all the abobe but get this error on the setup prepare AD.

    The Exchange Server setup operation didn't complete. More details can be found
    in ExchangeSetup.log located in the <SystemDrive>:\ExchangeSetupLogs folder.

    Wednesday, October 23, 2013 8:48 AM
  • Hi,

    From your error description, the user account you attempted the install isn't a member of the 'Schema Admins' or 'Enterprise Admins' groups. But you say that you can ping the DC. I recommend you to follow the steps below for troubleshooting.

    1. Please unjoin the domain at first.

    2. Rejoin the domain.

    3. Please refer to the below thread to install Exchange 2013 step by step.

    Planning and Deployment

    http://technet.microsoft.com/en-us/library/aa998636(v=exchg.150).aspx

    What's more, here is a similar therad for your reference.

    Exchange says my forest and domain are not up to date

    http://social.technet.microsoft.com/Forums/exchange/cs-CZ/0d8bc66e-2632-4bc4-bba4-be69e03c0497/exchange-says-my-forest-and-domain-are-not-up-to-date?forum=exchangesvrdeploy

    Hope it helps.

    Best regards,
    Amy


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

    • Proposed as answer by bheydari Wednesday, September 9, 2015 10:28 AM
    Thursday, October 24, 2013 2:36 AM
    Moderator
  • Hi

    I have searched everywhere on the internet, and ran through countless threads to resolve this one.  For me the problem was as follows:

    The account I had created to install Exchange was a member of the "Users" group, as well as all of the other required groups.  

    I ran the prerequiste checks again as Administrator and it seemed to work.  The only difference was that my Exchange Installation account was in the "Users" Group.  So I removed it.  And it worked.  

    Three days wasted.


     


    Monday, February 3, 2014 1:31 PM
  • i just register here to say thanks to you :)
    Thursday, April 16, 2015 2:45 PM
  • I was able to fix this by
    1). Running the exchange 2013 CU10 setup; "Setup.exe /PrepareAD /IAcceptExchangeServerLicenseTerms" on the domain controller with all the FSMO role. Forced replication to the site I was installing the new Exchange 2013 server

    2). running a CMD prompt as different user and run it with my domain admin account.
    Weird thing is that UAC is turned off and that I was already logged in with the same account. So I don't get why I had to run the CMD as different user, using the same credentials...

    Other details:
    - Experienced this problem with new server trying to install Exchange 2013 CU10, in an existing Exchange 2013 organization; there are already other Exchange 2013 CU9 servers installed in different AD sites.

    - The OS used was Windows 2012 R2 with Update1

    • Proposed as answer by Mani IT Wednesday, January 31, 2018 7:52 PM
    Friday, October 30, 2015 3:30 PM
  • I have researched this all over the internet and many of these answers are just regurgitation of other threads. I have check all the obvious problems. I am using the Domain Administrator Account, The Administrator account is a member of all the proper security groups. I have tried to run PrepareAD but I get a similar error about not having permission or being able to contact AD. I have ran dcdiag All DC's passed the tests preformed. I did get an error that the RPC server was not available but I determined that Remote management was being blocked by the firewall. I allowed the remote management services through the firewall and that error went away but the error persists.
    My Exchange server is a completely fresh install of server 2012 R2 and
    I need to know what could cause AD to not allow exchange to connect to it.

    Jeremy Robertson Network Admin

    • Proposed as answer by Saaralanka Friday, November 24, 2017 7:26 AM
    Monday, December 19, 2016 1:53 PM
  • I resolved this by moving the schema master to an AD in the same subnet as the Exchange server.  Came good immediately.
    Saturday, March 18, 2017 4:22 AM
  • I resolved the issue with re-logging in into the DC. By the way you could check the group membership via "WHOAMI /GROUPS" in a CMD.
    Friday, July 14, 2017 10:51 PM
  • I had this exact same problem in a environment that already contained an Exchange 2016 CU4 installation whilst trying to install and extra Exchange 2016 CU8.

    Installing CU4 instead fixed the problems and installed flawlessly. 

    Wednesday, January 10, 2018 9:39 AM
  • Hi Erik,

    I just want to Thank you.. I have tried the option 2, it was working fine.

    Mani

    Wednesday, January 31, 2018 7:55 PM
  • We had this exact same issue and the error messages were misleading. We found the root cause of the error by looking in the ExchangeSetup.log file located in C:\ExchangeSetupLogs.

    Bizarrely, the issue is that we were running the installer on a server located in a separate AD site to the domain Schema Master. Moving the server into the same subnet as the Schema Master and running setup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms allowed it to complete. Alternatively of course, you could move the Schema Master to the same site as the proposed Exchange Server if appropriate.

    • Proposed as answer by Fedor T Tuesday, May 15, 2018 5:19 AM
    Tuesday, February 27, 2018 3:11 PM
  • OMG, not a single guide mentioned this. This was the same issue I had. After an entire afternoon down the drain, I stumbled upon this post. Nowhere does any guide say that the schema master has to be in the same subnet. Thanks man.
    Monday, March 5, 2018 9:09 PM