If these are duplicates of other computers (which happens with cloned environments where the aforementioned tools have NOT been run), then you can see how this might be a problem. PASS Winhttp local machine access type Winhttp local machine Proxy.
You should really then run New SID from Sysinterals on any of the duplicate computers to resolve any potential issues in the future (not to mention the security issues involved with having duplicate SIDS on the network): You don't need to RUN New SID on each computer prior to fixing the duplicate ID issue in WSUS, but it may rear its ugly head later on, so if you can find the time, I would recommend fixing this issue as soon as you can.
Some questions to ask yourself: Some symptoms of this may also include computers randomly disappearing/reappearing from/into your WSUS console.
Another symptom is the computer will receive updates, but not report into the server properly (if at all! Each computer on a network requires a SID (Security IDentifier), which uniquely describes that computer account to the rest of the Windows network resources - supposedly not as big of an issue with computers in a domain environment as it is with workgroups.
If you don't see the GPO specified in the output of your GPResult, then you know you need to look to Active Directory as the source of the problem.
If you do see the GPO applied here, then it is more likely an issue with the client (i.e. In the GPO MMC, any OU that is blocking inheritance will have a blue exclamation point over the OU icon. PASS This version is WSUS 2.0 Checking AU Settings AU Option is 3 : Notify Prior to Install.
Check with your system administrator before you start altering these settings - - they might be there for a reason!