Win Server R2 WSUS does not recognize the solution for Win Server & WIN10

Hello everyone, today to share a question I have encountered. I believe that after Microsoft launched the Windows Server 2016 and Win10 operating system, a lot of students have been installed and tested the first time, want to feel the first time a new system platform brought about by experience.

But I do not know if any classmate found that if we build a server 2016 or WIN10 machine in the domain environment, the WSUS server in the domain may not be recognized, so it will directly cause the patch push failure, thus Server2016 and WIN10 terminals simply do not have access to Windows Update Services.

So what do we do? Today I would like to tell you the solution, so that our "early taste" trip is not panic!

First we look at the phenomenon.

As an example of Windows Server 2016, we first tried to update the service through WSUS and found that the system was able to identify patches that needed to be updated, but was not able to download them.

650) this.width=650; "alt=" Picture "src=" https://fud.community.services.support.microsoft.com/Fud/ filedownloadhandler.ashx?fid=32bf2607-1103-479e-bba2-3b9a29fc841d "/>

Or there is the following possible line, is the direct prompt update encountered an error.

650) this.width=650; "alt=" Picture "src=" https://fud.community.services.support.microsoft.com/Fud/ filedownloadhandler.ashx?fid=89cc7a73-c134-477e-a8fd-9dd1dbd07020 "/>

This is the first time we'll be thinking about going to WSUS to find out.

As we can see from this, we have installed a server in Windows Server 2016 that is recognized by WSUS as a version of the standard version of Windows Server 2008 (fully installed).

650) this.width=650; "height=" 446 "title=" image "style=" border-top:0px;border-right:0px;background-image:none; border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;margin:0px;padding-right:0px; "alt=" image " Src= "Http://s3.51cto.com/wyfs02/M02/8E/CF/wKioL1jLkF3wMnrrAAGtRpww_sc570.png" border= "0"/>

650) this.width=650; "alt=" Picture "src=" https://fud.community.services.support.microsoft.com/Fud/ Filedownloadhandler.ashx?fid=6625e9f5-be96-4e19-8f37-43f6549882a3 "/>

This makes sense, why our Terminal Server has not received the correct patch package. WSUS all admit to the OS, how to push the patch it?

So what do we need to do to rectify this error of WSUS?

The answer is to install a two patch

KB3095113

: Https://support.microsoft.com/zh-cn/help/3095113/update-to-enable-wsus-support-for-windows-10-feature-upgrades

And

KB3159706

: https://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB3159706%20

After downloading the two patches, install them in sequence

650) this.width=650; "height=" title= "image" style= "border-top:0px;border-right:0px;background-image:none; border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;margin:0px;padding-right:0px; "alt=" image " Src= "Http://s3.51cto.com/wyfs02/M02/8E/D1/wKiom1jLkF7jexdXAABY7TX2oj4074.png" border= "0"/>

There is nothing special to note for the first KB3095113 patch, which requires a reboot after installation.

But the second patch KB3159706 there are some places that need to be manually operated.

Let's take a look:

Double-click the patch installation package

650) this.width=650; "height=" 382 "title=" image "style=" border-top:0px;border-right:0px;background-image:none; border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;margin:0px;padding-right:0px; "alt=" image " Src= "Http://s3.51cto.com/wyfs02/M01/8E/D1/wKiom1jLkF_A_ZSBAAD5sUpTBwM740.png" border= "0"/>

System starts to install patches independently

650) this.width=650; "height=" 402 "title=" image "style=" border-top:0px;border-right:0px;background-image:none; border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;margin:0px;padding-right:0px; "alt=" image " Src= "Http://s3.51cto.com/wyfs02/M02/8E/D1/wKiom1jLkF-hocJPAADc07sHStE964.png" border= "0"/>

Installation complete, restart server required

650) this.width=650; "height=" 398 "title=" image "style=" border-top:0px;border-right:0px;background-image:none; border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;margin:0px;padding-right:0px; "alt=" image " Src= "Http://s3.51cto.com/wyfs02/M00/8E/D1/wKiom1jLkGCw-cnhAACpjH4xEBQ733.png" border= "0"/>

When the server restarts, open IIS and check that the WSUS you are using is HTTP or HTTPS protocol, and usually we are using the HTTP protocol of 8530.

Why do you want to see this? Because of the different protocols, the following manual operation methods are different.

650) this.width=650; "height=" 497 "title=" image "style=" border-top:0px;border-right:0px;background-image:none; border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;margin:0px;padding-right:0px; "alt=" image " Src= "Http://s3.51cto.com/wyfs02/M00/8E/CF/wKioL1jLkGPg_V7rAAPHQSAakdI413.png" border= "0"/>

First of all, if the HTTP protocol is 8530, OK then congratulations, your steps will be very simple.

1. First open the cmd command line

Enter the following command (the path is modified as appropriate)

"C:\Program files\update Services\tools\wsusutil.exe" postinstall/servicing

When you see the following words, the deployment is complete.

650) this.width=650; "height=" 224 "title=" image "style=" border-top:0px;border-right:0px;background-image:none; border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;margin:0px;padding-right:0px; "alt=" image " Src= "Http://s3.51cto.com/wyfs02/M00/8E/CF/wKioL1jLkGSj0STiAAC8x-nAUEM332.png" border= "0"/>

2. Next in the Server Manager Add Roles and Features Wizard select the . NET Framework 4.5 feature , the HTTP activation

650) this.width=650; "height=" 468 "title=" image "style=" border-top:0px;border-right:0px;background-image:none; border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;margin:0px;padding-right:0px; "alt=" image " Src= "Http://s3.51cto.com/wyfs02/M01/8E/CF/wKioL1jLkGWAByaUAAHE7Sm9EPs816.png" border= "0"/>

3. After the installation is complete, restart the WSUS service.

Here are the second class with the 8531 HTTPS protocol enabled, and your approach is a little more cumbersome.

2. Assign ownership of the Web. config file to the Administrators group (run at an elevated command prompt):

   takeown/f web.config/aicacls "C:\Program files\update services\webservices\clientwebservice\web.config"/grant Administrators:f

4. Locate the following path in the Web. config file:

   C:\Program files\update Services\webservices\clientwebservice\web.config

5. Make the following changes in the file.
   Note: This code example represents a block of text. Line spacing is used only to emphasize text changes and is displayed in bold.

   <services> <service name= "Microsoft.UpdateServices.Internal.Client" Behavi orconfiguration= "Clientwebservicebehaviour" >

                  <!--                    these  4 endpoint bindings are required for supporting both http  and https                 -->                < Endpoint address= ""                          binding= "BasicHttpBinding"                           bindingconfiguration= "SSL"                           contract= "Microsoft.UpdateServices.Internal.IClientWebService " />                 <endpoint address= "Secured"                          binding= "BasicHttpBinding"                           bindingconfiguration= "SSL"                          contract= " Microsoft.UpdateServices.Internal.IClientWebService " />

                  <endpoint  Address= ""                          binding= "BasicHttpBinding"                           bindingconfiguration= "Clientwebservicebinding"                          contract= " Microsoft.UpdateServices.Internal.IClientWebService " />                 <endpoint address= "Secured"                           binding= "BasicHttpBinding"                           bindingconfiguration= "Clientwebservicebinding"                           contract= "Microsoft.UpdateServices.Internal.IClientWebService"  />           </service>    </services>

7. Add the multiplesitebindingsenabled = "true" attribute to the bottom of the Web. config file as follows:

   </bindings> <servicehostingenvironment aspnetcompatibilityenabled= "true" multiplesitebindingsenabled= " True "/> </system.serviceModel>

Following the two methods described above, we then open the WSUS administration console.

The previous server has been identified as Windows (version 10.0), so don't be surprised, because server 2016 and WIN10 are the same architecture platform, so the display is the same.

650) this.width=650; "height=" 340 "title=" image "style=" border-top:0px;border-right:0px;background-image:none; border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;margin:0px;padding-right:0px; "alt=" image " Src= "Http://s3.51cto.com/wyfs02/M01/8E/CF/wKioL1jLkGbz0iU9AAKv0JRzlhE520.png" border= "0"/>

Haha, the patch was successfully pushed over, the installation was successful!

650) this.width=650; "height=" 497 "title=" image "style=" border-top:0px;border-right:0px;background-image:none; border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;margin:0px;padding-right:0px; "alt=" image " Src= "Http://s3.51cto.com/wyfs02/M02/8E/CF/wKioL1jLkGjgqT5UAAEnj6bdwCM122.png" border= "0"/>

Get!

Win Server R2 WSUS does not recognize the solution for Win Server & WIN10