Our approach to cloning our servers in our farm is similiar. We are
running HP 360's mirrored. I have including our cloning instructions
1. First disconnect server from network
2. Shut down and pull drive
3. Reboo
Pete Kuhn
Technical Staff Specialist MCNE, MCSE
Technical Deployment Team
University of Maryland Medical System
22 S. Greene St.
Mail Stop PP-33
Baltimore, MD 21201-1590
410-328-0381
"I haven't got the slightest idea how to change people, but still
I keep a long list of prospective candidates just in case I
should ever figure it out." -- David Sedaris
t > Select F2 to fail drives that are not responding.
4. Change password for Administrative account :
5. Change to Workgroup : Clone; change name : clone_template
6. Network properties : Configure TCP/IP settings
7. Manage > Services > change IMA to manual and stop service
8. Start > Run > M:\Program Files\Citrix\IMA\mf20.dsn edit, WSID :
"change to new computer name"
Clone
9. Start > Run > M:\Newsid\newsid.exe - Random
10. Shut down and pull drive
11. Run the following commands in this order
13. Reboot and put on network
There are other instructions that I removed. They were mostly recreating
the anonymous accounts. I scripted the process. The instructions referenced
changing some script statements to the new computer name. Between steps 2
and 3 you are installing a new drive in the machine you pulled the drive
from. In the new machine you are installing the pulled drive and booting
(while it is off the network of course).
>>> <Anthony_Baldwin@xxxxxxxxx> 5/2/2007 08:38 >>>
Nick,
I never actually done this, but I think Thomas' way sounds pretty slick...
http://www.thomaskoetzing.de/index.php?option=com_content&task=view&id=207&Itemid=262
Tony
"Angus Macdonald" <Angus.Macdonald@xxxxxxxxxxxxxxxxxxx>
Sent by: thin-bounce@xxxxxxxxxxxxx
05/02/2007 05:27 AM
Please respond to
thin@xxxxxxxxxxxxx
To
<thin@xxxxxxxxxxxxx>
cc
Subject
[THIN] Re: Server Replication
For our Citrix deployment we always build a first server and test it to
death. Once we're happy, we either use RAID mirroring to replicate the
contents of the hard drive to the other servers (break the mirror, move
one drive to another server, use that to rebuild its' own RAID array,
rinse and repeat) or, thanks to some troublesomely intelligent RAID
controllers on recent Dell servers, use Symantec Ghost to take an image of
the hard drive and restore it to the new servers.
Once the image is restored, take the server off the network before
starting it up. Login and run a SID-changing utility (like newsid) before
renaming the server, giving it a new IP address and tweaking the Citrix
DSN.
That's always worked for us.
-----Original Message-----
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx]On
Behalf Of Nick Smith
Sent: 02 May 2007 10:11
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Server Replication
A general question. Our ?farm? has finally reached the point where we will
need to be having identical servers (Yes I know relying on single servers
is bad practice, but cost constraints are high) in load-balanced mode.
This is plain Terminal Server 2003. I?m more or less on top of the
session-sharing elements, but would appreciate opinions on the best
methodologies/software to replicate current servers, and/or ensure new
builds are identical.
Any advice greatly welcomed.
Nick
This e-mail is confidential and is intended only for the attention of the
addressee.
If you are not the intended recipient, this e-mail should not be disclosed
to any other person.
Please notify the sender immediately and delete this e-mail from your
computer system.
Although this e-mail has been checked for viruses and other defects,
no responsibility can be accepted for any loss or damage arising from its
receipt or use.
