Chapter 1. Overview

This chapter provides an overview of the programs represented in this deployment guide. The technologies presented in this deployment guide can directly and indirectly help IT professionals because they help make personal computers easier to use, more self-sufficient, and provide powerful tools that facilitate and simplify rollouts. With the help of ThinkVantage Technologies, IT professionals spend less time solving individual computer problems and more time on their core tasks.

Major components

The major components of this guide are: v ThinkVantage Rescue and Recovery v ThinkVantage System Migration Assistant technology Note: Throughout this deployment guide, Lenovo has provided command scripts to assist administrators with performing installation and customization functions. These command scripts were modified to fit on the corresponding pages. Enter these command scripts as a one string command.

Rescue and Recovery

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 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.
The Rescue and Recovery 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 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. v 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. v Communicate Communication overview: Links to related help topics in the Rescue and Recovery environment. 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 Windows (R) partition in the \SWSHARE folder. Map network drive: Helps users access network drives for software downloads or file transfer. v Troubleshoot 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 CDs, 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. You can then purchase separate licenses for individual computers The ThinkVantage Technologies XML/ADM Supplement addresses configuring the Rescue and Recovery environment for deployment. 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.

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. 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
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 3. Rescue and Recovery customization
Before you install Rescue and Recovery, you should understand the customization available for Rescue and Recovery. This chapter provides information that can be used to customize. Previously, Rescue and Recovery was customized with tvt.txt files. Lenovo has updated customizing techniques; therefore, customizations are done through the registry and with the rnrdeploy.xml file. Once the default rnrdeploy.xml file is customized and installed, settings for Rescue and Recovery, are managed with the registry. You can get the default rnrdeploy.xml file by executing the Download Rescue and Recovery and Client Security Solution Toolkits at http://www.lenovo.com/pc/support/site.wss/document.do?lndocid= TVAN-ADMIN If you are installing Rescue and Recovery over previous versions the settings will be migrated from the tvt.txt files to the registry. Lenovo has created a supplement document to this deployment guide that provides the values and descriptions for each setting of the rnrdeploy.xml file. This supplement contains information for both the rnrdeploy.xml file and the settings used by Active Directory. This supplement can be downloaded from the Lenovo Web site located at http://www.lenovo.com/support/site.wss/document.do?sitestyle=lenovo &indocid=MIGR-66930 For more information about Active Directory, see Active Directory Support on page 105.

\MININT\INF \MININT\SYSTEM32\DRIVERS MAINBK.BMP MINIMAL_TOOLBAR(1).INI NORM1.INI
OPERA_010.CMD OPERA6.INI PDAGUIxx.INI (where xx is the language designation) STANDARD_MENU.INI

Vista considerations

The \minint directory does not exist on the Vista version of Rescue and Recovery. The new folder in Vista is called \tvtos and the entire preinstallation environment operating system is contained in a.wim file. To edit the.wim file, you need to obtain the imagex.exe file in the Microsoft OPK for Vista.

Using RRUTIL.EXE

The RRUTIL program is designed to access the Rescue and Recovery service partition and virtual partition data. This utility will work with both virtual partitions and type 12 partitions. This utility allows customization of the Predesktop Area (PDA) by administrators. Only an Administrator user can use this tool by default. You can obtain rrutil.exe from the Download Rescue and Recovery and Client Security Solution Web site located at: http://www.lenovo.com/pc/support/site.wss/TVAN-ADMIN.html#rnr The RRUTIL program works with the Rescue and Recovery filter driver on virtual partitions, and mounts type 12 partitions as a drive in order gain access. The opening of these partitions is only done long enough to perform the requested commands then closed again. Note: The RRUTIL program for Version 4.0 is not backwards compatible with earlier versions of Rescue and Recovery. This program allows administrators to perform the following functions: v v v v v v v v View directories in the Predesktop Area. Add or update files in the Predesktop Area. Delete files from the Predesktop Area. Rename files in the Predesktop Area. View the files in \RRbackups directories. Add backups to \RRbackups directories. Get files from \RRbackups directories. Display the disk space usage of \RRbackups directories.
Predesktop Area directory list
RRUTIL /lx [<path>dirlist.txt]
Create a list of the contents of the \preboot, \minint, or root directories of the Predesktop Area partition either virtual or type 12: 1. The data is written as a text stream of all the files in each sub directory to a file named dirlist.txt in a directory name supplied by the user, or to the root of drive c:\ if not path is given. 2. This would be the equivalent of the following DOS style command (dir * /s > c:\temp\dirlist.txt) in the directory of interest. Listing of the contents of the root of the PE partition would be dir * > c:\temp\dirlist.txt only. Example output:
Directory of \ 10/20/03 03/12/04 03/10/04 08/16/02 12/16/03 12/16/03 04/06/00 09/17/03 00:00:00 00:00:00 00:00:00 00:00:00 00:00:00 00:00:00 00:00:00 00:00:00 AM AM AM AM AM AM AM AM AUTOEXEC.ICR AUTOEXEC.bat BOOT.INI COMMAND.COM CONFIG.ICR CONFIG.SYS FINDDRV.BAT HIMEM.SYS

3. An optional command line input will be a text file to capture the output of this option.
4. Sample command: RRUTIL /lx [<path>dirlist.txt] Note: Enablement of the optional entry may be deferred to a later release. The following list provides the values for x: v 1 \preboot v 2 \minint v 4 <root of c:\ or root of type 12 partition> Multiple listings would be simple addition of each x. So \preboot and \minint would be a value of 3. dirlist.txt contents:
\minint\system32\drivers*.sys \preboot\startup\*.*
Get files from Predesktop Area directories
RRUTIL /g <path>getlist.txt <copy to location>
Copy individual files from the \preboot, \minint , or root of the PE partition either virtual or type 12: 1. A text file identifies the files that should be copied to a location specified in the command line. 2. The <copy to location> must be an existing directory that will receive the files from the Predesktop Area. The files will be copied in this directory in same tree structure as they are found in the Predesktop Area. This will avoid same name files from copying over each other. 3. Sample command: RRUTIL /g <path> getlist.txt <copy to location> getlist.txt contents:
\PELDR \preboot\startup\Restore.cmd \preboot\usrintfc\PDAGUI.ini
Note: Wildcards are not supported in this function. You must understand the Predesktop Area environment before attempting any modifications.
Put files in the Predesktop Area directories

RRUTIL /p <path>

Update (add/replace) files in \preboot, \minint, or root of the PE partition either virtual or type 12: 1. Place all the files in a temp folder on drive c:\. Based on location in the temp directory, the files will be copied into the PE partitions in the same locations. For example, to add/replace a file.cmd file in \preboot\startup, the user would place the file.cmd file in c:\tempdir\preboot\startup and then run the command RRUTIL /p c:\tempdir. 2. Sample Command: RRUTIL /p c:\PDATemp contained in c:\PDATemp would be a mirror image of the directory structure of \preboot, \minint, or root of Predesktop Area. The files in the root of c:\PDATemp would put the files in the root of the PE partition.
Delete files from the Predesktop Area directories
RRUTIL /d C:\temp\dellist.txt
Delete a file in the \preboot, \minint, or root of the Rescue and Recovery partition either virtual or type-12: 1. Delete the file(s) of \preboot. \minint, or root of the PE partition either virtual or type 12 based on the contents of a text file.
2. Dellist.txt must contain a tree structure of the files to be deleted from the PDA. 3. Sample Command: RRUTIL /d <path> dellist.txt dellist.txt contents:
\preboot\startup\custom.cmd Sample file name only \preboot\usrintfc\test.txt Sample file name only
Rename a file in the Predesktop Area

Note: Do not change or delete lines 13 and 14. In the [REBOOT] section of the pdaguixx.ini (where xx is the language designation) file, you can modify the values in the following lines:

NoShowChk= RebootText=

The two values for NoShowChk are 0 and 1. To hide the message, mark the check box. When the check box is marked, the value is set to 0. To have the message displayed, change the value to 1. If necessary, the font for messages in the [REBOOT] section can be changed. For example, this value can be set as follows:
RebootText = "Arial"
Note: The following sections of pdaguixx.ini (where xx is the language designation) are available in the file, but cannot be customized: [Messages], [EXITMSG], and [HelpDlg].

Removing Factory Restore

To hide the option to Restore to Factory Contents in Windows PE, rename the file \preboot\recover\Recovery.cmd to another name and that option will not appear on the wizard. That renamed.cmd file can later be run to restore from factory contents. If the Service Partition has been removed, then this step is not necessary.
Configuring the Opera browser
The Opera browser has two configuration files: the default configuration file, and the active configuration file. An user can make changes to the active configuration file, but loses changes made when Rescue and Recovery is restarted. To make permanent changes to the browser, edit the copies of both the opera6.ini and the norm1.ini that are on the %systemdrive% (C:) in the following folder path: C:\PREBOOT\OPERA\PROFILE. The temporary, active copy of opera6.ini is on the ramdrive (Z:) in the Z:\PREBOOT\OPERA\PROFILE directory. Notes: 1. To get, edit, and place the opera6.ini and norm1.ini files, see Using RRUTIL.EXE on page 25. 2. The Opera workspace has been modified to provide enhanced security. Some browser functions have been deleted.
Opera will not save settings after it is closed
If you are using Rescue and Recovery under Microsoft Vista and want to have the Opera browser remember its preferences during the current boot to the PreDesktop Area, modify the opera.exe file. Specify the full path to the settings file on the fifth line of the \preboot\opera\opera_web.cmd from
start opera.exe /Settings opera_default.ini %1
start opera.exe /Settings %tvtdrive%\preboot\opera\opera_default.ini %1
Note: If you reboot, your changed preferences will be lost even with this change.

E-mail

Rescue and Recovery provides support for Web-based e-mail through the Opera browser. Opera provides IMAP-based e-mail which can be enabled through the large enterprise configuration, but is not supported. To get the reference information on how to enable, read the System Administrators Handbook at: http://www.opera.com/support/mastering/sysadmin/
Disabling the address bar
To disable the address bar in Opera, complete the following procedure: 1. Get the file MINIMAL_TOOLBAR(1).INI from C:\PREBOOT\OPERA\ PROFILE\TOOLBAR by using the RRUTIL process described in Using RRUTIL.EXE on page 25. 2. Open the file for editing. 3. Locate the [Document Toolbar] section of the file. 4. Locate the Address0 entry. 5. Place a semicolon (; - a comment delimiter) in front of the Address0 entry. Note: Stopping here and continuing to step 7 disables the Opera toolbar, but leaves a nonfunctional Go button and toolbar graphic. To remove the Go button and the toolbar, continue with step 6. 6. Locate the following entries and then place a semicolon in front of each:

[ComputerSettings] DisplayResolution=800x600x16 or 1024x768x16
When the Rescue and Recovery environment starts, you see an additional window during startup that is titled Factory preinstallation. The colors are reduced from thousands to 256. 4. Put back the \MININT\SYSTEM32\WINBOM.INI file by using the RRUTIL process described in Using RRUTIL.EXE on page 25.

Startup applications

The Rescue and Recovery Windows PE environment has the ability to support a startup scripts, programs, or customized programs. These scripts or programs will be processed before the Rescue and Recovery Windows PE environment reaches the main PE interface page. The directory to place the scripts or programs is \Preboot\Startup. Scripts or programs in this directory are processed alphanumerically. For example, a script called a.bat would be processed before 1.exe. To place a script or program in this directory, complete the following steps: 1. Get the RRUTIL from the Lenovo Rescue and Recovery Administration Tools site at: http://www-307.ibm.com/pc/support/site.wss/TVAN-ADMIN.html 2. Create a Temp directory. 3. In the \Temp directory create the following directory tree: \preboot\startup.
4. Put the script or program into the \Temp\preboot\startup path. 5. From a command line, type in RRUTIL p \Temp. 6. To verify that the script or program was copied successfully, type in RRUTIL g from a command line. This will generate a file named getlist.txt. 7. Examine the contents of getlist.txt for the \preboot\startup directory. The script or program should be listed under this tree.

Passwords

The following are four password options available in the Predesktop Area: v Predesktop Area or Master Password v User ID and password or passphrase v Backup password v No password
Predesktop Area or Master Password
You can set an independent Predesktop Area password. This password is set through the command line interface, and is the only password option available if Rescue and Recovery 4.0 only is installed on the system. You can create this Predesktop Area password using the following command: C:\Program Files\Lenovo\Client Security Solution\pe_setupmasterpwd.exe. The parameters for this command are:
Table 16. Parameter pe_setupmasterpwd.exe create password pe_setupmasterpwd.exe verify password pe_setupmasterpwd.exe exists pe_setupmasterpwd.exe silent pe_setupmasterpwd.exe setmode values Description Creates the actual password. Verifies that the password is valid and that it can be used. Checks to see if the password exists. Hides all the messages. 0 = no authentication required 1 = user specific authentication required 2 = master password required

Backup password

The backup password can be set through the GUI Set Password or command line interface RRCMD with backup specified. Following are some examples:

<Registry_Excludes> Optional hive is either HKLM or HKCU. keyname is the keyname. Value is an optional command that specifies the registry value that is migrated. Specifies registry keys and values that you want to exclude from the selected registry entries. For example: <Registry_Excludes> <Registry> <hive>HKCU</hive> <keyname>Software\Adobe\Acrobat Reader\5.0\AdobeViewer </keyname> <value>xRes</value> </Registry> </Registry_Excludes>
<Files_Through_Registry> <OS> specifies the operating system and is one of the following values: v Windows Vista v WinXP v Win2000 v WinNT v Win98 <Registry> specifies the registry entry and is in the format hive, keyname, value, where: v hive is either HKLM or HKCU. v keyname is the keyname. v value is an optional command that specifies the registry value the is migrated. File is the file name. You can use wildcard characters. File is the file name. You can use wildcard characters. <Files_From_Folders> Optional <PreTargetBatchProcessing> Specifies customization files to be migrated For example: <Files_Through_Registries> <Files_Through_Registry> <OS>WinXP</OS> <Registry> <hive>HKCU</hive> <keyname>Software\Lotus\Organizer\99.0\Paths</keyname> <value>Backup</value> </Registry> <File>*.*/s</File> </Files_Through_Registry> </Files_Through_Registries>
<PreTargetBatchProcessing> <!CDAT[batch commands]] <PreTargetBatchProcessing>
<PreTargetBatchProcessing> performs Batch processing before <Registries> processing by Apply. For example: <PreTargetBatchProcessing> <!CDATA[copy /y c:\temp\*.* c:\migration del c:\migration\*.mp3 </PreTargetBatchProcessing>
<TargetBatchProcessing> <TargetBatchProcessing> <!CDAT[batch commands]] <TargetBatchProcessing> <TargetBatchProcessing> performs Batch processing after <Registries> processing by Apply. For example: <TargetBatchProcessing> <!CDATA[copy /y c:\temp\*.* c:\migration del c:\migration\*.mp3 <TargetBatchProcessing>
Creating an application file
To determine which application settings must be migrated for custom application files, you must carefully test the applications. Complete the following steps to create an application file: 1. Use a text editor that can handle Unicode to open an existing application.xml file. If you installed SMA in the default location, the application.xml files are located in the d:\%RR%\Migration\bin\Apps directory, where d is the drive letter of the hard disk drive. 2. Modify this application.xml file for the application and applications settings that you want to migrate. 3. Modify the information in the <Applications> section. 4. Modify the <Name> and <Verison> commands in the <Application Shortname=Shortname> section. 5. Determine the registry keys that must be migrated: a. Click Start, and then click Run. The Run window opens. In the Open field, type regedit and click OK. The Registry Editor window opens. b. In the left pane, expand the HKEY_LOCAL_MACHINE node. c. Expand the Software node. d. Expand the vendor-specific node, for example, Adobe. e. Continue navigating until you have located the registry key for the application. In this example, the registry key is SOFTWARE\Adobe\ Acrobat Reader\6.0. f. Set the value of theDetect field. For example:

Major worm attack

This example demonstrates one possible approach to combat a major virus. The basic approach is to turn off networking, then reboot to Rescue and Recovery, retrieve fixes, perform repairs, then boot back to Windows XP, install patches, and finally restore networking. A single message might be used to perform all of these functions through the use of flag files and the RETRYONERROR command. 1. Lockdown phase To accomplish lockdown phase, inform the user what is about to happen. If the attack is not extremely serious, the administrator can give the user the option to defer the fix until later. In the most conservative case, this phase would be used to disable networking and provide a short window, such as 15 minutes, for the user to save work in progress. The RETRYONERROR command is used to keep the script running and then the machine can be rebooted into the Rescue and Recovery environment. 2. Code distribution phase an repair phase Now that the threat of infection has been removed by disabling the network and rebooting to Rescue and Recovery, additional code can be retrieved and repairs accomplished. The network can be enabled or only certain addresses can be permitted for the time required to retrieve additional files. While in Rescue and Recovery, virus files can be removed and the registry can be cleaned up. Unfortunately, installing new software or patches is not possible because the patches assume that Windows XP is running. With networking still disabled and all virus code removed, it is safe to reboot to Windows XP to complete repairs. A tag file written at this time directs the script to the patch section after the reboot. 3. Patch and recovery phase
When the machine reboots in Windows XP, Antidote Delivery Manager begins processing again even before the user can log in. Patches should be installed at this time. The machine can be rebooted if the newly installed patches require it. Now that all cleanup and patching has been completed, the network can be enabled and the user is informed that normal operation is possible.

Minor application update

Not all maintenance requires the drastic measures previously described. If a patch is available, but a virus attack is not in progress, a more relaxed approach might be appropriate. A single script can control the operation through the use of the RETRYONERROR command and tag files. 1. Download Phase The process begins with a message box informing the user that a patch will be downloaded for later installation. Then, the patch can be copied from the server. 2. Patch phase The patch code is ready for installation and it is time to warn the user to start installation. If the user requests a delay, a tag file could be used to track the delay. Perhaps later requests to install the patch might be more urgent. Antidote Delivery Manager maintains this state even if the user powers off or reboots their system. When the user has completed all processing and is ready for a system reboot, the patch is installed and the system is rebooted, if required. Attention: After a system has been restored and rebooted, reboot the system again in order for changes to take effect.

Accommodating VPNs and wireless security
The Rescue and Recovery environment does not currently support either remote access Virtual Private Networks (VPN) or wireless network attachments. If a machine is using one of these network attachments in Windows XP, and then reboots to Rescue and Recovery, network connectivity is lost. Therefore, a script like the one in the previous example does not work because networking is not available in Rescue and Recovery to download files and fixes. The solution is to package all required files in the original message or download the needed files before rebooting. Place all necessary files in the directory with go.rrs. The script file must move the required files into their final positions before exiting the script (when the directory containing go.rrs on the client is deleted). Placing patches in the message file might not be practical if the patches are very large. In this case, the user should be informed, then networking is restricted to only the server containing the patch. Then the patch can then be downloaded while still in Windows XP. Although this can lengthen the exposure of Windows XP to a virus, the extra time is probably not significant.
Virtualization Module for Antidote Delivery Manager
Virtualization Module for Antidote Delivery Manager assists in the protection of valuable data and computer systems against harmful viruses and worms. Virtualization Module for Antidote Delivery Manager is designed to improve the safety and manageability of computer systems.
With Virtualization Module for Antidote Delivery Manager, administrators will be able to remotely disconnect a terminal from the network, if a threat has been established. Administrators will also be able to remotely shut down the infected terminal. When all threats are non-existent, the system can then be rebooted into the Rescue and Recovery Predesktop Area to recover any files that may have been corrupted.

Requirements

The following requirements are essential to operate Virtualization Module for Antidote Delivery Manager: v Internet Explorer 6.0 or higher. v Windows XP Professional or Home Edition with Service Pack 2 on the customer operating system (terminals). v Windows CE on the server operating system (server). v Antidote Delivery Manager installed. v Rescue and Recovery 3.1 or later installed. v 512MB of memory. v 30MB of free disk space. v Installed on an NTFS partition. v Intel processor that is compatible with virtualization technology (available on select Lenovo computers only). v Intel virtualization technology processor enabled in BIOS. v Logon with administrator privileges. Note: The communication between the server operating system and the client operating system has been designed to be invisible. The administrator interacts with the customer operating system equipped with a Web browser. Virtualization Module for Antidote Delivery Manager will not open on the server operating system.

Table 26. System and Administration Module System Administration Stop Windows XP Network Restart Description Assists in recovery of corrupted files. Allows you to manage server access and user accounts. You will see the following menu options: Server, and User Accounts. Allows you to stop network connections. Allows you to remotely restart a terminal that has been threatened with a virus or worm.
The following table provides information for System Health and Help.
Table 27. System Health and Help Module Health Description Allows you to monitor system health, and provides health status.
Table 27. System Health and Help (continued) Module Logs Description Allows you to view log files.

Installing certificates

The user interface for the Virtualization Module for Antidote Delivery Manager program is Web-based and uses CA (Certificate Authority) Root certificates to communicate. A default certificate is installed. You can use this default certificate, customize the default certificate, or use your own custom certificate. These certificates must be installed to communicate with the Virtualization Module for Antidote Delivery Manager program. The following steps provide instructions on how to install certificates: 1. Open a Web browser such as Windows Internet Explorer. 2. Type the following IP address in the address field: 192.168.0.12. 3. On the Security Alert from Internet Explorer, click View Certificate. 4. On the General Tab, Click Install Certificate, or if you are working with an existing certificate, make a note of the Serial Number in the Value field on the Details tab. 5. Type your User ID and password in the User ID and password fields on the Authentication prompt. Note: If your User ID and password does not authenticate, you will be continuously prompted for your User ID and password. The User ID and password requested at the Authentication prompt will need to be set up on the server computer. This User ID and password is set up in User Accounts located on the Control Panel in Windows. Virtualization Module for Antidote Delivery Manager requires a password set for this User Account. 6. From the main menu in the Virtualization Module for Antidote Delivery Manager program, click Manage and Configure. 7. In the Upload field, click Browse, and browse to your certificate. Certificates will have the file extension of.pfx. 8. Type in your password. 9. Click Submit. A prompt will display letting you know the file was uploaded successfully. 10. From the Virtualization Module for Antidote Delivery Manager menu, click Restart Target PC. This reboots the server computer and engages the installed certificate.

The INRR command can be used to determine if the script is running in the Rescue and Recovery environment. Return values are: v 0 = Current OS PE v 1 = Current OS is not PE v >1 = Error
Table 28. Antidote Delivery Manager commands (continued) Commands Description
STATUS [/QUERY location message_name | /CLEAR location] The STATUS /QUERY command can be used to determine if a script has been run, or is queued to be run. The location value must be one of the following: v FAIL the message has already run and failed v SUCCESS The message has been completed successfully v WORK The message is currently being run, or will run next time Antidote Delivery Manager is run. v CACHE The message is queued to run. The STATUS/CLEAR command will clear the location specified. Return values are: v 0 = if the specified message found or the command completed successfully v 1 = if the specified message not found or the command failed MAILMAN [/RRU | RESET | /MB mailbox | /STATUS This command checks for mailbox locations and processes fixes found there. The following list provides the parameters: v RRU This parameter runs.ZAP which is stored in the Post Restore directory after each restore. v RESET This parameter halts processing of the currently running script. Note: This parameter should only be used in extenuating circumstances since usage is likely to cause errors. v STATUS This parameter returns a bitmask to indicate the current condition of the Antidote program. Return values are: 0 = Antidote is configured properly 1 = No mailbox defined 2 = There are no keys defined, or NOSIG=1 is not defined
Supported Microsoft commands
The following table provides supported Microsoft commands:
Table 29. Supported Microsoft commands Commands ATTRIB.EXE CACLS.EXE CHKDSK.EXE Description Displays or changes file attributes. Displays or modifies access control list (ACLs) of files. Checks a disk and displays a status report.
Table 29. Supported Microsoft commands (continued) Commands COMP.EXE COMPACT.EXE CONVERT.EXE DISKPART.EXE FC.EXE FIND.EXE FINDSTR.EXE FORMAT.COM LABEL.EXE NET.EXE PING.EXE RECOVER.EXE REG.EXE REPLACE.EXE RRCMD.EXE SORT.EXE SUBST.EXE XCOPY.EXE Description Compares the contents of two files or sets of files. Displays or alters the compression of files on NTFS partitions. Converts FAT volumes to NTFS. You cannot convert the current drive. Partitions a drive. Compares two files or sets of files and displays the differences between them. Searches for a text string in a file or files. Searches for strings in files. Formats a disk for use with Windows. Creates changes or deletes the volume label of a disk. Provides the networking commands. Checks to see if a network resource can be reached. Recovers readable information from a bad or defective disk. Registry manipulation. Replaces file. Runs Backups from OS or restores from OS or Predesktop Area. Sorts input. Associates a path with a drive letter. Copies files and directory trees.

:: Make an ISO file here - ISO will reside in c:\SWTOOLS\rrcd
Note: The following seven lines of code (in bold font) are needed only if the system is not rebooted after install.
:: Set up the environment set PATH=%PATH%;%SystemDrive%\Program Files\Common Files\Lenovo\Python24 set PATHEXT=%PATHEXT%;.PYW;.PYO;.PYC;.PY set TCL_LIBRARY=%SystemDrive%\Program Files\Common Files\Lenovo\Python24 \tcl\tcl8.4 set TK_LIBRARY=%SystemDrive%\Program Files\Common Files\Lenovo\Python24 \tcl\tk8.4 set PYTHONCASEOK=1 set RR=c:\Program Files\Lenovo\Rescue and Recovery\ set PYTHONPATH=C:\Program files\Common Files\Lenovo\logger :: The next line will create the ISO silently and not burn it c:\Program Files\Common Files\Lenovo\Python24\python c:\Program Files\ Lenovo\spi\mkspiim.pyc /scripted :: The next line will create the ISO with user interaction and not burn it :: c:\Program Files\Common Files\Lenovo\Python24\python c:\Program Files\ Lenovo\Common\spi\mkspiim.pyc /scripted /noburn

Deployment scenario 4

This is an example of an installation on a desktop computer using these hypothetical customer requirements: v Administration Create Sysprep Base Backup with Rescue and Recovery. Use the local administrator account for administration of the computer. v Rescue and Recovery Use the Client Security passphrase to protect access to the Rescue and Recovery workspace. The master password will be set already in base backup, and you will receive no prompt for Windows password. Have log on present (GINA). Install and use Fingerprint software for logon both in Windows and the Predesktop Area. v Client Security Solution Install and run in Emulation Mode. - Not all of the IBM or Lenovo systems have a Trusted Platform Module (security chip). No Password Manager. - The customer is using an enterprise Single-Sign On solution instead. Enable Client Security passphrase. - Protect Client Security Solution applications through a passphrase. Enable Client Security Windows logon. - Login to Windows with Client Security passphrase. Enable End-User Passphrase Recovery feature. - Allow users to recover their passphrase by answering three user defined question and answers.
Encrypt Client Security Solution XML Script with password = XMLscriptPW. - Password protect the Client Security Solution configuration file. Fingerprint software may or may not be installed. On the preparation machine: 1. Login with the Windows local administrator account. 2. Install the Rescue and Recovery and Client Security Solution programs with the following options:

:: This line will create the ISO silently and not burn it C:\Program Files\Lenovo\Common\Python24\python C:\Program Files\Lenovo\Common\spi \mkspiim.pyc /scripted /scripted :: This line will create the ISO with user interaction and not burn it C:\Program Files\Lenovo\Common\Python24\python C:\Program Files\Lenovo\Common\spi \mkspiim.pyc /noburn /noburn

Appendix D. Notices

Lenovo may not offer the products, services, or features discussed in this document in all countries. Consult your local Lenovo representative for information on the products and services currently available in your area. Any reference to an Lenovo product, program, or service is not intended to state or imply that only that Lenovo product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any Lenovo intellectual property right may be used instead. However, it is the users responsibility to evaluate and verify the operation of any other product, program, or service. Lenovo may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to: Lenovo (United States), Inc 500 Park Offices Drive, Hwy 54 Research Triangle Park, NC 27709 USA Attention: Lenovo Director of Licensing LENOVO GROUP LTD. PROVIDES THIS PUBLICATION AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some jurisdictions do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. Lenovo may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. The products described in this document are not intended for use in implantation or other life support applications where malfunction may result in injury or death to persons. The information contained in this document does not affect or change Lenovo product specifications or warranties. Nothing in this document shall operate as an express or implied license or indemnity under the intellectual property rights of Lenovo or third parties. All information contained in this document was obtained in specific environments and is presented as an illustration. The result obtained in other operating environments may vary. Lenovo may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you. Any references in this publication to non-Lenovo Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this Lenovo product, and use of those Web sites is at your own risk Any performance data contained herein was determined in a controlled environment. Therefore, the result in other operating environments may vary

Rescue and Recovery 4.3 Deployment Guide
Updated: September 28, 2009
A ThinkVantage Technology publication
Third Edition (October 2009) Copyright Lenovo 2008, 2009. 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. Windows environment Rejuvenating. Hints and Tips. Log files. Create Rescue Media. 49. 49
Chapter 4. Best practices. 51
Scenario 1 - New rollouts. Preparing the hard disk drive. Installing. Updating. Enabling the Rescue and Recovery desktop. Scenario 2 - Installing on OEM systems. Best practices for hard drive setup: Option 1. Best practices for hard drive setup: Option 2. Scenario 3 - Installing with WIM files and Windows 7. Scenario 4 - Standalone install for CD or script files Scenario 5 - Working with Active Directory and ADM files. Corporate Active Directory Rollout. Scenario 6 - Performing a Bare Metal Restore from an Admin Backup. Scenario 7 - Manually creating the Service Partition of S drive. 58 58
Chapter 2. Installation. 5
Installation considerations. 5 Installing the Rescue and Recovery program. 6 Installation requirements. 6 Installation components. 7 Installation log files. 8 Rescue and Recovery installation. 9 Rescue and Recovery environmental variables. 13 Compatibility with BitLocker. 13
Chapter 3. Configurations. 15
XML and ADM file configurations. Recovery methods. Single file restore. File rescue. Operating system and applications. Restore system drive only. Rejuvenation. Full restore. Custom recovery. Backups. Scheduling backups and associated tasks. Sysprep Backup/Restore. Mapping a network drive for backups. Password Persistence. EFS file limitation. Battery power settings for backups. Completing a backup. Microsoft Message Queuing (MSMQ). Rescue and Recovery in the Windows environment Using the Rescue and Recovery program in the Windows environment. Working with the Predesktop Area. Working with WIM files and ImageX. Using RRUTIL.EXE. Customizing the preboot environment. Configuring the Opera browser. Changing the video resolution. Startup applications. Passwords. Password access. 48
Appendix A. Administrative tools. 61
Command line support. Mailman. AWizard.exe. SETPASSWORD. RELOADSCHED. RRCMD command-line interface. CLEANDRV.EXE. CONVDATE. CREATSP. InvAgent. MapDrv. Rescue and Recovery Boot manager control (BMGR32). BMGR CLEAN. Active Directory Support. Administrative (ADM) template files. Group Policy settings. 71 72
Appendix B. User tasks. 83
Windows 7. Create rescue media. Rescue and Recovery user interface switching. 83. 83. 84

Appendix C. Notices. 85

Trademarks. 86
Copyright Lenovo 2008, 2009

Preface

Information presented in this guide is to support Lenovo computers installed with the ThinkVantage Rescue and Recovery program. The Rescue and Recovery program 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 applying patches to a system when a restore operation is performed. The Rescue and Recovery program helps reduce IT management costs by decreasing helpdesk calls and desk-side visits, as well as improving user productivity. The Rescue and Recovery Deployment Guide provides the information required for installing the Rescue and Recovery program on one or more computers, and also provides instructions and scenarios on the administrative tools that can be customized to support IT or corporate policies. This guide is intended for IT administrators, or those responsible for deploying the Rescue and Recovery program to computers throughout their organizations. If you have suggestions or comments, communicate with your Lenovo authorized representative. This guide is updated periodically, and you can check the latest publication on the Lenovo Web site at: http://www.lenovo.com/support/site.wss/document.do?lndocid=TVAN-ADMIN For information about using various components included in the Rescue and Recovery workspace, refer to the online help system and user guides that come with the Rescue and Recovery program.

Access BIOS: Opens the BIOS Setup Utility program. v Communicate Communication overview: Links to related help topics in the Rescue and Recovery environment. 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. v Troubleshoot Diagnostic overview: Links to the Rescue and Recovery program 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 CDs, an internal drive or a detachable storage device such as a USB hard disk drive. Note: To boot from a USB hard disk drive or a second hard disk drive, ensure that the hard disk drive is not compressed. 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 files provide a readable way to view activities and a set of log entries. Note: The feature of viewing the log files is supported on select machine types of Lenovo-branded personal computers only. Warranty status The Rescue and Recovery program 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 the Rescue and Recovery program on non-Lenovo branded computers. You can then purchase separate licenses for individual computers.

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. the Rescue and Recovery program 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

The Rescue and Recovery program can 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.
For more information, see Rejuvenation on page 16.

Hints and Tips

For hints and tips on using the Rescue and Recovery program, see the Rescue and Recovery v4.3 Considerations document located at: http://www.lenovo.com/support

XML and ADM file configurations
Configurations for the Rescue and Recovery program are done with the XML file, through the registry, and with Active Directory. Once the XML file is customized and installed, settings for the Rescue and Recovery program 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=TVANADMIN#rnr

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 on page 16 v v v v v v File rescue on page 16 Operating system and applications on page 16 Restore system drive only on page 16 Rejuvenation on page 16 Full restore on page 17 Custom recovery on page 17
Notes: 1. The Rescue and Recovery program cannot capture cached credentials for a domain user after a restore operation. 2. The Rescue and Recovery program cannot restore partitions that are created and placed physically before the system drive. 3. The Rescue and Recovery program do not support a full restore operation if you boot your system from another external media. For example, if you perform a full restore operation from your USB hard disk drive, make sure that you boot your system from this USB hard disk drive as well.

Single file restore

Single file restore prompts the user for the Backup Storage location, and then the user selects a backup. The Rescue and Recovery program 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.

File rescue

File rescue used before restore, prompts the user for the backup storage location and then the user selects a backup. The Rescue and Recovery program will display the files that 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.

Completing a backup

Applications installed or uninstalled after the selected backup is created might need to be installed again to function correctly. Make sure that the system is connected to an AC power supply before initiating a backup, restore, rejuvenation, or archive procedure. Failure to do so can result in data loss or an irretrievable system failure.
Microsoft Message Queuing (MSMQ)
If you are using MSMQ, you might have problems starting the service after from an incremental backup. That is how the Rescue and Recovery program knows what files have changed so it can back them up. So, if all those files arent backed up on an incremental, then the files could get out of synch and cause the service to fail. Here are some registry settings that run a command before the Rescue and Recovery program takes a backup that sets the Archive bit on all files in the MSMQ directory. This means the entire directory will be backed up every incremental.
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Lenovo\Rescue and Recovery\Settings\Backup \PreBackup] "Pre"="cmd" "PreParameters"="/c attrib +A \"%windir%\\system32\\msmq\\*.*\" /S /D" "PreShow"=dword:00000000
Rescue and Recovery in the Windows environment
The following sections provide information on using the Rescue and Recovery program in the Windows environment and in the Predesktop Area.
Using the Rescue and Recovery program in the Windows environment
The Rescue and Recovery program in the Windows environment enables you to perform numerous types of backups. The following information instructs you on how to use backup files with the Rescue and Recovery program.
Include and exclude backup files with registry settings
The Rescue and Recovery program can include and exclude an individual file, a folder, or an entire partition. With Rescue and Recovery 4.3, these capabilities are controlled by the following registry entries which are the type REG_MULTI_SZ: v HKLM\SOFTWARE\Lenovo\Rescue and Recovery\Settings\BackupList v HKLM\SOFTWARE\Lenovo\Rescue and Recovery\Settings\ExcludeList v HKLM\SOFTWARE\Lenovo\Rescue and Recovery\Settings\OSAppsList Setting the base backup location: The following registry entry will set a base backup as soon as an installation is complete:

HKLM\Software\Lenovo\Rescue and Recovery\runbasebackuplocation DWord = location value
BackupList: The registry entry format is:
HKLM\SOFTWARE\Lenovo\Rescue and Recovery\Settings\BackupList v One line per include/exclude rule entry. v If more than one setting applies to a file or folder, the last setting applied is used. Entries at the bottom of the registry entry take precedence. v Entries must start with either: ; for a comment I for X for S for i for include files or folders that match the entry exclude files or folder that match the entry include Single Instance Storage on a file or a folder files or folder that you can choose to include
x for files or folders that you can choose to exclude s for files or folders that the user can choose to add to Single Storage The following are examples of entries:
S=* X=* i=* I=*.ocx I=*.dll I=*.exe I=*.ini I=*.drv I=*.com I=*.sys I=*.cpl I=*.icm I=*.lnk I=*.hlp I=*.cat I=*.xml I=*.jre I=*.cab I=*.sdb I=*.bat I=?:\ntldr I=?:\peldr I=?:\bootlog.prv I=?:\bootlog.txt I=?:\bootsect.dos I=?:\WINNT\* I=?:\WINDOWS\* X=?:\WINDOWS\prefetch\* I=?:\minint\* I=?:\preboot\* I=?:\Application Data\* I=?:\Documents and Settings\* I=?:\Program Files\* I=?:\msapps\* X=?:\Recycled X=?:\RECYCLER x=?:\Documents and Settings\*\Cookies\*
x=?:\Documents and Settings\*\Local Settings\History\* X=?:\Documents and Settings\*\Local Settings\Temp\* x=?:\Documents and Settings\*\Local Settings\Temporary Internet Files\* x=?:\Documents and Settings\*\Desktop\* x=?:\Documents and Settings\*\My Documents\* s=?:\Documents and Settings\*\Desktop\* s=?:\Documents and Settings\*\My Documents\* x=*.vol s=*.vol
ExcludeList: Within this section of the registry, you can choose to exclude software applications from the recovery process initiated by the Rescue and Recovery program. This GUI exclude list is managed through the registry at: HKLM\SOFTWARE\Lenovo\Rescue and Recovery\Settings\ExcludeList. OSAppsList: The Rescue and Recovery program 4.3 provides the ability to selectively restore particular files and folders when doing an OS & Apps restore through the registry key settings: HKLM\SOFTWARE\Lenovo\Rescue and Recovery\Settings\OSAppsList The OSAppsList setting will define what files, folders, or file types comprise the operating system and applications. This file can be customized by the administrator and a default external file will be provided. When the user chooses to recover the operating system, they will see a menu that allows them to choose Restore. Only with the following Windows options: Only files that match the rules contained in this external file will be restored. The administrator can customize the contents of this external file.

Trouble ticket

Because there is no way to transmit information through file transfer or e-mail from the Rescue and Recovery environment, the end user is directed to use the e-mail function integrated in the browser. The logging function packages the log events into a file, and directs the end user to e-mail the file after he or she completes the recovery process and logs onto Windows. The file received from the end user creates the Req 115 Trouble Ticket XML file, which combines (Current, HW, InvAgent, and PCDR diagnostic log information), and will be placed in a location which can be easily found and accessible from both the Rescue and Recovery environment and operating system C:\SWSHARE. The Diagnostics tool available in the Predesktop Area of the Rescue and Recovery program aids in problem determination. Output from tests performed by the Diagnostics tool are stored in a manner which can be viewed or transmitted to a help desk.
Rescue and Recovery interface switching
The Rescue and Recovery user interface provides the option to switch between the simplified user interface and the advanced user interface. The simplified user interface has a few basic options, while the advanced user interface has extended options. By default, you will see the simplified user interface each time the Rescue and Recovery program is started unless the setting is disabled. If the Simplified User Interface setting is disabled, the advanced user interface will be displayed each time the Rescue and Recovery program starts. You can disable the simplified user interface at the following Active Directory policy:
ThinkVantage\Rescue and Recovery\User Interface\Simple User Interface
You can disable interface switching so that a user will not be able to switch between the two interfaces. To disable the interface switching, set the following Active Directory policy to Disabled:
ThinkVantage\Rescue and Recovery\User Interface\Interface Switching
For additional information about Rescue and Recovery settings and working with Active Directory and Group Policy, 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=TVANADMIN#rnr

Put files in the Predesktop Area directories

RRUTIL /p <path>

Update (add/replace) files in \preboot, \minint, or root of the PE partition either virtual or type 0x07: 1. Place all the files in a temp folder on drive c:\. Based on location in the temp directory, the files will be copied into the PE partitions in the same locations. For example, to add/replace a file.cmd file in \preboot\startup, the user would place the file.cmd file in c:\tempdir\preboot\startup and then run the command RRUTIL /p c:\tempdir. 2. Sample Command: RRUTIL /p c:\PDATemp contained in c:\PDATemp would be a mirror image of the directory structure of \preboot, \minint, or root of Predesktop Area. The files in the root of c:\PDATemp would put the files in the root of the PE partition.
Delete files from the Predesktop Area directories
RRUTIL /d C:\temp\dellist.txt
Delete a file in the \preboot, \minint, or root of the Rescue and Recovery partition either virtual or type 0x07: 1. Delete the file(s) of \preboot. \minint, or root of the PE partition either virtual or type 0x07 based on the contents of a text file. 2. Dellist.txt must contain a tree structure of the files to be deleted from the PDA. 3. Sample Command: RRUTIL /d <path> dellist.txt dellist.txt contents:
\preboot\startup\custom.cmd Sample file name only \preboot\usrintfc\test.txt Sample file name only
Rename a file in the Predesktop Area
RRUTIL /r \<PDA-path>\oldfilename.ext newfilename.ext
Rename a file located in the Predesktop Area. This function only works on files in the Predesktop Area. The path to the file to be renamed must be included without the drive letter. The new name of the file should only include the name without any path information. Example:
RRUTIL r \preboot\usrintfc\peaccessibmen.ini peaccessibmen.old
Test for Rescue and Recovery being installed

RRUTIL /bq

This command can be used in a batch file to help in automated processing. If the Rescue and Recovery code is not installed on the system only, the functions that access the Predesktop Area will be available. Example:

RRUTIL bq

Results in the environment variable %errorlevel% being set to -2, if the Rescue and Recovery program is not installed on the system, or 0 if the Rescue and Recovery program is installed. Type echo %errorlevel% to see the results of the command.

Backup directory list

RRUTIL /bl <path>
List all of the contents of the \RRbackups directories. Display the file size and date of each file in the backup as well as its location. The list below is an example of a backup directory with a base backup and one incremental backup.

Enabling or specifying the full download path
There are numerous settings that you can set to enable display of the Save As window. The most straightforward method follows: 1. Get the C:\PREBOOT\OPERA\DEFAULTS\STANDARD_menu.ini file by using the RRUTIL process described in Using RRUTIL.EXE on page 30. 2. Locate the following string:

;;Item, 50761

3. Open the file for editing. 4. Locate the [Link Popup Menu]. 5. Remove the two semicolons, and then save the file. When the Rescue and Recovery program is closed and reopened, a user is able to right-click a link and the Save Target As option is displayed. This results in display of the Save As window. Note: Straight links (not redirected links) work with the preceding procedure. For example, if a link targets a.php script, Opera saves the script only, not the file to which the script points. 6. Put the file back by using the RRUTIL process described in Using RRUTIL.EXE on page 30. To specify a fixed download directory, do the following: 1. Get the C:\PREBOOT\OPERA\norm1.ini file by using the RRUTIL process described in Using RRUTIL.EXE on page 30. 2. Open the file for editing. 3. In the file, locate this line:
Download Directory=%OpShare%
4. Change %OpShare% to the full path of the directory to which you want downloaded files to be saved. 5. Save the norm1.ini file. When the Rescue and Recovery program is closed and reopened, Opera saves downloaded files to the specified directory. 6. Put the file back by using the RRUTIL process described in Using RRUTIL.EXE on page 30. Notes: 1. Customizing the full path for downloading does not enable users to save the target file, even if the link is redirected. 2. The Opera browser is configured to download only the.zip,.exe, and.txt file types, and customizing only changes Opera behavior for these file types. Internet access is provided to help users get up and running. For the purposes of the Rescue and Recovery program, the number of recognized file types is limited. If another file type needs to be transferred, create a.zip file, which can then be extracted.) 3. File types are recognized by MIME (Multipurpose Internet Mail Extensions) type rather than by file extension. For example, if a.txt file is named with.euy as an extension, the file is still open in the Opera browser as a text file.
Adding a specific file extension to the downloadable files list
You can add to the list of files that can be downloaded through the Rescue and Recovery browser. To add to the list, complete the following procedure: 1. Make sure that Opera is closed and that all Opera windows are closed, including the Rescue and Recovery help files. 2. Get the C:\PREBOOT\OPERA\norm1.ini file using the RRUTIL process described in Using RRUTIL.EXE on page 30. 3. Open the file for editing. 4. Locate the [File Types] section of the file.
5. Use the search function find the desired file, then do one of the following: v If the extension is found, but files with that extension do not work correctly, complete the following steps: a. Change the value following the extension from 8 to 1. (A value of 8 tells the browser to ignore the file. A value of 1 instructs the browser to save the file.) For example, change the following:

4. Put the script or program into the \Temp\preboot\startup path. 5. From a command line, type in RRUTIL p \Temp. 6. To verify that the script or program was copied successfully, type in RRUTIL g from a command line. This will generate a file named getlist.txt. 7. Examine the contents of getlist.txt for the \preboot\startup directory. The script or program should be listed under this tree.

Passwords

The following are four password options available in the Predesktop Area: v Predesktop Area or Master password v User ID and password or passphrase v Backup password v No password
Predesktop Area or master password
You can set an independent Predesktop Area password. This password is set through the command line interface, and is the only password option available if the Rescue and Recovery program 4.3 only is installed on the system. You can create this Predesktop Area password using the following command: C:\Program Files\Lenovo\Rescue and Recovery\pe_masterpw_app.exe. The parameters for this command are:
Table 21. Parameter pe_masterpw_app.exe -create pe_masterpw_app.exe -verify pe_masterpw_app.exe -remove pe_masterpw_app.exe -exists pe_masterpw_app.exe -silent Description Creates the actual password. Verifies that the password is valid and that it can be used. Removes the password Checks to see if the password exists. Hides all the messages.

Backup password

The backup password can be set through the GUI Set Password or command line interface RRCMD with backup specified. Following are some examples:
rrcmd backup location=L name=mybackup password=pass rrcmd basebackup location=L name=basebackup password=pass rrcmd sysprepbackup location=L name=Sysprep Backup password=pass

No password

This option uses no authentication and allows the user to enter the Predesktop Area without using a password.

Password access

There are three options for password access: v Master password v User ID and password or passphrase v No password

Master password

The master password is a single password that allows you access to the Predesktop Area and backups. This is set by using the command line interface, and is the only password option if Client Security Solution is not installed.
User ID and password or passphrase
This option uses the Client Security Solution code for password or passphrase management. The Client Security Solution GINA will prompt the user for this password or passphrase on startup of the Predesktop Area. This provides better security for a multi-user environment. If a user logs on using the GINA, that user is allowed access to that users files only, and no one elses. This option can be set through the command line interface or the GUI.

CLEANDRV /HDD=0

4. Install the operating system and applications. Build your donor system as though you were not installing the Rescue and Recovery program. The last step in the process is to install the Rescue and Recovery program.

Installing

This first step in the installation process is the extraction of the InstallShield executable to the c:\SWTOOLS directory. If you are going to install the Rescue and Recovery program on multiple systems, performing this process one time will reduce the installation time on each machine by roughly one-half. 1. Assuming that the installation file is located in the root of the C drive, create a file EXE_EXTRACT.cmd, which will extract the file z902zisXXXXus00.exe for Windows 7 (where XXXX is the build ID) to the C:\SWTOOLS\APPS\rnr directory:
:: This package will extract the WWW EXE to the directory c:\SWTOOLS for an :: administrative installation.
@ECHO OFF :: This is the name of the EXE (Without the.EXE) set BUILDID=z902zisXXXXus00.exe :: This is the drive letter for the z902zisXXXXus00.exe :: NOTE: DO NOT END THE STRING WITH A "\". SET SOURCEDRIVE=C: :: Create the RRTemp directory on the HDD for the exploded WWW EXMD c:\SWTOOLS :: Explode the WWW EXE to the directory c:\SWTOOLS start /WAIT %SOURCEDRIVE%\%BUILDID% /a /s /v"/qn TARGETDIR=c:\SWTOOLS" Copy z902ZAB10YYUS00.tvt and Z333ZAA10ZZUS00.tvt to c:\SWTOOLS\ (where YY and ZZ are build IDs) copy z902ZAB10YYUS00.tvt to c:\SWTOOLS copy Z333ZAA10ZZUS00.tvt C: to c:\SWTOOLS If you want installation for supported languages besides US, copy z902ZAB10YYUS00.tvt to c:\SWTOOLS (where YY is the build ID and CC is the country code). copy z902ZAB10YYUS00.tvt to c:\SWTOOLS IT IS ASSUMED TO NOT BE THERE.
2. You can make many customizations before the installation of the Rescue and Recovery program. Some examples in this scenario are: v Change maximum number of incremental backups to 4. v Set the Rescue and Recovery program to perform an incremental backup every day at 1:59 p.m. to the local hard disk drive and call it Scheduled. v Hide the Rescue and Recovery user interface to all users not in the local Administrators Group. 3. Customize the default rnrdeploy.xml file. Some parameters can be modified. See the ThinkVantage Technologies XML/ADM Supplement for more information. 4. In the same directory as the install MSI file, create an install.cmd file, which will perform several actions: v Copy the custom rnrdeploy.xml file into the installation package created in the c:\SWTOOLS directory: v Perform a silent installation of the Rescue and Recovery program without a reboot at the end. v Start the Rescue and Recovery program so that a base backup can be performed. v After the service is started, set up the environment to create an ISO image of the Rescue and Recovery CD (this is normally performed as part of a reboot). v Create the ISO image. v Create the base backup and reboot the system. 5. Modify the install.cmd code. The following represents the code for install.cmd:

Corporate Active Directory Rollout
For a corporate Active Directory rollout, complete the following steps: 1. Install either through Active Directory or LANDesk. a. Take backups and get reports through Active Directory and LANDesk of who and when they were taken. b. Give certain groups abilities to take backups, delete backups, schedule options, and password restrictions, then change groups and see if settings persists. c. Through Active Directory, enable Antidote Delivery Manager. Place packages to be run and make sure reporting is captured.
Scenario 6 - Performing a Bare Metal Restore from an Admin Backup
This section describes how to perform a Bare Metal Restore from an admin backup created by using a command-line such as below:
rrcmd basebackup location=U level=100 name="admin backup on USB HDD"
Note: You can change the value of the name parameter to create backups to other locations. For modifying the RRCMD parameters, see RRCMD command-line interface on page 61. Select either of the following methods to perform the Bare Metal Restore: v Method A: restore the system by using the following command-line:
rrcmd restore location=U level=100
v Method B: complete the procedure as follows: 1. Launch the advanced user interface from PDA. 2. Click Restore your system. 3. Make sure to select Do not preserve windows passwords during the following restoring process.
Scenario 7 - Manually creating the Service Partition of S drive
To manually create the Service Partition (SP) of S drive in the Windows 7 operating system, do the following: 1. Boot from the Windows 7 installation disc and proceed to the drive selection menu. 2. Press Shift + F10 to access the command line. 3. Type diskpart, then press Enter. 4. To clean the hard disk drive, follow the commands below: Note: The commands are case sensitive. a. Diskpart>sel disk 0 b. Diskpart>sel par 1 5. Restart the computer.
6. Boot from the Windows 7 installation disc again and proceed to the drive selection menu. 7. Create Partition 1 with a 1GB size for the service partition. 8. Create Partition 2 for the operating system. 9. Format Partition 2 and leave Partition 1 unformatted. 10. Press Shift + F10 to access the command line. 11. Type diskpart, then press Enter. 12. Follow the commands below: Note: The commands are case sensitive. a. Diskpart>sel disk 0 b. Diskpart>sel par 1 c. Diskpart>format fs=ntfs label="SYSTEM_DRV" quick 13. 14. 15. 16. 17. Install Windows 7 operating system on Partition 2. When installation completes, log in to Windows. Change the drive letter of the Partition 1 to S. Activate Partition 1. Copy C:\boot*.* to S:\, and restart the computer.

rrcmd restore location=U index=1 level=2

CLEANDRV.EXE

The cleandrv.exe file cleans all files on the drive. There will be no operating system after running this command. See Scenario 6 - Performing a Bare Metal Restore from an Admin Backup on page 58 for more information.

CONVDATE

The CONVDATE utility is provided as part of the Rescue and Recovery Administration tools. This utility is used to determine the HEX values of date and time and to convert date and time values into HEX values, and can be used to set a custom date and time in a backup field of the registry.
[Backup0] StartTimeLow=0xD5D53A20 StartTimeHigh=0x01C51F46
To run the CONVDATE utility, complete the following steps: 1. Extract the Rescue and Recovery Administration tools from: http://www.lenovo.com/support/site.wss/document.do?lndocid=TVANADMIN#rnr 2. Open a CMD window. 3. Type in Convdate. 4. Set the date and time in the convdate window. Note: The corresponding registry file values are: v High DWORD=StartTimeHigh v Low DWORD=StartTimeLow

CREATSP

This command creates a partition for Service Partition by desired megabytes. The drive letter is optional. The syntax is:
createsp size=x drive=x /y
The parameters for CREATSP are:
Table 24. Parameters size=x drive=x Description Size of service partition to create, in megabytes. The drive number to create the service partition on. If not specified, the first non-USB drive is used. This parameter is optional.
Table 24. (continued) Parameters /y Description Suppresses confirmation of the drive being cleaned. This parameter is optional.
Note: The bmgr32.exe file must be in the same directory as the createsp.exe file, and should be run from WinPE.

InvAgent

The InvAgent command can be found in C:\Program Files\Common Files\Lenovo\InvAgent\IA.exe. The IA.exe creates a local XML output file that it stores in the same folder. One XML file will be created. The name of the XML file is created by combining manufacturer, model-type, and serial number, for example, Lenovo-2373Q1U99MA4L7.XML. The scanner can be run from a command-line by using the following command-line syntax: v -help Show a short help message. v -listsections List all of the available sections of system information. v -listtables List all of the sections and the tables of system information. v -silent Run with no output to the screen. v -section section1 sectiont2. Return in the XML output file only the data from the specified section(s). v -vpd Only collect the vital product data. v -leveln Sections are grouped into levels; n=1 is the least amount of information, n=5 is the most information. v -query data.element.str Returns the value of the specified data element. v -register filename.ccd Registers a custom collector DLL with the agent. v -unregister filename.ccd Removes a custom collector DLL from the registered list. v -delete filename.ccd Deletes the custom collector DLL and any associated files. v -install Run by an admin account to install any drivers needed for data collection.

PreRestore

PrePDARestoreParameters

PrePDARestoreShow

PostRestore

PostWinRestore

Table 34. \Rescue and Recovery\Settings\Restore (continued) Policy PostRestore PostRestore PostRestore Setting PostWinRestoreParameters PostWinRestoreShow PostPDARestore Description The parameter that passes the command that is run following a restore operation from Windows. Default: None. Show or hide the command that is run following a restore operation from Windows. Default: Show. Command to run following a restore operation from the Rescue and Recovery workspace. Include the full path to the file, if that path is not in the environment variable. Default: None. The parameter that passes the command that is run following a restore operation from the Rescue and Recovery workspace. Default: None. Show or hide the command that is run following a restore operation from the Rescue and Recovery workspace. Default: Show.

PostPDARestoreParameters

PostPDARestoreShow

Rejuvenate

The following table provides the policy settings for Rejuvenate.
Table 35. \Rescue and Recovery\Settings\Rejuvenate Policy PreRejuvenate PreRejuvenateParameters PreRejuvenateShow PostRejuvenate PostRejuvenateParameters PostRejuvenateShow PostRejuvenateReboot Description Command to run prior to a rejuvenate operation. Include the full path to the file, if that path is not in the environment variable. Default: None. The parameter that passes the command that is run prior to a rejuvenate operation. Default: None. Show or hide the command that is run prior to a rejuvenate operation. Default: Show. Command to run following a rejuvenate operation. Include the full path to the file, if that path is not in the environment variable. Default: None. The parameter that passes the command that is run following a rejuvenate operation. Default: None. Show or hide the command that is run following a rejuvenate operation. Default: Show. Enable or disable a system reboot following a rejuvenate operation. Default: Enabled.

User Messages

The following table provides the policy settings for User Messages.
Table 36. \Rescue and Recovery\Settings\User Massages Policy BootableSecond BootableUSB MissedBackup NoBattery ScheduledBase PowerLossBackup Description Show or hide the Bootable Second message. Default: Hide. Show or hide the Bootable USB message. Default: Hide. Show or hide the Missed Backup message. Default: Show. Show or hide the No Battery message. Default: Show. Show or hide the Scheduled Base message. Default: Show. Show or hide the Power Loss Backup message. Default: Show.