Introduction This document describes how to manage the transfer of systems protected with McAfee® Drive Encryption from one McAfee® ePolicy Orchestrator® (McAfee® ePO™) server to another whilst preserving user assignments, user token, and other data. In this document, Drive Encryption 7.x.x refers to Drive Encryption 7.1.3, 7.2.0, and above. Overview The client system transfer functionality is only available in Drive Encryption version 7.x.x. With earlier versions, transferring a system from one McAfee ePO server to another will replace the user assignments and user token data on the system with data from the destination server, potentially losing user assignments and changing user credentials in the pre-boot environment. About this document This document is broken into several sections. The initial sections describe how to manage the transfer of systems between McAfee ePO servers, including pre-requisites and considerations of scalability to avoid server overload. The later sections give some helpful case studies to show how common Drive Encryption configurations can be managed.
Introduction This document describes how to manage the transfer of systems protected with McAfee® Drive Encryption from one McAfee® ePolicy Orchestrator® (McAfee® ePO™) server to another whilst preserving user assignments, user token, and other data. In this document, Drive Encryption 7.x.x refers to Drive Encryption 7.1.3, 7.2.0, and above. Overview The client system transfer functionality is only available in Drive Encryption version 7.x.x. With earlier versions, transferring a system from one McAfee ePO server to another will replace the user assignments and user token data on the system with data from the destination server, potentially losing user assignments and changing user credentials in the pre-boot environment. About this document This document is broken into several sections. The initial sections describe how to manage the transfer of systems between McAfee ePO servers, including pre-requisites and considerations of scalability to avoid server overload. The later sections give some helpful case studies to show how common Drive Encryption configurations can be managed.
