MSExchangeGuru.com

Error upgrading exchange 2016 Cu3 to 2016 CU4. Adding the entire error for the sake of keyword search.

Error in the command line was:

Performing Microsoft Exchange Server Prerequisite Check

Configuring Prerequisites                                 COMPLETED

Prerequisite Analysis                                     FAILED

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

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

Setup will prepare the organization for Exchange 2016 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

     The Mailbox server role isn’t installed on this computer.

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

     The Mailbox server role isn’t installed on this computer.

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

     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

     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

     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

     You must use an account that’s a member of the Organization Management rolegroup 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

     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

     You must use an account that’s a member of the Organization Management rolegroup 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

     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

     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

     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 MSexchangeGuru.com and site HQ, and wait for replication to complete.  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

     The forest functional level of the current Active Directory forest is not Windows Server 2003 native or later. To install Exchange Server 2016, 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

     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

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

I am sure that I was installing it on a Mailbox server that was working like a charm with exchange 2016 Cu3. I did check the registry to see if the Mailbox role had any water mark because of the last install and it was looking fine

Also I have confirmed the logged in account has the appropriate rights to upgrade the server

Surfed through the exchangesetup logs and found the below 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 the setup with prepare /AD parameter on a computer in the domain MsexchangeGuru and site DR, and wait for replication to complete”

So copied the setup to a DC on that site and ran

Setup.exe /p /iacceptexchangeserverlicenseterms

Post successfully running the prepareAD when I ran the exchange upgrade on exchange server it worked well.

Ratish Nair

Microsoft MVP | Exchange Server

Team @MSExchangeGuru.com

Posted January 18th, 2017 under Exchange 2016. RSS 2.0 feed. Leave a response, or trackback.