If you have been using Software Update Services (SUS) to distribute updates, some WSUS clients may be using the SUS client, while others may be using the WSUS client.The new WSUS client will replace the old SUS client, but both versions will be able to contact a SUS server.This is what I have done so far: 1) Changing Updates on local PC: 3) executed wuauclt /resetauthorization /detectnow 4)Synchronised and refreshed the group I am running out of ideas here. OK, the computer should show up in the All Computers group as well as the target group.The client is running Windows XP pro, WSUS version is 3.0 and is running on Windows 2008 R2 64-bit. If it's not showing up in the All Computers group, then I would suspect that the GPO isn't being applied.Clearly you can ping a server, but you can't communicate with WSUS on the WSUS port.
If you used SUS to deploy Windows XP with SP2, you cannot see the new Automatic Updates user interface, and none of the new WSUS client functionality is available.
You may have read my blogpost on the actions admins need to take to continue working with Windows XP in their networking environments. While many blogs and websites have shared similar information, one action is on everybody’s list: Update Windows XP with the latest updates. Without a fourth Service Pack for Windows XP, containing all the updates for Windows XP up till April 8th, 2014, it’s really about connecting a device running Windows XP to the internet and downloading the updates through Windows Update, or connecting a device to the corporate network and downloading updates from the on-premises Windows Server Update Services (WSUS) installation.
This, of course, is not the best of ideas: Every security expert has warned against connecting Windows XP boxes to the internet or your corporate network after April 8th…
WSUS requires that clients use a version of Automatic Updates compatible with WSUS.
You must update your WSUS clients' version of Automatic Updates by using the client self-update feature.