Automatically handle <Add> and <Replace> for Windows configuration profiles that <Add> for initial setting enforcement

[marko-lisica]

• @marko-lisica: User requested this because they want to edit Windows configuration profiles that use <Add> verb (e.g. WiFi profile that first must be added to the host with <Add> and if it's resent or updated it won't work, because if it's already set with <Add> on the host it must be edited with <Replace> verb.
  • @marko-lisica: In the interim use one configuration profile to initially <Add> setting to the hosts that don't have it already, and use another profile to edit setting with <Replace> verb. This is a complex workflow to enforce WiFi settings, where a user needs to find which hosts already have settings applied so they can use or accordingly. They might create a label for this (write a query to find a hosts that already have WiFI setting applied).
  • @marko-lisica: Eventually We could build feature to recognize if host has a setting applied and use appropriate verb (<Add> or <Replace>. MDM protocol returns status code 418 when setting is already applied, so that could be a signal to replace verb to <Replace> automatically by Fleet.
• @marko-lisica: There are 2 bugs that are related to this feature request - Fleet resending WlanXml CSP unnecessarily is causing errors #24394 & Windows profiles not resent to device on fleetctl gitops update #25030

---

User stories