Seperate Synthetic Transaction configurations for each AD Site RRS feed

  • Question

  • If i have a AD site A and AD site B, is it possible to configure SCOM so that the synthetic transactions in site A only test servers in that site and the same with transactions in site B. What i dont want is testing from CAS in site A against mailboxes in site B. Is this possible?




    Regards, Rob
    Friday, February 25, 2011 5:25 PM

All replies

  • Hi Rob,

    Do you have an internet-facing and non-internet-facing CAS server, because I find you ask another question:


    Frank Wang

    TechNet Subscriber Support in forum

    If you have any feedback on our support, please contact tngfb@microsoft.com  


    Please 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.
    Monday, February 28, 2011 6:24 AM
  • Yes, there are two seperate CAS pools in seperate AD sites. One is internet facing and it proxies to another pool that is not internet facing.


    This question was more around seperating monitoring of prod and dr sites. What we are seeing is that if the testing of internal cas servers is used against a test mailbox in the DR site, the WAN latency of the transaction throws an alarm. So the desire is to ensure that synthetic testing for the prod site and the dr site is only done with CAS and the test mailbox in each site respectively. We want no testing to transverse the WAN link.




    Regards, Rob
    Wednesday, March 2, 2011 2:46 AM
  • We are having the same exact issue.  If anybody has insight into this that would be great.  MS?


    Monday, March 21, 2011 4:24 PM
  • * Exchange Monitoring such that synthetic transaction rules for Site A only run in Site A.
    * These transactions test latency between mailboxes in Site A and Site B.
    * This may be possible if we do not monitor any servers in Site B.
    * Are the servers in Site A and Site B a part of the same Exchange topology - Yes.
    * One is internet facing and proxies to a CAS pool.
    * One possibility that comes to mind is separate Management Groups in order to continue monitoring all Exchange servers.
    * Other option would be to not monitor the servers in Site B - not suggested.

    Ketan Thakkar | Microsoft Online Community Support
    Thursday, May 5, 2011 2:32 AM