In this next demonstration,
I'll show you how to configure high availability for your VPN infrastructure.
So we'll begin by exporting the VPN server
configuration from our existing VPN server,
and to do that, I'm going to open up the PowerShell command window,
and the command to do that is just simply netsh.exe ras dump.
Now if I just hit Enter here,
it just outputs it to the screen and that's obviously not helpful for me.
So I want to do an up arrow and I want to pipe this to
the Out‑File PowerShell command, and then I'll specify a FilePath,
and then finally, I need to add the encoding type as ASCII.
Now you might be asking yourself why would you do that.
If I were to leave that off, and actually,
I'll just demonstrate that real quick.
If you leave that off, what you'll see is that the file format is in UTF‑16,
and bizarrely, this is not a supported file format for import.
So if I were to try and import this file as it stands now,
it would actually fail.
So you, as the administrator have two options.
You can actually just do File, Save As, and then set the encoding type to UTF‑8,
and then of course, we'll overwrite the file and now it's in the correct format.
The other option here is just to simply add that
encoding in the PowerShell output as ASCII,
and now you'll see that the encoding type is actually correct.
So once that's done, we're going to copy this file over to our new VPN server.
So here we are on our newly prepared VPN server,
and it's important to state that this VPN server should be configured as
identically as possible to your existing VPN server,
recommended to use the same version of Windows server.
If it's joined at the domain, you want to match that.
If you're using one or two network interfaces,
you'll want to make sure that those align as well.
And then finally,
you want to make sure that your network interfaces are
named the same across your VPN servers.
And then once we've done that,
we need to make sure that we have our certificates in place.
So let's open up the local computer certificate store,
and here, you'll see that I've already installed my public SSL certificate,
so you see I have the certificate and the private key there,
and I've also enrolled my IPsec certificate for IKEv2, so that certificate is installed as well.