Exchange 2003 on windows server 2003 having windows server 2008 root DC

255 pts.
Tags:
ForestPrep
Microsoft Exchange 2003
Microsoft Windows Server 2003
Windows Server 2008
I want to install the Exchange 2003 on windows server 2003. The problem is I am having windows server 2008 Domain controller as root DC. I am wondering if this configuration being supported by Microsoft?

I tried to run forestprep on windows server 2008 but was unable to run. I am getting the error as specified module couldnot be found.

 

Any answer to this would be highly appreciated.

Answer Wiki

Thanks. We'll let you know when a new response is added.

When we upgraded to Exchange 2007 our DCs were 2003 servers. We have since updated our DCs to 2008 with no problem running Exchange 2007 so this does work. I would get on the phone with Microsoft for support if you cannot get this to install.

Discuss This Question: 6  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • 423
    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.
    0 pointsBadges:
    report
  • mshen
    If forestprep doesn't work, does domainprep give you the same problem?
    27,385 pointsBadges:
    report
  • 423
    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.
    255 pointsBadges:
    report
  • Dwiebesick
    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.
    2,235 pointsBadges:
    report
  • 423
    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.
    255 pointsBadges:
    report
  • Dwiebesick
    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.
    2,235 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following