One is a bit more hamfisted then the other. Last step can be done two different ways. Once the scans complete you will be able to see what machines have IE 11 and what don't by looking at the patch status section which will list installed patches, pending patches, missing approved, missing denied etc. The scans will take a little while depending on how many machines you're scanning so be patient. (It's a good idea to schedule weekly scans on machines you manage, feel free to set that up now too.) Go to the scan machine section (still in patch mgmt at the top). Once you have applied the patches to the appropriate machines, you are going to have to scan the machines in order for Kaseya to know what patches are missing from each machine. (So if you have a policy saying approve all explorer patches and another one that says deny all explorer patches, the denial trumps the approval.) If the policies conflict with one another the most restrictive policy always wins. Keep in mind machines can have multiple policies applied to them. Go to the membership section and apply the new policy to whatever machines you would like to update. But there is more that is needed to be done. Now you have a patch policy that has approved only IE 11 and all it's patches. (You need both asterisks in front of and behind explorer).Īpprove all IE 11 patches from that list. Filter explorer in the title section and click apply. On the next page click the "filter" button. Click the pending approvals section (the header not a specific category). Next, go to the approval by policy section and make sure you select your new IE 11 policy. Create a new patch policy called "ie 11" or something that makes sense. it should be, but it's convoluted and somewhat cumbersome.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
January 2023
Categories |