We're testing Android for Work with some Zebra devices and seems like the Custom XML policies that are applied on prod, stopped working in Afw mode.. They are no longer listed as 'pending', 'failed' or 'implemented' on the device.
On our testings, we are enrolling devices using QRCode whith these DPC commands:
I guess that Afw changed the policy classification behavior to Zebra devices.... or the Zebra device is not being identified to XenMobile as a Zebra device (and just being identified as Afw).
Is there any way to trace the policy classification or to see why the policy is not being delivered to Zebra devices when Afw is enabled?
It's an onprem server, and they are using 10.8 version... We're planning to update as last try.
Question
Alessandro Miotto Marques1709152314
Hello all
The customer uses Android Zebra devices and there's some Custom XML policies configured in it's DG's, that are working as should be in his production,. This policies are configured like explained in this documentation.. https://docs.citrix.com/en-us/xenmobile/server/policies/custom-xml-policy.html
We're testing Android for Work with some Zebra devices and seems like the Custom XML policies that are applied on prod, stopped working in Afw mode.. They are no longer listed as 'pending', 'failed' or 'implemented' on the device.
On our testings, we are enrolling devices using QRCode whith these DPC commands:
"android.app.extra.PROVISIONING_DEVICE_ADMIN_COMPONENT_NAME": "com.zenprise/com.zenprise.configuration.AdminFunction",
"android.app.extra.PROVISIONING_DEVICE_ADMIN_SIGNATURE_CHECKSUM": "qn7oZUtheu3JBAinzZRrrjCQv6LOO6Ll1OjcxT3-yKM",
"android.app.extra.PROVISIONING_DEVICE_ADMIN_PACKAGE_DOWNLOAD_LOCATION": "https://play.google.com/managed/downloadManagingApp?identifier=xenmobile",
"android.app.extra.PROVISIONING_LOCALE": "pt_BR",
"android.app.extra.PROVISIONING_LEAVE_ALL_SYSTEM_APPS_ENABLED": true
I guess that Afw changed the policy classification behavior to Zebra devices.... or the Zebra device is not being identified to XenMobile as a Zebra device (and just being identified as Afw).
Is there any way to trace the policy classification or to see why the policy is not being delivered to Zebra devices when Afw is enabled?
It's an onprem server, and they are using 10.8 version... We're planning to update as last try.
Suggestions are welcome!
Link to comment
1 answer to this question
Recommended Posts
Archived
This topic is now archived and is closed to further replies.