cbmr dr ris-wds network boot setup

8/7/2019 Cbmr Dr Ris-wds Network Boot Setup

1/17

Network Booting CBMR and TBMR from aRIS/WDS Server for a WinPE Based Disaster

Recovery


2/17

Network Booting CBMR & TBMR from a RIS/WDS Server for a WinPE Based Disaster Recovery

Page 2

Section Title Page

1.0 Introduction 3

1.1 Using WinPE1 or WinPE2 3

2.0 RIS Server 4

2.1 Prerequisites 4

2.2

Prepare the CBMR or TBMR WinPE1 les for use on the

RIS Server 4

2.3Adding the CBMR or TBMR WinPE1 boot image to a RIS

server5

2.4Boot the CBMR or TBMR DR WinPE1 client from the RIS

server9

3.0 WDS server 12

3.1 Prerequisites 12

3.2 Adding the CBMR or TBMR boot image to a WDS server 12

3.3 Boot the CBMR or TBMR DR WinPE2 client from the WDSserver

17

Copyright 2003-2010 Cristie Software Ltd. All rights reserved.

The software contains proprietary information of Cristie Software Ltd.; it is provided under a license agreement containing

restrictions on use and disclosure and is also protected by copyright law. Reverse engineering of the software is prohibited.

Due to continued product development this information may change without notice. The information and intellectual property

contained herein is condential between Cristie Software Ltd. and the client and remains the exclusive property of Cristie Software

Ltd. If you nd any problems in the documentation, please report them to us in writing. Cristie Software Ltd. does not warrant that

this document is error-free.

No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, electronic,

mechanical, photocopying, recording or otherwise without the prior written permission of Cristie Software Ltd.

IBM Tivoli Storage Manager (TSM) and TIVOLI are trademarks of the IBM Corporation.

PC-BaX, Cristie Storage Manager (CSM), SDB, TBMR (Bare Machine Recovery for TSM) and CBMR (Cristie Bare Machine

Recovery) are trademarks of Cristie Software Ltd.

Cristie Software Ltd

New Mill, Chestnut Lane

Stroud GL5 3EH UK


3/17


Page 3

1.0 Introduction

RIS (Remote Installation Services) was introduced with Windows 2000 as an optional component. Initially,

it supported only the distribution of Windows 2000 Professional, but with Service Pack 3 allowed for

the remote installation of Windows 2000 Server. RIS was subsequently updated twice; once to support

Windows XP, and again to support Windows Server 2003.

With the release of Service Pack 2 for Windows Server 2003, RIS was replaced with Windows Deployment

Services (WDS) which supports the deployment of Windows 2008 R2 Server, Windows Vista and Windows

7.

This document gives an overview of how to setup the Windows PE based DR environment for CBMR so

that it can be network booted from a RIS or WDS server; it is not intended to be a fully instructional guide

for the process of installing RIS or WDS, or any advanced options thereof. For information relating to this,

you should consult the Microsoft installation guides which can be found at http://www.microsoft.com

This guide is also applicable to TBMR although the screen shots shown are all from a CBMR example. The

Method is exactly the same for both CBMR and TBMR.

In addition, this document assumes that you have a working RIS or WDS server already running. If you

do not, you should consult the Microsoft documentation in order to install and congure your RIS or WDS

server.

1.1 Using WinPE1 or WinPE2

At this point you should establish whether you are using WinPE1 or WinPE2. If you have downloaded

CBMR from the Cristie website, you can check the name of the ISO (eithercbmr622win86_x64-pe1 or

cbmr622win86_x64-pe2), or check the label on the CD if your copy of CBMR has been supplied to you

in this way.

You can also check by looking in the root of the CD or .ISO; since WinPE1 will have the le: CBMR_DR.ISO

in the root of the .ISO, whereas WinPE2 will not.

WinPE2 will not work on a RIS server; RIS is a service only used on versions of Windows Server up to and

including 2003 SP1 and Windows XP (WinPE1 technology).

WinPE2 is based on Windows Server 2008, Vista, and Windows 7 technology and should be used for

recovery of those operating systems.

If you are using WinPE2, therefore, you should refer to section 3.0 which covers how to boot from a serverrunning WDS. You can install WDS on a Windows Server 2003 by installing Service Pack 2, if you wish.

Note:

The scenario for the RIS Server, using WinPE1, used in this document was created using

Windows Server 2003 Enterprise Edition with Service Pack 1.

The scenario for the WDS Server, using WinPE2, used in this document was created using

Windows Server 2003 Enterprise Edition with Service Pack 2. Note that using WDS is exactly

the same in this version of Windows as it is in later versions of Windows Server (i.e. 2008R2).


4/17


Page 4

2.0 RIS Server

The following section relates to network booting CBMR or TBMR WinPE1 from a RIS server.

2.1 Prerequisites

Prior to installing RIS on a suitable server, please be aware of the following prerequisites:

RIS only works on a Windows Domain and the Domain (Active Directory) server must be available when

installing/conguring RIS.

DHCP must be congured and available on a server somewhere.

The RIS server must have a single NIC.

RIS image database must be installed on a separate disk or partition from the Windows Boot/System

partition(s).

The RIS server can be a member server if necessary.

Remember to authorise the RIS server in Active Directory during RIS installation.

2.2 Prepare the CBMR or TBMR WinPE1 les for use on the RIS Server

Before setting up the RIS environment for WinPE1, nd the appropriate les on the CBMR or TBMR

product CD or ISO image.

The les required are:

CBMR_DR.ISO (or TBMR_DR.ISO)

startrom.com

ntdetect.com

setupldr.exe

CBMR_DR.ISO will be found in the root directory of the CBMR product CD or ISO (as will its TBMR

equivalent). The other three les are supplied in a directory called risbootles on the root of the CD (or

ISO).


5/17


Page 5

2.3 Adding the CBMR or TBMR WinPE1 boot image to a RIS server

Boot images are Windows PE images that you boot a client computer into to perform a system restore

using CBMR or TBMR.

You can use the command line for this or Windows Explorer (as is shown in the examples). Ensure that

you have your CBMR or TBMR CD inserted in the CD/DVD drive in the server, or accessible through a valid

network connection, so that you can retrieve the les needed here.

1. Navigate to the \RemoteInstall\Setup\English\Images folder on the RIS server, and then

create a sub-folder for Windows PE called winpe:

2. Then create a sub-folder in the \winpe folder named: i386 (gure 2).

Figure 1

Figure 2


6/17


Page 6

3. Copy the customised

Windows PE ISO

image le (CBMR_

DR.ISO or TBMR_DR.ISO) from the

CBMR or TBMR

CD or ISO into the

winpe\i386 folder.

Figure 3

4. Create a sub-folder

in the \winpe\

i386 folder named

\templates.

Figure 4

5. Copy Ntdetect.

com, Setupdlr.

exe and Startrom.

com to the winpe\

i386\templates

folder. These les

can be found in the

RISBOOTFILES

folder in the root of

the CD or ISO.

Figure 5


7/17


Page 7

6. Rename Setupldr.exe to Ntldr (gure

6).

7. Create a text le named Winnt.sif in the \winpe\i386\templates folder with the following text:

[SetupData]

BootDevice = ramdisk(0)

BootPath = \i386\System32\

OsLoadOptions = /noguiboot /fastdetect /minint /rdexportascd /rdpath=%INSTAL

LPATH%\%MACHINETYPE%\cbmr_dr.iso

Architecture = i386

[RemoteInstall]

Repartition = No

[OSChooser]

Description = Cristie CBMR

Help = RIS Network Boot Setup - CBMR

LaunchFile = %INSTALLPATH%\%MACHINETYPE%\templates\startrom.com

ImageType = Flat

Version = 6.1 (0)

Figure 6

The cbmr_dr.iso le shown at the end of line 3 underSetupData (shown in bold above) should, of

course, be tbmr_dr.iso if you are using TBMR.


8/17


Page 8

If client computers fail to start using RIS restart the RIS service on the server by typing the following

commands:

net stop binlsvc

net start binlsvc

You will nish with the les in the templates directory as shown here (gure 7). This is the nal step andyou can now attempt to remote boot the client. See section 2.4.1: Boot the CBMR or TBMR DR WinPE1

client from the RIS server.

Figure 7

If you wish, you may check that the CBMR image is correctly installed by selecting Active Directory Users

and Computers from Administrative Tools.

Select Domain Controllers from the tree on the left of the window, right-click on the correct Domain

controller that is running RIS, select Properties and then the Remote Install tab, click the Advanced

Settings button and then select the Images tab.

The CBMR image should appear here along with any other images installed.


9/17


Page 9

2.4 Boot the CBMR or TBMR DR WinPE1 client from the RIS server

This section describes how to boot the CBMR or TBMR DR WinPE1 console on a computer that contains

a network adapter that supports PXE DHCP-based boot ROM. As stated earlier, the example used here is

CBMR, if you are using TBMR the menu options will reect this.

1. Make sure that the network adapter is set as the primary boot device in the computer BIOS.

2. Restart the client computer from the network adapter.

3. When you are prompted to do so, press F12 to start the download of the Client Installation Wizard.

4. At the Welcome screen, press ENTER (gure 8).

Figure 8

5. Enter a valid user name, password and domain name. The user name entered must have permissions

to add computer accounts to the domain. Next, press ENTER (gure 9).

Figure 9


10/17


11/17


Page 11

While this occurs, the display will show the address of the RIS server providing the download image.

Figure 13

9. When the download completes the CBMR or TBMR DR Console will start (gure 14). Once you have

agreed to the licensing term you can start the recovery as normal. Refer to whichever document isapplicable to your software; either the CBMR 6.2.x Windows Based Recovery Guide for WinPE1 or the

TBMR User Guideboth are supplied with the software.

Figure 14If you cannot see the CBMR image when booting from the RIS client, please check that all the syntax in

the Winnt.sif le is exactly as specied here. Even slight errors or omissions can result in the image not

being detected, or simply not working at all.


12/17


Page 12

3.0 WDS Server

As stated earlier, the scenario for the WDS Server used in this document was created using Windows

Server 2003 Enterprise Edition with Service Pack 2.

3.1 Prerequisites

AD DS. A Windows Deployment Services server must be either a member of an AD DS domain or adomain controller for an AD DS domain. The AD DS domain and forest versions are irrelevant; all domain

and forest congurations support Windows Deployment Services.

DHCP. You must have a working DHCP server with an active scope on the network because Windows

Deployment Services uses PXE, which relies on DHCP for IP addressing.

DNS. You must have a working DNS server on the network before you can run Windows Deployment

Services.

NTFS volume. The server running Windows Deployment Services requires an NTFS le system volume for

the image store.

Credentials. To install the role, you must be a member of the Local Administrators group on the server. To

initialize the server, you must be a member of the Domain Users group.

Boot & Install Images. Before you can deploy a custom image (i.e. a CBMR or TBMR image) you must

have at least on Boot Image and One Install Image installed. To achieve this, install the default images

provided on the installation CD for Windows Server 2008 R2.

Ensure the client machine has at least 512Mb of RAM which is the minimum amount of RAM for

using Windows PE2.

3.2 Adding the CBMR or TBMR boot image to a WDS server

1. Open the WDS console in your Windows Server and right-click on Boot Images (gure 15). Select

Add boot image from the menu.

Figure 15


13/17


Page 13

Figure 16

Figure 17

Figure 18

2. At this point, ensure that your CBMR

or TBMR CD is inserted into the CD/DVD drive, or is accessible via a

network connection. Click on the

Browse button and navigate to the

SOURCES folder on the root of the

CD (gure 17).

3. Select the BOOT.WIM le and click

Open. Note that this le is called

BOOT.WIM in TBMR also.

4. Click Next when the correct path

appears (gure 18).


14/17


Page 14

Figure 20

Figure 21

5. Click Next to conrm the name anddescription of the image (gure 19)

Figure 19

6. Review the information and click

Next to continue (gure 20).

7. The image will now copy on

to the WDS server (gure 21).

When this has completed click

Finish.


15/17


Page 15

Figure 22

Figure 23

The CBMR image will now appear in the WDS console (gure 22).

3.3 Boot the CBMR or TBMR DR WinPE2 client from the WDS server

This section describes how to boot the CBMR DR WinPE2 console on a computer that contains a network

adapter that supports PXE DHCP-based boot ROM. As stated earlier, the example used here is CBMR, if

you are using TBMR the menu options will reect this.

1. Make sure that the network adapter is set as the primary boot device in the computer BIOS.

2. Restart the client computer from the network adapter.

3. When you are prompted to do so, press F12 to start the download of the Client Installation Wizard.

4. You will then be presented with the image menu (gure 23). Select CBMR 6.2.2 DR Console.

5. The boot image will now load (gure 24). You will see the IP address of the WDS server from which the

image is loading in the bottom left-hand corner of the screen.


16/17


Page 16

6. When the download completes the CBMR or TBMR DR Console will start (gure 25). Once you have

agreed to the licensing term you can start the recovery as normal. Refer to whichever document is

applicable to your software; either the CBMR 6.2.x Windows Based Recovery Guide for WinPE2 or the

TBMR User Guideboth are supplied with the software.

Figure 25

Figure 24


17/17

Cristie Software Ltd, New Mill, Chestnut Lane, Stroud GL5 3EH, U.KTel: +44 (0)1453 847 000 Fax: +44 (0)1453 847 001 email: [email protected]

cbmr dr ris-wds network boot setup

Documents