Hello, and welcome again to Pluralsight.
This is Implementing Microsoft Always On VPN.
And in this module,
we're going to move on to provisioning our Always On VPN clients.
So at this point, we're ready to begin pushing out the client configuration.
But before we do that, we need to do a couple of rather crucial things here.
First, we need to perform some validation testing.
So we've built out the VP and infrastructure,
we have the NPS server setup, we have our VPN server set up,
but we need to know that this is all working correctly before we
start pushing out software settings to our clients.
And so what we're going to do is we're going to create a test VPN profile
on a client and configure it manually and then perform,
again, some validation testing.
We're going to make sure that we can connect to the VPN server,
make sure that we can authenticate, and,
importantly, access internal resources over the VPN,
make sure that our routing is working, and so forth.
And once we've done that, once that's successful,
then we'll move on to provisioning these client
configuration settings using Intune. Intune is the solution
of choice for managing Always On VPN.
It is not the only solution though, and there are other options as well, and
we're going to explore those too by deploying Always On VPN using PowerShell.
We'll use a PowerShell script and an XML configuration file, and I'll
demonstrate how to do that and what those use cases are for deploying Always
On VPN using PowerShell and, importantly, what some of the limitations of using PowerShell are.