The unholy mess that has emerged from Win10 WSUS Dual Scan

Topic

New Reply

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

Reply | Quote

Replies

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

Windows - commercial by definition and now function...

2 users thanked author for this post.

lurks about, abbodi86

Reply | Quote

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

Reply | Quote

*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

Reply | Quote

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.

Ex-Windows user (Win. 98, XP, 7); since mid-2017 using also macOS. Presently on Monterey 12.15 & sometimes running also Linux (Mint).

MacBook Pro circa mid-2015, 15" display, with 16GB 1600 GHz DDR3 RAM, 1 TB SSD, a Haswell architecture Intel CPU with 4 Cores and 8 Threads model i7-4870HQ @ 2.50GHz.
Intel Iris Pro GPU with Built-in Bus, VRAM 1.5 GB, Display 2880 x 1800 Retina, 24-Bit color.
macOS Monterey; browsers: Waterfox "Current", Vivaldi and (now and then) Chrome; security apps. Intego AV

1 user thanked author for this post.

GoneToPlaid

Reply | Quote

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.

Reply | Quote

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.

Reply | Quote

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.

Reply | Quote

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.

Reply | Quote

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!

Reply | Quote

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 . . .

~ Group "Weekend" ~

1 user thanked author for this post.

MrBrian

Reply | Quote

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 10 running in a remote session on my file server

1 user thanked author for this post.

Cascadian

Reply | Quote