Hello, I've just installed a new exchange 2010 in an environment, and when I make change to EMC it may take a couple of hour before the change show up in EMS, and same thing if I make change in EMS it will take long time to show up in EMC. Does anybody know why? I have other exchange 2010 setup in other environment and never had this problem. For example yesterday night I've create a new send connection using PowerShell, and it only showed up this morning in the Management Console. Thank ML

Both the Shell and the Console read information from Active Directory. If there are perceived delays, it may be simply that you need to refresh the screen. If there are real delays, they are probably due to Active Directory replication delays. It's hard to respond to specifics when you provide only generalities, so post the precise steps you are taking and exactly what you see if you want a better answer.Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

I will be happy to provide more information but here is what I have... let me know what you want precisely I open exchange powershell I do new-sendconnector with the proper parameter I do get-sendconnector, my new connector is listed I go to Exchange Manangement Console under Hub Transport/Send connector. Hit refresh. The new send connector will not appear. It will take at least 2 to 3 hours before it show up

A connector is stored in Active Directory as an object in the connectors container and both EMC EMS retrive information from there. So I suspect there is something wrong in your AD. I would investigate in that direction too

Any suggestion where to begin looking? BTW it does the same thing for other setting like receive-connector Thank ML

Check your AD replication health.Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

AD Replication is fine. I've done the test on 2 other servers (different environment) and the same happen. Change make from EMC will take some time before it's apply, and won't show up before a while in PowerShell. It seem that EMC change are queue somewhere, and then are process. However it seem that PS is immediate. For example if I change the HELO host name in a receive connector in powershell then telnet on the server, I will see the change immediately. If I do the same thing in EMC, it will take some time before it happen. ML

Run DCDIAG on your domain controllers.Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Dcdiag is clean, all test pass

Hi Do you run set-exchangeserver -staticdomaincontroller and –staticglobalcatalog to use specified Dc and DC? You can read this article. http://social.technet.microsoft.com/Forums/en-US/exchangesvradmin/thread/b7ae01be-a585-4357-a9b4-ad28f051b0a4Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Hi, Just tried it and no result. Is there a way to validate which DC is used for either EMC or EMS? Also if I do get-exchangeserver -DomainController exmo01.bio-amber.com | fl I get StaticDomainControllers : {} StaticGlobalCatalogs : {} StaticConfigDomainController : StaticExcludedDomainControllers : {} CurrentDomainControllers : {} CurrentGlobalCatalogs : {} The command I've issue was Set-ExchangeServer exmo01 -StaticDomainControllers exmo01.bio-amber.com -StaticGlobalCatalogs exmo01.bio-amber.com. Is there a delay for that command to be effective? I've even restart the service to see if it make any change. Thank ML

Hi, Think I've found the problem. Using EMC, Right-Click on either Organization or Server Configuration and i've selected a specific DC to use. Now change are seen immediately in both EMC and EMS. THank ML

That confirms that you have a problem with replication! If the changes aren't replicating between domain controllers in a few minutes, then your replication is slow. You didn't say whether these two servers are in different sites or not, but you might check to see if your replication interval is a couple of hours or something like that.Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

As I wrote in my first post, there should be something unespected in you AD replication. I guess it doesn't prevent your AD to work but you might experience latency when change other objects in your AD too. Please also run dcdiag with all options to test dns if you have ad integrated zones.

dcdiag is fine on all dc, What I suspect is that EMC is not taking a DC in the same site, which may slow down the replication. I should have to validate the precise delay it take to see if it matchup with the replication delay of remote site, but it's probably. What I will be curious is to see which DC the EMC is using when you don't specify one, to make sure it use one in the same site ML

If EMC is talking to a DC in the wrong site, then you should check your AD sites and subnets to ensure that all your subnets are in the correct sites.Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

They are, I'm just supposing that it's not taking in the proper site since there is no way to validate and replication take a long time for the EMC to replicate to local DC. ML

I maintain that they're not if what you're saying is happening.Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."