WSUS Client delayed update detection after assigned to new group

Question

Hello, fellow forum dwellers,
I'm experiencing some issues with my WSUS Client Management and couldn't find any answer in the library or forums. Thus I decided to write here:
Issue
When registering a new computer with WSUS and assigning a group, the updates, that have been assigned to that group aren't released to the Computer (searching will only yield the list available to the default group). After some hours (I'm currently trying
to measure just how many) suddenly the updates will become available as intended.
Why does it bother me?
That wouldn't bother me all that much for permanent clients (Using the term "client" to refer to WSUS client, independently of the actual OS type), however much of our work is spent rolling out devices to customers (who ought to receive them fully
updated). Completely non-uniform, preinstalled but non-updated hardware and OS rule out preupdated installation images unfortunately. This is putting a significant delay in our time spent on each individual device (and is sometimes putting a serious bottleneck
in our operation).
Infrastructure:
WSUS OS: Windows Server 2003 R2
WSUS Version: 3.2.7600.226
Computer-Folder Assignment: Serverside
Client-Configuration: Registry Modification (Clients are not domain members, settings are applied via Powershell Script)
Client OS: Windows 7, 8, 8.1, 2008 R2, SBS 2011, 2012
Client OS Architecture: x64 & x86
Localization: All clients & WSUS have uniform timezone and language
Any insights and help welcome :)
Cheers and thanks in advance,
Fred
There's no place like 127.0.0.1

Answer 1

Hello, fellow forum dwellers,
I'm experiencing some issues with my WSUS Client Management and couldn't find any answer in the library or forums. Thus I decided to write here:
Issue
When registering a new computer with WSUS and assigning a group, the updates, that have been assigned to that group aren't released to the Computer (searching will only yield the list available to the default group). After some hours (I'm currently trying
to measure just how many) suddenly the updates will become available as intended.
Why does it bother me?
That wouldn't bother me all that much for permanent clients (Using the term "client" to refer to WSUS client, independently of the actual OS type), however much of our work is spent rolling out devices to customers (who ought to receive them fully updated).
Completely non-uniform, preinstalled but non-updated hardware and OS rule out preupdated installation images unfortunately. This is putting a significant delay in our time spent on each individual device (and is sometimes putting a serious bottleneck in our
operation).
Infrastructure:
WSUS OS: Windows Server 2003 R2
WSUS Version: 3.2.7600.226
Computer-Folder Assignment: Serverside
Client-Configuration: Registry Modification (Clients are not domain members, settings are applied via Powershell Script)
Client OS: Windows 7, 8, 8.1, 2008 R2, SBS 2011, 2012
Client OS Architecture: x64 & x86
Localization: All clients & WSUS have uniform timezone and language
Any insights and help welcome :)
Cheers and thanks in advance,
Fred
There's no place like 127.0.0.1
After adding the computers to the group to get WSUS to recognize the new group you need to run the command on the client
wuauclt.exe /detectnow /resetauthorization
The /resetauthorization part is the one that makes sure the client checks to see which group it belongs to in WSUS.
The delay you are experiencing is the amount to time the client takes to "check in" with WSUS.
Hope this helps.