CHR1S (10th June 2010)
Anyway, in situations where PCs don't report back I've often taken a slightly brutal approach and deleted the PC from WSUS, renamed its C:\Windows\Softwaredistribution folder and then forced an update to get it to reregister with WSUS. More often that not it's shown up in the console pretty quickly and after a few reboot cycles as it does its updates, it reports back that all is well.
Of course, as long as it's picking up updates then the reporting issue can just be added to the infamous TODO list I guess :-)
And its now reported back!! Woooo!
Last question, will the clients all automatically update on its next scheduled cycle or will they all have to be forced?
I would suspect that if they have the same problem as the PC that's now working, things will just fall into place as they can now access the files they need :-)
Possibly wouldn't hurt to add "wuauclt /detectnow" to a startup script to try and coax them along but I don't think it's necessary.
I knew this would be IIS it just sounded right! The machines should report back on their next schedule I don't think a force will be needed.
Glad the issue is sorted Chris!
Big Thanks to you all for your help, its most appreciated
No problem mate thats what were here for :-)
There are currently 1 users browsing this thread. (0 members and 1 guests)