That is not a stupid question at all. In my experience, all compliance policies require the device to be powered on, with and internet connection, enrolled, and communicating with the console for it to actually perform the compliance action. With that said, a command will be sent from the console as defined in the policy, even if the device is not meeting those requirements, then it should take place on the device the next time is powered on/internet connection, etc. Your example of device check in for 2 days, then sent enterprise wipe. Let's say a device is turned off for 7 days. The command from the console will still be sent after 2 days(as defined in the policy), but it wont actually take place on the device until it is powered on with internet connection (7 days later in this example). So, it does not live on the device. As for the other question, I am not 100% sure why device wipe is not an option, but I would assume this is a limitation by apple.
That is not a stupid question at all. In my experience, all compliance policies require the device to be powered on, with and internet connection, enrolled, and communicating with the console for it to actually perform the compliance action. With that said, a command will be sent from the console as defined in the policy, even if the device is not meeting those requirements, then it should take place on the device the next time is powered on/internet connection, etc. Your example of device check in for 2 days, then sent enterprise wipe. Let's say a device is turned off for 7 days. The command from the console will still be sent after 2 days(as defined in the policy), but it wont actually take place on the device until it is powered on with internet connection (7 days later in this example). So, it does not live on the device. As for the other question, I am not 100% sure why device wipe is not an option, but I would assume this is a limitation by apple.