FDE access the data from another encrypted drive KES 12

[Meroine]

In this document, we are using host client01 as the host to access the data from another encrypted drive. Encrypted drive should be connected directly to the client01 using SATA cable, do not use SATA to USB devices.

Also, make sure that client01 does not have FDE encryption policy applied. It should have setting “Leave unchanged” for FDE specified; otherwise data on encrypted drive may be lost in certain cases.

If you connect encrypted drive from the host client02 to a client machine (client01 in this example) that is managed by the same administration server that was used to encrypt drive in question, then in order to gain access to the encrypted drive the following procedure should be followed:

Upon connecting an encrypted drive on the client host (client01) pop-up window will appear:

 

 

Alternatively, it can be accessed from the local KES GUI as follows:

Save challenge file (*.kesdc) somewhere.

In administration server console find the client host (client01 in our example) that is used to gain access to the encrypted drive – right click on it and select the “Grant access in offline mode”:

 

 

Important! You should select the client host that is used to gain access to the encrypted drive (client01 in our example), not the host that was used to encrypt the drive in question (client02)! Otherwise you will receive error “File corrupted. Failed to process encrypted device.” on the client host.

 Select Data encryption tab and then browse, select challenge file:

Save the response (*.kesdr) file:

On the client host (client01) use the response file to access the encrypted drive as shown below:

 

or simply double-click on it.

 

-          At this point all data on the encrypted drive should be accessible.

Important! Do not apply Encrypt all drives encryption policy to client01 host at any point in this scenario, otherwise it is possible that the data on this drive will be re-encrypted and thus corrupted.

-          If necessary to decrypt the original drive from client02 apply the decrypt all hard drives FDE policy to the client01 and wait for the drive in question to be decrypted to 100%.

-          Backup all user sensitive data from the accessed drive BEFORE applying the policy.

 

[Tahmeed702]

12 hours ago, Meroine said:

In this document, we are using host client01 as the host to access the data from another encrypted drive. Encrypted drive should be connected directly to the client01 using SATA cable, do not use SATA to USB devices.

Also, make sure that client01 does not have FDE encryption policy applied. It should have setting “Leave unchanged” for FDE specified; otherwise data on encrypted drive may be lost in certain cases.

If you connect encrypted drive from the host client02 to a client machine (client01 in this example) that is managed by the same administration server that was used to encrypt drive in question, then in order to gain access to the encrypted drive the following procedure should be followed:

Upon connecting an encrypted drive on the client host (client01) pop-up window will appear:

 

 

Alternatively, it can be accessed from the local KES GUI as follows:

Save challenge file (*.kesdc) somewhere.

In administration server console find the client host (client01 in our example) that is used to gain access to the encrypted drive – right click on it and select the “Grant access in offline mode”:

 

 

Important! You should select the client host that is used to gain access to the encrypted drive (client01 in our example), not the host that was used to encrypt the drive in question (client02)! Otherwise you will receive error “File corrupted. Failed to process encrypted device.” on the client host.

 Select Data encryption tab and then browse, select challenge file:

Save the response (*.kesdr) file:

On the client host (client01) use the response file to access the encrypted drive as shown below:

 

or simply double-click on it.

 

-          At this point all data on the encrypted drive should be accessible.

Important! Do not apply Encrypt all drives encryption policy to client01 host at any point in this scenario, otherwise it is possible that the data on this drive will be re-encrypted and thus corrupted.

-          If necessary to decrypt the original drive from client02 apply the decrypt all hard drives FDE policy to the client01 and wait for the drive in question to be decrypted to 100%.

-          Backup all user sensitive data from the accessed drive BEFORE applying the policy.

 

Edit the title as (Advices and Solutions)