1-Touch for Windows - How To

Topics | How To

Run CopytoCache

Test 1-Touch Boot CD-ROM for Mass Storage Recognition

Enable 1-Touch Boot CD-ROM for Mass Storage Recognition

Boot and 1-Touch Recover a Client using the 1-Touch ISO Image on a PXE Server

Integrate Service Packs for non-X86 Windows Distribution Packages

Perform 1-Touch Recovery with Broadcom NetXtremeII Driver Workaround

Run CopyToCache

Before You Begin

SQL service should be running when utilizing this tool.
The CommServe Cache directory location can only be configured from the Automatic Update Configuration (Download) window via the CommCell Console’s Control Panel. For more information, see Configure an FTP Site and CommServe Cache Directory.

Required Capability: Capabilities and Permitted Actions

To run CopyToCache:

Initiate Windows Explorer on your CommServe (or 1-Touch Server) and run the following program: <software_install_directory>/Base/CopyToCache.exe.
Enter or use the Browse button to navigate to the directory pointing to the <updatename>.exe to be copied to the CommServe Update Cache directory in the Update Location field box. Note the the current CommServe Update Cache directory location is displayed in the Cache Location field. The CommServe Update Cache directory location can only be configured from the Automatic Update Configuration (Download) window via the CommCell Console’s Control Panel. For more information, see Configure an FTP Site and CommServe Update Cache Directory.

1-Touch Only: Select the appropriate Copy Option. Refer to the following table.

If your computer (from which you are running CopyToCache) is:	And you select the following copy option(s):	The results are as follows:
CommServe (not 1-Touch)	Copy to cache	Updates will be copied to the designated CommServe Update Cache directory.
	Copy to 1-Touch	Updates will not be copied to the designated CommServe Update Cache directory.
	Copy to cache and Copy to 1-Touch	Updates will be copied to the designated CommServe Update Cache directory.
1-Touch (CommServe)	Copy to cache	Updates will be copied to the designated CommServe Update Cache directory.
	Copy to 1-Touch	1-Touch Updates will be copied to the default cache directory. See notes, 1-Touch for Windows.
	Copy to cache and Copy to 1-Touch	Updates will be copied to designated CommServe Update Cache, and 1-Touch Updates will be copied to the default cache directory. See notes, 1-Touch for Windows.
1-Touch (not CommServe)	Copy to cache	1-Touch updates will be copied to the default cache directory. See notes, 1-Touch for Windows.
	Copy to 1-Touch	1-Touch updates will be copied to the default cache directory. See notes, 1-Touch for Windows.
	Copy to cache and Copy to 1-Touch	1-Touch updates will be copied to the default cache directory. See notes, 1-Touch for Windows.

CopyToCache Copy Options are only enabled when a 1-Touch computer is detected in the CommCell environment.

Click the Copy Updates To Cache button to begin the copying process.
Click Exit.

To run CopyToCache in silent mode:

Launch the Command Line Prompt.
From the prompt, enter the following: CopyToCache.exe –f <directory path of patch to be copied>. Upon completion, status of the copy operation will be displayed; 0 for success, 1 for failure. If job failed, details regarding the reason for failure will be provided.
Note the following commands for the tool:
–c disables the Copy to cache option

–t disables the Copy to 1-Touch option

Refer to previous table to determine when it is suitable to disable/enable these options.

To copy and install a service pack, refer to:

1-Touch for Windows:

The \config\update.ini file for the selected update should include the following entry: [ONETOUCH]=Yes. Any Windows File System patch with this entry will be copied to the 1-Touch Server cache.
The location of the cache is determined by the following entry in the registry:
HKEY_LOCAL_MACHINE\SOFTWARE\CommVault Systems\Galaxy\Instance\SystemRecoveryServer\sZIMAGESSHARENAME=Images

The default Images is used by other processes and should not be changed.
Once copytocache is run successfully, it creates a CVUpdates folder and stores the update in the following directory: <software_install_directory>\SystemRecovery\Images\CVUpdates.

Test 1-Touch Boot CD-ROM for Mass Storage Recognition

Related Topics

1-Touch for Windows

Required Capability: See Capabilities and Permitted Actions

To test 1-Touch Boot CD-ROM for mass storage recognition:

Boot the computer with the 1-Touch boot CD-ROM. A command screen will appear, and DiskPart will start running.
As prompted, determine whether DiskPart recognizes all the required disk devices based on the list of displayed devices.
- If so, select Y and press Enter. A warning message displays. This is followed by a prompt asking if you want to continue 1-Touch. Select N and press Enter to abort the 1-Touch process. The computer can run 1-Touch without having to load additional drivers.
- If not, press either R to rescan or N to abort 1-Touch. A message displays stating that third-party drivers may be needed to run 1-Touch on this computer.

The procedure is now completed.

Enable 1-Touch Boot CD-ROM for Mass Storage Recognition

Related Topics

1-Touch for Windows

Required Capability: See Capabilities and Permitted Actions

To enable 1-Touch Boot CD-ROM for mass storage recognition:

Copy the hardware manufacturer's (primary and secondary) mass storage drivers to a floppy disk.
Reboot the computer.
Attempt to boot again from the CD-ROM drive.
Watch the bottom of the screen for a Windows prompt to load additional drivers. When this prompt displays, press F6.
Follow the Windows prompts to select the driver from the floppy disk for the disk drive hardware.
Continue the boot process by following the Windows prompts.
Continue with the recovery procedure. You will again be prompted to indicate whether DiskPart recognizes your hard disk devices. This time all the disks should be displayed. Enter Yes.

NOTE: If the 1-Touch boot CD-ROM requires a third-party mass storage driver, you must also populate the Windows distribution folder with mass storage drivers for this hardware. See Recovering Data in Case of Disaster for more information.

Boot and 1-Touch Recover a Client using the 1-Touch ISO Image on a PXE Server

Related Topics

1-Touch for Windows

Required Capability: See Capabilities and Permitted Actions

To boot and 1-Touch Recover a client using the 1-Touch ISO image on a PXE server:

Run a full system backup of the client along with the system state.
Run the 1 -Touch Client Preparation Wizard for the client to recover.
Create the 1-Touch Boot ISO Image using the 1-Touch Boot CD Wizard.
Add and configure the 1-TOUCH.iso image to the PXE Server.
On the client to recover, change the CMOS boot sequence to boot from the hard disk.
Start the client and manually press the appropriate key to select a PXE boot.
Upon complete restoration, set the CMOS back to PXE or the preferred boot method.

On the client, the 1-Touch Recovery should complete without any errors.

Reboot the client and verify that it has recovered the original configuration.

Integrate Service Packs for non-X86 Windows Distribution Packages

Related Topics

1-Touch for Windows

Required Capability: See Capabilities and Permitted Actions

To integrate Service Packs for non-X86 Windows Distribution Packages:

Copy the Windows folder, CD-ROM or DVD to a directory. (For example, from the Windows CD-ROM, copy *.* C:\winXP.)
NOTES
- Windows does not support removing slipstreamed service packs.
Download, copy and extract the Windows Service Pack executable to a directory. For example:
copy xpsp2.exe c:\winXPSP2

c:\winXPSP2\xpsp2.exe /u /x:C:\winXPSP2 (this will extract the i386 folder into C:\winXPSP2)
Update/integrate the Windows Directory with the Service Pack. For example:
cd winXPSP2\UPDATES

c:\winXPSP2\UPDATES\update.exe /s:C:\winXP

Of course, if there are spaces in the path, put quotes around the path. For example:

update.exe /s:"C:\win XP"

NOTES
- Detailed information about distribution folders and slipstreaming is available at http://www.microsoft.com. Help can also be found by typing the command with the /help flag (e.g., update.exe /help).

The slipstreamed service pack distribution can now be imported to the 1-Touch Server using the Windows Distribution.

Perform 1-Touch Recovery with Broadcom NetXtreme II Driver Workaround

Related Topics

1-Touch for Windows

Required Capability: See Capabilities and Permitted Actions

To perform a 1-Touch Recovery with a Broadcom NetXtreme II driver workaround:

Import the RIS and Windows Drivers to be Selected When Using the Client Preparation and 1-Touch CD Wizards

The 1-Touch Boot CD will use the Remote Installation Service (RIS) installation version of the NetXtreme II driver. The driver resides in the RIS directory of the standard NetXtreme II NIC driver, which is usually B06ND.INF.

The 1-Touch Client Preparation will use the new NetXtreme II NICS for the Windows Installation (usually BXBVD.INF and BXND.INF).

Obtain the required Broadcom drivers for the boot CD and Windows installation.
Gather the following Broadcom Netxtreme II NIC drivers:
- bxnd52x.sys (for the Windows install)
- bxvbdx.sys (for the Windows install)
- b06nd51x.sys (for the 1-Touch boot CD and RIS Driver)
Obtain any Mass Storage Drivers needed for the Windows installation (e.g., percsas.sys or mraid32.sys).

Create the Client Answer Files

Using the 1-Touch Client Preparation wizard, create the client answer files. Select any mass storage drivers and the BXBVD.INF and BXND.INF NIC drivers for the client Windows installation.

Create and Use the Required Batch Files

Once the answer files have been created, create simple batch files to set up the NetxTremeII driver so that it will be able to set static IP addresses during installation.
1. Create a batch file (e.g., netxtremeII2.bat) with the following contents:
  c:\onetouchtmp\netset c:\onetouchtmp\unattend.txt
Create a master batch file and add the following batch file paths and file name in the Clientfiles\%clientname%\unattend.txt file to the first command under the [GuiRunOnce] section so that it is displayed as follows:
NOTES
- If this step is not followed, only the first batch file will run and therefore cause a failure.
- You need not add the first call path below for systems that have HP OEM Teamed NICs.

Master.bat:

Call "C:\OneTouchTmp\netxtremeII2.bat"

Call "C:\OneTouchTmp\mapshare.bat"

Call "C:\OneTouchTmp\afterBoot.bat"

Add the following batch path and file name in the Clientfiles\%clientname%\unattend.txt file to the first command under the [GuiRunOnce] section so that it is displayed as follows:

[GuiRunOnce]

Command0="C:\OneTouchTmp\MASTER.bat"

Administer the NIC Setup Files

Copy the following NIC setup files to Clientfiles\%clientname%\$OEM$\$1\OneTouchTmp:
- netXtremeII2.bat (which was created in the step included under Create and Use the Required Batch Files)
- netset.exe (provided by Microsoft)
- unattend.txt (from Clientfiles\%clientname%)

Create the 1-Touch Boot CD and Recover the Client

Using the 1-Touch CD Wizard, create and burn a 1-Touch Boot CD and include any Mass Storage drivers needed and the NetXtreme II *RIS* driver (B06ND.INF).
NOTES
- When you are importing the RIS driver to the Boot CD Image, be sure to remove any Broadcom non-RIS drivers from the image. Otherwise, the non-RIS driver will be found at the boot and it will not connect.
Boot the client with the CD to begin the recovery.

Additional Steps for Systems with HP OEM NICs

NOTES

Perform the following steps only for systems with HP OEM NICs:

Boot the recovery client with the 1-Touch Boot CD. A pop-up will be provided indicating that the network interface cards found in the computer are different from those found at backup time. This is true because the backup captured the team virtual MAC address that was set by teaming, and this is a software-generated MAC address and not an actual address.
Verify or provide the correct information to the NICs found in the computer. This will update the Windows unattend.txt file and the Windows installation will not try to use the invalid MAC address and fail. The updated change needs to be copied to the proper location for the installation in the next step.
Copy the updated %1-Touch Server%\ClientFiles\%ClientName%\unattend.txt file to the %1-Touch Server%\ClientFiles\%ClientName%\$OEM$\OnetouchTmp folder.
Press Finish in the 1-Touch Boot CD STARTUPGUI to complete the recovery.

The procedure is now completed.