Herramientas de usuario

Herramientas del sitio


Clonación de máquinas

A. Newsid vs. SysPrep

The Machine SID Duplication Myth

Microsoft SysPrep

Herramienta de preparación del sistema para la implementación de Windows Server 2003 Service Pack 2

Microsoft Windows Server 2003 SP1 and Windows Server 2003 SP2 include an updated version of the System Preparation tool (Sysprep.exe) for Windows Server 2003. The Sysprep.exe program is located in the Windows Server 2003 SP1 Deployment Tools .cab file and in the Windows Server 2003 SP2 .cab file. Use this version of the Sysprep.exe program when you deploy Windows Server 2003 SP1 and Windows Server 2003 SP2.

To start the download, click the Download button and then do one of the following, or select another language from Change Language and then click Change.

  • Click Run to start the installation immediately.
  • Click Save to copy the download to your computer for installation at a later time.

B. Clonación de discos en XenServer

C. Esquema general de clonación de una máquina XenApp 5

Cloning XenApp Servers

Cloning a XenApp server involves the following:

  1. Creating a template image from a configured farm server, which means removing the image identity so that the image becomes a template you can reuse (servers have properties that contribute to their unique identity, such as the server name, domain membership, and Security ID (SID)).
  2. Distributing the image to the farm servers.
  3. Recreating the unique identity of each of these servers.
  4. Cloning techniques are used when creating a XenApp farm with provisioning technologies such as Citrix Provisioning services or Symantec Altiris. These techniques are also used with virtualization technologies that host XenApp, such as Citrix XenServer, the Windows Server 2008 Hyper-V feature, and VMWare environments.

Typical candidates for cloning are servers you must repeatedly install. In small or medium farms, you might only need to make cloned images of servers that will host published applications. In large farms, you might also create cloned images for the Create Farm server and infrastructure servers.

When preparing a server for cloning with Citrix Provisioning services, you can include any applications and other settings you want to appear in that image.

Although XenApp is compatible with server cloning, issues resulting from cloning software can cause the operating system or its add-ons to function incorrectly. When cloning XenApp servers, clone one server and check its operation in a test environment before deploying the image to the rest of the farm.

Preparing your Servers for Cloning

Before changing the SID on the server used to access the XenApp Advanced Configuration tool, add one of the following as a Citrix Administrator with read-write privileges:

  • A domain administrator
  • The Local Administrators group
  • A local administrator from a server where the SID will remain static

Important: Do not create an image of a server with an SSL certificate installed; SSL certificates are unique to the hardware.

Configuring Servers after Cloning

Zone settings are not retained when cloning a server. When the Citrix Independent Management Architecture service on the cloned server starts for the first time, the cloned server joins the Setup default zone. When deploying images to servers in multiple zones, assign zone information for each server after the cloning process.

After imaging your servers, join these servers to your farm by using the CHFARM command.

D. Procedimiento de clonación de un servidor XenApp 5


  • a system preparation utility, such as Microsoft Sysprep
  • third-party imaging software
  • 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. Install XenApp

After creating your farm, install XenApp on another server using Join Farm Setup, and join the farm you created.

2. Configure the server

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


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.


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

  • Delete the contents of the Local Host Cache in C:\Program Files (x86)\Citrix\Independent Management Architecture\imalhc.mdb by running dsmaint recreatelhc.
  • 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.
  • 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. WFCName.ini

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 image

Create an image of this installation using Citrix Provisioning services, Citrix XenServer, or third-party imaging software.

9. Deploy

Deploy this image to other servers using the tools provided by the imaging software.

10. Restart

To begin initializing the cloned image, restart the server where the image was deployed.

11. System Preparation

Using a system preparation utility or the imaging software, assigned the cloned image a new computer name.

12. HostName in registry

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. Create unique STA ID in CtxSta.config

  • 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.)
  • Using a text editor, open the CtxSta.config file in C:\Program Files (x86)\Citrix\System32.
  • 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.)
  • Enter the STA ID in the UID field in the CtxSta.config file. (For example, UID=STA020068554D01.)

14. Windows Services panel

In the Windows Services panel

  • Set the Startup type for Citrix Independent Management Architecture and the Citrix MFCOM service to Automatic.
  • Start the Citrix Independent Management Architecture service.
  • Start the Citrix MFCOM service.
  • Start the Citrix WMI service.
citrix/clonacion.txt · Última modificación: 2013/11/21 12:19 por jherrero