Lync 2013 Remote Watcher MP issues and solutions RRS feed

  • General discussion

  • This MP must easily be one of the trickiest to get working.. Mostly since the Lync setup required is tricky by itself..
    Note - the following was done with the Lync MP 5.0.8308.0 on SCOM 2012 SP1 UR4 using Windows Server 2012 as watcher nodes.

    Authentication for the transactions
    As our users/clients are in a different domain as the Lync servers we initially tried to set up watcher nodes in the user/client-domain using credential authentication. After tons of troubleshooting we finally gave this up as it just wouldn't work. Even with regular user accounts that would otherwise work. Even if performed on the FrontEnd Lync servers.
    Using the TrustedServer variant worked right away though.. Not an MP issue, but close in nature.

    The ABS / ABWQ queries fails due to watcher node computer account permissions
    The computer account for the watcher node had to be a member of the RTCUniversalReadOnlyAdmins AD group. When placed there and rebooted this test started working. There were nothing on this in the documentation.

    The MP Date/Time issue
    This MP has the most silly of bugs - the time/latency calculation that is used when creating events in the event log requires the Time/Date setting of the entire system (on which the SCOM agent runs) to be set to US English.
    If set to an EU/ISO value the latency is calculated to be ex. 900.000 seconds for a 30 sec transaction..

    I hope this is of help to others.

    • Edited by JonRunheim Wednesday, November 20, 2013 7:12 AM
    • Changed type Niki Han Wednesday, November 20, 2013 9:31 AM sharing
    Tuesday, November 19, 2013 4:15 PM

All replies

  • Thanks for sharing so much valueable solutions. I appreciated your efforts.

    Niki Han

    TechNet Community Support

    Wednesday, November 20, 2013 9:32 AM