Encrypted Disk Data Recovery

8/7/2019 Encrypted Disk Data Recovery

1/3

Encrypted Disk Data Recovery & OS Crash Recovery, PCNon - Self Encrypting Drive

Recovering from an operating system crash on a SecureDoc encrypted computer requires two computers:

y Device #1 = the computer that has crashed

y Device #2 = another computer that has SecureDoc installed in an unencrypted state

Encrypted drive data cannot be read by any computer that does not use the crashed drive's corresponding

encryption key file to decrypt the data. To recover data or perform a system restore/ recovery operation the

drive must be decrypted and boot log on uninstalled.

Prepare to decrypt the crashed computer

1. Remove and slave the crashed computer's hard drive to another SecureDoc installed computer that is

in an unencrypted state. Slaved drives may be connected with USB/Firewire adapters or internal

cabling.

Note: SecureDoc installers that do not automatically encrypt are available from the ITS EWDE

administrators, for access to these installers please submit a request via the ITS Help Desk

2. Log into the SecureDoc console, locate Device #2 as described above and select a user that has

administrative rights to that device (right-click the user and selectAccess Rights).

Note: It is recommended to use Autoboot for this process if it is a listed account.

3. If the selected user does not have full administrative access rights, assign them by selecting the Admin

Rights radio button and clickOK.

4. The encryption key of the crashed computer must be added to the chosen administrative account,

right-click that account and chooseModify User.

5. Navigate to "Selected Keys" and clickAdd.

6. Browse the folder list and locate the crashed device's named key, select the key and clickOK.


2/3

7. The key should now show up as listed for the user in Selected Keys as shown below. ClickSave in the

"Edit User Info" window.

8. Log into Device #2, locate the SecureDoc Control Center icon in the system tray, right-click and

select Communicate With Server. Server side changes will propagate to Device #2.

9. Restart Device #2

Decrypt the crashed computer's hard drive

1. Remove the hard drive from Device #1 and slave/attach it via USB/Firewire or internal cabling to

Device #2.

2. The SecureDoc Pre-Boot environment must be logged in with the account that has been assigned to

the crashed computer's encryption key file from Step 1. It is recommended that you use the Autoboot

account for this purpose since it is the default Pre-Boot environment log on account. If another account

is desired for this purpose, it may be added to Device #2 as the Autoboot default.

Note: Changes made to the Pre-Boot login require server communications within the operating system

and a reboot of the device to apply the changes.

3. Boot up Device #2, log in to the operating system and run the "SecureDoc Control Center" to verify that

the logged in account with administrative access is listed.

4. Data on Device #1's drive should now be accessible to Device #2 since the necessary encryption key

is in use. After data has been recovered the drive may be wiped and a fresh Operating System

installed.

Note: If system recovery is desired (e.g. Operating System environment) continue with the following

steps.

5. Boot up Device #2, log in to the Operating System, and run the SecureDoc Control Center as

Administrator by right-clicking on the following file and selectingRun as:

y C:\Program Files\WinMagic\SecureDoc-NT\SecurDoc.exe


3/3

6. Enter the password for the listed User ID or key file, Autoboot account by default, and clickLogin.

7. Once logged in Several tabs should appear in the "Control Center" window, selectDisk Encryption.

Note: If no tabs appear, double check the process in Step 1 and re-try

8. On the Disk Encryption tab, choose the hard drive to decrypt, usually labeled "HD2 e

Device#1Hostnamekey," and select Decrypt.

9. Select the correct encryption key, which should be identical to Device #1's name, and click

the Start button.

10. Decryption should begin immediately and may take several hours to complete.

Remove Boot Control

Assuming decryption has completed successfully, you must remove "SecureDoc Boot Logon" before further

operating system recovery can be attempted.

1. Select the Boot Control tab and click onInstall/Uninstall Boot Logon.

2. A window will pop-up. Select Uninstall Boot Logon.

3. Look for a radio button associated with the hard drive number that was decrypted in Step 2, most likely

"Hard Disk 2," and select it. Be sure the match is correct or Boot Logon will be uninstalled on the wrong

hard drive.

Note: If there is no match or if the radio button is grayed out, either Boot Logon was not installed and

does not need to be removed OR Boot Logon was installed and is corrupted.

4. Click OK to proceed.

5. Once Boot Logon is uninstalled, the Device #1 hard drive may be re-installed and OS recovery

procedures started.

Documents

Encrypted Disk Data Recovery