Hey Sean, The process is the same. To bring them into supervised status you'll need to wipe and enroll them again. And you can't use any previous iCloud backups in the process. I have had succ...
See more...
Hey Sean, The process is the same. To bring them into supervised status you'll need to wipe and enroll them again. And you can't use any previous iCloud backups in the process. I have had success using the proximity restores when going from device to device. In these cases I normally recommend you set a date going forward where all devices enrolled will be done through ABM setup. Trying to bring older devices into the fray is often chaotic and not worth the trouble. The only time it is really doable is if wiping the device is of no consequence to the use case at hand. Like Kiosks, and single use devices that have no personal data attached.
No, you can't functionally stop Apple from updating anything. You could go all crazy and and attempt to stop ALL apple communications on devices, but that would have other consequences. There are...
See more...
No, you can't functionally stop Apple from updating anything. You could go all crazy and and attempt to stop ALL apple communications on devices, but that would have other consequences. There are no rollbacks for Apps and if they are set for autoupdate, it will do so. Sad but true. Hopefully MS will address whatever the problem is quickly.
MDM is the way you know via hub etc. Application is a container solution, like ' container.' You can also use Boxer to enroll standalone as well. Thus you are managing the Application container ...
See more...
MDM is the way you know via hub etc. Application is a container solution, like ' container.' You can also use Boxer to enroll standalone as well. Thus you are managing the Application container only.
Abraham, your points are valid, but not all organizations are equal. You'd be surprised on how much this policy varies. COPE was designed specifically for this scenario and keeps the data separat...
See more...
Abraham, your points are valid, but not all organizations are equal. You'd be surprised on how much this policy varies. COPE was designed specifically for this scenario and keeps the data separate. The employee is responsible for the ' Personal' side. Andy, no it will not ask for their ID. since it is not the device owner in the end.
Up on the right, to the left of the Search List box is an icon that is a box with an arrow in it. Hovering over it reveals it is an export button. It will export the current view into a CSV.
Make a compliance policy that will install the SAM profile only after a certain condition is set, like having a passcode present etc. Otherwise there is no way to set precedence.
look at your APNS for applications, not MDM. They recently issued a renewal script for those: https://resources.workspaceone.com/view/clvzq5jfhk8h3cx47z2h/en
Delete does 2 things; 1. Enterprise Wipe (removes all managed data and unenrolls), 2. deletes the record from the console. If you want to fully wipe the device, you could issue a device wi...
See more...
Delete does 2 things; 1. Enterprise Wipe (removes all managed data and unenrolls), 2. deletes the record from the console. If you want to fully wipe the device, you could issue a device wipe first, then delete from the console. BUT, I generally just delete the device from the console and then erase the device through settings on the device. Like Dave said though, if the device is not DEP enrolled (Supervised) then you could run into activation lock issues. So beware of that situation too.
Probably had to do with sessions. Sounds like the devices have open sessions on the old server. By restarting IIS you are closing all sessions and they reconnect.
