Once the VPN infrastructure is in production and users are actively
using the system to access on‑premises resources,
monitoring things like system health and user activity is critical.
Administrators have a number of tools at their disposal to perform these tasks.
First, there is the Routing and Remote Access Management console,
and this is the console that we've been using throughout this course thus far
and you should be intimately familiar with it at this point.
The Routing and Remote Access Management console is
really ideal for configuration tasks, but in my opinion,
it's less well‑suited to daily operational use as you'll see here shortly.
However, it does have its own advantages,
and we'll talk through this in detail in the next demonstration.
Next, there is the Remote Access Management console,
so this is subtly different, but similar.
This is another GUI console that if your a direct access
administrator you'll already be familiar with,
but it is a more modern version of the RRAS Management console,
and in my opinion is a better choice for daily administrative tasks.
It's not a perfect tool, however,
and it does have its own limitations which will explore here shortly.
Finally, there is PowerShell.
Now,
PowerShell is ideal for any monitoring reporting tasks that require automation.
There is a lot of information that can be accessed using PowerShell,
and it also has the advantage of being able to perform these
tasks remotely and across multiple servers which can really be
helpful in larger deployments.
Using PowerShell is also helpful for pushing data to other systems, for example, SIM solutions like Splunk or other data repositories as well.