Jump to content

Recommended Posts

Posted

Hi all,

 

We're in the middle of preparation to deploy configuration via Intune. This is currently a 100% hybrid environment.

 

We're trying to do some Windows 10 --> 11 feature upgrades with some success... a full Win 11 upgrade to be accomplished over Easter hopefully pushed out from Intune.

We're currently testing deploying to device groups using Intune update rings.

 

However, unbeknownst to us, we've been made aware that a good number of our Win 10 machines have actually upgraded to 11 recently.

 

We still have a WSUS server that is distributing updates on-site, that is not pushing out the feature update.

 

This is what we're seeing on the clients....

 

1.thumb.JPG.1178c138d2a4d503e0396fb8a2afa48e.JPG

 

 

Some of the update policies are defined by MDM which I don't understand because we haven't configured this for any machine unless in the update ring group.

 

If a device is NOT in the update ring, it still seems to be picking up the updates defined for that ring.

 

The windows version being pushed out is 23H2.. the same version we have approved in our feature update policy.

 

 

2.jpg.6b0ff99c5e49b6bb353121f48df9717f.jpg

 

 

 

 

 

What is the default update behaviour in Intune/Azure?.. and why is the client ignoring the group policy, which should take precedence.

 

Also, we haven't deployed any Intune group policies to any users/devices yet either.

 

 

Any ideas?

 

 

 

Cheers in advance  :)

 

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...