Hello
I have an interesting 'issue' relating to Mandatory profiles in conjunction with UEM
We have created a mandatory profile for Windows 10 1803, and set the path to be used via Group Policy. Without the UEM agent on the desktop, when users login they load the Mandatory profile, and when you look in the User Profiles applet, the user is listed as having a profile of type 'Mandatory'. The mandatory profile works fine.
When I install the UEM Agent and point at the config share, the user logs on, but the profile is now of type 'roaming'. Its as if the Mandatory profile has been duplicated (as if it where the DEFAULT profile). Everything still work fine, but my customer wants an explanation. All I can think of is that this is by design so that the profile becomes writable to allow UEM to wrap around the imported AppData and registry etc.
Does anyone know (Pim?) is this by design? and if this behaviour is documented anywhere?
Thanks
Sean
