setup... 1 Exchange 2007 server 3 2003 domain controllers Domain Controller 1 (DC1) is being retired but whenever I take the Global Catalog off of it Outlook stops working. I have verified that the GC is on the other two domain controllers. I also put one of the domain controllers that is staying as the primary DNS of the Exchange server and rebooted. The Exchange services will not start if the GC is off on DC1. I looked through DNS and see that the two remaining DC's are listed as GC's I am running out of ideas and wanted to ask the forum before I bit the bullet and called Microsoft. Any suggestions/ideas would be appreciated. Thanks

Run this on your Exchange Management Shell , So that It will Look for anyother GC. We are not Hardcoding here. First Prefrence would be someother GC. Set-AdServerSettings -PreferredGlobalCatalog gc1.contoso.com http://technet.microsoft.com/en-us/library/dd298063.aspx Satheshwaran Manoharan | Exchange 2003/2007/2010 | Blog:http://www.careexchange.in | Please mark it as an answer if it really helps you

"set-adserversettings" is not recognized as the name of a cmdlet That is an Exchange 2010 cmdlet, this is Exchange 2007

I also tried right clicking on Organization Configuration and then Modify Configuration Domain Controller with the same result. When DC1 has the GC removed Exchange breaks.

Hey Sorry Swinney. Its AdminsessionSettings in Exchange 2007 The Below Link Should help http://exchangeserverpro.com/how-to-use-a-specific-domain-controller-in-the-exchange-2007-management-shellSatheshwaran Manoharan | Exchange 2003/2007/2010 | Blog:http://www.careexchange.in | Please mark it as an answer if it really helps you

http://technet.microsoft.com/en-us/library/bb123716(EXCHG.80).aspx http://searchexchange.techtarget.com/tutorial/Set-ExchangeServer-cmdlet-can-ease-domain-controller-workloads Set-exchangeserver -staticglobalcatalog ... should help

Thanks I will try and post the results

The set-exchangeserver cmdlet would not work at all. It would not change any values in AD nor did it error. After going through every aspect of Exchange and the OS I noticed that someone IPv6. Once I enabled that Exchange started to function normally and would switch to any operational GC.

The set-exchangeserver cmdlet would not work at all. It would not change any values in AD nor did it error. After going through every aspect of Exchange and the OS I noticed that someone IPv6. Once I enabled that Exchange started to function normally and would switch to any operational GC.