Link to home
Create AccountLog in
Avatar of ACCESS2008
ACCESS2008

asked on

Installing Exchange 2003 Server in my Exchange 5.5 Forest

Don't laugh; I am still using Exchange 5.5. I have a fairly simple Windows 2003 AD Domain Forest (running mixed mode) with three Child Domains. Two of the child domains have Exchange 5.5 Servers for their respective domains. My plan is to install one Exchange 2003 Server (New) and migrate all of the 5.5 Mailboxes from each 5.5 Server to this one Exchange 2003 Server one 5.5 Server at a time. I have read through the Microsoft Exchange 2003 Deployment and Planning Guides.  In all of my research I could not find any documentation on which domain (Where?) to install the new Exchange 2003 Server (top level or child level domain). There are no Servers in the top forest level domain except the domain controllers and none of the child domain administrators have access to the top level domain so I am not sure if it is the proper location. Maybe this does not matter but I wanted to give you as much information as possible. I was hoping someone could guide me on the proper location before I join the new Server to a domain.  Also any other information other than the two documents I mentioned above that I should be concerned about during this implementation.
ASKER CERTIFIED SOLUTION
Avatar of MegaNuk3
MegaNuk3
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
See answer
Avatar of ACCESS2008
ACCESS2008

ASKER

I thought that would be the answer but was not sure if it should be in the top level domain of the forest.  I read that I do NOT want to make the Server running Exchange 2003 a DC, correct?  But you do recommend that I join it to the child domain with the most mailboxes.  The top level domain and one of the child domains and one of the 5.5 servers (with the most users) is in the corporate office.  The second child domain and 5.5 servers in a remote office (both with high bandwidth 10MB pipes connected via VPN).  I was planning on using the ADC to move the mailboxes a few at a time over the weekend.  The third child domain is in another remote office that is using the second remote offices 5.5 server for mail (only a handful of users).
You can make it a DC, but it is not recommended due to the security risks.
Do a directory export of Exchange 5.5 and look for any mailboxes that have the same primary windows NT account and then sort those out.
Thanks.  I will most likely not make it a DC then.  What do I need to be concerned about or do with the mailboxes that have the same primary account?  How about primary users for distribution groups and other containers such as shared Calendars?

Thanks again.  I am going to award you the points but before I close this question do you have any more tips or insights before I proceed with this migration?
Create new disabled accounts for those resource mailboxes that are using the same primary windows NT account as the users, that way the ADC should be able to pair the mailboxes correctly.

DG/DLs & in-mailbox Calendars will be fine as long as you sort out the primary windows NT account issue