1
00:00:03,240 --> 00:00:07,060
So that brings us to the end of this module on provisioning Always On VPN

2
00:00:07,060 --> 00:00:10,990
clients. Got quite a bit accomplished in this module if I don't say so

3
00:00:10,990 --> 00:00:14,950
myself. We set up some initial connectivity tests,

4
00:00:14,950 --> 00:00:17,620
we set up our test client, and again,

5
00:00:17,620 --> 00:00:22,180
configured that VPN profile manually. As a part of that

6
00:00:22,180 --> 00:00:26,360
profile validation, we, if you'll recall, that we made sure

7
00:00:26,360 --> 00:00:28,200
that all of our routes were in place,

8
00:00:28,200 --> 00:00:33,210
made sure that we configured the IPsec policy to align with the VPN server,

9
00:00:33,210 --> 00:00:37,000
don't forget that critical aspect. And, of course, the

10
00:00:37,000 --> 00:00:39,860
critical point here is that before you push this

11
00:00:39,860 --> 00:00:42,010
configuration profile out to the masses,

12
00:00:42,010 --> 00:00:43,380
we want to make sure that everything's working,

13
00:00:43,380 --> 00:00:46,430
we just built this new infrastructure and we want to make sure

14
00:00:46,430 --> 00:00:50,100
that everything's functioning as expected, so that's really the

15
00:00:50,100 --> 00:00:51,910
important process there. Also,

16
00:00:51,910 --> 00:00:56,180
it does provide you the ability to extract that EIP configuration that

17
00:00:56,180 --> 00:00:59,990
you're going to use when you deploy the settings using Intune, or whether

18
00:00:59,990 --> 00:01:03,840
you're deploying those using XML because you'll need that information to

19
00:01:03,840 --> 00:01:06,830
build out those profiles on either platform.

20
00:01:06,830 --> 00:01:08,930
And finally, you know,

21
00:01:08,930 --> 00:01:13,190
we took a look at the VPN provisioning options, as you saw. Intune is

22
00:01:13,190 --> 00:01:18,350
probably, Intune is definitely the best way to go, but it is certainly

23
00:01:18,350 --> 00:01:20,990
easier, and more effective, and more efficient, has the best

24
00:01:20,990 --> 00:01:24,680
administrative experience, it is the path of least resistance for you as

25
00:01:24,680 --> 00:01:29,160
administrators when provisioning and manage Always On VPN, definitely

26
00:01:29,160 --> 00:01:32,390
consider using Intune. But again, as you saw,

27
00:01:32,390 --> 00:01:33,800
it is not the only option,

28
00:01:33,800 --> 00:01:39,200
so you, if you plan to use something like SCCM, or PDQ, or any

29
00:01:39,200 --> 00:01:43,760
variety of non‑Microsoft systems management platforms that can

30
00:01:43,760 --> 00:01:45,940
push out PowerShell scripts effectively,

31
00:01:45,940 --> 00:01:50,970
then you certainly can take advantage of the PowerShell options with the XML

32
00:01:50,970 --> 00:01:54,630
configuration file and push those out using our tools,

33
00:01:54,630 --> 00:01:58,770
specifically the AOVPN tools PowerShell module and using the

34
00:01:58,770 --> 00:02:03,590
new AOVPN connection PowerShell function in that module. It

35
00:02:03,590 --> 00:02:05,120
will make your life a lot easier.

36
00:02:05,120 --> 00:02:05,840
And again,

37
00:02:05,840 --> 00:02:09,330
you can deploy both device tunnels and user tunnels using

38
00:02:09,330 --> 00:02:13,640
PowerShell, using the function in that PowerShell module.

39
00:02:13,640 --> 00:02:14,440
So moving on,

40
00:02:14,440 --> 00:02:21,000
let's get to the next module where we're going to talk about some advanced configuration options.