So to summarize what we've learned about Scripps in group policy.
Scripts come in two flavors.
There's the computer start up and shut down scripts and for user, log on and log off scripts.
And you know, as I have mentioned, the role of scripts and the things that people have used scripts
for in the past have largely been usurped by group policy preferences.
But scripts still have a role if you're needing to perform complex logic.
So if you need to do conditional testing, if you need to do things that are just simply not available
in group policy preferences, then scripts still probably have a role.
But again, remember that scripts are only as good as you write them in terms of logging and logic to
ensure that they don't run when they don't need to.
So all of those things sort of mitigate the value of scripts unless you can guarantee that they're doing
the right things.
And again, they are a big source of slow down in complexity in an environment.
If you don't have good logging or good script execution testing going on because they're kind of a black
box.
You saw how I showed you the group policy results data that shows at least that the script executed,
which is at least something.
But it doesn't show you at all what happened during script execution.
So you only see the results of it.
And then as of Windows seven and higher versions in Server 2008 or two and above, scripts can now include
PowerShell and PowerShell scripts, you know, can have their own tab and can run in addition to regular
scripts.
One thing to note about PowerShell scripts is that the execution policy, by default on a Windows system
out of the box is set to restricted, which means that you have to sign the script in order for it to
run.
So if you need a different execution policy and this is going to affect log on and startup and shutdown
and log off scripts as well.
You're going to need to set the execution policy before you put your PowerShell scripts into group policy.
And then finally there's some script execution options and admin templates that I showed you that can
control everything from that maximum wait time to whether log on scripts, run synchronously, restart
up scripts, run asynchronously.
So you have some options there in terms of controlling script execution.
So as I mentioned in the next module, we're going to cover kiosk scenarios and so-called loopback processing.
So let's dive into that.