Network Discovery and WSUS
We have a number of machines running Win7 and getting their updates from a WSUS server on the same subnet. Unfortunately, they only seem to be able to contact the WSUS server when the Network Discovery feature is turned on for the client machines. For instance if I get on a client machine that has several updates available for installation and run wuauclt.exe /detect now to force a check of the available updates it will show that it last checked at the date/time I ran wuauclt and that there are currently 0 updates. However, if I turn Network Discovery on for that machine, re-run wuauclt, it will immediately find the updates that were waiting for that machine. This doesn't seem to be a connectivity issue, from that machine I can ping, RDP, and access file shares all on the WSUS server. We'd prefer to have Network Discovery turned off on our network but not at the cost of losing our updating capabilities. Can anyone provide some insight into this bizarre connection between WSUS and Network Discovery? Thanks!
October 13th, 2010 4:00pm

This behavior is by design. You may run the following command prior to launch Windows Update. netsh advfirewall firewall set rule group="network discovery" new enable=yes Or just enable Network Discovery in GPOs.Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Free Windows Admin Tool Kit Click here and download it now
October 15th, 2010 6:07am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics