I recently installed WSUS in a network and am now waiting for it to download all the updates I want to provide to other clients.
The updates are already approved. The installation is set up to only download approved updates. That is what it is doing right now.
So, this is going to take a while. In the meantime, I set up my group policies to make my clients aware of this new service.
Sadly, my Windows 7 test client (freshly installed), doesn't seem to think there are any updates available:
So, now I'm asking myself, is my setup broken? Or do I simply have to wait for those 140GB to download before it will all start to function properly.
The WindowsUpdate.log
on my test client seems to tell that my correct server is being used:
2012-05-19 15:44:25:523 944 43c AU ########### AU: Initializing Automatic Updates ###########
2012-05-19 15:44:25:523 944 43c AU # WSUS server: http://SRV-PDC
The log is also pretty clear on the number of updates that should be applied:
2012-05-19 15:44:27:133 944 85c Agent * Found 0 updates and 61 categories in search; evaluated appl. rules of 174 out of 895 deployed entities
...
2012-05-19 15:44:27:149 944 754 AU # 0 updates detected
The reportingevents.log
also indicates that no updates are available:
{6DB29978-5D20-4D80-9088-5F87D0CC3417} 2012-05-19 20:13:23:388+0200 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software Synchronization Windows Update Client successfully detected 0 updates.
{03B0D7A7-A599-41CE-B583-F2870CEF4225} 2012-05-19 20:13:23:388+0200 1 156 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment Check Reporting client status.