SOLVED

Exchange 2016 CU22 upgrade issues

Steel Contributor

Anyone having issues with the CU22 upgrade for Exchange Server 2016. I've installed the new pre-requisite for it and running it from cmd line using the new /IAcceptExchangeServerLicenseTerms_DiagnosticDataOFF option, but I'm getting every error possible:

Setup will prepare the organization for Exchange Server 2016 by using 'Setup /PrepareAD'. No Exchange Server 2013 roles
have been detected in this topology. After this operation, you will not be able to install any Exchange Server 2013
roles.
For more information, visit: https://docs.microsoft.com/Exchange/plan-and-deploy/deployment-ref/readiness-checks?view=ex
chserver-2016

Setup will prepare the organization for Exchange Server 2016 by using 'Setup /PrepareAD'. No Exchange Server 2010 roles
have been detected in this topology. After this operation, you will not be able to install any Exchange Server 2010
roles.
For more information, visit: https://docs.microsoft.com/Exchange/plan-and-deploy/deployment-ref/readiness-checks?view=ex
chserver-2016

The Mailbox server role isn't installed on this computer.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.UnifiedMessagingRole
NotInstalled.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.BridgeheadRoleNotIns
talled.aspx

There is a pending reboot from a previous installation of a Windows Server role or feature. Please restart the computer
and then run Setup again.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.PendingRebootWindows
Components.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

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

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.DelegatedBridgeheadF
irstInstall.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.DelegatedCafeFirstIn
stall.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.DelegatedFrontendTra
nsportFirstInstall.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.DelegatedMailboxFirs
tInstall.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.DelegatedClientAcces
sFirstInstall.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.DelegatedUnifiedMess
agingFirstInstall.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 core and site JoanKirner, 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.ForestLevelNotWin200
3Native.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.MailboxRoleNotInstal
led.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

5 Replies
I've tried this in a second Exchange organisation and got the same error
Hi Dan
Did you find a solution? I have the same situation

Don't you see this behaviour when the user account you are using to install it with doesn't have the correct permissions?

best response confirmed by Dan Snape (Steel Contributor)
Solution
I had to re-run the schema update and AD prep for this update. Once that was completed I was able to run the install successfully.
Hi Dan,
It works for me too.
Thank you
1 best response

Accepted Solutions
best response confirmed by Dan Snape (Steel Contributor)
Solution
I had to re-run the schema update and AD prep for this update. Once that was completed I was able to run the install successfully.

View solution in original post