CTX107406 - Server Cloning with Presentation Server 4.0

Citrix states in their article: CTX107406

CTX107406 - Server Cloning with Presentation Server 4.0

This document was published at: http://support.citrix.com/article/CTX107406

Document ID: CTX107406, Created on: Nov 7, 2005, Updated: Mar 21, 2006

Products: Citrix Presentation Server 4.0 for Microsoft Windows 2003

* This article amends pages 56-59 of CTX107059 – Advanced Concepts Guide

Server Cloning

Server cloning can provide more rapid deployment than a scripted installation. A few steps are required for cloning servers. These steps vary depending on the type of data store used for the farm, and are described in the following sections. Presentation Server is compatible with server cloning, but cloning software can cause the operating system or its add-ons to function incorrectly after being cloned. When using server cloning, it is important to clone one server and test its functionality before deploying the rest of the farm. Also, although Citrix supports server cloning if done by documented procedures, it is considered a best practice to use an automated installation process for building and rebuilding servers so that a clean server build is assured.

Caution: Do not image a server with an SSL certificate installed because SSL certificates are unique to the hardware.

Issues to Consider Before Cloning a Server

Zone settings are not retained when cloning a server. When the Citrix IMA Service on the cloned server starts for the first time, the server joins the default zone. The name of the default zone is the ID of the subnet on which the cloned server resides. When deploying images to servers on multiple subnets, assign zone information for each server after the imaging process completes.

Before changing the Security ID (SID) on the machine used to access the Presentation Server Console, add one of the following user accounts as an administrator with full privileges:

* A domain administrator
* The local administrators group
* A local administrator from a machine where the SID is not being changed
* Note: You must complete the following tasks before re-imaging a server that is already a member of a server farm.
* CTX108361 – Adding a Second STA Overwrites the Existing Entry in the Access Gateway Administration Tool

To prepare a server in a server farm for re-imaging

1. From the Presentation Server Console, remove the list of servers configured to host any applications.

2. Remove the server from the server farm by uninstalling Presentation Server.

3. If the server entry still exists in the Presentation Server Console server list,

right-click the server name and remove it from the server list.

4. Apply the system image and add the server to the server farm.

Important: If a server is not removed from a server farm before a new system image is applied to it, performance problems can result. The Presentation Server Console can display invalid data if the server is returned to the same server farm because the old server’s host record in the data store is applied to the newly imaged server.

If cloning is not an option, you can create custom unattended installation scripts for both the operating system and applications, including Presentation Server.

Note: Removal of the WSID (workstation ID) line from the DSN file is no longer necessary when imaging and deploying Presentation Server.

Rapid Deployment with Microsoft Access or MSDE

When using Microsoft Access or MSDE, you must install the first server in the new server farm that hosts the data store. You can image the second server in the farm for the deployment of additional servers.

To image a server for rapid deployment with Access

1. Install the first server in the farm.

2. Install a second server in the farm with an indirect connection to the data store you created on the first server.

3. With the second server successfully installed and restarted, log on to the console of the second server as a local or domain administrator.

4. On the second server, delete the Wfcname.ini file, if it exists, from the root drive of the server.

5. Stop the Citrix IMA Service using the Services Control Panel. Set the start up type to manual.

6. If Presentation Server, Enterprise Edition components are installed, see the paragraph “Cloning Citrix Presentation Server Enterprise Edition Systems” further in this document.

7. Take the image of the second server and then restart the second server.

8. Deploy the image obtained in Step 7.

Important: It is important that some type of SID generation utility be executed when deploying Windows 2000 Server or Windows Server 2003 images.

To set up the server and verify that it is added

1. Set the SID of the server with your chosen SID generator.

2. Rename the new server with a unique name.

3. Start the Citrix IMA Service and set the service to start automatically.

4. Verify that the server is successfully added to the farm by executing qfarm at a command prompt. If the addition is successful, the newly imaged server appears in the list of servers.

5. Modify the following registry values:-

HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\IMA
change value “ServerHost” to “[newservername]”
HKEY_CLASSES_ROOT\AppID\{BBBF5400-E091-11D8-AD76-005056C00008} – (note: this subkey may be alphanumerically different- you may need to search for Ctx_SmaUser to find the correct sub key)
change value “RunAs” to “ [newservername]\Ctx_SmaUser”

6. Reboot the server.

Rapid Deployment with Microsoft SQL Server, Oracle, or IBM DB2

When using Microsoft SQL Server, Oracle, or IBM DB2 for the server farm’s data store, you can image the first server in the farm and use it to deploy all other servers.

To image a server for rapid deployment with SQL Server, Oracle, or IBM DB2

1. Install the first server in the farm.

2. When the server is successfully restarted, log on to the console as a local or domain administrator.

3. Delete the Wfcname.ini file, if it exists, from the root drive of the server.

4. Stop the Citrix IMA Service and set the start up type to manual.

5. If Presentation Server, Enterprise Edition components are installed, see the paragraph “Cloning Citrix Presentation Server Enterprise Edition Systems” further in this document.

6. Take the image of the server and then restart the server.

7. Deploy the image obtained in Step 6.

Important It is important that some type of SID generation utility be executed when deploying Windows 2000 Server.

To verify that the server is added

1. Set the Security ID of the
server with your chosen SID generator.

2. Rename the new server with a unique name.

3. Manually start the Citrix IMA Service and set the service to start automatically.

4. Verify that the server is successfully added to the farm by executing qfarm at a command prompt on any server in the farm. If the addition is successful, the newly imaged server appears in the list of servers.

5. Modify the following registry values:-

HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\IMA
change value “ServerHost” to “[newservername]”
HKEY_CLASSES_ROOT\AppID\{BBBF5400-E091-11D8-AD76-005056C00008} – (note: this subkey may be alphanumerically different- you may need to search for Ctx_SmaUser to find the correct sub key)
change value “RunAs” to “ [newservername]\Ctx_SmaUser”

6. Reboot the server.

Cloning Citrix Presentation Server Enterprise Edition Systems

If you are running Resource Manager on a server with Presentation Server Enterprise Edition, you must delete the local database used by Resource Manager (named RMLocalDatabase) so that the cloned server does not retain information from the server you are using as the cloning source. The RMLocalDatabase is installed in Citrix Resource Manager\LocalDB in the default installation directory, %Program Files%\Citrix. On the cloned server, the RMLocalDatabase file is recreated automatically when the Citrix IMA Service starts.



Primary links

Custom Search

Who's new

  • japhabept
  • Rullydery
  • eagenorce
  • rittaarier
  • swasseZex

Who's online

There are currently 0 users and 5 guests online.

KrissysCorner.com RuthSwensonLaw.com CreativeLizardProductions.com

DISCLAIMER:

None of this has anything to do with us, someone else is responsible for the entire thing, and we have no idea who or why. We do not know anything about it. It may be alien life forms for all we know: we haven't a clue. You cannot blame us for anything that may result from your visit. That was entirely your own personal choice, made by you of your own volition, and without our knowledge. We do not, after all, have any control over you and cannot by any stretch of the imagination be expected to accept or acknowledge, be it legally or morally, any accountability for decisions made by you on an independent basis, utilizing your own free will, and without our intervention. We are therefore in no way, shape, or form answerable to anyone for any consequences arising from the aforementioned or indeed any other actions, similar or otherwise, because it was not us that did, or did not do anything. It is not even remotely our fault, and we are in no way prepared or willing to accept any liability, not even slightly, ever. We are, in fact completely and utterly blameless, in that it is definitely not our concern, and no blame can possibly be laid at our doorstep, even if we had one, the possession of which we hereby reserve as being entirely our own free choice. The onus is not on us at all, and furthermore, never has been. The entire matter is wholly beyond our control, and completely out of our hands, each of which are washed scrupulously clean of the whole business. We are not accountable for anything at all, and we hereby categorically deny all responsibility for all that has ever, or will ever happen. Our innocence is therefore wholly beyond doubt and absolutely unimpeachable, and so cannot, under even the remotest or unlikeliest circumstances, be brought into question. By clicking either on a link on this site, clicking on a link that leads to this site, or by arriving at this site by natural or supernatural means, you are in effect accepting responsibility for the fact that it is all entirely your own fault, down to the most miniscule detail, and that you are wholly accountable for whatever outcome may arise as a consequence of the aforementioned action or actions insofar as they were undertaken personally by you on an entirely voluntary basis and without any persuasion, coercion or influence from any party or parties other than yourself. Don't come sniveling to us, we are only figments of your imagination. I also agree that if I am ever with a contributor to this website during mealtimes I agree to pay for any super-sizing of their meal, or at least a nice dessert or one of those foo-foo drinks with an umbrella or a monkey. By admitting to have seen the worthless spineless drivel on this website (also known as content)

I Agree Wholeheartedly and Without Reservation to the above. (Except maybe for that part about the monkey.)

All Your Base Are Belong To Us.

Soylent Green Is People!

Never make a bet with a Sicilian when Death is on the Line!

No. Really, I do agree.