Sign in
 
Exchange Server TechCenter > Exchange Server 2010 Forums > Exchange Server 2010 > Edge Server keeps reverting settings
Ask a questionAsk a question
Search Forums:
 

QuestionEdge Server keeps reverting settings

  • Tuesday, November 03, 2009 10:58 AMAmelsfort Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    I'm running Exchange 2010 with only the Edge Transport-role on a Windows 2008 R2-server. When I change some settings (from the console or with the shell) I can see it's been changed. However, after a little while, the old settings are back!

    Even when I try to remove a receive-connector or the Edge-subscription, it's changed back after a little while.

    One other thing: this server was my DC a while ago, but I moved everything to another server and demoted this one. Now Exchange is still referring to this server as the DC. When I try 'Set-OrganizationConfig -DomainController <new server>', the command hangs. It never gives me any information, just hangs.

    Could someone explain this behaviour?
     

All Replies

  • Tuesday, November 03, 2009 11:06 AMMilind Naphade Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    Hello There.

    Do you see any log entries in application log while you try to change anything? Also, when you modify any setting using powershell make sure you enable verbose logging and via EMC use the shell logging feature to see what is the output.
    Milind Naphade | MCTS:M (Exchange 2007 and 2010) | http://www.msexchangegeek.com RSS Feed
     
  • Tuesday, November 03, 2009 12:50 PMAmelsfort Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    When removing the edge-subscription, I get the following events:
    1. (PID 1352, Thread 6) Task Remove-EdgeSubscription successfully removed object '<server>' of index 0.
    2. The Attachment filtering configuration was loaded.
    3. A configuration update for Microsoft.Exchange.Transport.TransportSettingsConfiguration has successfully completed.
    4. A configuration update for Microsoft.Exchange.Transport.TransportServerConfiguration has successfully completed.

    But then, after 34 second, I see:
    5. (PID 1352, Thread 13) Task Get-EdgeSubscription activating Provisioning Cache.
    6. A configuration update for Microsoft.Exchange.Transport.TransportServerConfiguration has successfully completed.
    7. A configuration update for Microsoft.Exchange.Transport.ReceiveConnectorConfiguration has successfully completed.
    8. A configuration update for Microsoft.Exchange.Transport.ReceiveConnectorConfiguration has successfully completed.
    9. A configuration update for Microsoft.Exchange.Transport.ReceiveConnectorConfiguration has successfully completed.
    10. A configuration update for Microsoft.Exchange.Transport.ReceiveConnectorConfiguration has successfully completed.
    11. A configuration update for Microsoft.Exchange.Transport.ReceiveConnectorConfiguration has successfully completed.
    12. Forefront TMG detected changes in Microsoft Exchange Server or Microsoft Forefront Protection configuration, and reapplied the e-mail policy configuration on server '<server>'.
    13. (PID 1352, Thread 18) Task Get-EdgeSubscription deactivating Provisioning Cache.

    Event #12 is an error, all others are informational.