PRODUCT IOTS » product-uem 6.3.0 GA

Environment details
Staging server(620)

Prerequisites
Login to the server and Enrolled windows device

Steps
create ADMX policy and apply to a device

Description

When sending the policy payload in ADMX, we are including all the policies under each category along with their configuration status. For example, consider the App-V ADMX policy. If we enable a policy called "Streaming_Package_Source_Root," a few other policies (e.g., Streaming_Reestablishment_Retries, Streaming_Reestablishment_Interval, Streaming_Location_Provider, Streaming_Location_Provider_Prompt, Streaming_Certificate_Filter_For_Client_SSL, Streaming_Certificate_Filter_For_Client_SSL_Prompt, Streaming_Verify_Certificate_Revocation_List, Streaming_Shared_Content_Store_Mode, Streaming_Allow_High_Cost_Launch, Streaming_Require_Publish_As_Admin, Streaming_Support_Branch_Cache) are sent in the payload as "Not configured." This behavior causes some issues on the device side. To mitigate this, we need to send the payload including only the enabled policies and their respective data.

Result
"[{\"name\":\"Streaming_Package_Installation_Root\",\"status\":\"NOT_CONFIGURED\"},{\"name\":\"Steaming_Autoload\",\"status\":\"NOT_CONFIGURED\"},{\"name\":\"Streaming_Package_Source_Root\",\"status\":\"ENABLED\",\"data\":[{\"Package_Source_Root_Prompt\":\"aaaaaaaaa\"}]},{\"name\":\"Streaming_Reestablishment_Retries\",\"status\":\"NOT_CONFIGURED\"},{\"name\":\"Streaming_Reestablishment_Interval\",\"status\":\"NOT_CONFIGURED\"},{\"name\":\"Streaming_Location_Provider\",\"status\":\"NOT_CONFIGURED\"},{\"name\":\"Streaming_Certificate_Filter_For_Client_SSL\",\"status\":\"NOT_CONFIGURED\"},{\"name\":\"Streaming_Verify_Certificate_Revocation_List\",\"status\":\"NOT_CONFIGURED\"},{\"name\":\"Streaming_Shared_Content_Store_Mode\",\"status\":\"NOT_CONFIGURED\"},{\"name\":\"Streaming_Allow_High_Cost_Launch\",\"status\":\"NOT_CONFIGURED\"},{\"name\":\"Streaming_Support_Branch_Cache\",\"status\":\"NOT_CONFIGURED\"}]",