Content in the ESU Patching Add-on for Windows 2012 site has been added.
ESU Key Management: Install and Activate MAK - Windows Server 2012 and Windows Server 2012R2
ESU Key Management: Deactivate and Uninstall MAK - Windows Server 2012 and Windows Server 2012R2
ESU Key Management: Synchronize Client Setting to WMI - Windows Server 2012 and Windows Server 2012R2
ESU Key Management: Add Client Setting to Minimize WMI Usage - Windows Server 2012 and Windows Server 2012R2
ESU Key Management: Remove Client Setting to Minimize WMI Usage - Windows Server 2012 and Windows Server 2012R2
Deploy Pre-Requisites for Installing Windows 2012 ESU Keys
Reason for Update:
Providing fixlets to automate installation/activation and uninstallation of MAK-based ESU keys, and fixlets to minimize use of the WMI query that checks ESU key status on systems using a MAK.
Patch fixlets will follow beginning on 14 November Patch Tuesday.
Please contact your BigFix representative for access to this Fixlet content.
Actions to Take:
None
Published site version:
ESU Patching Add-on for Windows 2012, version 4
(Site republished to include all announced content)
We just activated and enabled Win2012 ESU and the external site gathered at version 6 but the included prep baseline is referencing superseded fixlets:
Anyone else see this/is this a general issue? Do we need to copy and fix the baseline ourselves?
The KBs referenced in the prereqs are all superseded in the Patches for Windows site. The servicing stack updates were superseded by other servicing stack updates, so we just followed the supersedence path for those and included those in the baseline. The licensing preparation updates were superseded by monthly OS rollups, though, so we manually altered the license prep fixlets in the baseline to remove the supersedence relevance and also included the last pre-ESU monthly OS rollups.
TL;DR: the licensing prep fixlets in the baseline differ from the source fixlets because they’re not superseded. So you should be able to use the baseline as is.
We are/were late getting licenses sorted. As a result things were a bit unclear since the ESU site purpose and this process “started” last month. Much of the required content is already installed under our standard patching activities so we are in very good shape.
The handful of servers remaining in scope were likely excluded from patching or had issues.