Certain edits may generate a conflict and might not be possible to publish. For example, editing a BIOS Settings policy that applies to a particular platform cannot be reassigned to a different platform, as BIOS settings may or may not be the same for both platforms. In this case, a new BIOS Settings policy needs to be created. Deleting a Policy by clicking on the trash-icon removes it immediately from HP Connect. Adding/Removing Groups to a Policy For a policy to be enforced on HP supported devices, it must be published to an Azure AD device group. A device group can also be removed from the policy.
When adding or removing Connect policies from a device group, any existing published policies (for the selected group) will be recreated with the changes made. To add or remove device groups, in the Policy List window, select the Policy to be modified, and click on ‘ Add or Remove Groups’ . When adding an Endpoint Manager group and clicking on Save , a dialog asks to ‘ Publish’ or just Close’ to save the Policy without publishing. If selecting ‘ Publish’ , the policy is updated to the organization’s tenant, where will then be enforced via its remediation and compliance task. Policy Conflict Resolution – Feature Change!
If an existing group device Policy exists for a similar type (Updates, Settings, Authentication) for the same platform, it will result in a conflict, and the new policy will replace existing policy when published. User can prevent the new policy from overwriting the existing policy by unchecking the Group selection in the conflict dialog. User will no longer need to resolve the conflict by confirming to Apply new policy or keep current policy. User can View the difference by clicking on the View button. The View dialog will display the current policy and the effects of publishing the new policy. Page 11 September 27, 2022 Version 1.2.0 © 2022 HP Development Company, L.P.
The information contained herein is subject to change without notice.