[THIN] Re: Imaging a Citrix server

  • From: "Hutchinson, Alan" <Alan.Hutchinson@xxxxxxxxxxxxxxxxxx>
  • To: <thin@xxxxxxxxxxxxx>
  • Date: Wed, 22 Feb 2006 19:01:40 -0000

I must be missing something (and have been for a while) - I've usually
use the move to workgroup, move to domain that Damon does below figuring
that if MS can't get the new SID issue sorted with this process then
what hope is ther for us?

Am I missing something?

Regards,

Alan. 

-----Original Message-----
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On
Behalf Of Jim Hathaway
Sent: 22 February 2006 17:42
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: Imaging a Citrix server

Your process cleaned up a bit... ;)

1. On server used to create the image I run "chfarm" drop the server to
a temporary access based Farm then stop the IMA service.
2. move the server to a workgroup
3. break the NIC team
4. Set both adapters to use DHCP
5. Delete any remaining profiles.
6. Ghost image up to network using the "-FDSP" switch
        - The FDSP switch when creating the image doesn't matter. Use
this switch when RESTOREING an image. 

To bring the image down I do the following.

1. Drop Ghost Image using the "-FDSP" switch (ghost.exe -FDSP)
2. Run Ghostwalker from the dos shell ghost uses (changes machine name
and SID).
        - Alternative here, load up the OS and run newsid.exe
(http://www.sysinternals.com/Utilities/NewSid.html) changes SID and
machine name.
3. create nic team, Set Ip on team, Reboot
4. join the domain 
5. Start the IMA service, run chfarm again and rejoin the farm
6. Publish desktop to server.

You can image with metaframe installed, you just need to be carefull.
Newsid.exe or ghstwalk.exe are both free sid / name changing utilities.
Ghstwalk comes with ghost, and you'll find it in the program directory,
it's limitation is that new machine names have the same character limit
as the existing name. So machine name = bob, with ghstwalk you can only
rename the server something with 3 charectors, with newsid you don't
have this limitation. 

HTH

J

-----Original Message-----
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On
Behalf Of Damon Edwards
Sent: Wednesday, February 22, 2006 9:02 AM
To: thin@xxxxxxxxxxxxx
Cc: Ron Morvay
Subject: [THIN] Re: Imaging a Citrix server

I create new images often.  I dont have time to use Sysprep every time,
I am not as well versed in the process as I need to be.  I currently
follow the proceedures listed below.

1. On server used to create the image I uninstall citrix.
2. Join a workgroup
3. Change name to generic name
4. break the NIC team
6. Set both adapters to use DHCP
6. run Adaware
7. Delete any remaining profiles.
8. Ghost image up to network using the "-FDSP" switch

To bring the image down I do the following.

1. Drop Ghost Image using the "-FDSP" switch
2. Change Name and create team, Reboot
3. Set Ip on team, Join domain, reboot
4. Install Metaframe
5. Configure connection settings and permissions
6. Publish desktop to server.

I havent had any issues with security using this method, I have been
warned about possible SID conflicts but havent experienced any.  My
drives are always correct.  If I try to image with MF installed I have
all kinds of issues.



---- Ron Morvay <rmorvay@xxxxxxxxx> wrote: 
> Unfortunately, I was not here when these servers were built and there
is
> no documentation, I have checked the servers for a Sysprep folder (I
> always copy the folder to the local from my network) and there is not
> one, so I have to assume that it was not used.  
> 
>  
> 
> Best Regards,
> 
> Ron Morvay
> 
> Technical Support Analyst
> 
> Roman, Inc
> 
> ________________________________
> 
> From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On
> Behalf Of Joe Shonk
> Sent: Wednesday, February 22, 2006 10:00 AM
> To: thin@xxxxxxxxxxxxx
> Subject: [THIN] Re: Imaging a Citrix server
> 
>  
> 
> Or as my second statement states, connect to the registry remotely and
> change the drive letters that way...
> 
>  
> 
> Also, were you using Sysprep?
> 
>  
> 
> Joe
> 
>  
> 
> ________________________________
> 
> From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On
> Behalf Of Michel Roth
> Sent: Wednesday, February 22, 2006 1:16 AM
> To: thin@xxxxxxxxxxxxx
> Subject: [THIN] Re: Imaging a Citrix server
> 
>  
> 
> Ron,
> I have found the -FDSP or similar switches to not work. It this is the
> case, drive letters revert to C: etc. 
> When this happens, my experience is that you can not log in and can
not
> connect remotely to the box.
> 
> Regards,
> Michel Roth
> www.thincomputing.net
> 
> If this is the case, you have to have a repair bootCD/DVD handy with a
> registry editing tool. The you can revert the drive letters to the
> original values. 
> 
> On 2/21/06, Joe Shonk <joe.shonk@xxxxxxxxx> wrote:
> 
> Just use the -FDSP switch...  Worst case, is you'll have to connect to
> the registry remotely and map the drive letters to right disk id.
> 
>  
> 
> Joe
> 
>  
> 
> ________________________________
> 
> From: thin-bounce@xxxxxxxxxxxxx [mailto: thin-bounce@xxxxxxxxxxxxx
> <mailto:thin-bounce@xxxxxxxxxxxxx> ] On Behalf Of Ron Morvay
> Sent: Tuesday, February 21, 2006 9:24 AM
> To: thin@xxxxxxxxxxxxx
> Subject: [THIN] Imaging a Citrix server
> 
>  
> 
> All,
> 
> I have to image our Citrix servers prior to upgrading them; I know
that
> there is an issue with cloning and drive mapping. Can anyone share
there
> success/failures in regards to this issue. I will be using Ghost ver
8.2
> 
>  
> 
> Best Regards,
> 
> Ron Morvay
> 
> Technical Support Analyst
> 
> Roman, Inc
> 
>  
> 
>  
> 
************************************************
For Archives, RSS, to Unsubscribe, Subscribe or 
set Digest or Vacation mode use the below link:
//www.freelists.org/list/thin
************************************************


====================================================================

This e-mail and any files transmitted with it are confidential and are
intended solely for the use of the individual to whom they are
addressed. If you are not the intended recipient or the person
responsible for delivering the e-mail to the intended recipient, be
advised that you have received this e-mail in error and that any use,
dissemination, forwarding, printing or copying of this e-mail is
strictly prohibited. If you have received this e-mail in error, please
immediately advise the sender by reply e-mail and delete the e-mail.  We
appreciate your cooperation.
====================================================================

************************************************
For Archives, RSS, to Unsubscribe, Subscribe or 
set Digest or Vacation mode use the below link:
//www.freelists.org/list/thin
************************************************


************************************************
For Archives, RSS, to Unsubscribe, Subscribe or
set Digest or Vacation mode use the below link:
//www.freelists.org/list/thin
************************************************

Other related posts: