Well, the only way I can think of to scan your network for Microsoft fixes is to run the Microsoft Network Security Hotfix Checker (Hfnetchk.exe) Tool. Here is a list of switches that let you specify what machine(s) you want to scan:
-h - This switch specifies the NetBIOS computer name to scan. The default location is the local host. You can scan multiple host names if you separate each host name entry with a comma, for example:
hfnetchk -h computer1 , computer2 , server1 , server2
-fh -This switch specifies the name of a file that contains NetBIOS computer names to scan. There is one computer name on every line with a 256 maximum in every file, for example:
hfnetchk -fh computers_to_scan.txt
-i - This switch specifies the Internet Protocol (IP) address of the computer to scan. You can scan multiple IP addresses if you separate each IP address entry with a comma, for example:
hfnetchk -i 172.16.1.10,172.16.1.50,192.168.1.10
-fip - This switch specifies the name of a file that contains addresses to scan. There is one IP address for every line with a 256 maximum for each file, for example:
hfnetchk -fip IP_addresses_to_scan.txt
-r - This switch specifies the IP address range to be scanned, with ipaddress1 and ending with ipaddress2 inclusive, for example:
hfnetchk -r 172.16.1.1-172.16.1.35
HINT : You can use the previous switches in combination, for example:
hfnetchk -h computer1 , computer2 -i 172.16.1.10 -fip ipaddresses.txt -r 172.16.1.50-172.16.1.90
