Our organization is going to migrate from Exchange 2010 to Exchange 2013 CU13. We are going to change our exchange topology by installing hyper-V virtual 2013 servers at each location and setting up a DAG so the locations can fail over to each other if need be. The first site has no exchange server there any more- there were two 2010 servers (Mailbox and CAS) but they were properly uninstalled and no longer show up in the Exchange organization. I also cleaned up and removed any other extraneous servers that may have previously failed or been uncleanly removed- I was able to do all cleanup using Exchange installation tools and did nothave to use ASDI Edit or Schema Management to accomplish any of these tasks- We have a pristine environment. The first Exchange 2013 server is now ready to install. I ran setup.exe /PrepareSchema, setup.exe /PrepareAD, and Setup.exe /PrepareAllDomains. All completed successfully. Then I went to install Exchange. When it got to Organization Preparation 1/9, it failed. Here is the error:
Error:
The following error was generated when "$error.Clear();
initialize-ExchangeUniversalGroups -DomainController $RoleDomainController -ActiveDirectorySplitPermissions $RoleActiveDirectorySplitPermissions
" was run: "Microsoft.Exchange.Data.Directory.ADObjectEntryAlreadyExistsException: Active Directory operation failed on USMDSVRDC2.corp.local. One or more attribute entries of the object 'CN=Organization Management,OU=Microsoft Exchange Security Groups,DC=corp,DC=local' already exists. ---> System.DirectoryServices.Protocols.DirectoryOperationException: The object exists.
at System.DirectoryServices.Protocols.LdapConnection.ConstructResponse(Int32 messageId, LdapOperation operation, ResultAll resultType, TimeSpan requestTimeOut, Boolean exceptionOnTimeOut)
at System.DirectoryServices.Protocols.LdapConnection.SendRequest(DirectoryRequest request, TimeSpan requestTimeout)
at Microsoft.Exchange.Data.Directory.PooledLdapConnection.SendRequest(DirectoryRequest request, LdapOperation ldapOperation, Nullable`1 clientSideSearchTimeout, IActivityScope activityScope, String callerInfo)
at Microsoft.Exchange.Data.Directory.ADDataSession.ExecuteModificationRequest(ADObject entry, DirectoryRequest request, ADObjectId originalId, Boolean emptyObjectSessionOnException, Boolean isSync)
--- End of inner exception stack trace ---
at Microsoft.Exchange.Data.Directory.ADDataSession.AnalyzeDirectoryError(PooledLdapConnection connection, DirectoryRequest request, DirectoryException de, Int32 totalRetries, Int32 retriesOnServer)
at Microsoft.Exchange.Data.Directory.ADDataSession.ExecuteModificationRequest(ADObject entry, DirectoryRequest request, ADObjectId originalId, Boolean emptyObjectSessionOnException, Boolean isSync)
at Microsoft.Exchange.Data.Directory.ADDataSession.Save(ADObject instanceToSave, IEnumerable`1 properties, Boolean bypassValidation)
at Microsoft.Exchange.Data.Directory.Recipient.ADRecipientObjectSession.Save(ADRecipient instanceToSave)
at Microsoft.Exchange.Management.Tasks.InitializeExchangeUniversalGroups.AddMember(ADObject obj, IRecipientSession session, ADGroup destGroup, WriteVerboseDelegate writeVerbose)
at Microsoft.Exchange.Management.Tasks.InitializeExchangeUniversalGroups.CreateAndValidateRoleGroups(ADOrganizationalUnit usgContainer, RoleGroupCollection roleGroups)
at Microsoft.Exchange.Management.Tasks.InitializeExchangeUniversalGroups.InternalProcessRecord()
at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".
So to me it looks like Exchange is trying to run the prepare steps again and failing because everything is prepared already. How do I get past this- Is there a switch that tells Setup to skip this step?
Thanks!