Initially it auto-detected the machines and they all reported in at least once if not more (several on 5/5, some on 5/7 and one on 5/8).However, since then none of machines have reported in.WSUS builds on SUS by expanding the range of software it can update.The WSUS infrastructure allows automatic downloads of updates, hotfixes, service packs, device drivers and feature packs to clients in an organization from a central server(s).In the previous posts we have seen Installation, Configuration, Managing the WSUS 3.0 SP2.Before we start troubleshooting WSUS issues, lets take a look at some of the log files created by WSUS server.Apart from these log files, there are 2 more log files that are really important.
If you want to refresh Group Policy sooner, you can go to a command prompt on the client computer and type in a console with Administrative permissions: gpupdate /force.
The machines are Windows 8.1 - we recently moved to Win 8, however if I check the old WSUS server all the Win 8 machines are reporting in daily (or thereabouts).
I looked around on the net and the general consensus seems to be that there is no way to force a machine to immediately report? Any thoughts on why these machines would be found initially but then pretty much immediately stop reporting?
Could it be some conflict with the AD policy which had originally pointed them to the old WSUS server (I didn't set up that policy so I'm not terribly familiar with it)?
Open a CMD window and do a gpresult /v, you can see what WSUS policy is applied to the may need to reset authorization and there is a way to get it to report it is /updatenow.
SUS ran on a Windows Server operating system and downloaded updates for the specified versions of Windows from the remote Windows Update site which was operated by Microsoft.