[THIN] Re: Server Replication

  • From: Anthony_Baldwin@xxxxxxxxx
  • To: thin@xxxxxxxxxxxxx
  • Date: Wed, 2 May 2007 08:38:22 -0400


I never actually done this, but I think Thomas' way sounds pretty slick...



"Angus Macdonald" <Angus.Macdonald@xxxxxxxxxxxxxxxxxxx> 
Sent by: thin-bounce@xxxxxxxxxxxxx
05/02/2007 05:27 AM
Please respond to


[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 
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.
This e-mail is confidential and is intended only for the attention of the 
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. 

Other related posts: