Separate patch management builds

Andrew_Kuntz1
New Contributor II

Does anyone know how they plan to handle intel and m1 versions for patch management (Ex: Zoom)?

4 REPLIES 4

alessio_tedesco
New Contributor III

You can create two smart groups - one for devices running on intel and one for devices running on M1 - and scope the patch policies to the smart groups; would this solution suite your needs?

Andrew_Kuntz1
New Contributor II

@alessio.tedesco How would this be possible when you can only push one policy to a definition?

alessio_tedesco
New Contributor III

What do you mean?
I've just created 2 patch policies for the same target version. You can try scoping a patch policy for intel and the other one for m1.
I' haven't tested it yet, just thinking about a possible solution
ecd98314d53b40fab6cee12b99046cdb

joshsw
New Contributor II

The issue is that only one package is allowed per definition version. You can't assigned both an AppleSilicon and Intel package to the same definition version.