Here's the scoop!!
Full Windows 2003 migration Completed. 1 exchange 5.5 server from old domain, now in new 2003 Domain running Windows 2000.
Using the exdeploy wizard on new exchange 2003 server.
Get to the ADC tools and recieve the following message:
Error: The organization o=PPI is...
I agree with the Private IP assignments. The way that works is that all of the addresses on your internal network will be private (ie. non accessible from outside unless allowed) You would need to have hardware that supports NAT (network address translation) You would then only use you...
If the user that you are using for the merge is a member of Domain Admins or enterprise Users, make sure that they also have send/receive allow!!
The easiest way that I have found is to create a user strictly for the migration
That may help.....
Ian
AD is already in place. We have merged with another company which is running on an NT 4.0 Domain with a single Exchange 5.5 server. We need to migrate this server to an exchange 2003 server in our domain.
We have been testing various methods in the lab, exmerge, the migration tool and so on...
This is how I configured the drives on our Exchange 2003 server.
Mirrored (on the RAID controller) 18 GB SCSI hard drives:
6 GB for main OS system drive (C: )
4 GB for main OS swap page file (P: )
6.5 GB for Active Directory NTDS drive (N: )
4, 72 GB SCSI hard drives setup in a RAID 5...
I am currently testing various methods of migrating from 5.5 to 2003. I have 3000 mailboxes to migrate and the exchange servers are in two seperate Domains. The 5.5 server is in an old NT 4.0 Domain and the 2003 is in a new 2003 Domain
Any ideas on the best way to approach to this?
Thanks
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.