08-14-2023 04:28 AM - edited 08-14-2023 04:32 AM
Hey Folks,
Hope you had a great summary holiday - says a guy lives on a sunny island with eternal summer (minus the holiday, of course) 😂.
Apologies for the delay. Let’s dive back into our topic.
Since we gained the overall patching visibility in part 1, it's time to take action on those outdated systems.
TL;DR
Get the script here - this time, it’s PowerShell 😀.
The idea is - create a group for the outdated systems, attach the patch policies, and let the enforcement take over.
- Powershell 7+
- Jumpcloud powershell module
- OS: MacOS, Windows, Linux
- Use an API key from a JC admin with at least JC manager permission.
- Create or get the most aggressive patch policy IDs for respective OSes.
$outdatedSystems = Import-csv "/the-path-to/outdatedSystems-2023-08-14.csv" # The CSV exported from Patch Dashboard step 2
$apiKey = '' # Your JC manager admin API key
# Create or provide the most agressive patch policy IDs for respective OSes
$winPolicyID = 'winPolicyID'
$macPolicyID = 'macPolicyID'
$linuxPolicyID = 'linuxPolicyID'
P.S. If there are “long-term residents” lingering after a period (typically 7+ days), consider using JC cmd for targeted-enforced updates. I highly recommend reaching out to the end user before taking action to avoid potential disruptions when the device reboots. For example:
I’ve kept this part manual as the user communication is crucial - We definitely don't want unexpected device reboots in the midst of important tasks.
And that’s it folks, have a great start of your week!
New to the site? Take a look at these additional resources:
Ready to join us? You can register here.