I'm not sure if this is an issue or just coincidence, but has anyone stumbled upon this issue?
I did a fresh install of XP and pushed all my ePO stuff to it, including EEPCv6 agent/client. After both were installed and I could see the registry keys as well as the installation folders, ePO would not recognize that it was installed and the client would not enforce my policy to encrypt and therefore encryption would not start. I was logged in with a local admin account and had yet to logon with a domain account. I removed and reinstalled the agent/client but logged in with a domain account and after reinstalling the agent/client, encryption finally started.
I had observed the same thing. It might have something to do with EE user based policy which is mandatory. I guess until user is determined, encryption cannot really start. To me, it looks that EE product and user policies are intertwined quite badly, and both need to be triggered to "activate" encryption.
Since EEPC 6 Does not have support for stand alone accounts it does require a domain account to start the encryption. In the future when it does allow stand alone accounts this issue should go away. The "function" of this is to prevent you from mass deploying EEPC and locking out users who don't login to the domain. It's actually pretty nice to know that the software checks that the currently logged in user has an account assigned to the machine before implementing preboot and encrypting.
Maybe it is "nice" but not flexible for many deployment strategies, where you may use different account to deploy software than user's account.
Now, that "deployment" account must be domain account and assigned to PC, to trigger initial disk encryption.
If the user has an account why would a deployment strategy require them to be logged in as anyone else? Unlike with v5 you don't have to run the installer as an administrator. Unless they don't login to the domain, in that case its not a supported configuration with V6.0 anyways. The added flexibility/feature should be available in future releases.