Using PDQ Deploy to address Microsoft’s Security Advisory – June 2017

Security advisory? Didn’t we just go through this with WannaCrypt/WannaCry?! It just goes to show you, the job of a SysAdmin is never done.

Although not related to WannaCrypt, Microsoft has just announced a Security Advisory related to vulnerabilities that are at heightened risk of exploitation. For supported operating systems, the patches for these vulnerabilities are already included in our PDQ Deploy Package Library with the Monthly Rollup, Security-only Updates, and Cumulative updates packages. However, no longer supports Windows XP, Windows Vista, Windows 8, or Server 2003 and we no longer create packages for them. But, you didn’t think we’d leave you in a lurch, did you?

Creating your own packages

Even though we haven’t created packages for all operating systems included in Microsoft’s announcement, we do have detailed guidance on how to create your own packages for this very purpose. Please be advised any information pertaining to patching unsupported operating systems is provided, as-is. With that said, here are the steps you will need to create these packages on your own:

  1. Identify and download the desired patch(es) from the list of older platforms.
  2. Create package(s) as outlined in ‘Creating a Windows Update Package’.
  3. Test said package(s).
  4. Deploy at will.

Additionally, we provided instructions on how to create a Dynamic Collection in PDQ Inventory to identify computers that are missing a Microsoft KB patch. This can not only be used to identify computers with vulnerabilities, but be used as a target for deploying your new packages.

Additional Resources

For additional information from Microsoft, see also:

March Security Update for Older Platforms
Catalog of Updates for the above Security Update

2 responses

Your email address will not be published.

Your Name

This site uses Akismet to reduce spam. Learn how your comment data is processed.