Validating signature wuident cab 0x80096001
) as "Microsoft Signed: NA" whereas previously everything was "Microsoft Signed: Yes".
If your client computers are pointed to the WSUS server and you do not see the WSUS client user interface shown above, see the next section. For this reason, you must have a Web site running on port 80, even if you put the WSUS Web site on a custom port.Microsoft is conducting an online survey to understand your opinion of the Technet Web site.If you choose to participate, the online survey will be presented to you when you leave the Technet Web site. This virtual directory holds the WSUS-compatible Automatic Updates. Using Group Policy to point client computers to your WSUS server should eventually cause an Automatic Updates detection and client self-update.For more information about this process, see Deploying Microsoft Windows Server Update Services ( Some computers might already have the WSUS client installed.The reason for those NA response is that the files concerned are simple compressed xml files - and cannot be signed.
I suspect that it's a hold-over, and not relevant any longer - but my coding skills aren't good enough to know for certain.
Hi,we are running the latest Version of KSC and Administration Agent, 10.2.434 including Patch B.
Now we have began to configure our administration server for acting as a WSUS Server and got some issues regarding the Windows Update Agent.
Computer type Laptop System Manufacturer/Model Number HP Pavilion dv7-2173cl Entertainment Notebook PC OS W7 pro 32-bit.
Memory 4GB Graphics Card ATI Mobility Radeon HD 4650 (M96) Sound Card Altec Lansing with SRS Premium Sound and Sub-Woofer Monitor(s) Displays 17.3 Diagonal HD High-Definition HP LED Bright View W Screen Resolution 1600 x 900 Is it as clear cut as Noel DP makes out?
The Web site on port 80 does not have to be dedicated to WSUS.