The unholy mess that has emerged from Win10 WSUS Dual Scan

[woodyDa Boss]

Those of you who just go about your business with Windows don’t need to worry. But the folks who are in charge of Windows Update servers should be con
[See the full post at: The unholy mess that has emerged from Win10 WSUS Dual Scan]

4 users thanked author for this post.

NetDef, MrBrian, PerthMike, ch100

[MicrofixAskWoody MVP]

KISS for MS?  (for those unfamiliar with forumspeak k.i.s.s = keep it simple stupid) 🙂

| 2x Group A- W8.1x64 | Group A+ Linux x64 Hybrid | Group B W7x64 Pro | Group W XP Pro

No problem can be solved from the same level of consciousness that created IT - AE

2 users thanked author for this post.

lurks about, abbodi86

[anonymous]

I love this snippet at the bottom of that article:
“Things might change with the soon to be release Win10 1803 Release.”

Thanks Microsoft. As it wasn’t difficult enough to keep our WSUS controlled workstations in a working condition…

1 user thanked author for this post.

woody

[Jan K.AskWoody Lounger]

*franticly waves raised arm*

Me, Sir!

Sir! Sir, I know, Sir!

Do you think they could make this a bit more complicated?

Yes.

Yes, I think they can.

3 users thanked author for this post.

columbia2011, Cascadian, woody

[OscarCPAskWoody Lounger]

My PC runs Windows 7 and here I am, reading about yet more Win 10 big problems, feeling unusually smug, for a change. How very strange.

The Patch Lady’s List shows nothing bad, so far, with Win 7 patches, neither  have I heard elsewhere of any serious problems with them  — yet.

So far this month, there are no new monsters, the likes of Specter, Meltdown, etc., scary enough to make one consider patching in a hurry, with much preliminary agonizing over it.

So now I can wait, in unaccustomed tranquility, and wish you all the very best of luck.

Group B, Win 7 Pro SP1 x64.

1 user thanked author for this post.

GoneToPlaid

[ch100AskWoody MVP]

Those forum members who understand this stuff and use Windows 10 Pro could take an idea or two from this table even if not using a managed environment.
Thanks for posting Woody!
Very valuable information. 🙂

1 user thanked author for this post.

Jan K.

[PerthMikeAskWoody Lounger]

You know things are <bleep> when you have to put in firewall rules to specifically block workstations from going direct to Microsoft servers despite all the settings you’ve put in place.

No matter where you go, there you are.

[tommyb0yAskWoody Lounger]

This answers many of my “What the heck?!? Why is this 2016 server auto updating when it’s pointed to WSUS” questions.

Thanks for posting about this.

• This reply was modified 4 months ago by  PKCano.
• This reply was modified 4 months ago by  PKCano.
• This reply was modified 4 months ago by  tommyb0y. Reason: Fixed content, per rules
• This reply was modified 4 months ago by  tommyb0y.

[milliaAskWoody Lounger]

Of course, this presumes that workstations can update drivers from WSUS as they’re supposed to. I think it only works on about 10% of my machines.

[lawrenceBAskWoody Lounger]

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!

[NetDefAskWoody Lounger]

That chart is . . .  hideous . . .  And it fails to illuminate some well known GPO conflicts that produce unexpected behaviors.  The SBS Diva explained it perfectly in her recent post at

https://www.askwoody.com/2018/patch-lady-no-its-not-wsuss-fault/

Microsoft is hiring the wrong technical documentation writers! Still . . .

1 user thanked author for this post.

MrBrian

[MrJimPhelpsAskWoody MVP]

Rather than spending a huge amount of time trying to make sense of this intentional mess, I’m going to spend that time figuring out the final few Linux issues I am having. I would much rather invest my time in me than in Microsoft.

Group "L" (Linux Mint)
with Windows 8.1 running in a VM

1 user thanked author for this post.

Cascadian

[Author]

Posts