I am working with the release v6 now for a week and it seems a little, how should I say, brattish.
I push the client task for the EEPC Agent and Host package to my machines and there are a couple quirks. When the McAfee Agent checks in for new policies the EEPC Host installs first and prompts for a reboot. This if fine but the EEPC Agent does not install right after EEPC Host. The machine may get rebooted and will not be active. This means after a reboot and the McAfee Agent will check for policies/ updates again and finally install the EEPC Agent. So it will be a good practice to schedule the EEPC Agent to install first and the EEPC Host to install after.
Now when both are installed I notice it takes very long time for EE to become active and start encryption. This is even with checking for policies, enforcing policies, Collect and send props, and updating security. I have everything properly configured. My EE Product Settings and UBP are assigned to my systems and the proper EE users are assigned to the systems. I see that the EE policy is being updated but no activation and encryption. After a few minutes I reboot (no MEE PBA as of this point) and logon to Windows as user that has MEE UBP assigned through ePO. This was the same user I used as when I was installing EE Agent and Host. Sometimes it finally starts encryption and sometimes it does not. Sometimes I have to log off and log back in as a different user to kickstart the encryption. Every time I notice the encryption progress bar was already 1/4 complete. It is like the activation/encryption did start after the first reboot but the EE Agent did not show it on the Quick Settings status screen. This can be a problem for administrators and users to tell if the machine is truly activated or what stage of encryption status. In v5 you could tell right away after the first synchronization occured and the encryption progress from the MEE Client Status window.
The systems are Windows XP SP3. Anyone else seeing this issue?
Message was edited by: chris.schaber on 11/25/09 9:18 AM