After you unlink the GPO, the clients/servers need to reboot (or else you need to reprocess the GPOs and also restart the WUservice on each client/server.
Also, WSUS group-based-targeting requires that the WSWUS group-name exist in WSUS (so you could change the name or membership) AND it also requires that the WSUS group name be set in registry (or via GPO) on each client/server (so you could change or remove that GPO/registry setting).
De-scoping the groups/members is one way to do it, but you do also need to reset the WU settings on the clients anyway (unless Ivanti comes along and takes over that stuff) but you don’t want to leave those GPO settings hanging around as they are likely to eventually bite you on the @ss 😉
DonP
--
You received this message because you are subscribed to the Google Groups "ntsysadmin" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ntsysadmin+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ntsysadmin/CAHBr%2B%2BjsquZujZH83DYtsQdCSWfWJDEqkUZgcBBtEM1gye3vtw%40mail.gmail.com.
Client-side-targeting (aka group-based-targeting) Manage additional Windows Update settings - Windows Deployment | Microsoft Learn
Manage additional Windows Update settings - Windows Deployment | Microsoft Learn
From (distant) memory, AUOptions:3 was the original default back in the day?
o 3: Automatically download and notify of installation.
There are a few settings there that you can use to stop patching from happening, if that’s your goal? But I’d guess you don’t want to cripple WU too much as Ivanti will probably need some bits of it?
DonP