Deployment of Citrix MetaFrame Presentation Server Using Open Manage Remote Install on Dell PowerEdge 1655MC Servers

clutteredreverandData Management

Oct 31, 2013 (3 years and 11 months ago)

140 views






Deployment of Citrix MetaFrame Presentation Server Using Open
Manage Remote Install on Dell PowerEdge 1655MC Servers












Revision 1.0

10
/
09/2003



Mike East

Senior Test Engineer

Citrix Systems, Inc.












2

Table of Contents



Blade Server Architecture

................................
................................
................................
........
3

Rapid Deployment of Citri x MetaFrame Presentation Server

................................
.......................
3

Server Cloning

................................
................................
................................
.....................
4

Pre
-
Cloning Consi derations

................................
................................
.............................

4

To prepare a server i n a MetaFrame server farm for re
-
imaging
................................
........

4

Rapid Deployment with Microsoft Access or MSDE
................................
............................

5

Rapid Deployment with Microsoft SQL Server, Oracle, or IBM DB2

................................
....

5

To image a server for rapi d deployment with SQL Server, Oracle, or IBM DB2

...................

5

Cloning on MetaFrame
PRESENTATION SERVER
e Systems

................................
...............

6

To capture the MetaFrame image to Rapid Instal l

................................
............................

6

To

Deploy the Cloned MetaFrame Image to other Servers

................................
................

7

Post image setup and verification
................................
................................
....................

9

Rip and Replace
................................
................................
................................
...................
9

Scripting confi guration after imaging
................................
................................
...................

10

Appendix A


Tested Components

................................
................................
..........................

11



3

Blade Server Architecture

Blade servers

have int
roduced the concept of modular computing. With blades, administrators no
longer have to man
a
ge multiple systems with unique management tools, hardware, etc. Blade
s
and their corresponding

management software
packages
allow for true modular computing. Dell’
s
blade offering centers around the

Dell
TM

PowerEdge
TM


1655MC

platform
. Administrators can
manage Dell blade servers using the Dell OpenManage
TM


IT Assistant software that ships with
the Dell blade servers. This version of IT Assistant provides complete
support for managing all
Dell blade servers, as well as other Dell servers, desktops, and portables, in an organization's IT
environment.

Systems management has taken a new direction with the arrival of blade servers. No longer is
there only the concept of

a single monolithic server, which comprises
of
one chassis enclosing
one
set of hardware components
.
Now

several
self
-
contained servers, or

blades
,

are contained

within a main chassis. Each blade has its own processor(s), memory, I/O subsystem, set of har
d
drives, operating system (including instrumentation), and other basic server components.

Multiple blades plug into one chassis and share its redundant infrastructure components, such as
power supplies and fans. The chassis also contains two Gigabit Ether
net network switches, which
connect internally to two network interface cards (NICs) embedded on each blade.

Additionally, integrated in the chassis are Dell ERA hardware and firmware. The ERA module
monitors

and manages

all the shared infrastructure comp
onents of the chassis.

The Dell

b
lade

servers

are

an ideal fit for Citrix MetaFrame
Presentation Server

environments.
With “server sprawl” issues
and increasing data center costs, the most
frequently
asked question
has been shifting from “How many

Citrix

M
etaFrame
users can I get on a box?” to “How many
Citrix MetaFrame
users can I get per square foot?”. Blade servers in the

dual processor

market
are traditionally twice a
s

dense as
the Dell PowerEdge 1650/1750
1U dual

capable

servers. This
means 84 servers
can now be placed into a
standard
42U Rack.

Blades allow for higher density
without compromising scalability. Tests in the Citrix
e
Labs have shown that single server
scalability of blade systems versus similar configured rack
-
optimized hardware

are very si
milar

(for more details see
http://www.dell.com/citrix)
.


Blades, along with their management capabilities allow the foundation to act as the core
infrastructure for Citrix MetaFrame
Presentation Server

farms. Blades offer on demand computing
with rip
-
and
-
replace functionality, easy growth, and rapid deployment in the data center.


Rapid Deployment of Citrix MetaFrame Presentation Server


The Dell 1655MC
b
lades are managed through Dell’s

OpenManage
management
software.
Remote Install is used for imaging bla
de servers. A base image can b
e installed on a single
machine.

T
his is

then captured and

stored on the image server
, which

can then be deployed to
all the other like servers in data center.
This allows
for
rapid growth of a Citrix MetaFrame server
farm to
accommodate increased demand and rapid growth.


Once t
he base O
perating System is imaged

and
the imaging software can
perform

unattended
install
s of

MetaFrame with an answer file or

the image can be created with
MetaFrame already
installed


4


Server Cloning

On
e

of the options for rapidly deploying Citrix MetaFrame Presentation Servers is server cloning.
With server cloning, the base images are
created

with MetaFrame Presentation Server already
installed on the system. In order to deploy MetaFrame
using this m
ethod
, a

few manual steps are
r
equired
. These steps vary depending on the type of data store used for the farm,
as

described in
the sections

below
. MetaFrame
Presentation Server

and its Feature Releases are compatible with
server cloning, but cloning softw
are can
have compatibility restrictions
that cause the operating
system or its add
-
ons to function incorrectly after being cloned. When using server cloning, it is
important to clone one server and test its operation before deploying
its image to
the rest
of the
farm.

For this whitepaper, support of cloning has been verified with Dell OpenManage Remote
Install v1.0 and v1.2.

Caution:
Do not attempt to image a server with an SSL certificate installed because SSL
certificates are unique to the hardware.

Pre
-
Cloning Considerations

Zone settings are not retained when cloning a server. When the cloned server starts for the first
time, the MetaFrame
Presentation Server

joins the default zone. The name of the default zone is
the
network
ID of the subnet on which
the cloned server resides. When deploying images to
servers on multiple subnets,
join
each server
to the proper zone
after the imaging process
completes.


Feature Release level settings are not retained when clo
n
ing a server. The pr
oper Feature
Release le
vel
need
s

to be set for each cloned server that is added to the farm. This can easily be
set on all servers using the

Citrix

Management Console.


Prior to changing the Security ID (SID) on the machine used to access the

Citrix

Management
Console, add one
of the following as a Citrix Administrator with read
-
write privileges:

1.

A domain administrator

2.

The Local Administrators group

3.

A local administrator from a machine where the SID is not being changed

Caution:
Do not attempt to use
OpenManage Remote Instal
l

to restore an image of a
MetaFrame server with remapped drives. Remapped drives will partially revert to the original
configuration on the deployed server rendering the server unusable. Servers with remapped
drives may be duplicated using a hardware solu
tion such as
PERC RAID
controllers with
RAID1 drive mirroring.

T
he
following

tasks

must be performed

before re
-
imaging a server that is already a member of a
MetaFrame server farm.

To prepare a server in a MetaFrame server farm for re
-
imaging


1.

From the
Management Console, remove the list of servers configured to host any applications.

2.

Remove the server from the server farm by uninstalling MetaFrame
P
resentation Server
.

3.

If the server entry still exists in the Management Console server list,
r
ight
-
cl
ick and manually
remove the server name from the server list.

4.

Apply the system image and add the server to the server farm.


5

Important:
If a server is not removed from a MetaFrame server farm before a new system
image is applied to it, performance probl
ems can result. The Management Console can display
invalid data if the server is added back to the same server farm. This is because the old
server's host record in the data store is applied to the newly imaged server.

If cloning is not an option, such as
when configuring with remapped drives, create custom
unattended installation scripts for both the operating system and applications, including
MetaFrame
Presentation Server
.

Rapid Deployment with Microsoft Access or MSDE

Manually install the first server i
n the new MetaFrame
Presentation Server

farm that wil
l host the
data store. I
mage the second server in the farm
in order to
deploy additional servers.



To image a server for rapid deployment with Access or MSDE

1.
Follow all necessary steps from the

Citr
ix MetaFrame
XP

for Windows with F
eature

Release 3
Administrator’s Guide

to install the first MetaFrame
Presentation Server

into the farm.

2.

Install a second MetaFrame
Presentation Server

into the farm with an indirect connection to
the data store created

on the first server.

3.

With the second server successfully installed and restarted, log on to the console of the
second server as a local or domain administrator.

4.

On the second server, delete the Wfcname.ini file, if it exists, from the root drive o
f the
server.

5.

Stop the IMA service using the Services Control Panel. Set the startup type to Manual.

6.

If MetaFrame
XP
e components are installed, see
the “Cloning on MetaFrame XPe Systems”
section
below
.

7.

Take the image of the second server and then

restart the second server.

8.

Deploy the image obtained in Step 7.


Rapid Deployment with Microsoft SQL Server, Oracle, or IBM DB2

When using Microsoft SQL Server, Oracle, or IBM DB2 for the server farm
’s

data store, image the
first server in the farm a
nd use it to deploy all other servers.

Note:
Removal of the WSID line from the DSN file is no longer necessary when imaging a
nd
deploying Metaframe Presentation Server

with Feature Release 3.


To image a server for rapid deployment with SQL Server, Oracle
, or IBM DB2

1.

Follow the steps from the
Citrix MetaFrame
XP

for Windows with Feature Release 3
Administrator’s Guide

for installing the first MetaFrame
P
resenation Server

into the farm.

2.

When the server is successfully restarted, log on to the console as
a local or domain
administrator.

3.

Delete the
Wfcname.ini

file, if it exists, from the root drive of the server.

4.

Save the changes to the DSN file.

5.

Stop the IMA service and set the startup option to Manual.

6.

If MetaFrame
XP
e components are installe
d, see the

“Cloning on MetaFrame XPe Systems”
section

below.


6


Cloning on MetaFrame
XP
e Systems


If Resource Management is installed, recreate the RMLocalDatabase prior to making an image of
the server.


To recreate the RMLocalDatabase
:

1.

Delete %Program File
s%
\
Citrix
\
Citrix Resource Manager
\
LocalDB
\
RMLocal Database.*.

2.

The next time the IMA

service is started, it

recreate
s

the database


Cloning and Deployment

Onc
e the pre
-
installation steps are

successfully completed on the source server, it is ready to be
capt
ured to the image server.

To capture the MetaFrame image to Rapid Install

1.

Install the Dell OpenManage R
emote Install Agent on all

of

the b
lade servers.

2.

From the
Dell OpenManage
Remote Install Server, select the source server and choose the
capture option.

Note: In previous versions of Remote Install, the source server first need
s

to be placed in the
Admin state by clicking the Reset option in the System Properties page in order to capture
the image.



7


To Deploy

the Cloned MetaFrame Image to O
ther Servers

1.

P
lace the target server into the Admin state by resetting the system from the
Systems/Properties page.



2.

Select the image created in the previous steps.



8



3.

Next choose the configuration file to apply to the MetaFrame server.


Note
: The configuration file

gives the option to run scripts as part of the configuration.
Since these scripts are run prior to the renaming of the server during the install process,
do not start IMAService as it will put duplicate entries into the data store for the same
server.




4.

Begin the Deployment of the image.


9




Post image setup and verification

1
.

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

2
.

Verify that the server was successfully added to the farm by executing
qfarm

at a command
prompt on a
ny server in the farm. The newly imaged server will appear in the list of servers.



Note
: If the MetaFrame server is
required
to have remapped drives, it is best to run drive
remap after the imaging process is complete due to incompatibilities.


Most ima
ging software suites allow the administrator to define scripts to run on the server after
imaging
is
complete
d
. Feature Release 3 ship
ped with a new
command
-
line
utility called App
Util.
This utility allows for the scripted deployments of Installation Manag
er Pac
kages to MetaFrame
servers. Using

this utility, the administrator can script various different configurations of a
MetaFrame installation depending on the application silo in which it resides. Once the machine is
through imaging, the script will exec
ute and the

specified

IM package will be deployed to the
server.


Rip and Replace

Administrators can designate individual blades for

specific

applications or end users and change
the cha
ssis association of blades
easily.
B
lade
s can move

from one chassis to

another without

10

affecting the ope
ration of other blades. During the

discovery cycle, IT Assistant automatically
detects when a blade has been moved from one chassis to another and accor
dingly moves the
blade's identity

to the appropriate chassis group in
the system tree. Similarly, IT Assistant
dynamically updates its reporting if a blade is
swapped

from one slot to another

within a chassis
.

In

the event of a hardware failure, blades present the
capability
to simply pull out the
server

e
xpe
riencing the fai
lure and replac
e

it with a new server blade. MetaFrame can then be imaged
back down the blade
, using the same process through Remote Install that was used before.
It is
important to note that this is NOT an automated function, the administrator must perfor
m the
same deployment ste
ps as is required to image a new blade
. If the blade server assumes the
same name, it will continue to function in the capacity as the previous
ly

MetaFrame server that
had the same name.

If the image already contains the applicatio
ns that were previous published,
when the server returns to the

Up


state, it will
a
ccept load
-
balanced client connections
immediately without any administrative interaction. If applications are deployed via Installation
Manager, the deployment and publis
hing of the application can be scripted using the AppUtil
command.


AppUtil usage:


AppUtil.exe /q

AppUtil.exe /i <App ID> <Hostname>

AppUtil.exe /u <App ID> <Hostname>


/q

List available published applications.

/i

Add a server to the configured server li
st for the specified published application. If the
selected application publishes an Installation Manager package, running this utility with
this option also installs the packaged application.

/u

Remove a server from the configured server list for the spec
ified published application. If
the application published an Installation Manager package, using this option does not
uninstall the package.


In order to deploy an application, first run
apputil.exe /q

to get the application ID of the
published application

or published Installat
ion Manager package. After the a
pplication ID is
known, run
apputil /i <App ID> <Hostname>

to published the application on the target server.


Note: For servers
that were previously hosting an

indirect data store, the data store need
s

to

be

migrated to the new server following the restoration steps outlined in the
MetaFrame Advanced
Concepts Guide

which can be found at www.citrix.com
.




Scripting C
onfiguration after
I
maging

The MFCOM SDK allows for the scripting of configuration opti
ons through most sc
ripting
languages. Using

the MFCOM SDK, new ap
plications can be published,

data collector preference
level can be set, load
-
evaluators
can be
applied, etc. This allows MetaFrame configuration

changes

to be applied
dynamically
. Please ref
er to the MFCOM SDK documentation for scripting
usage.



11

Appendix A


Tested Components


Hardware:

Dell PowerEdge 1655MC


Software:

Dell Open Manage Remote Install v1.0

Dell Open Manage Remote Install v1.2

Dell Open Manage Remote Install Agent v1.0

Dell Op
en Manage Remote Install Agent v1.0

Citrix MetaFrame
XPe

Feature Release 3