We are about to make a major push into encrypting our Macs with FileVault 2, starting with 10.8.x devices and moving down to 10.7. I've followed the whitepaper on Administering FileVault 2 on Mountain Lion and have it working OK in the lab, but I did notice that if a user reboots his/her Mac and does *not* enter in their password (using Current or Next User setting) to begin the FileVault process, that the machine simply reboots. FileVault 2 encryption never beings, and because the policy set to run only "once per computer", it never runs again.
I am wondering if there's away around this. Specifically, how can I configure the policy to reapply itself on machines that are not encrypting or that are not encrypted? Is setting the Execution Frequency to "Ongoing" the proper course of action? Is there anyway to remove / hide the "Cancel" button when the user is prompted to encrypt?
thanks,
mike
