I am looking for some assistance with the process for this. I've read several posted articles on MS' site and others, and I'm still stuck.
I have a Windows 2000 SP4 server as the only server in my domain, so it is the DC, GC, and holds all FSMOs (verified). I have verified that the domain is at a Windows 2000 native functional level. This same server is running Exchange 2000 SP3.
I have loaded up a brand new Windows 2008 x64 Standard Server. The intent is to have this be the new DC, GC, FSMOs, and also run Exchange 2007. I looked into the reqs for a Windows 2008 server to be a DC in a Windows 2000 domain, that seemed OK. I went to run adprep /forestprep, and received an error about a Schema Conflict with Exchange 2000. I researched that issue more, and found that people were running into that also with Windows & Exchange 2003. They got around it by running the Exchange 2003 version of adprep, then run Windows 2003 adprep, and all was good. Along the way, though, I found articles that said if I'm running Windows 2008 DC's in a domain (more accurately Site) with Exchange 2000 Servers, then I must configure DSAccess on those servers to only talk to the Windows 2000 DC, and that the Windows 2000 DC must stay around until the Exchange 2000 Server goes away.
So, I configured DSAccess on the Exchange server to manual, and told it to only look at the Windows 2000 DC. So now I must be ready to prep my domain, right?
Exchange 2007's setup program must be run with the following switches -
setup.com /PrepareLegacyExchangePermissions fails, telling me the Schema Master must be a Windows 2003 Server or higher.
So, it appears I have a Catch-22. I can't do adprep /forestprep or /domainprep in order to promote my Windows 2008 server to a DC, and I can't prep my domain via Exchange 2007 tools either. Do I have to load up a Windows 2003 DC in between to make this smoother??
Thanks in advance.