Question about Updates

[O365-Zende]

Hi, just had a load of updates drop on the deployer.

My question is, how are we supposed to add them?

• They don't seem to have the same settings (small part of the original) as the original policy. So it's not a direct replacement.
• I went through it side by side, and all the settings listed were the same as my original except 1, which I amended.
• So why are extra settings included if they haven't changed or are already in the original policy?

Just a little clarity, please.

[Michael-eit]

This needs way more detail. what settings? what policy? what updates?

[O365-Zende]

This needs way more detail. what settings? what policy? what updates?

Ok, the OIB Web Portal https://deploy.openintunebaseline.com/
It is showing a number of updates to 3.8 on some policies.
Examples

• Win - OIB - SC - Microsoft Edge - U - User Experience - v3.8
• Win - OIB - SC - Microsoft OneDrive - U - Configuration - v3.8
• Win - OIB - SC - Microsoft Store - D - Configuration - v3.8

These updates don't seem to be full policies, as they only have a few items in them.
When I compare the previous policy to the latest side by side. They may have 15 items in the 3.8 but only 1 or 2 items are actually different from the 3.7 I am currently running as an example.

Am I doing it correctly by comparing the 2 policies, old and new, then adjusting the main policy with the amendments and then changing the version number of the old policy?

Does that make more sense?

[Michael-eit]

I have never used that tool. But what you are discribing would be correct. updating is just removing and dead bits adding the new bits, updating the name then testing before deploying. I normally run out of the "https://github.com/SkipToTheEndpoint/OpenIntuneBaseline/blob/main/WINDOWS/SETTINGSOUTPUT.md" update my dev tenant. then push to ourselves, then to clients.

[O365-Zende]

I have never used that tool. But what you are discribing would be correct. updating is just removing and dead bits adding the new bits, updating the name then testing before deploying. I normally run out of the "https://github.com/SkipToTheEndpoint/OpenIntuneBaseline/blob/main/WINDOWS/SETTINGSOUTPUT.md" update my dev tenant. then push to ourselves, then to clients.

The issue I'm having is the newly imported policy often already has similar settings that are in my lower version policy, but the updated one isn't a true replica, as it has loads of missing settings as well, which I have in the lower version policy.

Ok, so your method, whatever is listed in those files, is the "truth", per se (i.e., the latest complete policy set)

I'll have a look, thanks.

[Michael-eit]

I have a bunch of other tweaks that our clients want/need and other things I want on or changed for whatever reason. I think I imported OIB back in 2.7 or something. I have not imported it since. Anything new I go through update the older versions test any deploy. its not meant to be a compliance set you just toss on a tenant and call it job done (though i worry so many people are doing that and not learning the why).
My recomendation, chip through it understand what each setting or change does and apply the update where needed.