asked on Windows Server 2003 to 2008 Trust
Hi All,
Just a quick sanity check / brain storm.
I have taken over the care of a network with the plan of scrapping their old nasty exchange infrastructure.
192.168.0.x/24 = HQ (companyuk.local)
192.168.1.x/24 = NEW COLO (additional site to companyuk.local)
x.x.x.x = OLD COLO (Public address only) - Completely separate site AD (company.co.uk)
The old colo contains an Exchange 2003 server, New colo contains an Exchange 2010 server which we will be migrating accounts to.
I want to set up a trust between the two for migration purposes.
Since company.co.uk (the actual domain name, not the AD domain name on the exchange 2003 box) is also used for a website and various portal/crm which are located on another box and used internally, what problems am I going to face by creating a trust?
Can I create the trust without having the zone file for company.co.uk ?
What issues am I likely to face?
Thanks.
Just a quick sanity check / brain storm.
I have taken over the care of a network with the plan of scrapping their old nasty exchange infrastructure.
192.168.0.x/24 = HQ (companyuk.local)
192.168.1.x/24 = NEW COLO (additional site to companyuk.local)
x.x.x.x = OLD COLO (Public address only) - Completely separate site AD (company.co.uk)
The old colo contains an Exchange 2003 server, New colo contains an Exchange 2010 server which we will be migrating accounts to.
I want to set up a trust between the two for migration purposes.
Since company.co.uk (the actual domain name, not the AD domain name on the exchange 2003 box) is also used for a website and various portal/crm which are located on another box and used internally, what problems am I going to face by creating a trust?
Can I create the trust without having the zone file for company.co.uk ?
What issues am I likely to face?
Thanks.
Windows Server 2003ExchangeActive Directory
Last Comment
Whiterat
ASKER
Hi KenMcF,
The AD FQDN is unfortunately company.co.uk .
It is a public facing server with an access list allowing everything between the 2.
Thanks.
The AD FQDN is unfortunately company.co.uk .
It is a public facing server with an access list allowing everything between the 2.
Thanks.
Then as long as the DNS server for "company.co.uk" has all the correct records and there is no NAT between the two domains you can create conditional forwarders on each and should be good if I understand your topology correct.
ASKER
There is NAT running on the new domain...
It is not supported to do a trust with NAT. Take a look at this thread and the links provided.
http://social.technet.microsoft.com/forums/en-US/winserverDS/thread/9dffd77b-6991-48bb-9ddf-6f6d605be594
http://social.technet.microsoft.com/forums/en-US/winserverDS/thread/9dffd77b-6991-48bb-9ddf-6f6d605be594
ASKER
:(
In which case can you think of a good way to perform the migration besides ExMerge ?
In which case can you think of a good way to perform the migration besides ExMerge ?
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
Ran out of time to test anything special, just ended up using exmerge
You said it has "company.co.uk" as the email doamin but not AD.
Also not sure what you mean by "Public addresses only", Do these servers have public IP addresses and are live on the internet? Is there a VPN tunnel or other connection between the two domains?
To setup the trust and provide DNS resolution I would create conditional forwarders in each Domain to point to the other.
http://support.microsoft.com/kb/304491