Lenovo R50p User Manual
Rescu e an d Recov ery 4.2
Deployment
Guide
Updated: September 27, 2007
A ThinkVantage Technology publication
Rescu e an d Recov ery 4.2
Deployment
Guide
Updated: September 27, 2007
First Edition (October 2007)
© Copyright Lenovo 2007.
Portions © Copyright International Business Machines Corporation 2005.
All rights reserved.
LENOVO products, data, computer software, and services have been developed exclusively at private expense and
are sold to governmental entities as commercial items as defined by 48 C.F.R. 2.101 with limited and restricted
rights to use, reproduction and disclosure.
LIMITED AND RESTRICTED RIGHTS NOTICE: If products, data, computer software, or services are delivered
pursuant a General Services Administration ″GSA″ contract, use, reproduction, or disclosure is subject to restrictions
set forth in Contract No. GS-35F-05925.
Contents
Preface . . . . . . . . . . . . . . .v
Chapter 1. Overview . . . . . . . . .1
Predesktop Area . . . . . . . . . . . . .1
Windows environment . . . . . . . . . . .2
Rejuvenating and migrating . . . . . . . . .2
Hints and Tips . . . . . . . . . . . . . .3
Antidote Delivery Manager . . . . . . . . .3
Chapter 2. Installation . . . . . . . . .5
Installation considerations . . . . . . . . . .5
Overinstall considerations . . . . . . . . .5
Installing Rescue and Recovery . . . . . . . .6
Installation requirements . . . . . . . . .6
Installation components . . . . . . . . . .8
Installation log files . . . . . . . . . . .9
Installing Rescue and Recovery 4.2 with existing
versions . . . . . . . . . . . . . . .9
Rescue and Recovery installation . . . . . .10
Compatibility with Vista Bitlocker . . . . . .14
Chapter 3. Configurations . . . . . .17
XML and ADM file configurations . . . . . . .17
Recovery methods . . . . . . . . . . . .17
Single file restore . . . . . . . . . . .17
File rescue . . . . . . . . . . . . . .17
Operating system and applications . . . . .18
Rejuvenation . . . . . . . . . . . . .18
Full restore . . . . . . . . . . . . .19
Custom recovery . . . . . . . . . . .19
Express Repair . . . . . . . . . . . .22
Factory content/Image Ultra Builder . . . . .23
Backups . . . . . . . . . . . . . . .23
Scheduling backups and associated tasks . . .23
Mapping a network drive for backups . . . .23
Sysprep Backup/Restore . . . . . . . . .27
Password persistence . . . . . . . . . .27
Battery power settings for backups . . . . .27
Completing a backup . . . . . . . . . .28
Microsoft Message Queuing (MSMQ) . . . . .28
Rescue and Recovery in the Windows environment 28
Using Rescue and Recovery in the Windows
environment . . . . . . . . . . . . .28
Working with the Predesktop Area . . . . . .31
Vista considerations . . . . . . . . . .32
Using RRUTIL.EXE . . . . . . . . . . .32
Customizing the preboot environment . . . .38
Configuring the Opera browser . . . . . . .43
Changing the video resolution . . . . . . .49
Startup applications . . . . . . . . . .49
Passwords . . . . . . . . . . . . . .50
Password access . . . . . . . . . . . .51
Log files . . . . . . . . . . . . . . .51
Chapter 4. Rejuvenation and migration 53
Creating a command file . . . . . . . . . .53
File commands . . . . . . . . . . . . .54
File-migration commands . . . . . . . . . .57
Examples of file-migration commands . . . . .61
Selecting files during the capture phase . . . .61
Migrating additional application settings . . . .62
Creating an application file . . . . . . . .67
Example of an application.xml file for Adobe
Reader . . . . . . . . . . . . . . .69
Chapter 5. Best Practices . . . . . . .75
Scenario 1 - New rollouts . . . . . . . . . .75
Preparing the hard disk drive . . . . . . .75
Installing . . . . . . . . . . . . . .75
Updating . . . . . . . . . . . . . .77
Enabling the Rescue and Recovery desktop . . .77
Scenario 2 - Installing on OEM systems . . . . .78
Best practices for hard drive setup: Option 1 . .79
Best practices for hard drive setup: Option 2 . .79
Scenario 3 - Installing on a laptop . . . . . . .80
Scenario 4 - Installing on a desktop . . . . . .82
Scenario 5 - Installing on Type 12 service partition 84
Scenario 6 - Installing with WIM files and Windows
Vista . . . . . . . . . . . . . . . . .85
Scenario 7 - Standalone install for CD or script files 85
Scenario 8 - Working with Active Directory and
ADM files . . . . . . . . . . . . . . .85
Corporate Active Directory Rollout . . . . .86
Appendix A. Administrative tools . . .87
Command line support . . . . . . . . . .87
Mailman . . . . . . . . . . . . . .87
AWizard.exe . . . . . . . . . . . . .87
SETPASSWORD . . . . . . . . . . . .87
RELOADSCHED . . . . . . . . . . .87
RRCMD command-line interface . . . . . .87
CLEANDRV.EXE . . . . . . . . . . .89
CONVDATE . . . . . . . . . . . . .89
CREATSP . . . . . . . . . . . . . .90
eGatherer . . . . . . . . . . . . . .91
MapDrv . . . . . . . . . . . . . .92
Rescue and Recovery Boot manager control
(BMGR32) . . . . . . . . . . . . . .93
BMGR CLEAN . . . . . . . . . . . . .96
SP.PQI . . . . . . . . . . . . . . . .97
Active Update . . . . . . . . . . . . .97
Active Update Parameter File . . . . . . .98
Active Directory Support . . . . . . . . . .98
Administrative (ADM) template files . . . . .98
Group Policy settings . . . . . . . . . .99
Appendix B. Antidote Delivery
Manager . . . . . . . . . . . . . 121
Installing the Antidote network component . . . 121
© Lenovo 2007. Portions © IBM Corp. 2005. iii
Windows Vista . . . . . . . . . . . . 121
Windows XP . . . . . . . . . . . . 121
Antidote with Windows Vista . . . . . . . . 122
Repository . . . . . . . . . . . . . . 122
Antidote Delivery Manager and Windows
commands . . . . . . . . . . . . . . 123
Antidote Delivery Manager utilization . . . . . 123
Major worm attack . . . . . . . . . . 123
Minor application update . . . . . . . . 125
Accommodating VPNs and wireless security . . . 125
Antidote Delivery Manager command guide . . . 126
Supported Microsoft commands . . . . . . . 129
Preparation and installation . . . . . . . . 130
Preparation . . . . . . . . . . . . . 130
Configuration . . . . . . . . . . . . 130
Repository . . . . . . . . . . . . . 130
Schedule information . . . . . . . . . . 131
Signing Key . . . . . . . . . . . . . 131
Network Drives . . . . . . . . . . . 131
Installing the Antidote network component . . 132
Server infrastructure . . . . . . . . . . 132
Simple system test – display notification . . . . 132
Deployment . . . . . . . . . . . . . . 132
Examples . . . . . . . . . . . . . . 135
Example scripts . . . . . . . . . . . . 137
Virtualization Module for Antidote Delivery
Manager . . . . . . . . . . . . . . . 137
Requirements . . . . . . . . . . . . 137
Installation . . . . . . . . . . . . . 138
Overview . . . . . . . . . . . . . . 138
Appendix C. User tasks . . . . . . . 141
Windows Vista . . . . . . . . . . . . . 141
Windows XP . . . . . . . . . . . . . 142
Windows 2000 . . . . . . . . . . . . . 142
Create rescue media . . . . . . . . . . . 143
Rescue and Recovery user interface switching . . 143
Appendix D. Notices . . . . . . . . 145
Trademarks . . . . . . . . . . . . . . 146
iv Rescue and Recovery 4.2 Deployment Guide
Preface
This guide is intended for IT administrators, or those responsible for deploying the
Rescue and Recovery™ program to computers throughout their organizations. The
goal of Rescue and Recovery is to reduce costs by avoiding helpdesk calls,
desk-side visits, and improve user productivity. Rescue and Recovery is an
essential tool that enables users and administrators to restore backups, access files,
diagnose problems, and make Ethernet connections if the Microsoft® Windows
®
operating system will not open or run correctly. It also enables deployment of
critical updates to systems that are corrupted or off the network, as well as
automatically apply patches to a system when a restore is performed. This guide
provides the information required for installing the Rescue and Recovery
application on one or more computers, provided that licenses for the software are
available for each target computer. It also provides information on the many
aspects of the tool that can be customized to support IT or corporate policies.
This deployment guide is developed for IT professionals and the unique challenges
that they encounter. If you have suggestions or comments, communicate with your
Lenovo authorized representative. Periodically, these guides are updated, so check
the Lenovo We b site for future publications.
Information presented in this guide supports ThinkVantage™ programs and does
not support Lenovo™ 3000 technology. For information regarding Lenovo 3000
technology, refer to the Lenovo Web site located at:
www.lenovo.com
Rescue and Recovery provides function and application help. For questions and
information about using the various components included in the Rescue and
Recovery workspace, refer to the online help system for the components located at:
http://www.lenovo.com/thinkvantage
© Lenovo 2007. Portions © IBM Corp. 2005. v
vi Rescue and Recovery 4.2 Deployment Guide
Chapter 1. Overview
Rescue and Recovery represents a unique combination of ThinkVantage
Technologies. This integrated application provides a suite of powerful tools that
can be used even if the Microsoft Windows operating system will not start.
Rescue and Recovery has the following features:
v The Rescue and Recovery Predesktop Area that starts even if the Windows
operating system will not boot.
v The Rescue and Recovery Windows environment that allows for backing up
files, file rescue, and recovery of the operating system and files.
v Antidote Delivery Manager
Rescue
with a few basic operations, or stay with the advanced user interface with
extended options. For more information on interface switching, see “Rescue and
Recovery interface switching” on page 30.
Note: Some features of Rescue and Recovery run under the Windows operating
system. In some instances, system information used in the Rescue and Recovery
environment are gathered while Windows is running. If the Windows operating
system malfunctions, that malfunction alone will not prevent the Rescue and
Recovery environment from operating normally. Windows functions are not
configured in the Rescue and Recovery environment.
Predesktop Area
The Rescue and Recovery Predesktop Area provides an emergency workspace for
users who are unable to start Windows on their computers. Running under
Windows PE (Preinstallation Environment), the environment offers the Windows
look, feel, and function and helps users solve problems without consuming IT staff
time.
The Rescue and Recovery Predesktop Area has four major categories of functions:
v Rescue and Restore
v
v
and Recovery includes the option to switch to a simplified user interface
– Recovery overview: Links users to help topics about the various recovery
options that are provided.
– Rescue files: Enables users to copy files created in Windows applications to
removable media or to a network and to continue to work even with a
disabled workstation.
– Restore from backup: Enables users to restore files that have been backed up
with Rescue and Recovery.
Configure
– Configuration overview: Links to Rescue and Recovery environment help
topics about configuration.
– Recover password or passphrase: Provides a user or an administrator with
the ability to recover a password or passphrase in the Rescue and Recovery
environment.
– Access BIOS: Opens the BIOS Setup Utility program.
Communicate
– Communication overview: Links to related help topics in the Rescue and
Recovery environment.
© Lenovo 2007. Portions © IBM Corp. 2005. 1
– Open browser: Starts the Opera Web browser (Web or Intranet access requires
a wired Ethernet connection).
– Download files:Allows you to download needed files to the partition in the
\SWSHARE folder in the Windows partition.
– Map network drive: Helps users access network drives for software
downloads or file transfer.
Troubleshoot
v
– Diagnostic overview: Links to Rescue and Recovery diagnostics help topics.
– Diagnose hardware: Opens the PC Doctor application that can perform
hardware tests and report results.
– Create diagnostic disks:Enables you to create a set of diagnostic diskettes.
– Boot from another device: Enables you to boot from the Rescue and Recovery
CD, a set of back up CD’s, an internal drive or a detachable storage device
such as a USB hard disk drive.
– System information: Provides details about the computer and its hardware
components.
– Event log: Provides details of recent user activities and listings of computer
hardware to aid in problem determination and resolution. The log viewer
provides a readable way to view activity and asset log entries.
– Warranty status
Rescue
and Recovery is available on Lenovo-branded personal computers that
come with preinstalled software. It is also available for purchase as a CD file so
that organizations can benefit from Rescue and Recovery on non-Lenovo branded
computers. Yo u can then purchase separate licenses for individual computers
Note: The last Windows administrator ID is the only ID that can automatically
carry over from Windows to the Predesktop Area. Windows limited and power
users will need to retype their user ID and passwords to logon to the Predesktop
Area.
Windows environment
The Rescue and Recovery Windows environment enables users to rescue lost data,
applications, and operating systems with the touch of a button. This capability
reduces time-consuming help desk calls, which result in support cost savings.
You can schedule backups of all users’ computers, thereby limiting risk and
downtime. Rescue and Recovery offers your clients an extra layer of support by
pre-configuring automatic external backup to a server or external storage. Backups
are encrypted by default with the 256 AES key.
Rejuvenating and migrating
With Rescue and Recovery, you can migrate a user’s work environment from one
system to another upon rejuvenating from a backup. A user’s work environment
includes the following items:
v Operating-system preferences, such as desktop and network connectivity
settings.
v Files and folders
v Customized application settings, such as bookmarks in a We b browser or editing
preferences in Microsoft® Word.
v User accounts
more information, see Chapter 4, “Rejuvenation and migration,” on page 53.
For
2 Rescue and Recovery 4.2 Deployment Guide
Hints and Tips
For hints and tips on using Rescue and Recovery 4.2, please see the Rescue and
Recovery v4.2 Considerations document located at:
www.lenovo.com/support
Antidote Delivery Manager
Antidote Delivery Manager is an antivirus, anti-worm infrastructure included in
Rescue and Recovery. The objects are easy to implement, and allow an
administrator to initiate network blocking and recovery within minutes of a
reported problem. Antidote Delivery Manager can be launched by one
administrator and it functions on systems that are both network and non-network
attached. Antidote Delivery Manager compliments existing antivirus tools rather
than replacing them, so maintaining virus scanning tools and obtaining patches are
still required. Antidote Delivery Manager provides the infrastructure to halt
destruction and apply the patches.
Chapter 1. Overview 3
4 Rescue and Recovery 4.2 Deployment Guide
Chapter 2. Installation
Prior to installing Rescue and Recovery, you can customize the Rescue and
Recovery XML file for your enterprise and then deploy it to client systems. The
XML file packaged with Rescue and Recovery is named rnrdeploy.xml. Once the
XML file is customized and installed, settings for Rescue and Recovery are
managed with the registry or Active Directory. For more information, see the
accompanying XML/ADM Supplement for the deployment guide located on the
ThinkVantage Technologies Administrator Tools page:
http://www.lenovo.com/support/site.wss/document.do?lndocid=TVAN-ADMIN#tvsu
Installation considerations
Rescue and Recovery has two main interfaces. The primary interface operates in
the Windows XP, Windows 2000 or Windows Vista™ environment. The secondary
interface (the Rescue and Recovery Predesktop Area) operates independently of
either Windows XP or Windows 2000 operating system, in the Windows PE
environment.
Notes:
1. Rescue and Recovery only works with the non-BIOS version of Computrace if
Rescue and Recovery is installed first, and then Computrace is installed.
2. If you attempt to install Storage Management Subsystem on a computer with
Rescue and Recovery installed with the Windows PE area already installed as a
virtual partition, then Storage Management Subsystem will not install. Both
Windows PE and Storage Management Subsystem use the C:\minint directory
for its file system. The way to have both installed at the same time is to install
Rescue and Recovery 4.2 as a type 12 partition. See “Scenario 6 - Installing with
WIM files and Windows Vista” on page 85 for instructions.
3. A possible security risk may be created when the Microsoft Recovery Console is
installed on a system with Rescue and Recovery. Microsoft Recovery Console
looks for all folders with the path C:\*\system32\config\ and if it finds that
path it assumes it is an operating system. If the registry entries that require a
Windows password are not present, then recovery console will allow a user to
choose the operating system and then gain access to the entire hard drive
without needing to enter a password.
4. If you are using Microsoft Vista make sure you have an adequate amount of
free space on your local drive. This space is needed for Rescue and Recovery to
create a shadow copy of the partition so it can back up locked files.
Overinstall considerations
A new backup must be taken after installation of Rescue and Recovery 4.2 because
old backups from previous versions will be deleted during installation. This
backup can be done by using either a script or the user interface.
Notes:
1. If installing Rescue and Recovery 4.2 over versions, 1.0, 2.0, or 3.0 you will
have to take a backup first. If you are installing Rescue and Recovery 4.2 over
version 3.1 you don’t need to take a backup, but it is recommended.
2. Backup files captured by previous versions of Rescue and Recovery 1.0, 2.0,
and 3.0 cannot be recovered by Rescue and Recovery 4.2.
© Lenovo 2007. Portions © IBM Corp. 2005. 5
Installing Rescue and Recovery
The Rescue and Recovery installation package was developed with InstallShield
10.5 Premier as a Basic MSI project. InstallShield Premier 10.5 uses the Windows
Installer to install applications, which gives administrators many capabilities to
customize installations, such as setting property values from the command line.
This chapter describes ways to use and execute the Rescue and Recovery setup
package. For a better understanding, read the entire chapter before you begin to
install this package.
When installing this package, please refer to the Readme file that is posted
Note:
on the Lenovo web page at:
http://lenovo.com/pc/support/site.wss/document.do?lndocid=MIGR-4Q2QAK
The Readme file contains up-to-the-minute information on software versions,
supported systems, system requirements, and other considerations to help you
with the installation process.
Installation requirements
This section addresses system requirements for installing the Rescue and Recovery
package on Think branded systems. A number of legacy computers from IBM® can
support Rescue and Recovery provided that they meet the requirements specified.
For best results, make sure that you have the latest version of the software
installed. To obtain the latest version of Rescue and Recoveryand information
about IBM-branded computers that support Rescue and Recovery, see the
following Lenovo We b site:
http://www.lenovo.com/thinkvantage
Requirements for IBM and Lenovo computers
IBM-branded and Lenovo-branded computers must meet or exceed the following
requirements to install Rescue and Recovery:
v Operating system: Windows Vista, Microsoft Windows XP with Service Pack 1
or Windows 2000 with Service Pack 3 or greater.
v Memory: 128 MB for Windows 2000 and Windows XP, 512 MB for Windows
Vista
– In shared memory configurations, the BIOS setting for maximum shared
memory must be set to no less than 8 MB.
– In non-shared memory configurations, 120 MB of non-shared memory.
Note: If a computer has less than 200 MB of non-shared memory, Rescue and
Recovery will run; however, the user will be unable to start more than one
application in the Rescue and Recovery environment.
v Internet Explorer 5.5 or greater must be installed.
v 2.4 GB of free space on your hard drive.
v VGA-compatible video that supports a resolution of 800 x 600 and 24-bit color.
v Supported Ethernet card.
v User must have administrative privileges.
Requirements for installing non-IBM or non-Lenovo computers
Installation on non-IBM or non-Lenovo computers have the following
requirements:
Installation requirements: 2.4 GB of free hard disk space. The base install uses
930 MB.
6 Rescue and Recovery 4.2 Deployment Guide
Minimum system memory requirements: 256 MB system RAM to install Rescue
and Recovery.
Hard disk drive configuration: The Rescue and Recovery program is not
supported on the factory pre-loads for original equipment manufacturer (OEM)
computers (non-IBM or non-Lenovo).
Note: For the Rescue and Recovery program, the OEM computers hard disk drive
must be configured according to recommendations in “Scenario 3 - Installing on a
laptop” on page 80.
Support for booting from external media (CD/DVD and USB): Non-IBM or
non-Lenovo computer and devices (USB hard disk drive, CD-R/RW,
DVD-R/RW/RAM, or DVD+R/RW) must fully support one or more of the
following specifications:
v ATAPI Removable Media Device BIOS Specification
v BIOS Enhanced Disk Drive Services - 2
v Compaq Phoenix Intel® BIOS Boot Specification
v El Torito Bootable CD-ROM Format Specification
v USB Mass Storage Class Specification Overview (Each device must comply with
the command block specification in the section 2.0 Subclass code in the ″USB
Mass Storage Class Specification Overview.″)
v USB Mass Storage specification for boot-ability
requirements:
Video
v Video compatibility: VGA-compatible video that supports a resolution of 800 x
600 and 24-bit color
v Video memory:
– On non-shared video memory systems: a minimum 4 MB of video RAM
– On shared video memory systems: a minimum of 4MB and maximum of 8
MB can be allocated for video memory.
Application
compatibility: Some applications that have complex filter driver
environments (such as antivirus software) might not be compatible with the Rescue
and Recovery software. For information regarding compatibility issues, refer to the
Readme file and various utilities that accompany the Rescue and Recovery
software. For additional information see the Lenovo We b site at:
http://www.lenovo.com/thinkvantage
Network adapters for Rescue and Recovery: The Rescue and Recovery
environment supports only wired PCI-based, Ethernet network adapters. Network
device drivers included in the Rescue and Recovery environment are the same
drivers that are pre-populated in Microsoft Windows XP Professional operating
system and are independent of the Windows operating system. For supported
IBM-branded and Lenovo computers, required drivers are included with Rescue
and Recovery software.
If an OEM network device in your computer is not supported, refer to the device
manufacturer documentation for instructions to add support for system-specific
network drivers. Request drivers from your OEM.
Chapter 2. Installation 7
Installation components
This section contains installation components of Rescue and Recovery.
Administrative installation procedure
The Windows Installer can perform an administrative installation of an application
or product to a network for use by a workgroup or for customization. For the
Rescue and Recovery installation package, an administrative installation unpacks
the installation source files to a specified location.
You can obtain the setup package from:
www.lenovo.com/support
To run an administrative installation execute the setup package from the command
line using the /a parameter:
setup.exe /a
An administrative installation presents a wizard that prompts the administrative
user to specify the locations for unpacking the setup files. The default extract
location is C:\. You can choose a new location which may include drives other
than C:\. For example, other local drives or mapped network drives. Yo u can also
create new directories during this step.
To run an administrative installation silently, you can set the public property
TARGETDIR on the command line to specify the extract location:
setup.exe /s /v"/qn TARGETDIR=F:\TVTRR"
Note: If your version of Windows Installer is not current, setup.exe is configured
to update the Windows Installer engine to version 3.0. This update will cause the
installation action to prompt for a reboot even with an administrative extract
installation. Use the reboot properly to prevent a reboot in this situation. If the
Windows Installer is at least version 3.0, setup.exe will not attempt to install.
or
msiexec.exe /i "Lenovo Rescue and Recovery.msi" /qn TARGERDIR=F:\TVTRR
Once and administrative installation has been completed, the administrative user
can make customizations to the source files, such as adding settings to the registry.
To install from the unpacked source after customizations are made, the user calls
msiexec.exe from the command line, passing the name of the unpacked MSI file.
Using msiexec.exe: To install from the unpacked source after making
customizations, the user calls msiexec.exe from the command line, passing the
name of the unpacked *.MSI file. msiexec.exe is the executable program of the
Installer used to interpret installation packages and install products on target
systems.
msiexec /i "C:\WindowsFolder\Profiles\UserName\
Personal\MySetups\project name\product configuration\release name\
DiskImages\Disk1\product name.msi"
Note: Enter the preceding command as a single line with no spaces following the
slashes.
For information on command line parameters and public properties, go to the
Microsoft We b site at:
www.microsoft.com
8 Rescue and Recovery 4.2 Deployment Guide
Installation log files
The log file rrinstall40.txt is created in the %temp% directory if the setup is
launched by setup.exe (double click the main install.exe, run the main executable
without parameters, or extract msi and execute setup.exe). This file contains log
messages that can be used to debug installation problems. This log file is not
created when running the setup directly from the MSI package; this includes any
actions performed from Add/Remove Programs. To create a log file for all MSI
actions, you can enable the logging policy in the registry. To do this, create the
value:
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Installer]
"Logging"="voicewarmup"
Installation examples
The following table shows installation examples using setup.exe:
Table 1.
Description Example
Silent installation with no reboot. setup.exe /s /v”/qn REBOOT=”R””
Administrative installation. setup.exe /a
Silent administrative installation specifying
the extract location for Rescue and Recovery.
setup.exe /a /s /v”/qn TARGETDIR=”F:
\TVTRR””
Silent uninstallation setup.exe /s /x /v/qn. setup.exe /s /x /v/qn
Installation with no reboot. Create an
installation log in temp directory for Rescue
setup.exe /v”REBOOT=”R” /L*v %temp%
\rrinstall40.log”
and Recovery.
Installation without installing the Predesktop
setup.exe /vPDA=0
Area setup.exe /vPDA=0.
The table below shows installation examples using Rescue and Recovery.msi:
Table 2.
Description Example
Installation msiexec /i “C:\TVTRR\Rescue and
Recovery.msi”
Silent installation with no reboot msiexec /i “C:\TVTRR\Rescue and
Recovery.msi” /qn REBOOT=”R”
Silent uninstallation msiexec /x “C:\TVTRR\Rescue and
Recovery.msi” /qn
Installation without installing the Predesktop
Area
msiexec /i “C:\TVTRR\Rescue and
Recovery.msi” PDA=0
Installing Rescue and Recovery 4.2 with existing versions
If you are installing Rescue and Recovery 4.2 on a machine with Rescue and
Recovery 3.1 installed, you can use the over-install feature. If you are installing
Rescue and Recovery 4.2 over versions 1, 2 or 3.0, uninstall the previous version
through Windows Add/Remove programs and then install Rescue and Recovery
4.2. See “Overinstall considerations” on page 5 for more information.
Chapter 2. Installation 9
Rescue and Recovery installation
The following instructions are for the files that can be downloaded separately from
the Large Enterprise individual language files download page.
1. The main installation executable for Rescue and Recovery is:
v Z501ZISXXXXUS00.EXE for Windows XP and 2000
v Z503ZISXXXXUS00.EXE for Windows Vista
XXXX is the build ID. This is a self-extracting installation package that
where
extracts the installation source files and launches the installation using the
Windows Installer. It contains the installation logic and the Windows
application files. The package does not contain any of the Predesktop Area files.
Note: Windows Vista uses a different package than Windows XP and 2000.
2. Predesktop Area US Base (approximately 135 MB): This is the password
protected zip file that contains the entire Predesktop Area US base. Its name is
in the format
v Z501ZABXXXXUS00.TVT for Windows XP and 2000
v Z503ZABXXXXUS00.TVT for Windows Vista
AB determines the compatibility of the Predesktop Area and XXXX is
where
the build id. This file is required to install the Predesktop Area on all language
systems. This file must be in the same directory as the main installation
package (either installation executable or Rescue and Recovery.msi if extracted
or OEM install). The exceptions to this are if the Predesktop Area is already
installed and does not need to be upgraded or if the property PDA=0 is set on
the command line when executing the installation and the Predesktop Area
(any version) does not already exist. The installation executable contains a file
pdaversion.txt that contains the minimum version of the Predesktop Area that
can work with that version of Windows. The installation executable installer
will look for a Predesktop Area file using the following logic:
v Old Predesktop Area (Rescue and Recovery 1.0 or 2.X) exists or no
Predesktop Area exists:
The installer will look for a .tvt file with a compatibility code (for example:
AA, AB) that is equal to the minimum version compatibility code and a level
that is greater than or equal to the minimum version (all other version fields
in the .tvt filename must match the minimum version exactly). If a file is not
found meeting these criteria, the installation is halted.
v New (Rescue and Recovery 3.0 or greater) Predesktop Area exists:
The installer will compare the current Predesktop Area’s compatibility code
against the minimum version compatibility code and take the following
actions based on the results:
– Current code > Minimum code:
The installer presents a message that the current environment is not
compatible with this version of Rescue and Recovery.
– Current code = Minimum code:
The installer compares the current version level against the minimum
version level. If the current level is greater than or equal to the minimum
level, the installer looks for a .tvt file with a compatibility code (for
example: AA, AB) that is equal to the minimum version compatibility
code and a level that is greater than the current version level (all other
version fields in the .tvt filename must match the minimum version
exactly). If it does not find a file, the install process continues without
updating the Predesktop Area. If the current level is less than the
10 Rescue and Recovery 4.2 Deployment Guide
minimum level, the installer will look for a .tvt file with a compatibility
code (AA or AB). that is equal to the minimum version compatibility code
and a level that is greater than or equal to the minimum version level (all
other version fields in the .tvt filename must match the minimum version
exactly). If a file is not found meeting these criteria, the installation is
halted.
– Current code < Minimum code:
The installer will look for a .tvt file with a compatibility code (for
example: AA, AB) that is equal to the minimum version compatibility
code and a level that is greater than or equal to the minimum version (all
other version fields in the .tvt filename must match the minimum version
exactly). If a file is not found meeting these criteria, the installation is
halted.
Predesktop Area language packs (approximately 5 – 30 MB each): There are
v
16 language packs for Windows PE that are supported in Rescue and
Recovery 4.2. Each language pack is named in the format
Z501ZABXXXXCC00.tvt where XXXX is the build ID and CC represents the
language. One of these files is required if the Predesktop Area is being
installed on a non-English system or a system with a non-supported
language and must be in the same directory as the main installation and the
US Predesktop Area .tvt file. If the Predesktop Area is being installed or
updated and a language pack is required, the installation looks for the
minimum level of language pack required in a version file contained within
the installation executable. The installation also looks for a language pack .tvt
file that is greater than any current language pack that is already installed
and greater or equal than the minimum version required.
Following is a list of languages supported in Rescue and Recovery 4.2:
– Brazilian Portuguese
– Danish
– Dutch
– English
– Finnish
– French
– German
– Italian
– Japanese
– Korean
– Norwegian
– Portuguese
– Russian
– Spanish
– Swedish
– Simplified Chinese
– Traditional Chinese
Chapter 2. Installation 11
Rescue and Recovery custom public properties
The installation package for the Rescue and Recovery program contains a set of
custom public properties that can be set on the command line when running the
installation. The available custom public properties are:
Table 3.
Property Description
PDA Specifies whether to install the Predesktop
Area. Default value is 1. 1 = install
Predesktop Area. 0 = do not install
Predesktop Area. NOTE: This setting is not
used if any version of the Predesktop Area
already exists.
CIMPROVIDER Specifies whether to install the Common
Information Model (CIM) Provider
component. Default is to not install the
component. Specify CIMPROIVIDER=1 on
the command line to install the component.
EMULATIONMODE Specifies to force the installation in
Emulation mode even if a Trusted Platform
Module (TPM) exists. Set
EMULATIONMODE=1 on the command line
to install in Emulation mode.
HALTIFTPMDISABLED If the TPM is in a disabled state and the
installation is running in silent mode, the
default is for the installation to proceed in
emulation mode. Use the
HALTIFTPMDISABLED=1 property when
running the installation in silent mode to
halt the installation if the TPM is disabled.
ENABLETPM Set ENABLETPM=0 on the command line to
prevent the installation from enabling the
TPM
NOCSSWIZARD Set NOCSSWIZARD=1 on the command line
to prevent the Client Security Solution
Wizard from being displayed when an
administrator logs on and has not been
enrolled. This property is for someone who
wants to install Client Security Solution, but
use scripting later when configuring the
system.
CSS_CONFIG_SCRIPT Set CSS_CONFIG_SCRIPT=”filename” or
“filename password” to have a configuration
file run after the user completes the
installaiton and reboots.
SUPERVISORPW Set SUPERVISORPW=”password” on the
command line to supply the supervisor
password to enable the chip in silent or
non-silent installation mode. If the chip is
disabled and the installation is running in
silent mode, the correct supervisor password
must be supplied to enable the chip,
otherwise the chip is not enabled.
12 Rescue and Recovery 4.2 Deployment Guide
Including Rescue and Recovery in a disk image
You can use your tool of choice to create a disk image that includes Rescue and
Recovery. This deployment guide provides basic information regarding
PowerQuest and Ghost as it applies to this application and installation.
Note: If you plan to create an image, you must capture the Master Boot Record.
The Master Boot Record is critical for the Rescue and Recovery environment to
function correctly.
Using PowerQuest Drive Image based tools with Rescue and Recovery
If the PowerQuest DeployCenter tool PQIMGCTR is installed in the following
location (X:\PQ), you can create and deploy an image with Rescue and Recovery
with the following scripts:
Minimum script files:
Table 4. X:\PQ\RRUSAVE.TXT
Script language Result
SELECT DRIVE 1 Selects the first hard disk drive.
SELECT PARTITION ALL
Selects all partitions.
(Needed if you have a type 12 partition or if
you have multiple partitions in your image.)
Store with compression high Stores the image.
Table 5. X:\PQ\RRDEPLY.TXT
Script language Result
SELECT DRIVE 1 Selects the first hard disk drive.
DELETE ALL Deletes all partitions.
SELECT FREESPACE FIRST Selects first free space.
SELECT IMAGE ALL Selects all partitions in image.
RESTORE Restores the image.
Image creation:
Table 6. X:\PQ\PQIMGCTR / CMD=X:\PQ\RRUSAVE.TXT /MBI=1 / IMG=X:\IMAGE.PQI
Script language Result
SELECT DRIVE 1 Selects the first hard disk drive.
X:\PQ\PQIMGCTR Creates the image program.
/CMD=X:\PQ\RRUSAVE.TXT PowerQuest script file.
/MBI=1 Captures the Rescue and Recovery Boot
Manager.
/IMG=X:\IMAGE.PQI Creates the image file.
Image deployment:
Table 7. X:\PQ\PQIMGCTR / CMD=X:\PQ\RRDEPLY.TXT /MBI=1 / IMG=X:\IMAGE.PQI
Script language Result
SELECT DRIVE 1 Selects first hard disk drive.
Chapter 2. Installation 13
Table 7. X:\PQ\PQIMGCTR / CMD=X:\PQ\RRDEPLY.TXT /MBI=1 / IMG=X:\
IMAGE.PQI
(continued)
Script language Result
X:\PQ\PQIMGCTR Creates the image program.
/CMD=X:\PQ\RRDEPLY.TXT Creates the PowerQuest script file.
/MBR=1 Restores the Rescue and Recovery Boot
Manager.
/IMG=X:\IMAGE.PQI Creates the image file.
Using WIM files, ImageX and Windows Vista
Windows Vista deployment is based on disk imaging with ImageX. ImageX utilizes
file based imaging with WIM files instead of sector-based image formats.
Considering this formatting development, use the scenario in “Scenario 6 Installing with WIM files and Windows Vista” on page 85 when installing and
deploying Rescue and Recovery on Windows Vista.
Using Symantec Ghost-based tools with Rescue and Recovery
When you create the Ghost image, you must use the command line switch -ib to
capture the Rescue and Recovery Boot Manager. Also, the image must capture the
whole disk and all partitions. Refer to the documentation provided by Symantec
for specific details on Ghost.
Rescue and Recovery environmental variables
The following table contains environmental variables which are created when
Rescue and Recovery is installed. These variables can be used when creating
scripts or when changing to a desired directory from a command prompt. For
example, to change to the Rescue and Recovery folder from a command prompt,
type “CD %rr%” and press enter.
Table 8.
Environmental variable Directory
%rr% c:\Program Files\Lenovo\Rescue and Recovery
%SWSHARE% c:\Program Files\Lenovo
%TVTCOMMON% c:\Program Files\Common Files\Lenovo
Note: For a complete list of variables, run the ’set’ command on a computer that
has Rescue and Recovery installed.
Compatibility with Vista Bitlocker
To achieve compatibility with Bitlocker, Rescue and Recovery needs to be installed
after the partitions are properly set up. When setting up the Bitlocker partition the
recommended way to do so is to use the tool from Microsoft called the Bitlocker
Driver Preparation Tool. The boot partition that is created should be at least 2GB in
size.
To install Vista Bitlocker without using this tool, you must have two partitions on
your system when installing Vista. One should be 2GB and marked active; this is
where the boot files reside. The other will be where your OS is installed and where
your data will reside. When Vista is installed, it will detect this and should install
only the boot files to the smaller partition. Both partitions should be type 0x07.
14 Rescue and Recovery 4.2 Deployment Guide
When installing Rescue and Recovery on a system with Bitlocker and a service
partition is not available, the following two commands should be run to prevent
the Vista OS from asking for the Bitlocker key every time it boots. These
commands are:
bcdedit -deletevalue {globalsettings} extendedinput
and
bcdedit -deletevalue {globalsettings} extendedinput
Notes:
1. When setting up Bitlocker on Vista, the bitlocker partition should be after the
OS partition for best results. If it is placed before the OS partition,, the partition
number will need to be updated in the Rescue and Recovery ADM settings.
2. When restoring a system that is using Microsoft Vista, and Bitlocker, a message
will show up that there was an error at shutdown. this can be ignored and
everything should operate normally.
Chapter 2. Installation 15
16 Rescue and Recovery 4.2 Deployment Guide
Chapter 3. Configurations
This chapter provides information that you will need to configure Rescue and
Recovery for your enterprise. Within this chapter, you will find the following
topics:
v “XML and ADM file configurations”
v “Recovery methods”
v “Backups” on page 23
v “Rescue and Recovery in the Windows environment” on page 28
v “Working with the Predesktop Area” on page 31
v “Log files” on page 51
XML and ADM file configurations
Configurations for Rescue and Recovery are done with the XML file, through the
registry, and with Active Directory. Once the XML file is customized and installed,
settings for Rescue and Recovery are managed with the registry or Active
Directory. For more information, see the accompanying ThinkVantage Technologies
XML/ADM Supplement for the deployment guide located on the ThinkVantage
Technologies Administrator Tools page:
http://www.lenovo.com/support/site.wss/document.do?lndocid=TVAN-ADMIN#tvsu
Recovery methods
Within this section, you will find information for restore types and recovery
methods such as rejuvenation, custom recovery, and express repair. The following
methods are used for restoring files:
v “Single file restore”
v “File rescue”
v “Operating system and applications” on page 18
v “Rejuvenation” on page 18
v “Full restore” on page 19
v “Custom recovery” on page 19
v “Express Repair” on page 22
v “Factory content/Image Ultra Builder” on page 23
Note:
after a restore.
Single file restore
Single file restore prompts the user for the Backup Storage location, and then the
user selects a backup. Rescue and Recovery will display files that the user is
authorized to access. The user then selects the files, folders, or both to be restored
and the system will restore them to their original locations.
Rescue and Recovery cannot capture cached credentials for a domain user
File rescue
File rescue used before restore, prompts the user for the backup storage location
and then the user selects a backup. Rescue and Recovery will display the files that
© Lenovo 2007. Portions © IBM Corp. 2005. 17
the current user is authorized to access. The user then selects the files, folders, or
both to be rescued. Excluding the local hard disk, the system will display available
file locations where the files can be rescued. The user will need to choose a
destination with sufficient space for the rescued files and the system restore files.
Operating system and applications
Operating system and Applications gives the user the option to select a backup
before the system deletes files. Files designated to be deleted are defined by the
rules in the registry. When a backup has been selected, the system will restore the
files defined by the registry from the selected backup. There are options in the
registry file that can specify a program to run before a restore or after a restore. See
the ThinkVantage Technologies XML/ADM Supplement for more information about
registry settings and values.
Notes:
1. Operating system and Applications always use Password Persistence.
2. Operating system and Applications restore is not available from CD/DVD
backup.
can add custom tasks to run before and after both Backups and Restores. See
You
ThinkVantage Technologies XML/ADM Supplement for the backup and restore
settings.
Rejuvenation
When you need to rejuvenate your system, the Rescue and Recovery program will
optimize system performance by taking a new incremental backup and then
defragment your hard drive. The rejuvenation process helps eliminate viruses,
adware and spyware, while maintaining your current settings and data.
To rejuvenate your system, complete the following steps:
1. From the Rescue and Recovery interface, click the Restore your system from a
backup icon. The Restore your system screen is displayed.
2. On the Restore your system screen, select Rejuvenate your system.
3. Choose the drive and backup that you want to use to rejuvenate your system
by completing the following procedure:
a. Select the appropriate drive from the drop-down menu of available drives.
Backup files on the selected drive are displayed by the Rescue and
Recovery interface.
b. Select the backup file that you want to use to rejuvenate your system.
c. Click Next.
d. Confirm that the selected backup is the one that you want to use to
rejuvenate your system, and then click Next to begin the restoration process.
Note: Do not power off your computer during this operation.
e. Click OK. A progress bar is displayed.
can add custom tasks to run either before or after a rejuvenation. See the
You
ThinkVantage Technologies XML/ADM Supplement for the rejuvenation settings.
Note: Some operating system settings are stored in the registry. Considering
rejuvenation restores your registry from a backup and restores certain registry keys
captured from the current system settings, you may find some inconsistencies after
the rejuvenation process. For example, if you have a shared folder in a backup and
18 Rescue and Recovery 4.2 Deployment Guide
not at the time of the rejuvenation process, it will be shared again after completing
a rejuvenation from that backup. Also, if you have a shared folder at the time of
the rejuvenation process but it was not in the backup, the folder will still be shared
after rejuvenation finishes.
Full restore
Full restore deletes all files on the local drive, and then restores the files from the
selected backup. If password persistence is selected, the most recent password
available will be restored.
Custom recovery
As an extension of the Rescue and Recovery program, custom recovery technology
has been added to the recovery process. Users will interact with this custom
recovery method through the Rescue and Recovery and the Lenovo Base Software
Selector programs. By performing a custom recovery, users have the option of
including and excluding individual components such as applications, device
drivers or operating systems as part of the recovery process. Administrators will
define what options a user will have during a custom recovery process with the
ThinkVantage Base Software Administrator program.
The Base Software Administrator program is a versatile software utility that you
can use to accomplish custom recovery and preinstallation related tasks. With the
Base Software Administrator program, you can customize the recovery process for
users and you can create personalization files used to automate the preinstallation
setup for Windows.
Customizing the recovery process
In today’s electronic environment, computer systems are threatened by malicious
activity with the distribution of viruses, worms, and Trojan horses. Technology and
anti-virus software has improved in the fight against malicious activity; however,
there are times when the software on a computer will need to be renewed by
removing malicious files and starting over. Rescue and Recovery is a valuable tool
in the renewal process by providing methods to restore a computer in the event
the computer is sold, recycled, transferred to another area or needs to be put in an
operational state after all other methods of recovery has failed.
Various types of recovery methods can be used to renew computer systems. The
Base Software Administrator program utilizes the full factory recovery method and
the custom factory recovery method. The full factory recovery method restores the
factory contents of the hard drive that consists of components such as applications,
device drivers, and the operating system. Factory components are installed at the
factory prior to the purchase of a computer. Using the Base Software Administrator
program, you can control the recovery options that are available to the user during
the recovery process. The following list provides the recovery methods you can
designate a user to perform:
v Full factory recovery only
v Custom factory recovery only
v Either a full factory recovery or a custom factory recovery
Components
components are in a custom packaged format and are contained in the service
partition of the computer. From a recovery standpoint, components are categorized
as follows:
v Required components are always installed upon recovery.
consist of applications, device drivers, and operating systems. These
Chapter 3. Configurations 19
v Optional components are displayed for the user on the Base Software Selector
menu.
v Restricted components are not installed upon recovery, and are not displayed to
the end user.
Manifest
files: Customizing the recovery process is controlled with manifest files.
The Base Software Administrator program can create custom manifest files.
Manifest files have the extension .cfi, and contain information about the
components within the service partition where it resides. Manifest files also control
the selections available to the user during a custom recovery. The information
contained in a manifest file includes component categorization such as required,
optional, and restricted. In addition, manifest files contain meta-data, such as
descriptions and comments.
Preinstallation setup
To accomplish preinstallation setup, you can use the Base Software Administrator
program to create personalization files. A personalization file has the file extension
of .per and contains information needed to automate the preinstallation setup for
Windows. The recovery process reads the personalization file, extracts the data
from the personalization file and places the data in the correct Windows control
files. Yo u can save time and effort by using the Base Software Administrator
program to customize personalization files and then deploying those
personalization files onto user computers. For example, you can create a
personalization file to set the Time Zone for Windows and then deploy that
personalization file to a users computer; therefore, a user will not have to manually
validate the Time Zone settings.
Personalization files: Personalization files are customized by defining the settings
with the Base Software Administrator program. The following tables provide a
description of each type of setting that can be defined.
The General settings table provides the settings used to define the user name,
organization and time zone for a computer:
Table 9. General settings
Windows control file
Setting
keyword Description
Name FullName= Sets the user name for the
computer.
Organization OrgName= Sets the organization the
computer belongs to, such as
a specific department or
location.
Time zone TimeZone= Sets the time zone for the
computer.
The Network settings table provides the settings used to assign the computer
name, administrator password and the workgroup or domain of the destination
computer:
Table 10. Network settings
Windows control file
Setting
keyword Description
Computer name ComputerName= Sets the name for the
computer.
20 Rescue and Recovery 4.2 Deployment Guide
Table 10. Network settings (continued)
Windows control file
Setting
keyword Description
Administrator password AdminPassword= Sets the administrator
password.
Encrypted administrator
password
EncryptedAdminPassword= Sets the encrypted
administrator password.
Workgroup JoinWorkgroup= Sets the workgroup for the
computer.
Domain JoinDomain= Sets the domain for the
computer.
Domain administrator DomainAdmin= Sets the domain
administrator for the
computer.
Domain administrator
password
DomainAdminPassword= Sets the domain
administrator password for
the computer.
Advanced settings are used to define one or more commands that can be run the
first time a user logs on to his or her system.
Command line interface: The following executable supports a command line
interface for the Base Software Administrator program and is supported under
WinPE and the Windows environment:
TBSADMIN.EXE [/DEPLOY [/SILENT] [/BOOTSP=YES|NO]
[/MANIFEST="<path>"] [/PERSONALIZATION="<path>"]]
The following table provides the switches for the Base Software Administrator
program.
Table 11. Switches
Switch Description
/DEPLOY Required to trigger a deploy. If /BOOTSP,
/MAN or /PER is also specified, the deploy
wizard is not displayed.
/SILENT Suppresses any message boxes for error or
successful completion. (For return codes, the
following table.)
/BOOTSP Takes an explicit Y or N value to indicate
whether the service partition should be set
active. For example, /BOOTSP=Y. A value of
N allows the adminitrator to reset the C:
partition active again, so recovery doesn’t
automatically occur on next reboot.
The executable returns the following codes:
Table 12. Return codes
Return code Return message
0 Success
1 Unable to access service partition.
Chapter 3. Configurations 21
Table 12. Return codes (continued)
Return code Return message
2 Error copying manifest file into service
partition
3 Error copying personalization file into
service partition
4 Error deleting file from service partition
5 Error writing AUTO.TAG file in service
partition
6 Error setting service partition active
Express Repair
Also known as Fast Restore, Express Repair monitors and fixes operating system
files from an alternate boot environment if they have changed or been corrupted
outside of normal operating system by file corruption, or a virus. After Rescue and
Recovery is installed and after a Windows operating system update, Express
Repair stores the latest copy of each critical file including the checksum behind the
Rescue and Recovery filter driver in its own database. Monitored files are listed in
KernelFile.xml. The Express Repair database is located in the following path:
C:\RRBackups\FR
Express Repair supports the following operating systems:
v Windows XP
v Windows Vista 32 bit
v Windows Vista 64 bit
During
restore operations launched from Windows or the preboot environment
such as Quick Restore, Rejuvenation, or Full Restore, Express Repair files and
checksums are deleted to avoid mismatching of operating system files. As a result,
Express Repair stores all critical files and associated checksums after the next boot
into the operating system. When a user boots to Windows PE, checksum compares
critical operating system files. If a difference is detected, the user is prompted
update files based on the latest version in the database, or boot to Windows. If a
difference is not found, or if database not found, Express Repair exits and continue
boot into Windows PE.
You can turn off Express Repair by setting the following policy in Group Policy:
ThinkVantage\Rescue and Recovery\Settings\Fast Restore
The default value is Enabled. If this value is Enabled or not set, then Express
Repair will run normally in the operating system and the Predesktop Area. If this
value is Disabled, then Express Repair will not run in the operating system or in
the Predesktop Area. For more information on Group Policy and ADM files, see
the accompanying XML/ADM Supplement for the deployment guide located on
the ThinkVantage Technologies Administrator Tools page:
http://www.lenovo.com/support/site.wss/document.do?lndocid=TVAN-ADMIN#tvsu
Note: The XML and ADM file refer to Express Repair as Fast Restore.
22 Rescue and Recovery 4.2 Deployment Guide
Loading...