Hi Stefan, Thanks for the response. This problem manifests no matter how I try to deploy multiple configurations inside a Windows Mobile profile: Adding additional settings to an existing profile results in the task completing successfully, but none of the additional settings are applied and the device always reports as non-compliant due to no PIN being set - the PIN is set as demonstarted by having to enter a PIN to unlock the device. Creating a new profile containing all the required settings and transferring this to the device results in the existing profile being replaced. The device then reports non-compliant due to no PIN, although a PIN is set and required to unlock the device, and none of the additional settings are applied. This occurs with any profile containing anything other than password settings. The only way to clear non-compliance is to unenrol the device and enrol again. and am awaiting a response. I have a support case open Regards, Neil.
↧