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.
Cloning a XenApp server involves the following:
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.
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:
Important: Do not create an image of a server with an SSL certificate installed; SSL certificates are unique to the hardware.
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.
To clone a server
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.
After creating your farm, install XenApp on another server using Join Farm Setup, and join the farm you created.
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.)
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.
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.
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.
Create an image of this installation using Citrix Provisioning services, Citrix XenServer, or third-party imaging software.
Deploy this image to other servers using the tools provided by the imaging software.
To begin initializing the cloned image, restart the server where the image was deployed.
Using a system preparation utility or the imaging software, assigned the cloned image a new computer name.
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.
In the Windows Services panel