{"id":13132,"date":"2020-02-12T23:45:01","date_gmt":"2020-02-12T22:45:01","guid":{"rendered":"http:\/\/159.69.82.204\/win\/?p=13132"},"modified":"2021-01-24T11:58:07","modified_gmt":"2021-01-24T10:58:07","slug":"windows-7-esu-questions-and-more-answers-part-4","status":"publish","type":"post","link":"https:\/\/borncity.com\/win\/2020\/02\/12\/windows-7-esu-questions-and-more-answers-part-4\/","title":{"rendered":"Windows 7: ESU questions and more answers – Part 4"},"content":{"rendered":"

\"win7\"[German<\/a>]Administrators who have chosen to participate in the Extended Security Updates program will need to make some enhancements in order to receive security updates for Windows 7 SP1 and Windows Server 2008 and Windows Server 2008 R2 in February 2020.<\/p>\n

<\/p>\n

\"\"I'm going to take this up again briefly because Microsoft has given all administrators an unpleasant surprise regarding Extended Security Updates (ESU).<\/p>\n

Background: Extended Security Updates (ESU)<\/h2>\n

I've covered it several times in my blog: Companies can still get security updates for Windows 7 SP1 and Windows Server 2008 and Windows Server 2008 R2 after the support ends (January 14, 2020). However, the Extended Security Updates Program (ESU) must be booked. Afterwards the ESU license had to be activated on the clients. I had mentioned the necessary boundary conditions and steps in several blog posts (see links at the end of the article).<\/p>\n

Meanwhile it is also clear that Windows 7 SP1 Ultimate is covered in the ESU program. This was unclear for some time, as Microsoft had partially removed the reference to the Ultimate from its support articles. The following screenshot shows that the Ultimate SKU is covered.<\/p><\/blockquote>\n

<\/p>\n

Update KB4538483 mandatory for ESU<\/h2>\n

Microsoft had even provided a test update KB4528069<\/a> (in 2019), which was downloaded from the Microsoft Update Catalog and then installed manually.<\/p>\n

\"Update<\/p>\n

The update only appeared at startup and was then installed without any further messages. So I thought, it's sufficient \u2013 but on 2\/11\/22020 I was surprised, however, that no security updates came on my ESU machine. In the meantime the update has been removed from the Microsoft Update Catalog.<\/p>\n

For this purpose, Microsoft provided the Techcommunity article on the ESU program<\/a>, in which the notes on the requirements (SSU, SHA-2) were updated. For ESU systems, update KB4538483<\/a> must be manually downloaded from the Update Catalog and then installed.<\/p>\n

\"Windows<\/p>\n

Only then the client receives its security updates via Windows Update. An additional move from Microsoft, Susan Bradley picked it up at bei askwoody.com<\/a>.<\/p>\n

ESU-Key may have to be reactivated<\/h2>\n

In addition, the following information is included in the preamble to the Extended Security Updates (ESU) Licensing Preparation Package for Windows 7 SP1 and Windows Server 2008 R2 SP1<\/em> (Update 4538483<\/a>):<\/p>\n

IMPORTANT <\/strong>Some customers using Windows Server 2008 R2 SP1 who activated their ESU multiple activation key (MAK) add-on before installing the January 14, 2020 updates might need to re-activate their key. Re-activation on affected devices should only be required once.\u202f For information on activation, see this blog<\/a> post.<\/p>\n

IMPORTANT<\/strong> WSUS scan cab files will continue to be available for Windows 7 SP1 and Windows Server 2008 R2 SP1. If you have a subset of devices running these operating systems without ESU, they might show as non-compliant<\/u> in your patch management and compliance toolsets.<\/p>\n

IMPORTANT<\/strong> Customers who have purchased the Extended Security Update (ESU)<\/a> for on-premises versions of this OS must follow the procedures in KB4522133<\/a> to continue receiving security updates after extended support ends on January 14, 2020. For more information on ESU and which editions are supported, see KB4497181<\/a>.<\/p><\/blockquote>\n

Caution, probably outdated support articles<\/h2>\n

At Twitter<\/a> blog reader Karl points out that Microsoft's support articles include some outdated information about the requirements for ESU patches. This affects the following articles:<\/p>\n