Looking for Closure in a Relationship with two DCs
Posted on 2013-01-01
I’m having difficulty retiring a failing GC / DC / Exchange Server (server1).
It’s running Windows Server 2003 with Exchange 2007 SP3. The hardware is failing and the server needs to be replaced. It’s a small business with 5 clients machines and a single server.
The replacement server (server2) is running Windows Server 2008 R2 with Exchange Server 2010 SP2.
I installed the replacement server; promoted it using DCPromo, set it up as a GC, transferred all FSMO roles, and enabled it as a DHCP and DNS server (and a WINS server for good measure since the clients are on XP). Ran adprep /forestprep from the Windows Server 2008 R2 CD on server1. There were no problems. The login scripts automatically were synced on both servers. I moved all the file shares and updated the login scripts to point to server2. Users logged into and their drive mappings all point to server2 now.
Then installed Exchange 2010 SP2 on server2. Moved the send and receive connectors from server1 to server2. Changed the router to send 80, 25 and 443 to server2. Moved all mailboxes. So far so good. Enabled Exchange to use server2 as the GC. Tested OWA and ActiveSync. Good to go at this point.
When I attempted to shut down server1, Exchange would not allow connections. Users could not log into the network unless they had a hard coded IP. Right away that pointed me towards DHCP as an issue, but the scope of server2 does not overlap with server1’s DHCP scope. DNS is also working fine. NSLOOKUP resolves to server2.
I have not actually done a DCPROMO on server1 to demote it to a member server in fear losing the domain, nor have I uninstalled Exchange 2007 on server1 to officially retire it. I have done this in the past and yet somehow I feel I missed something. Right now server1 is on life support. Server2 cannot function unless server1 is on.
Can someone help me figure out what I missed?