Mark Minasi's Tech Forum
Register Calendar Latest Topics
 
 
 


Reply
  Author   Comment  
Jon_AK

Avatar / Picture

New Friend (or an Old Friend who Built a New Account)
Registered:
Posts: 71
Reply with quote  #1 
Good morning,
Installed WSUS onto our Server 2016 box this morning - 6 hours ago now.  All appeared to go well with no errors and the sync completed in about 30 minutes.  I set the group policy for windows updates and the intranet server  I forced a gpupdate from two clients and so far I have been able to get only 1 client to show up in the WSUS console but only after running wuauclt /detecnot & wuauclt /reportnow.

I checked to make sure in IIS that the server was listed there with the correct port of 8530 & 8531, verified this in the client registry settings and made sure all the services were started but still only 1 client shows in the console with the status of "computer has not reported yet". Launched a browser pointed at http://servername/iuident.cab but receive only a blank screen, same as if I launch a browser without the .cab file added.

One note about IIS, I had installed the SMTP role/feature a few months ago in order to facilitate email capability with a couple MFP's that would not cooperate with using the exchange online email server.  Could this be an issue?  The server name I discovered is the same server name I used in WSUS.
0
donoli

Senior Member
Registered:
Posts: 598
Reply with quote  #2 
Possible solutions:

https://community.spiceworks.com/topic/286814-wsus-and-iis


https://social.technet.microsoft.com/Forums/ie/en-US/dc1019d8-a63a-46f0-ad54-948696e59c89/wsus-on-server-2012-client-not-browse-iuidentcab?forum=winserverwsus
0
Jon_AK

Avatar / Picture

New Friend (or an Old Friend who Built a New Account)
Registered:
Posts: 71
Reply with quote  #3 
On the Technet forum I was advised about running WSUS on a DC and what could happen to the database.  Granted it would be nice to have another machine or at least a VM to host these additional services but like everything, only takes money....  Due to that discussion, I stumbled upon a link in my searches and found a guy that used powershell to uninstall WSUS and the WID database feature.  After running the powershell cmdlet, re-booting and then deleting the contents of the Windows\WID folder, the re-installation of WSUS and the database cured all ills.  All clients appeared immediately after group policy had been applied.  Unless you knew that the database was stored in the WID folder, no way of knowing where to find it to be deleted.  Simple script but worked first time out.  Powershell script I found: 
Quote:
Uninstall-WindowsFeature -Name UpdateServices,Windows-Internal-Database -Restart
0
donoli

Senior Member
Registered:
Posts: 598
Reply with quote  #4 
Quote:
After running the powershell cmdlet, re-booting and then deleting the contents of the Windows\WID folder, the re-installation of WSUS and the database cured all ills.


That's good news.
0
Previous Topic | Next Topic
Print
Reply

Quick Navigation:

Easily create a Forum Website with Website Toolbox.