Hello,
Until now, we were using WSUS to update our SH, it was not running too bad.
We are now trying to use WUfB and for this we created a 'Windows 10 update ring' policy.
It looks like this,
Two of these machines (SH 2S and SH v1) are getting this policy since the 3rd of March. The other one since the 4th of March.
These machines are not receiving the old configuration profile used to configure wsus.
These machines have always had access to WindowsUpdate, it is not blocked by our proxy.
The maintenance window for the SH is from 8pm for 5 hours.
The problem we are seeing is that the 'last scan time' stays desperately on 'not scanned yet',
Of course, it is quite hard to do some troubleshooting because we don't have physical access to the devices.
Is there something we forgot to configure ?
Thanks for your advice
Marc
A small update, today I looked at the results and noticed that the 'Quality update version' has changed on the machines :
But the 'last scan time' is still on 'not scanned yet'.
The field 'update status' doesn't seem to be quite reliable as it always indicate 'up to date'.
So it seems to be working, the machines seem to have installed the latest CU but not the feature update. I can't be sure unless I go physically to each devices and check them.
Marc