8. Rapid Server Deployment

Rapid deployment of MetaFrame Servers gives you the following benefits.

       The ability to deploy a MetaFrame server in minutes rather than hours

       The ability to guarantee consistency amongst MetaFrame servers

You can accomplish this through server cloning or scripted unattended installations as documented below.

8. 1.        How to Clone a Citrix MetaFrame XP Server

Now that you completed the installation of the first server and with the procedures documented from the first server build, you completed the second server.   You are now ready to take advantage of the benefits of MetaFrame XPs support for cloning technologies.  

Note:  Cloning a MetaFrame server that is acting as the Access data store host server is not supported. 

For future growth, ease of server deployment and disaster recovery purposes, it is desirable that you use system-imaging utilities to clone MetaFrame XP servers.  A few manual steps are required for cloning MetaFrame XP servers.  Please be very careful and make sure you complete every step and double checking your work is advisable.  If you forget to change the server DSN file, you run the risk of corrupting the IMA data store and that could cause farm wide issues.

Microsoft Sysprep v1.1

In order to successfully clone a Microsoft Windows Server you will need to utilize Windows 2000 System Preparation Utility (Sysprep).  Sysprep is a utility that ships in \Support\Tools\deploy.cab on the Windows 2000 product CD.

Sysprep is a simple utility that prepares a PCs hard disk for:

       Disk duplication   Sysprep allows you to copy fully installed systems when the hardware is similar. It modifies the local computer security identifier (SID) so that it is unique to each computer.

       Automating Mini-Setup   Sysprep creates a shortened GUI-mode setup that takes 3 to 10 minutes instead of 20 to 30 minutes and prompts the end user only for required and user-specific information, such as accepting the Microsoft license agreement, computer name, domain properties and TCP/IP addresses.

Conditions of Sysprep with the current version of Windows 2000

       Sysprep runs only if the computer is a member of a workgroup, not a domain.

       You can run additional programs at the end of Mini-Setup by providing a Cmdlines.txt in your Sysprep folder.

For more information on the Microsoft Sysprep utility please refer to Microsoft TechNet. (http://www.microsoft.com/technet)

8. 1. 1 Steps required to clone a MetaFrame XP Server

In order to successfully clone a Citrix MetaFrame Server you will need to follow these steps.

1.       Install and configure the MetaFrame XP server as discribed in the installation procedures in this document.

2.       Install any image applications.

3.       Copy sysprep.exe and setupcl.exe to c:\sysprep.  Sysprep can also be located on the Microsoft TechNet Server Utilities CD in the x:\WIN2KSRV\SYPREP11\SYSPREP.EXE self extracting executable.

4.       Remove the server from the domain and reboot when prompted.

5.       Empty all the event logs, recycle bin and clear documents and settings.

6.       Delete the Wfcname.ini file from the root drive of the server, if it exists.

7.       Edit the Mf20.dsn file with Notepad or another text editor. By default, the DSN file is at %ProgramFiles%\Citrix\Independent Management Architecture.

For a Microsoft SQL Server installation, the DSN file should look similar to this:

[ODBC] DRIVER= SQL Server

UID= SQL_USERNAME

DATABASE= NAME_OF_DATABASE

WSID= NAME_OF_MF_SERVER

APP= Citrix IMA

SERVER= NAME_OF_SQL_SERVER

Remove the following line:

WSID= NAME_OF_MF_SERVER.

The DSN now looks like this:

[ODBC]

DRIVER=SQL Server

UID=SQL_USERNAME

DATABASE=NAME_OF_DATABASE

APP=Citrix IMA

SERVER=NAME_OF_SQL_SERVER

8.       Save the changes to the DSN file.

9.       If  Resource Management is installed then you will need to recreate the RMLocalDatabase.  To recreate the RMLocalDatabase:

         Delete C:\%Program Files%\Citrix\Citrix Resource Manager\LocalDB\RMLocalDatabase.*.

         Open the ODBC Data Source Administrator.  For Windows NT TSE, choose Start > Settings > Control Panel > Data Sources (ODBC).  For Windows 2000, choose Start > Settings > Control Panel > Administrative Tools > Data Sources (ODBC)

         Select the System DSN tab in the ODBC Data Source Administrator dialog box.

         Select RMLocalDatabase from the list.

         Click Create.

         Enter C:\%Program Files%\Citrix\Citrix Resource Manager\LocalDB\RMLocalDatabase.mdb in the database name box.

         Click OK in each dialog box to exit the ODBC Data Source Administrator and then close the Control Panel when finished.

10.  top the IMA service and set the startup option to Manual.

11.  Run sysprep.exe from c:\sysprep and follow on screen instructions.

12.  Take the image of the server.

13.  Deploy the image obtained in Step 10.

14.  Add WSID= NAME_OF_MF_SERVER to %ProgramFiles%\Citrix\Independent Management Architecture\MF20.dsn

15.  Follow the mini-setup wizard created by sysprep.

16.    Manually start the IMA service and set the service to start automatically.

17.    Verify that the server was successfully added to the farm by executing qfarm at a command prompt on any server in the farm. The newly imaged server should appear in the list of servers.

8. 2.        Windows 2000 Unattended Install For Thin Client Servers

The Unattended install process consists of 2 Major Sections:

       Hardware Configuration

       Unattended Windows 2000 Setup and Configuration

8. 2. 1 Hardware Configuration

Hardware Configuration is the first step of the unattended install. Unlike other types of unattended installs this install is not hardware dependent.  But if the equipment is not fully supported by a standard Windows 2000 install you may need to add various drivers to the unattended install source files and unattended.txt file.  There are also multiple ways to configure the hardware for unattended installs.

        Option 1. Standard Hardware Configuration Tools Use IBMs ServerGuide CD or similar tools based on the hardware vendor to configure the hardware to the point where it asks for the Operating System Setup Disks or CD.

        Option 2. Automated Hardware Configuration Tools Such as IBMs Automated Update and Configuration CD, these tools are used to replicate the hardwares configuration onto multiple machines of the same type.

Standard Thin Client Server Configuration:

Four HDDs in two RAID1 arrays with High Rebuild Priority.  Two 10/100 Ethernet adapters

8. 3.        Unattended Windows 2000 Setup and Configuration

The Unattended Windows 2000 setup is the core of any type of unattended server installation used no matter what hardware configuration options are selected. This phase focuses on Three Main Parts:

1.        The Unattend.txt File

2.        The Distribution Directory Structure.

3.        The Post Install Commands.

Each part is critical in the process of the unattended install and configuration, you must use caution in modifying any of these parts.

8. 3. 1 Unattended.txt File

Also referred to as the answer file, this is the core component of the Windows 2000 Unattended Install. This file is used to answer all of the questions that you would normally see during a regular installation. Multiple configurations of this file can be maintained for different server configurations. It is not required to name this file unattend.txt but its name must not be greater than the DOS name limitation of 8.3 characters.

The Answer file contains many sections and options that can be changed. The definitions of each section, sub-section and value can be found in Appendix Z . For this document we will focus on the main sections that would possibly be modified in the Thin Client Server Configuration. This is a sample of this file:

The following sections and parameters are most likely candidates for modification:

[GuiUnattended]

    AdminPassword=*

This is where you would change the Local Administrator password on the server being built. The * leaves the password blank, replace the * with what you would like the password to be.

[UserData]

ComputerName=TJAXTSW2K6

This is the section where you change the name of the server that is to be built.

[GuiRunOnce]

       "c:\utils\ibmset.cmd"

      "C:\winnt\system32\rundll32.exe setupapi,InstallHinfSection DefaultInstall 129 c:\reboot.inf"

The GuiRunOnce section is the place where you specify the commands that are to be executed after Windows 2000 setup has done, it reboots after the GUI portion of setup. The commands must specify an absolute path to the batch file or executable and must be in quotes as seen above. This section is where you run unattended scripts to install things such as applications, tools, resource kits and system tools. The example above places a .cmd file in the startup group to complete the unattended install of Citrix Metaframe and Timbale and reboots the server. Note: This section can contain no more than 6 entries!

[Components]

This is the section where you choose what components are installed or not installed (example. Solitaire, IIS, CD Player) Refer to Appendix Z to see what components install by default and which components this file installs or instructs setup not to install.

[Identification]

    JoinDomain=

    DomainAdmin=

    DomainAdminPassword=

This section tells setup what domain to join and what account is used to create the machine account in that domain.

8. 3. 2 Distribution Directory Structure

The following is the directory structure where all of the files for the unattended portion on the Windows 2000 Setup reside. This also where any files for specialized drivers, applications, or any other items you want added to the Unattended Install Must Reside.

Example-1

Note: All Files and Directories Must Follow the 8.3 Naming Scheme. E.g. No Directory Name can be over 8 characters long and no file name can be more than 8.3 characters long. Also no directory structure can be over 55 characters!

\i386

This is the root of the directory structure, this is also where the share point that the unattended install floppy connects to start the install. This share point name should be named \\Servername\DistShare . The answer file should be located here. All of the files for the Windows 2000 operating system reside here. Also when you integrate a service pack or hot fix, this is the directory to integrate it to.

\$OEM$

Holds all supplemental folders and files for an automated or customized Win2K installation.

\$OEM$\Textmode

Contains updated mass storage drivers and HAL files required during the text-mode portion of Win2K Setup. This is where you would add drivers for RAID cards and such that arent supported by the original Windows 2000 Install.

\$OEM$\$$

Contains files that Win2K Setup copies to the %Windir% (e.g., C:\winnt) folder during installation.

\$OEM$\$$\Help

Contains custom Help files that Win2K Setup copies to the %Windir%\Help folder during installation.

\$OEM$\$$\System32         

Contains custom files that Win2K Setup copies to the %Windir%\System32 folder during installation.

\$OEM$\$1

Represents the root of the drive on which you installed Win2K (aka the boot partition) and contains any files that Win2K Setup should copy to the boot partition during installation.

\$OEM$\$1\subfolder

Represents a sub folder to be copied to the root of the drive on which you installed Win2K (aka the boot partition) and contains any files or subfolders that Win2K Setup should copy to the boot partition during installation. For example, in this installation I have created three folders that will be copied to the boot partition (see Example 1.) The three folders are \diskfix \drivers and \utils . The diskfix directory contains a Microsoft Hotfix that fixes problems with disk performance counters. The drivers directory contains the drivers used during unattended installations.  It contains the PnP drivers for the ethernet adapter, IBMs onboard service processor and IBMs active PCI service. The \utils directory contains scripts, registry files and utility files used to do various things during the unattended install process and are called by the GUIRunOnce section or the CMDLINES.txt.

\$OEM$\$1\Pnpdrivers

Contains new or updated PnP drivers. The user specifies the folder name in the unattend.txt file used during unattended installations. For example, this folder might be named \$OEM$\$1\Pnpdrvs.  For the Thin Client Unattended Install the directory is called DRIVERS.

\$OEM$\drive_letter

Represents the root of a particular volume on the system (e.g., \$OEM$\D represents the D drive) and contains any files that Win2K Setup should copy to this volume during installation

\$OEM$\drive_letter\subfolder

Represents a particular subfolder of the drive (e.g., \$OEM$\D\MyFolder) and contains any files that Win2K Setup should copy to the subfolder during installation. Multiple instances of this type of folder might exist under the \$OEM$\drive_letter folder.

8. 3. 3 Post Install Commands.

The Post install commands are used to execute unattended scripts to install things such as registry entries, applications, tools, resource kits and system tools. (Note: Any scripts or Installations you use must not require any user interaction or it will cause the entire process to halt until the request is answered!) The Post Install Commands portion of the unattended install process has two main places to specify commands that are to be executed during the unattended install process:

1.        CMDLINES.TXT

2.        GUIRUNONCE Section of the Answer file.

CMDLINES.TXT

The cmdlines.txt file is used to specify commands to execute during the registering components portion of setup at the end of the GUI phase of setup.

You can use the cmdlines.txt to execute unattended scripts to install things such as registry entries, applications, tools, resource kits and system tools.  The cmdlines.txt file must reside in the $OEM$ directory of the distribution folders. Each command you want to have executed must contain the exact path and be surrounded by quotes. The cmdlines.txt file for the Thin Client Unattended Install looks like this:

 [Commands]

 "C:\utils\regedit /s c:\utils\win2kreg.reg"

 "C:\diskfix\Q278662.EXE /q"

Remember when adding commands the order you add them in the file because they execute in that order. The cmdlines.txt is the best place to add registry that effect the HKCU registry key because any entry is applied to all HKCU created forward.

GuiRunOnce

The GuiRunOnce section is the place where you specify the commands that are to be executed after Windows 2000 setup has done its reboot after the GUI portion of setup. This section is where you run unattended scripts to install things such as applications, tools, resource kits and system tools. The example above places a .cmd file in the startup group to set the CD-ROM drive letter to L:, creates the D: partition on the un-configured drive.moves the pagefile to D: and completes the unattended install of Citrix Metaframe and Timbale.

Note: This section can contain no more that 6 entries!

[GuiRunOnce]

      "c:\utils\ibmset.cmd"

      "C:\winnt\system32\rundll32.exe setupapi,InstallHinfSection DefaultInstall 129 c:\reboot.inf"   

8. 3. 4 Commands Executed Using  CMDLINES.TXT

CMDLINES.TXT For Thin Client Install

[Commands]

"C:\utils\regedit /s c:\utils\win2kreg.reg"

"C:\diskfix\Q278662.EXE /q"

C:\utils\regedit /s c:\utils\win2kreg.reg

This command uses the regedit tool to import the win2kreg.reg file into the registry. See Appendix C for registry entries added during unattended install.

C:\diskfix\Q278662.EXE /q

This applies the Microsoft Hotfix that fixes problems with disk performance counters.

8. 3. 5 Commands Executed Using GUIRUNONCE

[GUIRUNONCE] section for Thin Client Answer file.

[GuiRunOnce]

      "c:\utils\ibmset.cmd"

      "C:\winnt\system32\rundll32.exe setupapi,InstallHinfSection DefaultInstall 129 c:\reboot.inf" <- Note: This is one line

C:\utils\ibmset.cmd

This command places a .cmd file in the startup group.  The calls a batch file to set the CD-ROM drive letter to L: creates the D: partition on the un-configured drive, moves the pagefile to D: and completes the unattended install of Citrix Metaframe and Timbale

C:\winnt\system32\rundll32.exe setupapi,InstallHinfSection DefaultInstall 129 c:\reboot.inf

This command initiates a file reboot of the system after all the additional components are installed.

8. 3. 6 Registry Entries Added During Unattended Installs

win2kreg.reg

Use this file to add registry entry changes that will be common to any Windows 2000 server installation. The file looks like this:

pagefild.reg

This file configures the system to use a 4GB Page File on the D: Drive. This is what the file looks like:

8. 3. 7 Scripts For Installing Vendor Products During Unattended Installs

C:\utils\reboot.bat

This .bat file reboots the server to allow Windows 2000 finish installing devices and executes commands that set the CD-ROM drive letter to L:, creates the D: partition on the un-configured drive. moves the pagefile to D: and completes the unattended install of Citrix Metaframe and Timbale. This also calls a script to clean up any Utilities used during unattended install:

c:\utils\finish.cmd

This command calls the diskset.cmd, moves the pagefile location to D: and add the admins to the local admin group.

c:\utils\diskset.cmd

This command changes the Cd-Rom drive letter to L: and creates the partition on the un-configured drive creating the D: partition. The Script is as follows:

c:\utils\diskpart /s c:\utils\diskset.txt

Diskpart is the tool from Microsoft to modify disk configurations; the diskset.txt file contains the configuration information.

c:\utils\format1.cmd

This command formats the newly configured partition automatically. The script is as follows:

format d: /fs:ntfs /q<c:\utils\y.bat

c:\utils\regedit /s c:\utils\pagefild.reg

This command uses the regedit tool to import the pagefiled.reg file into the registry. See Appendix C for registry entries added during unattended install.

C:\utils\addadmin.cmd

This adds the "CSX\Domain Admins" to the local admin group

c:\utils\MetaXP.cmd

This command executes the unattended install of Citrix Metaframe

c:\utils\MetaXP.bat

This maps a drive and copies the installation files and then deletes the drive.

call         i:\utils\DSTuner.exe

This command executes the unattended install Timbale

C:\cleanup.cmd

This command cleans up the temporary files that were used during the unattended install: (e.g. Setup files, scripts.)

8. 3. 8 Unattended Install Boot Floppy

This floppy FDISKS the primary partition formats the drive and connects to the distribution share.

Autoexec.bat

a.bat