Home » Lenovo Manuals » Desktops » Lenovo ThinkCentre M92z » Manual Viewer

Lenovo ThinkCentre M92z (English) Rescue and Recovery 4.3 Deployment Guide - Page 63

Best practices for hard drive setup: Option 1, Creating a bootable Rescue and Recovery CD

View all Lenovo ThinkCentre M92z manuals

Add to My Manuals
Save this manual to your list of manuals

Page 63 highlights

Some OEMs store pointers to their product recovery code in the Master Boot Record sector. OEM product recovery code may interfere with the Rescue and Recovery Boot Manager installation. Consider the following scenarios and best practices to ensure the Rescue and Recovery program provides the desired functions and features: Best practices for hard drive setup: Option 1 This scenario covers new image deployments that include the Rescue and Recovery program. If deploying the Rescue and Recovery program to existing OEM clients that contain OEM product recovery code, run the following test to determine if the OEM product recovery code interferes with the Rescue and Recovery program: 1. Set up a test client with the image that contains the OEM product recovery code. 2. Install the Rescue and Recovery program. If eight free sectors in the Master Boot Record (MBR) do not exist as a result of the OEM product recovery code, you will see the following error message: Error 1722. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your personnel or package vendor. If you are using an OEM image for the base operating system, ensure that the Master Boot Record does not contain the product recovery data. You can do this in the following way: Attention: Running the following command will erase the entire contents of the target hard disk drive. After running, you will be unable to recover any data from the target hard disk drive. 1. Use the cleandrv.exe available from the Lenovo ThinkVantage Technologies Administrator Tools Web page at: http://www.lenovo.com/support/site.wss/document.do?lndocid=TVANADMIN#rnr to ensure all sectors are cleared from the Master Boot Record on the hard disk drive that you plan to use to create your base image. 2. Package the image according to your procedures for deployment. Best practices for hard drive setup: Option 2 Deploying the Rescue and Recovery program on existing clients requires some effort and planning. This scenario provides another option for a hard drive setup. Note: If you receive Error 1722 and need to create eight free sectors, call the Lenovo help desk to report the error and obtain further instructions. Creating a bootable Rescue and Recovery CD The Rescue and Recovery program builds and burns the rescue media CD from the current service area contents, rather than from a pre-assembled ISO image. However, if an appropriate ISO (.iso) image is already present, because it was preloaded or because it had been built before, that image will be used to burn the CD, rather than to create a new one. Because of the resources involved, only one instance of the CD burning application may be running at any given time. If it is running, attempting to start a second instance will produce an error message and the second instance will abort. In Chapter 4. Best practices 55

Section	Page
Contents	5
Preface	7
Chapter 1. Overview	9
Predesktop Area	9
Windows environment	10
Rejuvenating	10
Hints and Tips	11
Chapter 2. Installation	13
Installation considerations	13
Installing the Rescue and Recovery program	14
Installation requirements	14
Requirements for Lenovo computers	14
Requirements for non-Lenovo computers	14
Installation components	15
Administrative installation procedure	15
Using msiexec.exe	16
Installation log files	16
Rescue and Recovery installation	17
Rescue and Recovery custom public properties	19
Including the Rescue and Recovery program in a disk image	19
Using PowerQuest Drive Image based tools with Rescue and Recovery	20
Using WIM files, ImageX, and Windows 7	21
Using Symantec Ghost-based tools with Rescue and Recovery	21
Rescue and Recovery environmental variables	21
Compatibility with BitLocker	21
Compatibility with BitLocker without TPM	21
Best practice of BitLocker encryption on a system with the Rescue and Recovery program	22
Chapter 3. Configurations	23
XML and ADM file configurations	23
Recovery methods	23
Single file restore	24
File rescue	24
Operating system and applications	24
Restore system drive only	24
Rejuvenation	24
Full restore	25
Custom recovery	25
Customizing the recovery process	25
Preinstallation setup	26
Backups	28
Scheduling backups and associated tasks	28
Sysprep Backup/Restore	29
Sysprep backup changes in Windows 7	29
Restore a Sysprep Backup	29
Mapping a network drive for backups	30
Setting up user accounts for network backups	30
Capturing a Sysprep utility image in the base backup	30
Capturing a multiple partition machine and excluding files in a Sysprep backup	31
Supported Sysprep multiple drive configurations	33
Password Persistence	33
EFS file limitation	33
Battery power settings for backups	33
Completing a backup	34
Microsoft Message Queuing (MSMQ)	34
Rescue and Recovery in the Windows environment	34
Using the Rescue and Recovery program in the Windows environment	34
Include and exclude backup files with registry settings	34
Trouble ticket	36
Rescue and Recovery interface switching	36
Working with the Predesktop Area	37
Working with WIM files and ImageX	38
Using RRUTIL.EXE	38
Predesktop Area directory list	38
Get files from Predesktop Area directories	39
Put files in the Predesktop Area directories	39
Delete files from the Predesktop Area directories	40
Rename a file in the Predesktop Area	40
Test for Rescue and Recovery being installed	40
Backup directory list	40
Get files from \\RRBackups directories	41
Put files in the \\RRBackups directories	41
Determine \\RRBackups space consumed	41
Example: pdaguixx.ini	42
Example 1: Adding device drivers (such as ethernet) to the Predesktop Area	43
Example 2 : Adding mass-storage controller drivers (such as SATA) to the Predesktop Area	44
Customizing the preboot environment	44
Changing the main GUI fonts	44
Changing the environment background	45
Editing pdagui.ini	45
Changing entries and functions in the right panel	47
Removing Factory Restore	49
Configuring the Opera browser	49
Opera will not save settings after it is closed	49
E-mail	50
Disabling the address bar	50
Customizing bookmarks	50
Changing proxy settings	51
Enabling or specifying the full download path	52
Adding a specific file extension to the downloadable files list	52
Changing the behavior of files with specific extensions	53
Adding a static IP address	54
Changing the video resolution	55
Startup applications	55
Passwords	56
Predesktop Area or master password	56
Backup password	56
No password	56
Password access	56
Master password	57
User ID and password or passphrase	57
No password	57
Log files	57
Create Rescue Media	57
Chapter 4. Best practices	59
Scenario 1 - New rollouts	59
Preparing the hard disk drive	59
Installing	59
Updating	61
Enabling the Rescue and Recovery desktop	61
Scenario 2 - Installing on OEM systems	62
Best practices for hard drive setup: Option 1	63
Best practices for hard drive setup: Option 2	63
Creating a bootable Rescue and Recovery CD	63
Creating the recovery ISO file and burning to a CD sample script file	64
Scenario 3 - Installing with WIM files and Windows 7	64
Scenario 4 - Standalone install for CD or script files	65
Scenario 5 - Working with Active Directory and ADM files	65
Corporate Active Directory Rollout	66
Scenario 6 - Performing a Bare Metal Restore from an Admin Backup	66
Scenario 7 - Manually creating the Service Partition of S drive	66
Appendix A. Administrative tools	69
Command line support	69
Mailman	69
AWizard.exe	69
SETPASSWORD	69
RELOADSCHED	69
RRCMD command-line interface	69
How to replace a file in a base backup	71
How to restore a backup from specific system	71
CLEANDRV.EXE	72
CONVDATE	72
CREATSP	72
InvAgent	73
MapDrv	74
Using MapDrv	75
Rescue and Recovery Boot manager control (BMGR32)	75
BMGR CLEAN	78
Active Directory Support	79
Administrative (ADM) template files	79
Defining manageable settings	80
Group Policy settings	80
Rescue and Recovery	81
Settings	81
User interface	81
Backup	84
Restore	88
Rejuvenate	89
User Messages	89
Mapping network drive	90
Scheduler tasks	90
Appendix B. User tasks	91
Windows 7	91
Create rescue media	91
Rescue and Recovery user interface switching	92
Appendix C. Notices	93

Match case Limit results 1 per page

Some OEMs store pointers to their product recovery code in the Master Boot

Record sector. OEM product recovery code may interfere with the Rescue and

Recovery Boot Manager installation.

Consider the following scenarios and best practices to ensure the Rescue and

Recovery program provides the desired functions and features:

Best practices for hard drive setup: Option 1

This scenario covers new image deployments that include the Rescue and

Recovery program. If deploying the Rescue and Recovery program to existing

OEM clients that contain OEM product recovery code, run the following test to

determine if the OEM product recovery code interferes with the Rescue and

Recovery program:

Set up a test client with the image that contains the OEM product recovery

code.

Install the Rescue and Recovery program. If eight free sectors in the Master

Boot Record (MBR) do not exist as a result of the OEM product recovery code,

you will see the following error message:

Error 1722. There is a problem with this Windows

Installer package. A program run as part of the

setup did not finish as expected. Contact your

personnel or package vendor.

If you are using an OEM image for the base operating system, ensure that the

Master Boot Record does not contain the product recovery data. You can do this in

the following way:

Attention:

Running the following command will erase the entire contents of the

target hard disk drive. After running, you will be unable to recover any data from

the target hard disk drive.

Use the cleandrv.exe available from the Lenovo ThinkVantage Technologies

Administrator Tools Web page at:

http://www.lenovo.com/support/site.wss/document.do?lndocid=TVAN-

ADMIN#rnr to ensure all sectors are cleared from the Master Boot Record on

the hard disk drive that you plan to use to create your base image.

Package the image according to your procedures for deployment.

Best practices for hard drive setup: Option 2

Deploying the Rescue and Recovery program on existing clients requires some

effort and planning. This scenario provides another option for a hard drive setup.

Note:

If you receive Error 1722 and need to create eight free sectors, call the

Lenovo help desk to report the error and obtain further instructions.

Creating a bootable Rescue and Recovery CD

The Rescue and Recovery program builds and burns the rescue media CD from the

current service area contents, rather than from a pre-assembled ISO image.

However, if an appropriate ISO (.iso) image is already present, because it was

preloaded or because it had been built before, that image will be used to burn the

CD, rather than to create a new one.

Because of the resources involved, only one instance of the CD burning application

may be running at any given time. If it is running, attempting to start a second

instance will produce an error message and the second instance will abort. In

Chapter 4. Best practices