EEPC 6.2 Migration to EPO 5.0.1 Server
I just completed moving a handful of laptops running EEPC 22.214.171.1245 from an old EPO server to a new EPO server and wanted to share my experience in case it's helpful to anyone. We have an old EPO server running EPO 126.96.36.1999 along with about 20 PCs and laptops running EEPC 188.8.131.525. We recently built a new EPO server running version 184.108.40.206 and recently imported the packages and extensions for EEPC 220.127.116.116. We configured new EEPC policies and tasks on the new server rather than attempt to transfer them over. The EEPC policies on each EPO server are a little different, but they both use the same Active Directory source for EEPC users.
I was told by a McAfee Support Engineer for EPO that in order to migrate the EEPC agents to the new EPO server, I would need to decrypt each unit before migrating it to the new EPO server. Based on a few internet searches, including in this forum, I found evidence to indicate that prior to EEPC 6.2, that was true. However, it appears that with EEPC 6.2 and higher, EEPC will upload the keys to a new EPO server.
Rather than registering the old EPO server with the new EPO server as a 'Registered Server' and using the 'Transfer Agent' functionality, I decided to just try deploying version 4.8 of the McAfee Agent from the new (18.104.22.168) EPO server to 'take ownership' of the agent. Once the new agent was successfully installed and a wakeup call sent, the agent immediately received an inherited McAfee Agent Product Deployment Task that installed EEAgent and EEPC 22.214.171.1246. Sometimes the agent was still using an old repository list, and so the tasks would fail. After a couple more wakeup calls, though, the agent would eventually get the current repository list and I would just use the ‘Run Client Task Now’ functionality to deploy the new EEPC components.
After the new policies applied, users had to set their EEPC password again and go back through self-recovery enrollment, but that wasn't a big deal for us. I would imagine if you used the "Transfer Agent" functionality, the user's password and self-recovery information would also be transferred, but I am not sure as we did not test it.
I've completed this with about five laptops so far and have had great success. This included Windows 7 Professional, Windows 7 Enterprise, and Windows XP operating systems. Obviously, depending on how your policies are configured and what versions of EEPC/EPO you are using, your experience might vary. However, because EEPC support on EPO 5.0.1 was just recently announced and added to the Product Compatibility List on August 30th, 2013, there wasn't a great deal of information available regarding migration of EEPC agents to EPO 5.x.