admin
0 pts. | Aug 24 2009 1:18PM GMT
Thanks for your feedback. The problem is running the forestprep on Windows server 2008 DC. As in our case the root DC is windows server 2008. And we want to install exchange server 2003 and not exchange server 2007.
Mshen
23535 pts. | Aug 24 2009 10:43PM GMT
If forestprep doesn’t work, does domainprep give you the same problem?
423
255 pts. | Aug 25 2009 5:10AM GMT
I tried running the forestprep and domainprep on the member server with enterprise admin credentials and I could install the exchange server 2003. Everything looks running fine without any issues.
However, if we go by the concepts, it says the forestprep has to be run on root DC. But in my case as above its violating the concept of running forestprep on root DC.
Dwiebesick
1760 pts. | Aug 25 2009 2:39PM GMT
If you have a 2008 as the root of your forest, and you joined your 2003 servers to this network, your forest (I will assume only one domain) and domain will already have the lastest schema and there is no need to try running adprep
You can check the schema version in the registery HKEY_LOCAL_MACHINESystemCurrentControlSetServicesNTDSParametersSchema-Version and 44 would be Server 2008 RC.
423
255 pts. | Aug 26 2009 6:35AM GMT
I checked the same and its showing 44 as the schema version. However, the schema related to Exchange server 2003 also gets modified even though we have Windows server 2008 as Root DC.We can see some new tabs added for user properties specific to exchange server.
By not running adprep you mean not running the forestprep and only running domainprep on the member server?
I will try that as well on some other test server which I have.
Dwiebesick
1760 pts. | Aug 26 2009 3:38PM GMT
There is only one schema, so yes when you look at your exchange it should have the NEW schema, as it is applied at forest level. You cannot have different schemas in forest that is why for the 5 FSMO there is only one and only one schema master. You will never have two schema masters in a forest nor can you ever have different schema in an organization. If you try, you will have very bad experiences.






