Windows Server Remote Access (Community)

AP.Remote.Access Management Pack

Install the Management Pack, a Profile will be created called "AP Remote Access Login", add a Login Account to this profiles and distribute to your Remote Access Servers, this should be a Domain Account that has rights to run the Powershell Command Get-RemoteAccess on the Remote Access Servers. Without this Account being correctly distributed Discovery won't happen! Don't forget if Running SCOM 2019 to give this account "Log on as a service" rights on the Remote Access Servers. Discovery Happens every 4 Hours, so be patient!

The Microsoft Management Pack only creates the Root Remote Access object and Sites if you are using Multisite, I have added a bit to the discovery script that will create a single site named your "ConnectTo" name if you aren't running Multi-Site this can be over-ridden on the Discovery, it's called CreateSingleSite, set this to false and behaviour reverts back to Standard Microsoft 2012.R2 Management Pack behaviour!

Windows Server Remote Access (RRAS) Management Pack for VPN and Direct Access

This MP is an adaptation of the Windows Server 2012R2 Remote Access Management pack. I basically took the WS 2012R2 MP, changed the discovery to be version agnostic, which has been tested with Windows Server 2012, 2012R2, 2016, and 2019, disabled all the event collection rules, and renamed a lot of the ID’s to be a bit more standardized.

This MP will discover and monitor all your RRAS servers on Windows Server 2012 and later.