Tutorials

Windows 10 showing as Vista in WSUS and not updating at all.

1. Open WSUS Manager to have a look at what I mean.
   
2. Easiest way to fix this is to download and install SQL Management Studio 2014 Express from http://www.microsoft.com/en-us/download/details.aspx?id=42299 and run a script. Click Download.
   
3. Choose the 64bit version because the server is x64 and we only need Management Studio. Click Next.
   
4. Click Save.
   
5. Click Run
   
6. Click Yes
   
7. Click OK.
   
8. Click ‘New SQL Server stand-alone installation or add features to an existing installation’.
   
9. Click Next
   
10. Check Management Tools and click Next
    
11. Setup is complete, click Close.
    
12. If you are logged in as the admin you created when you initially installed the server you will find that you cannot connect to the WID with those credentials.
     
    You need to enable the build in ‘administrator’ account for this. This is done from ADUC. Log out with your ‘normal’ admin account and login with the ‘administrator’ account.
    Once that is done start SQL Server 2012 Studio Management. Click Connect.
    
13. There is the SUSDB and we are going to have a look in the tables because there is solution to our problem.
    
14. We need to change tbComputerTargetDetail.
    
15. In order to do that we need to run a query. Click New Query and type:

    UPDATE  [SUSDB].[dbo].[tbComputerTargetDetail]
    SET     [OSDescription] = 'Windows 10'
    WHERE   [OSMajorVersion] = '10'
            AND [OSMinorVersion] = '0'
            AND [OldProductType] = '1'
            AND ( [OSDescription] <> 'Windows 10'
                  OR [OSDescription] IS NULL
                )

    
    
    and click Execute. Now you should see (1 row(s) affected)
     
16. Now we need to restart WSUS Service.
    
17. Now if we go back to the WSUS Manager we see that our Windows 10 Workstation reports as a Windows 10 PC and no longer as a Vista client. But there is more to this. If you look at the below screenshot you see that our Windows 10 is listed as a Windows 10 client in the ‘All Computers’ hive but if we look in the Clients hive it does not show up.
    
18. It does show my other PC which is a Windows 8.1 laptop but no Windows 10.
    
19. The answer to this problem can be found on the Windows 10 laptop by running gpresult /r. We will see that the RSOP shows that the Contoso WSUS Client Settings GPO was filtered out because of the WMI filter that we used. That WMI filter was created when we applied Group Policies from our Dashboard and those WMI settings don’t know about Windows 10 because it did not exist. Bottom line is that we are going to make our own WSUS WMI filters and apply those to our WSUS GPO’s
    
20. On the server choose Group Policy Management from the Tools menu in Server Manager. Right click WMI Filters and choose to create a new WMI filter with the name WSUS Clients Group Policy WMI Filter and set it to [select * from Win32_OperatingSystem where ProductType = "1"]. That basically says look for all Operating Systems but make sure they are only Client Operating Systems. This way WSUS will work with all old and new Client Operating Systems.
    
21. Now we need to change the WMI filter for the WSUS Client Settings GPO to our newly created WSUS Clients Group Policy WMI Filter.
    
22. On the Windows 10 PC open an elevated command prompt and type gpupdate /force to update the Group Policy processing. The result look good. Just to be sure I reboot the Windows 10 laptop and run wuauclt /reportnow.
    
23. Just a quick check at the WSUS Manager on the server and bingo. Live is good!