Scalability

There is a direct correlation between the performance of the client transfer solution and the number of Drive Encryption users assigned to each system.

The number of user assignments that needs to be made by the destination server in a single ASCI is:

numAssignments = numSystemsTransferred x numUsersNeedingAssignment

Equally, the number of user data transfers that need to be made in a single ASCI is:

numDataTransfers = numSystemsTransferred x numUsersPerSystem

Each system will also transfer its encryption and recovery keys during this ASCI, so systems should be transferred in batches.

The McAfee ePO infrastructure provides a limited bandwidth that could become overwhelmed if too many systems are transferred at once, or the number of users requiring to be assigned to each system in the destination server is excessive.

When enabling the system transfer feature, it's possible to prevent the system transfer from occurring when the number of users that will be assigned to the system during the transfer exceeds a specified limit (configurable maximum number).

In the example given above, if the number of users in List A exceeds the limit (configurable maximum number), then system transfer will be abandoned and a suitable error event sent up to the destination server. Note that the limit applies only to those users that are not currently assigned to the system (either explicitly or through inheritance from a branch) in the destination server when the transfer starts.

Branch assignments of Drive Encryption users within the source server need to be configured manually within the destination server before systems are transferred. If this step is omitted, the system may fail to transfer if it reaches the maximum user assignment limit.