I currently have an exchange 2007 server and an exchange 2003 server. The 2003 server runs active directory,the 2007 server doesn't. I would like to demote the 2003 box remove active directory and retire the server. The problem is I can't get the 2007 box to use any Global Catolog Server except the 2003 box.All servers run Server 2003 sp2 all patches up to date . There are 2 other DC's both configured as Global Catalog Servers. It's a single forest domain.I've tried various suggestions, remove the gc role from the 2003 box, delete the dns entry for the 2003 gc, flush the dns cache on both servers, reboot both servers, waited 12 hours for replication, forced replication, added the registry entry to statically assign a specific gc server. All without success. Everytime I change the gc for the 2007 box, the Information Store service refuses to start and writes to the event log that it is unable to find any available global catalog servers even though it lists the other 2 gc in the error.Any and all help will be appreciated.Thanks

How are you trying to get the Exchange server to see the new GC? Are you using the cmdlet 'Set-ExchangeServer'? There is a switch in the cmdlet to statically set the GCs. Rob

Hello,I've tried every method i can find. I've set the GCs statically in the registry. through users and computers ntds settings,through both the exchange 2007 gui and the powershell.if I change it through the powershell or the gui, it drops the old gc but never finds the new one. all users are disconnected from the exchange server. i've tried to point the 2007 box to a different gc and then waited 12 hours. checked the settings and the gc setting on the 2007 server is empty.so far it will see the 2003 exchage server as the only gc on the lan.Thanks

Is there anything stopping you from moving all mailboxes to Exchange 2007 and removing the Exchange 2003 software from the DC/Exchange 2003 server? There are two reasons I say this: 1. Microsoft doesn't support running dcpromo to change the AD role on a server with Exchange 2003 on it. It's known to break some Exchange components but I wonder if there are bigger issues here. 2. Exchange on a DC is a bad idea because the local Exchange installation will only ever use the DC that is also installed onto that box. I'm also wondering if this somehow affects the Exchange 2007 server. Therefore, by removing the Exchange 2003 software and rebooting you leave it as a DC only. I'd be interested to know if this makes any difference if you go down this route.

I installed AD on the exchange 2003 when I first put it on the network several years ago. The Exchange 2007 doesn't and won't run AD. I am hoping to use the Exchange 2003 server as an archive server, a place to keep mailboxes of employees who have left the company but who's mail still needs to be accessed occasionally. Can I uninstall AD from the Exchange 2003 box? If I move all the mailboxes and uninstall Exchange 2003 then demote the box to a member server, are there any problems reinstalling exchange 2003? I also want to look into clustering the 2 exchange servers together to create a redundant failover. Thanks

Sorry, but you've confused me. If you want to reinstall E2K3, why are you mentioning looking into clustering the two servers together? They'll be running different versions of Exchange. Also, I'm not sure you'll be able to reinstall E2K3 on a server in an organisation that contains an E2K7 server. If you're looking at E2K7 clustering, then be aware that the CAS and Hub Transport roles cannot coexist on the same box as the Mailbox server role that you're clustering. You'll need additional hardware to achieve your goal.