Jump to content

Recommended Posts

Posted

Hi all,

 

An odd bug I found today that I thought I'd share here as its Education specific.

 

Currently preparing to roll out 1803, I've made a new build which is working well (side note - just edited the WIM offline, no deploy and capture this time! :eek:). But, after a bit of testing it turned out that our new 1803 build won't update reliably from our 2012 WSUS server, not even to report in. If I remove GP settings, it updates online just fine.

 

After much testing, I found out that the following GP setting was the culprit:

 

 

No idea why, as this is just a power policy override to allow laptops in carts to update overnight. But, if this policy setting was enabled, I could not connect to my onsite WSUS server. I've junked it as it wasn't important, but I'd love to know why it was a problem...

  • 8 months later...
Posted

I found this out recently to, still not fixed in 1809. I've raised it with WSUS Guru Adam Marshall who was going to look into it.

 

It would be a really handy feature if it worked.

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 account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...