WSUS - This computer has not yet contacted

varkanoid said:
I would make sure your WSUS server is up to date first. There was an option in the wizard setup (or in options) that you had to tick to make sure your WSUS was up to date.

It shouldnt recognise Win10 machines as Vista.

https://community.spiceworks.com/topic/1265378-windows-10-showing-up-as-vista-in-wsus

although this is for Windows Server 2012
Click to expand...

This is the WSUS download I installed.

Do yo mean check that my WSUS mechanism is update or that the server it's self is up to date?

Seems I have a two factor issue.

1. The Win 10 machines are showing up as Vista.
2. I believe I have this issue as well.

Regarding this issue, if I click for updates enough times it does eventually return a green "Windows is up to date" message. But I refreshed the WSUS and it still shows the ! and says the machine hasn't checked in yet and shows 0% Installed/Not installed Percentage.

Hmm on the Win 7 client, if I go in to View update history it shows it updated Microsoft Security Essentials today, which must be the update check I just ran and it must have picked it up from the WSUS.
 
Last edited:
Before I reinstalled the WSUS there was no Win 10 listed in the classifications section.

Now there is. So presumably it must be the latest version already.

win10.jpg


How do I go about updating it?
 
Make sure the server itself is up to date and that you have the option for WSUS to update itself enabled.
To be honest if I had this issue I would A) see if I can find a licence for Windows 2008 R2 and B) wipe the server and reinstall the OS and WSUS from scratch.
Failing that just do B) with the Windows Server Standard you have.
Its only way to be sure.

I never had this problem (Win 2008 R2) and I had way more devices than you did so I cant understand why its exceeding limits.

opethdisciple said:
Before I reinstalled the WSUS there was no Win 10 listed in the classifications section.

Now there is. So presumably it must be the latest version already.

win10.jpg
Click to expand...

Should only have Windows 10 ticked you dont need the rest of the Win 10 options
 
Check for updates ran on machine hosting WSUS.

650Mb of updates found. Installing now.

WSUS autoupdate I do remember is turned on already. I'll turn off all thr other Win 10 options as advised.
 
Well...

I've updated the host machine it's self over night.

Still we have ! marks against most PC's and it is not detecting the Win 10 or Win 8.1 machines properly. They are showing up as Vista and XP64 respectively.

However, most of the machines are now sitting at 98% rather than 0% which they where showing yesterday. So maybe over time it will indeed sort it's self out.
 
Sometimes a complaint is actually a good thing.

User came to me this morning saying their computer was applying 182 windows updates....

:p

Seems like the WSUS is doing it's job then! :D
 
OK.... guess I have to sort this out.

The WSUS seems to be working so that's good. However, the machines are so far behind that when the updates get applied where talking 80-180 updates here.

This is holding the end user up.

How do I go about changing the time that updates get applied?
 
The GPO sets the time the updates are applied. eg ours are 3am Thursday only with a check in period set to 6 hrs (the one that has a maximum of 22) no autorestart. Have a look at the other settings too you can change the time it nags users to reboot, or not tell them at all etc. You could set all the PC's to install at 11pm and enable auto reboot after install so it does a restart at night and then users wont have to wait the next morning. Obviously once set tell all your users to leave their PC's on when they go home.

Or do what I did at the beginning just tell them to make a cuppa coffee/tea whilst its updating at boot up. :)
 
Last edited:
It was set to:

Auto download and schedule the install
Install Day every day
Install time at 3am

---

Auto download and notify for install is the default. Maybe I should set it to that?

I hoping that would give the end user at least an option of when to apply the update.

However according to the discription for this option it gives the end user the option of what to install. I dont want them to have the option to deselect any updates. :o

"Auto download and notify for install - Default option
This AU option is particularly useful to ensure that an update installation happens at a time most convenient for the local administrative end user in relation to work imperatives, maintenance windows, and planned or end of the day shutdowns. This option permits the automatic download to occur in the background, but gives the client administrative end user the ability to select which downloaded updates to install and when to install them. After automatic downloads are completed, an icon appears in the notification area. When users click the icon they can see which updates were downloaded and select all or some of them to install."

With option 3 Auto download and notify for install, I'm hoping it's the one where when the user chooses shutdown it will start installing the updates.
 
Last edited:
You would be better off having auto download and schedule to install
install time 3am
auto restart

so updates download, install at 3am then auto restart PC.
All done out of hours. Providing the PC is on of course.
Then once clients are up to date set what you want.
 
So it seems this is working now. (Well more and more machines on the network are downloading and applying windows updates. We still have ! in the WSUS and 99% applicable/non applicable)

I looked at one of the PC's on Fri and before this week it was almost 3 years ago they had seen a Windows update!! :eek:

Was thinking about this actually because the machines have between 80-180 updates pending.

Maybe I should have just pushed out the recent Win 7 rollup?
 
A completely unpatched Windows 7 or Windows 2008 R2 machine will require multiple "hits" from the WSUS server before it can update itself (there is a known bug that kicks in after x number of changes that causes it to fail). The default setting is every 22 hours, which is why you are slowly starting to see stuff happening now. If you changed the GPO to a few hours (I wouldn't recommend it unless you know what you are doing) it would probably all be resolved in 24h.

That Win7 rollup may have a few bugs (has at least one extremely serious one). I'd stay away for now.
 
Yeah you are better off letting it run its course. Dont forget sometimes you have to let x update install before y can be installed too. eg .net updates.
 
rotor said:
A completely unpatched Windows 7 or Windows 2008 R2 machine will require multiple "hits" from the WSUS server before it can update itself (there is a known bug that kicks in after x number of changes that causes it to fail). The default setting is every 22 hours, which is why you are slowly starting to see stuff happening now. If you changed the GPO to a few hours (I wouldn't recommend it unless you know what you are doing) it would probably all be resolved in 24h.

That Win7 rollup may have a few bugs (has at least one extremely serious one). I'd stay away for now.
Click to expand...

For the moment the DC and Wind sever machines are excluded from receiving updates. I did this on purpose as they are critical machines and I don't want to break them.

Whats the industry standard thing to do with DC on the network?

Allow them to auto update or manually manage it?
 
opethdisciple said:
For the moment the DC and Wind sever machines are excluded from receiving updates. I did this on purpose as they are critical machines and I don't want to break them.

Whats the industry standard thing to do with DC on the network?

Allow them to auto update or manually manage it?
Click to expand...

Dont know what the industry standard is but we've got a forest of about 15 and they all auto update one day a week and reboot at 1am.

Although thats different for us as if one goes down AD still works as the client just uses one thats available to log on. Single DC probably manual.
 
To do them all automatically you'd have to have multiple GPOs to setup different time windows for them so they didn't all reboot at the same time. Assuming you have a small number of them, I'd do them manually. Just make sure you have a reminder set every month.
 
You must log in or register to reply here.
Back
Top Bottom