The Future of Exchange Starts Here: Exchange Server 2010 SP1 Is Now Available

"Setup needs to contact the Active Directory schema master but this computer is not in the same Active Directory domain as the schema master (DC=xxxx,DC=xxx,DC=xxx).

Click here for help... http://go.microsoft.com/fwlink/?linkid=30939&l=en&v=ExBPA.14&id=2376fec1-b9ce-44db-beb6-cb9ac4788988

http://go.microsoft.com/fwlink/?linkid=30939&l=en&v=ExBPA.14&id=2376fec1-b9ce-44db-beb6-cb9ac4788988

Error:

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 <RootDOMAINNAME> and site <SITENAME>, and wait for replication to complete. "

I got this error while trying to install 2010 in a child domain (with empty root containing Schema Master) after I had gone through all of the schema extensions/preps using the pre-SP1 code (NOT beta/RC, but bits downloaded from Premier site).  

I got my hands on the SP1 code, and after discovering that it is indeed the whole enchilada, and not just a patch I tried to perform an install using that source.  That's when I got the errors during the  pre-req checks.  Strange, in that that they didn't pop

up when I used the pre-SP1 code, but there was  no getting by them with the SP1 bits.

So, I copied the SP1 up to my Root domain, RE-RAN all of the Schema extension commands using the new bits, and re-tried the install back in my child domain.

Guess what?  It worked this time!  No AD schema errors thrown.  

So.  Exchange team, does SP1 introduce new schema values/attributes that require a re-run of the '/prepareAD'?  This is REALLY strange and any confirmation 1 way or another would be appreciated.

Tx,

El Kabong