Hello,
We are running Exchange 2013 CU6 currently and would like to test the upgrade to CU12. To test this, I have restored a backup using Veeam to our VMWare cluster one of our Domain Controllers, a client computer and the Exchange server. They are
all isolated on their own virtual switch with no network uplink. There is a veeam surebackup proxy server that can allow internet access if we setup a proxy server address in these machines, but I do not currently have that configured.
The client can open Outlook 2010 and see the mailbox. They can all ping eachother and its basically an isolated island. Since Exchange appears to be working (can access EAC, OWA and Outlook from the client), things appear to be working besides
a few Exchange event logs about the other two domain controllers not being able to be contacted.
When I run the CU12 update on this test exchange I get pretty much every error imaginable from the prerequsite check. I then tried it via command line to see if that would bypass it and I get the same errors. Why aren't any of the roles being
detected? It seems its up and running in this test network bubble.
Any other way to test CU6 to CU12?'
Administrator: Windows PowerShell
PS C:\Exchange2013-CU12> c:\Exchange2013-CU12\setup.exe /m:upgrade /IAcceptExchangeServerLicenseTerms
Welcome to Microsoft Exchange Server 2013 Cumulative Update 12 Unattended Setup
Copying Files...
File copy complete. Setup will now collect additional information needed for installation.
Languages
Mailbox role: Transport service
Client Access role: Front End Transport service
Mailbox role: Client Access service
Mailbox role: Unified Messaging service
Mailbox role: Mailbox service
Management tools
Client Access role: Client Access Front End service
Performing Microsoft Exchange Server Prerequisite Check
Configuring Prerequisites COMPLETED
Prerequisite Analysis FAILED
Setup will prepare the organization for Exchange 2013 by using 'Setup /PrepareAD'. No Exchange 2007 server roles have b
een 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
This is fine, we removed our Exchange 2007 a year or two ago. Setup will prepare the organization for Exchange 2013 by using 'Setup /PrepareAD'. No Exchange 2010 server roles have b
een 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
This is fine, we never had Exchange 2010. The Mailbox server role isn't installed on this computer.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.UnifiedMessagin
gRoleNotInstalled.aspx
Yes it is, why do you think Outlook and OWA work from my test client? The Mailbox server role isn't installed on this computer.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.BridgeheadRoleN
otInstalled.aspx
This seems to be a duplicate of the above. The Active Directory schema isn't up-to-date, and this user account isn't a member of the 'Schema Admins' and/or 'E
nterprise Admins' groups.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.SchemaUpdateReq
uired.aspx
I'm logged in with a Domain Admin, and also right clicked and ran PowerShell as administrator. I should have all the rights in the world. 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.GlobalUpdateReq
uired.aspx
I'm logged in with a Domain Admin, and also right clicked and ran PowerShell as administrator. I should have all the rights in the world. You must be a member of the 'Organization Management' role group or a member of the 'Enterprise Admins' group to co
ntinue.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.GlobalServerIns
tall.aspx
I'm logged in with a Domain Admin, and also right clicked and ran PowerShell as administrator. I should have all the rights in the world. You must use an account that's a member of the Organization Management role group to install or upgrade the first M
ailbox server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedBridge
headFirstInstall.aspx
I'm logged in with a Domain Admin, and also right clicked and ran PowerShell as administrator. I should have all the rights in the world. You must use an account that's a member of the Organization Management role group to install the first Client Acces
s server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedCafeFi
rstInstall.aspx
I'm logged in with a Domain Admin, and also right clicked and ran PowerShell as administrator. I should have all the rights in the world. You must use an account that's a member of the Organization Management role group to install the first Client Acces
s server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedFronte
ndTransportFirstInstall.aspx
I'm logged in with a Domain Admin, and also right clicked and ran PowerShell as administrator. I should have all the rights in the world. You must use an account that's a member of the Organization Management role group to install or upgrade the first M
ailbox server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedMailbo
xFirstInstall.aspx
I'm logged in with a Domain Admin, and also right clicked and ran PowerShell as administrator. I should have all the rights in the world. You must use an account that's a member of the Organization Management role group to install or upgrade the first C
lient Access server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedClient
AccessFirstInstall.aspx
I'm logged in with a Domain Admin, and also right clicked and ran PowerShell as administrator. I should have all the rights in the world. You must use an account that's a member of the Organization Management role group to install the first Mailbox serv
er role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedUnifie
dMessagingFirstInstall.aspx
I'm logged in with a Domain Admin, and also right clicked and ran PowerShell as administrator. I should have all the rights in the world. Setup encountered a problem while validating the state of Active Directory: Setup has determined that the schema ma
ster domain controller dc1.domain.com is not available or cannot be contacted. 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
This is expected, that is a physical machine. I only restored our virtual domain controller, but I can assure you the domain works. The client can log into ad with any valid credentials that are not cached on it already. The forest functional level of the current Active Directory forest is not Windows Server 2003 native or later. To i
nstall 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.ForestLevelNotW
in2003Native.aspx
The forest and domain functional level are 2008 R2. We haven't raised it to 2012 R2 yet. 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
WRONG. Like I said before I can log into any domain account I choose. I have a DC up and running in the test environment.
The Exchange Server setup operation didn't complete. More details can be found in ExchangeSetup.log located in the
<SystemDrive>:\ExchangeSetupLogs folder.
Any ideas?