I have been receiving LDAP Search Time - sustained for 5 minutes, warning from our operations manager server concerning our exchange server. Upon further investigation I noticed that the exchange server was attempting to perform LDAP queries to a domain controller in a different site then the actual exchange server is located on, although I do have a global catalog server on the same site as the exchange server. I logged into that exchange server and noticed alot of latency of the mpls line connecting our 2 offices. Since the dc that the exchange server was making ldap requests is in a different site, and since their was so much latency on the line, this caused the ldap search requests to time out. What I am really looking to do is to change the DC or GC that the particular exchange server in question points to. I was going to use the modify domain controllers from the action menu of server and or organization configuration, but as I understand it, this will change the DC or GC for the whole exchange organization, which I do not want to happen since we have more then one exchange server at different sites. I just want to correct the problem for the one server in question as the other servers are on the same site as the DC exchange is configured to access. I did some research and saw the command set-exchangeserver, but I have a few questions before I implement the command.First could this command be run such that it only affects one of my exchange servers and not all of the exchange servers in the organization? Which option would be the correct option for affecting the ldap search query the global catalog, or the domain controller? Shouldn't the exchange server by default only perform an LDAP search on the gc in the same site as it is?

I would suggest you to check below thread before setting static DC/GC with Set-ExchangeServer... http://social.technet.microsoft.com/Forums/en-US/exchangesvrmonitoring/thread/2940a261-7658-4c58-ae3d-ab01e27c3c18 Amit Tank | MVP Exchange Server | MCITP: EMA | MCSA: M | http://ExchangeShare.WordPress.com

Thanks for the fast response. It is true that we do have a public folder configuration that is only available in our exchange server in the other site. The only reason for this public folder is for our BES server to communicate with the GAL. With that said, the reason the public folder, and the information store for that matter are off on the server in question is because it is a DR server. We use an application called double take to perform the replication, instead of exchange scr. Double take requires that the information store is off. Is their a way to force the server to look locally instead of querying our other site. Greg

I installed the latest management pack. Will that help prevent my server from querying to the other site? If I run the set-exchangeserver command could that force it to only scavange dc's in the local site?

Well, I understood that you have thissituation, but that was for Exchange 2003 and a fix was avialable so not sure if this applies to Exchange 2007 also, checkout the registry mentioned in the link. May be this is not Exchange issue because if you track the ldap call from Exchange servers with NetMon you may get proper idea where these calls are going. I feel that SCOM LDAP search rules need to betweaked and you may try posting this in SCOM newsgroup to get help for setting override for this rules. SCOM NewsGroup:http://technet.microsoft.com/en-us/opsmgr/bb839593.aspx Of course you can point local DC and GC for Exchange server byspecifying it in Set-ExchangeServer cmdlet but that will make your Exchange serverhandicap becausewhen DC/GC goes down, Exchange will not able to search additional DCs/GCs... Set-ExchangeServer "ExchangeServerName" -StaticDomainControllers DC1,DC2,DC3 -StaticGlobalCatalogs GC1,GC2,GC3 Set-ExchangeServer http://technet.microsoft.com/en-us/library/bb123716.aspx Amit Tank | MVP Exchange Server | MCITP: EMA | MCSA: M | http://ExchangeShare.WordPress.com

If I do run the command at the bottom of your post, can I undo that command? Basically I just want to stop the messages for right now, and start them back up when we add bandwidth to our point to point connection.

Sure, you can with below cmdlet to remove static DCs/GCs... Set-ExchangeServer "ExchangeServerName" -StaticDomainControllers $Null -StaticGlobalCatalogs$NullAmit Tank | MVP Exchange Server | MCITP: EMA | MCSA: M | http://ExchangeShare.WordPress.com

I ran this command and it worked like a charm no more messages.