I'm not seeing how to use that option and apply it only to the systems that are in the process of migrating from the old encryption to the new. We do not want change the reboot policy for everyone. We just need the reboots for this specific product deployment.
I'd like to configure this with a query result and client tasks or sever tasks to fully automate this.
Maybe a query that finds all the systems with the old encryption product still installed after we send the uninstallation file to those systems, pushes drive encryption agent to the system and then prompts the user to reboot. After that reboot is completed, install drive encryption product and prompt for reboot 2. After the second reboot is complete push EEGO and prompt for reboot 3. That would be one way to do this that would allow the users to control reboots.
If it cannot be done that way or users ignore the reboot prompts and take no action, then our next choice would be to just schedule the reboots of the systems still with the old encryption product.
To do it this way, we could do the following:
1. Copy the uninstallation trigger file to all systems with old encryption product via our AD Group Policy (assuming there is no way for ePO to do this).
2. Use ePO to query systems that do not have MDE active and also still have the old encryption product installed.
3. Send email notification to users of the computers in the query results telling them their workstations will reboot automatically every morning for the next 3 days.
5. Schedule push of MDE agent to systems in the query results on day 1 at 3AM with forced reboot.
6. Schedule push of MDE client on day 2 at 4AM with another forced reboot. This installation should only happen on systems that have the MDE agent successfully installed and not the MDE product.
7. Schedule push of MDE EEGO on day 3 at 5AM with another forced reboot. This installation should only happen on systems that have both MDE agent and MDE client successfully installed, but still missing EEGO.
How could this be automated?