Generally speaking, when should we expect these to be added? I know (and did) download the .zip file and upload them, but then we have âmultipleâ Edges in the system, which makes it a bit complicated to make/update policy, as weâre referencing multiple âEdgesâ. Replace âEdgeâ with âChromeâ, or anything really.
What is the âexpectedâ release of Cloud ADMX updates? And are these release notes anywhere; IE, do they come out with a new .1 release type thing, or are they added into the console âwheneverâ?
We donât currently have a set scheduled to do this. I try to go in every few months and do a sweep of all of the provided ADMX templates and update what there is to update. If itâs in-between updates and there is something that you need done ASAP, you can always create a ticket for it and weâll do it for you.
Sorry, I got pulled away on some other tasks which means Iâm going to be that jerk that posts a reply towards the end of a Friday afternoon, lol. Is this something thatâs testable? Yes. However, grabbing an ADMX file that weâre not using and/or testing on something thatâs already in production both seem a little âextraâ at the moment, so Iâm hoping you already have an answer instead of making us test Hereâs the scenarioâŚ
Customer uploads Edge ADMX file/policy (CE) because it updated.
Customer creates or updates an EPM/PP LPM Administrative Templates Manager policy (CP) based on CE.
Netwrix updates/uploads the same Edge ADMX file/policy (NE).
Customer deletes CE (because it makes everything cleaner and why have multiple uploads of the same ADMX?).
Does the CP remain unchanged because the ADMX policies/definitions are still present in the customerâs tenant/environment because the NE is still present?
Does the CP bomb out because it no longer has the underlying ADMX policies/definitions are no longer present?
As it is in Group Policy, so it is in the cloud. The ADMX template is just there for a GUI representation of the configuration options. Once the policy is created, itâs no longer required (unless you want to edit it).
Further, it actually doesnât know where the ADMX file is located, and it doesnât care. It only knows the path within. Whether itâs Client side or PolicyPak (Endpoint Policy Manager) side, updated or an older version of the ADMX, it doesnât know or care. As long as the path, setting and options are the same, it will match up.
Thanks, John. That makes sense. In that case⌠when you, Netwrix, update ADMX files on your end, are they a rip and replace? Iâm still thinking of the Edge ADMX files because that makes it easy and can be applied to others. Currently, the Edge ADMXâs display name from Netwrix is âMS Edge - 135.0.3179.66.â Letâs pick a random policy like âEnable the default search provider.â If we create an LPM policy based on that Edge ADMX definition,
then Netwrix updates the Edge ADMX so it now has a display name something like 136.x.x.x, will our previously created âEnable the default search providerâ LPM internal policy turn red (uneditable but still applicable)?
Will it remain status quo because of the underlying namespace and filename remaining the same?
Iâm sure you can probably see where Iâm getting with this⌠will we need to recreate LPM policies with each updated ADMX file if we need to edit said policy?
Yes, it is a rip and replace. But No, it wonât turn red unless that policy was deprecated (and yes, still applicable).
There is usually very little differences between versions. They usually keep the old configs around for a while. And even if they are deprecated, theyâll quite often put them in a âDeprecatedâ folder where they are still accessible.
Hereâs the scenarioâŚ
