barryreilly
asked on
Is there anything special or extra to do if i want to change from a 2000 to 2003 domain if i have an exchange 2000 cluster
Scenario:
Windows 2000 domain with 3-4 domain controllers, two exchange 2000 clusters in two different physical offices.
3 office locations
the windows 200 domain has two domains due to the different companies under the one forest.
the primary tasks is to buy new 2003 R2 servers, make them DCs, two in the primary office and one in each of the others
make the first of them the new primary DC , global catalog etc...
i know you have to prep the forest and then domains
but my only concern is what if any impact this will have on the existing exchange clusters?
or should all the prep tasks have to be done both in succession and on same day ,,, in other words can i just forest prep on a friday evening, then domain prep the domain that office uses and leave the 2nd domain in the forest for the next weekend.
are there other thing s i need to take into consideration?
Windows 2000 domain with 3-4 domain controllers, two exchange 2000 clusters in two different physical offices.
3 office locations
the windows 200 domain has two domains due to the different companies under the one forest.
the primary tasks is to buy new 2003 R2 servers, make them DCs, two in the primary office and one in each of the others
make the first of them the new primary DC , global catalog etc...
i know you have to prep the forest and then domains
but my only concern is what if any impact this will have on the existing exchange clusters?
or should all the prep tasks have to be done both in succession and on same day ,,, in other words can i just forest prep on a friday evening, then domain prep the domain that office uses and leave the 2nd domain in the forest for the next weekend.
are there other thing s i need to take into consideration?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Exchange 2000 note: Please make sure you read Windows 2003 ADPrep Fix for Exchange 2000 before installing the first Windows Server 2003 DC in your existing organization.
What do I need to do to make sure Exchange 2000 runs fine on my Windows Server 2003 forest?
If you've installed Exchange 2000 into the forest before running ADPrep, you have to correct some mistakes that were made in the Exchange 2000 schema extensions.
Specifically, both ADPrep and Exchange 2000 define labledURI, houseIdentifier and secretary attributes, but Exchange 2000 does not use the correct LDAP display names (lDAPDisplayName) as defined in RFC 2798.
If you run ADPrep after Exchange 2000 has been installed without fixing these attributes, you can end up with duplicate schema objects with different lDAPDisplayName attributes
To solve the problem, you must run the inetorgpersonfix.ldf file that is located in \support\ tools\support.cab. This LDIF file fixes the lDAPDisplayName attributes of the three attributes.
First save the inetorgpersonfix.ldf file, then import it using the ldifde utility. Here is an example where we will be importing into the mycorp.com forest:
ldifde.exe /i /f inetOrgPersonFix.ldf /c "DC=X" "DC=mycorp,DC=com"
Note that inetorgpersonfix.ldf uses DC=X as the forest path, which is why we needed to use the /c switch to replace it with our own forest path.