Exchange 2010 setup problems - FederatedEmail account missing

Trying to install Exchange 2010 on Windows 2012.

Installation of Hub Transport role fails as FederatedEmail account is missing.

However, running setup.com /PrepareAD also fails as follows:

"Setup encountered a problem while validating the state of Active Directory: The Active Directory organization configuration version (15763) is higher than Setup's version (14322). Therefor, PrepareAD can't be executed."

This box is to replace an existing SBS 2008 machine with Exchange 2007.  So it is also a domain controller and the forestprep has been run in order to add it as a domain controller.

How can I reinstate the FederatedEmail account ?
LVL 1
devon-ladAsked:
Who is Participating?
 
devon-ladConnect With a Mentor Author Commented:
This fix was supplied by Microsoft using adsiedit...they said this was an "unsupported" fix, but the only way to resolve the problem.

1. Select Properties of Default Naming Context>CN=Microsoft Exchange System Objects
2. Change objectVersion to 13040
3. Select Properties of Schema>CN=Schema,...>CN=ms-Exch-Schema-Version-Pt
4. Change rangeUpper to 14734
5. Select Properties of Configuration>CN=Configuration,...>CN=Services>CN=Microsoft Exchange>CN=First Organization
6. Change objectVersion to 14322

After making these changes I was able to successfully install Exchange 2010 and migrate data over from Exchange 2007.
0
 
Shreedhar EtteCommented:
Execute below command on Exchange 2007 Powershell:
Get-mailbox -arbitration

Does it report any output?

Also refer this article:
http://careexchange.in/how-to-recreate-system-mailbox-federatedemail-discoverysearchmailbox-in-exchange-2010/
0
 
devon-ladAuthor Commented:
Get-mailbox -arbitration fails on the Exchange 2007 box, but I thought arbitration mailboxes only exist in 2010 onwards so I would expect this to fail?

As far as that link is concerned - the first step is running setup.com /PrepareAD.  As mentioned above I have tried this and it fails.
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
MaheshArchitectCommented:
I think Exchange (AD) Schema is already upgraded to Exchange 2013 CU3 (15763)
You are trying to update exchange schema from Exchange 2010 SP3 Media (14322)

Obviously, you will get error
http://eightwone.com/references/schema-versions/

Mahesh
0
 
devon-ladAuthor Commented:
Thanks - already tried this approach.  The item CN=FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042 does not exist anyway.
0
 
devon-ladAuthor Commented:
I've tried the resolution steps 2 and 3 from http://support.microsoft.com/kb/978776

But I get "Load balancing failed to find a valid mailbox database" when running the new-mailbox command

I've also tried running /PrepareAD from the Exchange 2013 setup - given that it should be the same schema version it's using.  But even this reports that the schema in use is newer than that of the setup program.

Going round in circles here.  No more ideas?
0
 
devon-ladAuthor Commented:
No one got any more ideas?

We're stuck now because neither the 2010 or 2013 installations will complete due to neither being able to create the arbitration mailboxes as the AD schema version is too high.
0
 
devon-ladAuthor Commented:
Solution provided by Microsoft.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.