Replies

That’s been my experience so far, Woody.

Though, contrary to the KB4538483 article, I did not have to reboot after installing it to be offered the Feb OS rollup and Office security updates (all of which installed successfully.)

All from WSUS FWIW. Tested 3 machines so far.

Thanks EP,  looks like you’re correct about them not producing an ESU test update for 32-bit 2008. Confirmed by microsoft in the comments at https://techcommunity.microsoft.com/t5/windows-it-pro-blog/how-to-get-extended-security-updates-for-eligible-windows/ba-p/917807

So, my only remaining mystery: Windows Web Server 2008 R2 not activating with the 2008 ESU key. Will try to open a ticket with them. I really think they forgot to test this Edition with the ESU key. Or intentionally are not supporting it.

jabeautty: Thanks, good thought, but no, these machines have full internet access.

Deanna: No, neither of those, thanks for the suggestion though.

Considering it’s on all 3 of my “Windows Web Server 2008 R2″ servers, and none of my normal R2 Std/Ent servers, I really wonder  if microsoft just forgot to test ESU on this edition.

I’ll pull some event logs when I have a second and post them, maybe that will shed more light.

FWIW, we’ve got multiple 2016 LTSB machines affected (some with HP printers, some with non-HP.)

1 user thanked author for this post.

woody

I am, reluctantly, going to move forward with the August patches (~500 PCs) and will just deal with the breakage on a case by case basis.

The fairly catastrophic downside should an exploit for the latest RDP RCEs begin to circulate trumps the annoying, but not earth-shattering, impact of breaking some apps here and there.

Situations like these make me really despise the all-or-nothing approach MS has taken with these forced rollups. And I don’t think it’s done a d*** thing for patch reliability, like they claimed it would.

 

Same here, 2008R2 DC, at 2008R2 functional levels. March security only.

‘netdom /?’ doesn’t even work, gives same error.

Runs successfully against my domain when run from a non-DC Server 2016 machine.

Thank you for this. I have a few Server 2016 GUI VMs, and they’re all brutally slow to update.

Unfortunately, I bought a bunch of 2016 licenses about 6 months ago, opting out of an overpriced Campus server agreement, so 2019 isn’t really an option for me.

I assumed they would eventually resolve these issues (the MS forum threads are full of people with similar complaints.) But 2016 has been out for over two years, and I’m starting to wonder.

 

1 user thanked author for this post.

alQamar

Thank you for this post.  We’re a Windows 7 shop, trying to get a handle on pushing Windows 10 security updates (but not feature/version updates) through WSUS.

What a mess!

Unfortunately, the WSUS ‘update needed’ logic for 4100480 seems broken. I have 115 x64 Win7 machines, patched using WSUS, which have the Jan,  and then the Feb, Security rollups installed, and only 4 of them show up as needing 4100480.

Two other users report similar findings in comments at https://www.askwoody.com/forums/topic/patch-lady-new-update-for-windows-7-kb-4100480/#post-179324

2 users thanked author for this post.

woody, MrBrian

mobartz wrote:

OK, this is frustrating. I think their WSUS detection is botched.

Same here.  We have maybe 115 x64 Windows 7 machines being updated with WSUS. They had the Jan., and then the Feb., security only rollup installed.

Of those, only 4 show 4100480 as ‘needed’.

What a mess, all of this.