ProVal Tech’s Consultant Tobin goes over how to apply procedure via policy in your Kaseya VSA. Tobin uses the non-compliant view in the policy to schedule recuring procedures, create policies, and edit your procedures and policies. He also gives insight on how to set days and times in the week to distribute these procedures via policy.
Step by Step:
- Today I will show you how to use the non-compliant view in a policy to schedule a recurring procedure that will update Windows 10 to the latest build. The principles shown here can be used with any view and any agent procedure not just Windows 10 updates.
- First thing we’re going to do let’s navigate to policy management let’s navigate to policies.
- Select the folder that you want to create the policy in.
- Select add policy from the top, give your policy a name for this one I’ll do Windows 10 upgrade.
- Select ok to create and then select the policy itself once the screen loads.
- Now we can see we have the name description here we’re going to use the Windows 10 non-compliant view and the beauty of using this policy with this view is that as machines fall in and out of this view they will automatically be applied with this procedure.
- So if you add a new computer to your VSA and it’s running 1909 it will automatically fall in line with this view and we’ll apply this policy to the machine.
- So let’s select our agent procedure, add procedure, locate your procedure in your library, select it, and select add by selecting on it you can either remove or you can edit the procedure.
- So let’s go ahead and click edit and you have a couple of different options here for your recurrence you could do it once you could do it daily weekly. We’re going to do weekly we’re going to make sure that the schedule is based on the time zone of the agent that way if it’s set to run at midnight and the server is in a different time zone it will still run at midnight on the computer itself.
- We’re also going to set our distribution window I’m going to set it to 60 minutes this can vary depending on what the procedure is doing and how many computers you have in your environment.
- If you have a large amount of computers you may want to push this distribution window out even more so let’s go ahead and we’ll do every one week on Wednesday night. I’m going to do no end date to this because I want this to be perpetual I want this to continue as machines are added and removed from the environment.
- I’m also going to do skip if offline for this one and the reason being is because this Windows 10 procedure is going to cause the computer to reboot it’s going to take some time I don’t want that to queue up when the computer is turned on.
- If I uncheck skip offline the procedure will be queued if I have skip if offline checked the procedure will not queue it will check to see if that machine is online at that time and if it is not it will not view that procedure to the computer.
- Let’s go ahead and select schedule then at the top we’re going to do save and apply all right let’s select apply now.
- Then we need to put this policy into our org and machine group so that it can be assigned.
Let’s go down to assignment organization machine groups and I’m going to put this in the global organization because I do want this to be applied on every computer in the VSA.
- You could put this in a machine group or in an organization level if you wanted to but for this purpose of this procedure I want this to apply to all computers and I want to make sure that all these machines are being updated as much as possible.
- Let’s go ahead and expand our folder, select the policy that you’ve created, and let’s drag it over to global.
- So there’s our policy right here, now next thing we need to do is we need to make sure that this gets pushed to the machines that it’s to be applied to.
- So let’s select machines and here’s the machines that fall into that view let’s go ahead and right-click reprocess policies.
- Give it just a moment and what you want to do is you want to make sure that when you select the machine you want to make sure that you’re seeing that policy that you created down here under assigned to this machine by association with organization / machine groups.
- This is how you will know that it’s being automatically pushed to these machines.