Okay.
So now let's deploy a startup script.
So I've got a GPO called Scripts Policy, and I'm going to go ahead and edit it.
And go in under computer configuration policies, windows, settings, scripts and I'll double click
start up.
And if I go show files, I've got this log on that file that I created in a previous example.
I'm going to go ahead and delete that since I'm creating a startup script here.
Actually I can't deleted from this location, so I'll go ahead and go to the add button.
I'm going to say browse and I can go ahead and delete it from here.
Now I'm going to create a new script called Startup Dot Bat, and I'm just doing this within the Explorer
browser because it's easy to do.
I could go ahead and do this from within the Explorer if I wanted to.
But the fact that it takes me right to the location in serviceable means it's easy for me to do this
up here.
Now what I'm going to do is I'm going to paste in a command and all this is doing is it's using the
red dot XY command to add a value to the registry.
Under HQ, I underscore local underscore machines, backslash software, backslash test app and the
value is called enabled.
And I'm setting it to one with the type of reg underscore D word.
And this is a good example because ordinarily a regular user would not be able to make a modification
to HQ.
I underscore local underscore machine.
They're permissioned away from that.
So I'm going to go ahead and save this batch file.
And then I'm going to select it by clicking open here.
And you'll see I've selected start up dot bat.
I don't have any script parameters on this particular script, but I could use that if I needed to.
So I've got my script.
I'm going to go ahead and click Apply.
And now, because this is a promising policy, what I'm going to do is I'm going to come up to the marketing
for you, which is where my computer account is, and I'm going to link that Scripps policy to the marketing.
Oh, you were my computer account is remember it's per computer, so I need to do that execution that
linking at the oh you that contains computer objects.
Okay.
So now what I'm going to do is I'm going to go to my Windows seven client and restart it.
Remember, I need a restart in order for the machine to actually pick up the script.
So I'm going to go ahead and do the restart.
And we'll see what happens when the machine comes back up.
Now my machine is coming back up.
So we're going to go ahead and see if we can see the execution of that script.
So it's applying computer settings.
And now you saw it flash by.
It applied scripts.
Now I'm logging back on to the machine and I'm going to go ahead and verify that I received that script's
policy by checking the registry to see if my registry entry made it.
So I'm going to go ahead into the registry editor.
And if I come in under HQ, underscore local underscore machine software there's my test app key set
to enabled with the value of enabled is set to one.
So my script was delivered.
Now remember I mentioned that you can use our soapie to get validation of some of this information.
Let's go back to my server and I'm going to show you a little sneak peek of what we're going to be talking
about in a later module around troubleshooting.
I'm going to go into the group policy results wizard.
And I'm going to collect against the Win7 client that I have in my domain that I just delivered a startup
script to.
And I'm going to say don't display user settings.
I'm just interested in the computer settings.
And once that report runs.
We'll go into details and we'll go down to Settings Startup and you'll see the last runtime is listed
here.
And so that tells me that the script actually ran and it was delivered by the scripts policy.
So I've got the capability of delivering startup scripts that can make changes to the system that users
can't make.
And I can verify that those are at least being delivered using results set of policy or group policy
results.