CCNP Training 

Image-based Installations of NLB Clusters

Image-based Installations of NLB Clusters

Image-based installations, also known as disk cloning or simply cloning, is the fastest method of deploying Windows Server 2003, Enterprise Server. Image-based installations are useful if you are deploying computers that have similar hardware and you want to perform quick, clean installations with minimal end user interaction

Cloning NLB Clusters consists of the following steps:

1. Building a master installation on a master computer. Building a master installation includes installing and configuring the operating system and any software and drivers you need to include on your virtual hard disk.
2. Preparing the master installation with the Sysprep tool. This includes configuring and running the Sysprep tool on the master computer.
3. Generating a virtual hard disk of the master installation with the disk-imaging tool. This includes saving each virtual hard disk to a permanent storage location.
4. Loading virtual hard disks on destination computers that will make up a cluster.

Using SYSPREP to prepare for imaging

 

Building a Master Installation

You need to setup a master computer which you will use to build a master installation and later to create a virtual hard disk.

Building a master installation includes installing and configuring the operating system and any software and drivers you need to include on your virtual hard disk.

Prepare the master installation.

After you have prepared a master installation on the master computer, you need to prepare a virtual hard disk for cloning. Microsoft provides a tool called sysprep that allows you to prepare an image for cloning. The tool can be found on the Windows Advanced Server 2003 CD in the \support\tools directory. When you run sysprep on the master computer, you can supply one of the following two switches: -factory or reseal.

You can use Factory mode to install additional drivers and applications at the stage after the reboot that follows Sysprep. Normally, running Sysprep as the last step in the pre-installation process prepares the computer for delivery. When rebooted, the computer starts Mini-Setup. By running Sysprep with the -factory option, the computer reboots in a network-enabled state without starting Mini-Setup. In this state, Factory.exe processes its answer file, Winbom.ini, and performs the following actions:

1. Copies drivers from a network source to the computer
2. Starts Plug and Play enumeration
3. Stages, installs, and uninstalls applications on the computer from source files located on either the computer or a network source
4. Adds customer data

When finished, run Sysprep with the -reseal option to prepare the virtual hard disk for cloning.

For example, you can create a master installation that contains a minimal set of drivers, run sysprep -factory, create an image of the installation, and copy the image to multiple destination computers. If any destination computers require additional drivers, run sysprep -factory on the destination computer and load those drivers at that time.

For more information about the Factory mode and winbom.ini file, refer to Microsoft Windows XP Preinstallation Guide. This document is located in Deploy.cab on the Windows Server 2003 CD.

If you do not need to install any additional drivers or applications on the destination computers, run sysprep in the Reseal mode.

Sysprep and Sysprep.inf Answer file

To completely automate NLB cluster installation, you will need to use the sysprep.inf file which is an answer file used by sysprep during and after Mini-Setup.

Required Sections and Entries in sysprep.inf

A fully unattended Setup requires the following sections and entries:
Required section Required entries in that section Comments
[Unattended] UnattendMode

TargetPath

  
[GuiUnattended] AdminPassword

TimeZone

  
[Identification] JoinWorkgroup You may instead specify JoinDomain, DomainAdmin, and DomainAdminPassword.
[LicenseFilePrintData] AutoMode

AutoUsers

 Requires AutoUsers ifAutoMode = PerServer.
[Networking]   Required to configure network protocols.
[UserData] ComputerName

FullName

  

Please refer to the Operating System Sections and Entries for Unattended Install section of this document for an explanation of what each of these entries is used for.

NLB-specific Sections and Entries

See section NLB-specific Sections and Entries for NLB specific configuration options in the sysprep.inf answer file.

 

Payless MCSE Boot camp offers Payless MCSE boot camp, MCSE training boot camp, MCSE certification boot camp, MCSE Cisco Boot camp, MCSE Certification training boot camp. MCSE Training certification boot camp, MCSE Boot Training Camp, MCSE boot certification camp, MCSE UK Boot camp, MCSE san Mateo Boot camp, MCSE Japan boot camp, MCSE USA Boot camp, MCSE Europe Boot camp, MCSE guaranteed boot camp.

  • Do you want to become  Real MCSE, CCNA or CCNP certified?
     
  • Do you want to Payless for certification?
     
  • Do you want to finish in 2/3 weeks?

 

 

 

 

MCSE Boot Camp, CCNA Bootcamp, CCNP Boot camp training in UK, USA, JAPAN, India
CCNA Training, MCSE Training, A+ Certification, MCSA, CCNP, Network+, Security+, CISSP, MCSD, CCSP,

MCSE Exam, free Real Exam Test, Guide, Prepare MCSE

 

MCSE Guide

Free MCSE
Free MCSE Training
MCSE
MCSE 2003
MCSE Books
MCSE Boot Camp
MCSE Brain dumps
MCSE Certification
MCSE Exam
MCSE Free
MCSE Jobs
MCSE Logo
MCSE Online
MCSE Online Training
MCSE Practice
MCSE Practice Exams
MCSE Practice Tests
MCSE Requirements
MCSE Resume
MCSE Salary
MCSE Self Paced Training Kit
MCSE Study
MCSE Study Guide
MCSE Study Guides
MCSE Test
MCSE Testing
MCSE Training
MCSE Training Kit
MCSE Training Video
MCSE Windows 2003
Microsoft MCSE Training
Training MCSE
Windows 2003 MCSE

 

 

MCSE : Security Specialist

 

Remote Access Protocols

 

In Windows 2003, you can establish a remote connection by using either dialup remote access or a virtual private network (VPN). To establish a remote access connection to a Windows 2003 network, you can select from the following remote access protocols:

 

  • Dial-up protocols
  • VPN protocols

 

These remote access protocols are supported by Windows 2003 and provide interoperability with third party remote access components. Understanding the features of each protocol will help you decide which protocol is appropriate for your network.

 

 

Dial-up Protocols

Windows 2003 supports dial-up remote access protocols, such as Serial Line Internet Protocol (SLIP) and Point-to-Point Protocol (PPP), to provide clients with access to a variety of remote access servers.

 

SLIP

SLIP allows remote access clients to connect to a remote access server through a modem. This allows client computers running Windows 2003 to connect to SLIP servers. A SLIP server is a remote access protocol component on the remote access server that services connection requests from SLIP clients.

Although client computers running Windows 2003 can connect to SLIP servers, Routing and Remote Access does not itself include a SLIP server component. Therefore, you cannot use a computer running Windows 2003 as a SLIP server. Instead, you can use a server running UNIX as a SLIP server. SLIP is an industry standard protocol that addresses TCP/IP connections made over serial lines. SLIP is supported by Routing and Remote Access and gives clients running Windows 2003 access to Internet services. SLIP has several limitations:

 

  • Support is limited to TCP/IP. You cannot use SLIP to directly transfer other network protocols, such as IPX/SPX or NetBEUI.
  • A static IP address is required. SLIP requires the client to configure all of the TCP/IP configuration parameters, such as the IP address, prior to establishing a connection to the server.
  • It typically relies on text-based logon authentication sessions and usually requires a scripting system to automate the logon process.
  • It transmits authentication passwords as clear text. This might result in a security compromise because passwords are not encrypted during user authentication.

 

 

PPP

PPP is a set of industry-standard protocols that enable remote access clients and servers to operate in a network consisting of components manufactured by multiple vendors. PPP supports encrypted password authentication. PPP is an enhancement to the original SLIP specification and provides a standard method for sending network data over a point-to-point link.

 

PPP support enables computers running Windows 2003 to connect to remote networks through any server that complies with PPP standards. PPP compliance also enables a server to receive calls from, and provide access to, other vendors’ remote access software. The PPP architecture enables clients to use any combination of NetBEUI, TCP/IP, and IPX/SPX network transport protocols. You can run applications  written to the IPX/SPX, NetBIOS, or Windows Sockets (WinSock) interface on a remote computer running Windows 2003. The PPP architecture enables a server to download and configure TCP/IP parameters

 

 


© Vibrant Worldwide Inc.