Has anyone gone through the process of migrating EEPC 6.1 clients from ePO 4.5 to ePO 4.6 and have a procedure that they are willing to share?
I have approx 150 EEPC clients, mainly VIPs and mobile laptop users and need to progress with the minimum disruption to users and exposure of unencrypted data during the process. I understand from documentation and service requests that this "is not supported" but my thoughts run along these lines:
1. Decrypt endpoint
2. Uninstall EEPC application and client to clear links to ePO 4.5.
1. Install new ePO agent.
2. Wakeup agent and update policies.
3. Reinstall EEPC agent and application.
Does this seem overkill? I have tried just a decrypt and then the ePO 4.6 agent but then EEPC fails to trigger into encryption.
Having just fallen foul of the issue where moving encrypted clients down the AD OU structure wipes all the allowed users from the preboot environment (KB72615) and annoys VIP users, I can't afford this process to be disruptive!
All thoughts most welcome.
Thanks for your swift response.
These are 2 separate, existing, production servers as I am migrating users between 2 data centres. The EEPC encrypted machines are currently on the ePO 4.5 server and I need to move them to the new ePO 4.6 server. Once complete, the ePO 4.5 server will be decommissioned.
Firstly, there is no option to migrate Endpoint Encryption users between ePO servers.. This is currently being looked into.
But you can migrate a EEPC client machine from one ePO Server to another. In order to for this to work, you will need to ensure the following:
Once you have done this, you have two options.
In both cases, it will require at least 2 ASCIs to ensure that the machine keys have been transfer to the new ePO Server and the users.
Please ensure you test this with a test machine first.
Hope this helps.Message was edited by: whgibbo on 24/11/11 08:56:30 CST