Clone Citrix server

Website Visitors:

This task requires a system preparation utility, such as Microsoft Sysprep, third-party imaging software, and a text editor.

This task assumes you want to clone a server for the purpose of hosting published applications and that a relational database (Oracle, SQL Server, or DB2) is hosting the data store. C is the drive on which XenApp is installed.

If you are using Citrix Provisioning services, using the PVS PS Integration Utility can accelerate the integration process by automating some steps.

Important: Citrix strongly recommends that you create initial images on a test farm, not in a production environment. These instructions are for guidance only, and will vary depending on the environment and imaging software.

Caution: The following procedure requires editing the registry. Using Registry Editor can cause serious problems that can require you to reinstall the operating system. Citrix cannot guarantee that problems resulting from incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk.

  1. After creating your farm, install XenApp on another server using Join Farm Setup, and join the farm you created.
  2. Configure the server with settings you want on all servers. (For example, you might want to configure policies, set the data collector election preference to Not Preferred if this image will be used for servers hosting published applications, or add printer drivers.)
  3. Configure XenApp services.
    • Stop the Citrix MFCOM Service, and set its Startup type to Manual.
    • Stop the Citrix Independent Management Architecture, and set its Startup type to Manual.
    • Stop the Citrix WMI Service
  4. Configure the registry.
    1. In the registry on the server, set HKLM\SOFTWARE\Wow6432Node\Citrix\IMA\RUNTIME\PSRequired to 1. This key is in HKLM\SOFTWARE\Citrix\IMA\Runtime\PSRequired on XenApp, 32-bit edition. This forces the server to communicate with the data store so that the local host cache is updated with the new information.
    2. Delete the value for HKLM\SOFTWARE\Wow6432Node\Citrix\IMA\ServerHost. This key is in HKLM\SOFTWARE\Citrix\IMA\ServerHost on XenApp, 32-bit edition.
  5. Delete the contents of database local persistent cache files.
    1. Delete the contents of the Local Host Cache in C:\Program Files (x86)\Citrix\Independent Management Architecture\imalhc.mdb by running dsmaint recreatelhc.
    2. Delete the contents of the Application Streaming Offline database cache in C:\Program Files (x86)\Citrix\Independent Management Architecture\RadeOffline.mdb by running dsmaint recreaterade.
    3. In mixed farm environments, if you are cloning a Presentation Server 4.5 with Feature Pack 1 server, delete the Resource Manager database cache in C:\Program Files (x86)\Citrix\Citrix Resource Manager\LocalDB\RMLocalDatabase.mdb.
  6. Remove the workstation Identification (WSID) from DSN files. Using a text editor, open the files MF20.dsn and RadeOffline.dsn in C:\Program Files (x86)\Citrix\Independent Management Architecture, and delete the line that specifies the WSID.
  7. If you are cloning a system which might have had an older XenApp plug-in installed on it at one time, delete the C:\WFCName.ini file. This file was created by previous versions of the XenApp hosted plug-in.
  8. Create an image of this installation using Citrix Provisioning services, Citrix XenServer, or third-party imaging software.
  9. Deploy this image to other servers using the tools provided by the imaging software.
  10. To begin initializing the cloned image, restart the server where the image was deployed.
  11. Using a system preparation utility or the imaging software, assigned the cloned image a new computer name.
  12. Set HKLM\SOFTWARE\Wow6432Node\Citrix\IMA\Logging\HostName to the new computer name. This key is in HKLM\SOFTWARE\Citrix\IMA\Logging\HostName on XenApp, 32-bit edition.
  13. Edit the CtxSta.config file to create a unique STA ID. (If you do not change this to a unique STA ID, the Secure Gateway and other components cannot uniquely identify the new server.)
    1. Using a text editor, open the CtxSta.config file in C:\Program Files (x86)\Citrix\System32.
    2. Use the MAC address of the new server to which you applied the clone to create the STA ID. Remove any colons or spaces from the MAC address and preface it with “STA.” (For example, the MAC address 02-00-68-55-4D-01 becomes STA020068554D01.)
    3. Enter the STA ID in the UID field in the CtxSta.config file. (For example, UID=STA020068554D01.)
  14. In the Windows Services panel:
    1. Set the Startup type for Citrix Independent Management Architecture and the Citrix MFCOM service to Automatic.
    2. Start the Citrix Independent Management Architecture service.
    3. Start the Citrix MFCOM service.
    4. Start the Citrix WMI service.

Posted in Citrix eDocs

Want to learn more on Citrix Automations and solutions???

Subscribe to get our latest content by email.

If you like our content, please support us by sponsoring on GitHub below: