Hi Michel, Remapped drives aren't that hard to handle once you know that volume drive letters are defined by the DosDevices entries under HKLM\System\MountedDevices. The Citrix article cloning article mentions the IMA and XTE service entries but conveniently forgets that the DCOM and ICA listener ACLs use the user SID including Mchine SID. So basically all the ctx_smauser ACL stuff gets hosed as well as the ctx_configsvr. If you follow the instructions, you'll end up with a broken server. I'm in the process of getting some scripting together using dcomperm and tsconsec to automate the whole post-clone process for PS4, plus a bit of extra scripting to fix a few minor places where PS4 fails to update the new server name (like the XTE/IMA settings and a bit of printer stuff etc). It's unfortunately not nearly as simple as Metaframe XP was. The alternative is using mfcfg to fix the ICA listener ACL (remove unknown SD and add ctx_smauser) and dcomcnfg to fix the ctx_smauser and ctx_configsvr DCOM ACLs. Search the Citrix knowledgebase for ctx_smauser and use the DCOM ACL instructions in the document that describes how to recreate the sma_ctxuser as a guide. If you've got to clone PS4 the easiest path to make sure things work is to uninstall PS4 and reinstall after cloning. Of course if you upgraded to PS4 from XP and you've got 100+ applications installed, then it's it's an easy choice as to whether you rebuild or clone :-( regards, Rick Ulrich Mack Volante Systems ________________________________ From: thin-bounce@xxxxxxxxxxxxx on behalf of Michel Roth Sent: Wed 9/08/2006 19:55 To: thin@xxxxxxxxxxxxx Subject: [THIN] Re: Using a Ghost image to build a new server Hi Angela, I know it's tempting to clone a server however it's not recommended as far as I'm concerned. There's always some setting that you didn't take into account that will cause conflicts. The time saved with cloning will be lost in troubleshooting weird problems afterwards. If you do want to go ahead with it, make sure that your server drives are not remapped, depending on your version of Ghost, this could leave you with an inaccessable server. Citrix also has a document up on server cloning. The docuement pertains to CPS4 but contains enoug info to get you going: http://support.citrix.com/article/CTX107406&searchID=-1 Good luck! Regards, Michel Roth. On 8/9/06, Angela Smith <angela_smith9@xxxxxxxxxxx> wrote: Hi I need to build a new server to add to my Citrix farm. I dont want to manually build this. I have a ghost image of an existing system that I want to use for a new server. All hardware is the same. The Ghost image contains: Windows 2000 Std SP4 Metaframe XP 1.0 Server is in domain Server is in Citrix farm Lots of apps Image is not SYSPREPed. Its a straight Ghost. Applications are not name specific. Do I simply do the following to get this new server up and running: - remove server from domain - rename server to new name - Change SID - change IP Do I need to uninstall/reinstall Metaframe? Will this server be reliable? Ive seen documents that explain how to create a ghost SYSPREP image but not a document for me scenario (ie existing std ghost image) Thanks _________________________________________________________________ Thousands of jobs, millions of opportunities. Begin here! http://a.ninemsn.com.au/b.aspx?URL=http%3A%2F%2Fninemsn%2Eseek%2Ecom%2Eau&_t=757263760&_r=Hotmail_End_Text_Jul06&_m=EXT ************************************************ For Archives, RSS, to Unsubscribe, Subscribe or set Digest or Vacation mode use the below link: //www.freelists.org/list/thin ************************************************ ##################################################################################### This e-mail, including all attachments, may be confidential or privileged. Confidentiality or privilege is not waived or lost because this e-mail has been sent to you in error. If you are not the intended recipient any use, disclosure or copying of this e-mail is prohibited. If you have received it in error please notify the sender immediately by reply e-mail and destroy all copies of this e-mail and any attachments. All liability for direct and indirect loss arising from this e-mail and any attachments is hereby disclaimed to the extent permitted by law. #####################################################################################