none
How to force configuration refresh for Exchange 2010 Hub Transport Server RRS feed

  • Question

  • Hello,

    I've made some research about this issue but found nothing, so perhaps someone could answer me :

    Configuration : Two Exchange 2010 SP3 Servers (multi-role : CAS/HUB/MBX).

    I want to automatically enable/disable some transport rules, by scheduled powershell script. But when I enable/disable a rule, it takes several hours before those rules become effective on mail flow... As I need to be accurate on rule timing, it's a real problem.

    I've read and tested the "restart exchange transport service" method. OK... but as I have 10 rules to activate/deactivate daily, it seems very aggressive to restart echange hub service each time... 

    Could you tell me if it exists another "soft" method to force Hub transport service to refresh its configuration (rule configuration in my case).

    thanks in advance.



    mercredi 3 avril 2013 14:25

Réponses

  • C'est tout à fait normal sur Exchange 2010, une grande partie de la configuration obtenue de l'AD est mise en cache, dans votre cas le cache dont dépend vos règles si elles manipulent les destinataires se met à jour sur un intervalle de 4h.

    Each Hub Transport server maintains a recipient cache that is used to look up recipient and distribution list information. The recipient cache reduces the number of requests that each Hub Transport server must make to an Active Directory domain controller. The recipient cache updates every four hours. You can't modify the recipient cache update interval. Therefore, changes to transport rule recipients, such as the addition or removal of distribution list members, may not be applied to transport rules until the recipient cache is updated. To force an immediate update of the recipient cache, you must stop and start the Microsoft Exchange Transport service. You must do this for each Hub Transport server where you want to forcibly update the recipient cache.

    Source : http://technet.microsoft.com/en-us/library/bb124703(v=exchg.80).aspx


    Bruce Jourdain de Coutance - Consultant Exchange http://brucejdc.blog.free.fr


    jeudi 4 avril 2013 12:46
    Modérateur

Toutes les réponses

  • I've read and tested the "restart exchange transport service" method. OK... but as I have 10 rules to activate/deactivate daily, it seems very aggressive to restart echange hub service each time... Could you tell me if it exists another "soft" method to force Hub transport service to refresh its configuration (rule configuration in my case).

    I dont know of any, restart the service is the fastest way.


    Bruce Jourdain de Coutance - Consultant Exchange http://brucejdc.blog.free.fr

    mercredi 3 avril 2013 14:57
    Modérateur
  • Bonjour,

    ce qui n'est pas normal, c'est que la modification des règles prennent plusieurs heures à s'activer!

    Effectivement, le redémarrage du service est la méthode la plus utilisée, aucune perte de message n'étant à craindre.

    A bientôt,


    Thierry DEMAN. Exchange MVP. MCSE:Messaging 2013 (75 MCPs). https://mvp.support.microsoft.com/profile=CE2B565B-B13D-4C24-B04D-F0D5766D14A1 http://www.faqexchange.info

    mercredi 3 avril 2013 18:12
    Modérateur
  • Thanks all for your response... so I have to find why this hub transport takes so long to refresh its configuration...
    jeudi 4 avril 2013 12:21
  • C'est tout à fait normal sur Exchange 2010, une grande partie de la configuration obtenue de l'AD est mise en cache, dans votre cas le cache dont dépend vos règles si elles manipulent les destinataires se met à jour sur un intervalle de 4h.

    Each Hub Transport server maintains a recipient cache that is used to look up recipient and distribution list information. The recipient cache reduces the number of requests that each Hub Transport server must make to an Active Directory domain controller. The recipient cache updates every four hours. You can't modify the recipient cache update interval. Therefore, changes to transport rule recipients, such as the addition or removal of distribution list members, may not be applied to transport rules until the recipient cache is updated. To force an immediate update of the recipient cache, you must stop and start the Microsoft Exchange Transport service. You must do this for each Hub Transport server where you want to forcibly update the recipient cache.

    Source : http://technet.microsoft.com/en-us/library/bb124703(v=exchg.80).aspx


    Bruce Jourdain de Coutance - Consultant Exchange http://brucejdc.blog.free.fr


    jeudi 4 avril 2013 12:46
    Modérateur
  • ok merci beaucoup pour vos réponses.

    vendredi 5 avril 2013 08:07