gjefferies Posted July 21, 2017 Posted July 21, 2017 Hi, I am currently testing Server 2016 and so far it is going well, but I have a problem with the 2016 server getting any updates from our WSUS server running on a 2012 R2 box. The 2016 server appears in the All computers in WSUS, but appears as o/s version Windows 10 and never reports in (Status Not yet reported in) When I check from updates from the 2016 server it returns error 0x8024401c I've manually installed the latest cumulative update on 2016 to see if that helped and it made no difference. I set a Windows 10 1703 computer to get updates from the WSUS Server and it reports and pulls down updates fine. Anyone else experience this problem and found a fix? Thanks Gareth
robsonma Posted July 21, 2017 Posted July 21, 2017 I have seen this before, On your WSUS Server check you are all up to date with patches ect, run windows update and install all of the updates. It is an issue with your Server 2012 not recognizing the Server 2016 OS
gjefferies Posted July 21, 2017 Author Posted July 21, 2017 Thanks for your reply, Yes the WSUS server is up to date, regarding patches etc. I've come across other people with the issue regarding wsus not detect the o/s version, but the threads end without a fix. Cheers Gareth
gjefferies Posted July 21, 2017 Author Posted July 21, 2017 Seem to have resolved the issue by doing the following 1. Add a MIME-Type for '.esd application/octet-stream' in IIS on the WSUS server. 2. Made the following changes in the IIS Application Pool for the WSUS Page: Queue Length: 25000 from 10000 Limit Interval (minutes): 15 from 5 "Service Unavailable" Response: TcpLevel from HttpLevel Private Memory Limit (KB): 0 from 18342456 3. edit the web.config ( C:\Program Files\Update Services\WebServices\ClientWebService\web.config ) for WSUS Stop the IIS and do following changes: replace with One of my test 2016 servers started to communicate with the WSUS Server and downloaded patches, the other didn't, but after disabling IPv6 this one also did too. They still report as Windows 10 though. Thanks Gareth
franna01 Posted January 17, 2019 Posted January 17, 2019 Just did items 2 and 3 this in my lab environment and it worked. Win 2016 WSUS server is now patching itself as well as the Win 10 and 2012 systems. Thank you for posting.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now