Grasp Technologies
asked on
Exchange 2013 CU2 upgrade AD error
In my development environment, which is an exact replica of production, I am testing the upgrade for Exchange 2013 to CU2. When running the install all the prereq checks pass just fine, however once it begins to actually install I get the following error:
Error:
The following error was generated when "$error.Clear();
install-AdministrativeGrou p -DomainController $RoleDomainController
" was run: "Active Directory operation failed on "domain controller". The object 'CN=Folder Hierarchies,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Admin istrative Groups,CN="domain",CN=Micr osoft Exchange,CN=Services,CN=Co nfiguratio n,DC="doma in",DC=com ' already exists.".
My thinking on this is, well of course it already exists, as this is simply an upgrade of the current Exchange 2013 CU1 (Version 15, Build 620.29). However this causes the installation to fail.
I have attempted to manually do the ADSCHEMA and ADPREP upgrades before running the software upgrade and both run with out error, however the software upgrade still fails.
Google hasn't found much on this particular error so I am wondering if anyone has any thoughts.
Thanks in advance!
Error:
The following error was generated when "$error.Clear();
install-AdministrativeGrou
" was run: "Active Directory operation failed on "domain controller". The object 'CN=Folder Hierarchies,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Admin
My thinking on this is, well of course it already exists, as this is simply an upgrade of the current Exchange 2013 CU1 (Version 15, Build 620.29). However this causes the installation to fail.
I have attempted to manually do the ADSCHEMA and ADPREP upgrades before running the software upgrade and both run with out error, however the software upgrade still fails.
Google hasn't found much on this particular error so I am wondering if anyone has any thoughts.
Thanks in advance!
Seems this error is common and I am not sure of possible cause. Some people have issues and some don't with the upgrade. From what I have seen so far an escalated call to Microsoft is what has been done in my experience.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I received the solution from both Microsoft tech support and a reply to my TechNet forum post.