1
00:00:03,070 --> 00:00:07,240
So to summarize what we've learned about Scripps in group policy.

2
00:00:08,200 --> 00:00:10,210
Scripts come in two flavors.

3
00:00:11,210 --> 00:00:16,700
There's the computer start up and shut down scripts and for user, log on and log off scripts.

4
00:00:17,670 --> 00:00:22,080
And you know, as I have mentioned, the role of scripts and the things that people have used scripts

5
00:00:22,080 --> 00:00:26,190
for in the past have largely been usurped by group policy preferences.

6
00:00:27,170 --> 00:00:31,310
But scripts still have a role if you're needing to perform complex logic.

7
00:00:32,310 --> 00:00:37,440
So if you need to do conditional testing, if you need to do things that are just simply not available

8
00:00:37,440 --> 00:00:41,310
in group policy preferences, then scripts still probably have a role.

9
00:00:42,270 --> 00:00:47,850
But again, remember that scripts are only as good as you write them in terms of logging and logic to

10
00:00:47,850 --> 00:00:50,220
ensure that they don't run when they don't need to.

11
00:00:51,090 --> 00:00:56,310
So all of those things sort of mitigate the value of scripts unless you can guarantee that they're doing

12
00:00:56,310 --> 00:00:57,270
the right things.

13
00:00:58,230 --> 00:01:02,880
And again, they are a big source of slow down in complexity in an environment.

14
00:01:03,860 --> 00:01:09,320
If you don't have good logging or good script execution testing going on because they're kind of a black

15
00:01:09,320 --> 00:01:09,830
box.

16
00:01:10,810 --> 00:01:16,780
You saw how I showed you the group policy results data that shows at least that the script executed,

17
00:01:16,780 --> 00:01:18,160
which is at least something.

18
00:01:19,080 --> 00:01:23,010
But it doesn't show you at all what happened during script execution.

19
00:01:24,000 --> 00:01:26,280
So you only see the results of it.

20
00:01:27,250 --> 00:01:33,790
And then as of Windows seven and higher versions in Server 2008 or two and above, scripts can now include

21
00:01:33,790 --> 00:01:39,550
PowerShell and PowerShell scripts, you know, can have their own tab and can run in addition to regular

22
00:01:39,550 --> 00:01:40,060
scripts.

23
00:01:41,030 --> 00:01:47,240
One thing to note about PowerShell scripts is that the execution policy, by default on a Windows system

24
00:01:47,240 --> 00:01:52,400
out of the box is set to restricted, which means that you have to sign the script in order for it to

25
00:01:52,400 --> 00:01:52,820
run.

26
00:01:53,780 --> 00:02:00,140
So if you need a different execution policy and this is going to affect log on and startup and shutdown

27
00:02:00,140 --> 00:02:01,820
and log off scripts as well.

28
00:02:02,800 --> 00:02:08,800
You're going to need to set the execution policy before you put your PowerShell scripts into group policy.

29
00:02:09,750 --> 00:02:15,270
And then finally there's some script execution options and admin templates that I showed you that can

30
00:02:15,270 --> 00:02:20,580
control everything from that maximum wait time to whether log on scripts, run synchronously, restart

31
00:02:20,580 --> 00:02:22,410
up scripts, run asynchronously.

32
00:02:23,370 --> 00:02:27,540
So you have some options there in terms of controlling script execution.

33
00:02:28,520 --> 00:02:35,120
So as I mentioned in the next module, we're going to cover kiosk scenarios and so-called loopback processing.

34
00:02:36,080 --> 00:02:37,730
So let's dive into that.