So to test this VPN connection, there's a couple of different ways to do it,
but I actually like to do it right through UI,
and we can do that very quickly by just clicking on our
Test session and then clicking Connect.
And it probably goes without saying,
your device needs to be on the public internet or not
on your internal network because, obviously,
we want to test this from the outside.
So, I'm going to go ahead and click Connect.
I've already connected this laptop to an external
network, it's not on my lab network anymore,
so we'll click Connect.
And if everything went well and according to plan,
we should see a Connected status here.
That means that the VPN connection is established,
properly authenticated, there were no issues,
and the connection is up.
We can look at this connection using PowerShell.
We use the Get‑VpnConnection command,
and you should see that the connection status shows as Connected.
Great.
But that doesn't really do a whole lot for us other than tell us that
at least part of the configuration is successful.
We're able to get to it from the internet and authenticate, we
really need to see if we can get to some resources.
So let's go ahead and ping some internal resources.
I'm going to go ahead and ping my domain controller now.
That looks good,
and you'll see that it responded using IPv6, let's make
sure IPv4 routing is working as well.
Fantastic.
And name resolution is working because I'm pinging these by their hostname.
Now let's make sure that we can get to a file server without being prompted for
authentication because that's obviously critical as well.
Looks fantastic.
Now let's move a file.
I have a random folder here with some random binary files.
We'll just drag one of those over the desktop, and looks
like file transfer is working good.
So fantastic.
It looks like we have a successful VPN connection
at least with the SSTP protocol.
So,
let's go ahead and disconnect and let's make sure our IKEv2 is
working with device certificate authentication,
which is basically going to be simulating our device‑based connection.
So here I'm going to go back to the VPN control panel here,
and then we'll choose Disconnect.
And now I want to make another change,
a quick change to this Test profile, so I'm going to right‑click,
choose Properties.
And here I'm going to go to Security, so we tested SSTP with EAP authentication,
this would simulate the parameters or the configuration settings for
our user tunnel. Now I want to test what would essentially or
effectively be a device tunnel connection.
So I'm going to switch to IKEv2,
and then I'm going to switch to using a machine certificate for
authentication, so I'm going to click OK. And now I'm going to launch this
connection once more, and we're connected successfully. So once again,
let's just make sure that all of the routing is in place and it looks like
everything's working according to plan.
So great news, we validated our connection,
so we can start preparing to deploy this configuration broadly.
But before we proceed, we need to get our EAP configuration file extracted here.
Now,
essentially what we're looking at here if we look at our
adapter properties, and by the way,
I want to go back and change the settings here before
we do this. Change the settings,
go back to Security, and switch back to Extensible Authentication Protocol
because all of this information we need to export to an XML file. And to do
that, you'll install the AOVPN tools module.
And, of course,
I've already done that on this test client. We can see
that we have the module installed here.
So,
the command that we want to run and the function that we
want to use is Get‑EapConfiguration.
So we're going to run the command Get‑EapConfiguration,
and then we're going to specify the connection name,
which was simply test.
Again, if you're using spaces in those names,
you'll have to provide that name in quotes.
So once that's done, it saves that file out to a file called eapconfig.xml,
so let's take a quick look at that.
And there it is,
all of the EAP configuration that we clicked and typed into those windows
earlier, all saved in an XML file, and this file you will need when we get to
the step where we start creating our Intune profiles.
Intune is going to ask us for this information,
so go ahead and save this somewhere that you can reach it,
and then we'll press on with configuring our VPN device configuration profiles in Intune.