Want to win a PS4? Go Premium and enter to win our High-Tech Treats giveaway. Enter to Win

x
?
Solved

Cloning an existing Citrix virtual server

Posted on 2013-01-28
16
Medium Priority
?
1,308 Views
Last Modified: 2013-02-12
Hello,
I am currently in the process of a Citrix XenApp 6.5 farm roll out. I have 2 servers built, and would like to build a total of 8. The 2nd server is just a basic application server (no WI or anything special) and I would like to clone it in VMware to avoid having to build it from scratch and install all those PITA applications. If I clone this server, what needs to be done as far as getting the farm to recognize it as a new citrix server with a different name? Would would be the steps? I am not a top level Citrix engineer, so if you could dumb it down a bit for me, that would help drastically :)

Much appreciated!
0
Comment
Question by:kjs00333
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
16 Comments
 
LVL 124

Accepted Solution

by:
Andrew Hancock (VMware vExpert / EE MVE^2) earned 2000 total points
ID: 38826932
0
 
LVL 26

Expert Comment

by:Tony J
ID: 38827145
This is the officially supported method:

http://support.citrix.com/proddocs/topic/xenapp65-install/ps-image-prep.html

I believe the tools referenced in the URL above may have changed / disappeared.

In actual fact, by the way, you were right to have a second server as you cannot (using Citrix's tools) clone the first server in the farm.
0
 
LVL 12

Expert Comment

by:Daniel Borger
ID: 38831011
once you have te server how you want it use the Citrix Role configuration to generalize for PVS/cloning. this will do everything needed on the Citrix side.

Copy the VM
boot copied vm and run Sysprep
Start copied VM and rename.. once it's booted it will join the XenApp farm.

The important step to note is copying your master and running sysprep. IN 2008 you only get 3 syspreps unless you get fancy with the XML files. by copying the master you don't lose any of your 3 rearms.
0
Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 

Author Comment

by:kjs00333
ID: 38831223
Ok, by following the guides listed, now it thinks my old server I cloned is now the new server name..even though both servers are there.

Example:
Original server: CTX004
Cloned to CTX005

After I cloned the VM, I booted into the newly cloned machine and ran the Citrix Xen App cloning tool. Afterwards I sysprepped the server and rebooted (did not use the generalize option, only OOBE. Generalize would constantly blue screen the server). I joined the server to the domain and the newly cloned server was now showing up in the farm in the server list.. perfect right?!  no.

Now I am unable to connect to my orginal server (CTX004), it just says that the xen app server is not accepting connections via PN agent. I can telnet over port 1494, the Citrix IMA service is running and able to RDP successfully into the server. When I publish the desktop to only go to the NEWLY cloned server (CTX005) it works..

so I'm convinced the newly cloned server name just took the place of the old and left the old server in the server listing visible from the app center.

In short.. CTX004 is now CTX005. Not a clone, just a rename and joined to farm but the old is stuck in there.
0
 

Author Comment

by:kjs00333
ID: 38831253
I am also convinced of this because when I publish the application for CTX005 only, and then configure the ICA client for CTX004, it will still connect pointing me to CTX005. But when I publish the application for CTX004 only, it will not connect at all.

This is what leads me to believe the newly cloned server took the place of the old with just a different name.  
Is there a way to fix this?
0
 

Author Comment

by:kjs00333
ID: 38831491
Ok update:  Over web interface, all servers are working properly. In the app center, it shows me connected to my newly cloned server and everything seems to be fine.  But why is it telling me my xen app servers is not accepting connections over the pn agent?  All 4 of them are not accepting connections now except my first server in the farm. Is there something within the PN Agent site that needs to be changed?
0
 
LVL 12

Expert Comment

by:Daniel Borger
ID: 38831527
New servers added to worker group?
0
 

Author Comment

by:kjs00333
ID: 38831589
I don't have any worker groups defined, but they are all in the same zone. All servers are working via WI, but not working over PN Agent.

Just as a test, im going to reboot my PN Agent site server and see if that may clear some things up.
0
 
LVL 12

Expert Comment

by:Daniel Borger
ID: 38831596
You can also enable the citrix policy to trust XML service requests.
0
 

Author Comment

by:kjs00333
ID: 38831618
The Citrix policy is defined that way. 1 of my servers works when connecting via PN Agent, but the other 3 don't.
0
 
LVL 12

Expert Comment

by:Daniel Borger
ID: 38831627
Stop IMA service and recreate LHC?
0
 

Author Comment

by:kjs00333
ID: 38831713
I am not familiar with that process. How do I go about that?
0
 
LVL 12

Expert Comment

by:Daniel Borger
ID: 38831729
command line:

net stop imaservice
dsmaint recreatelhc
net start imaservice
0
 

Author Comment

by:kjs00333
ID: 38832194
I think this problem more points to the PNAgent site in IIS as everything else seems to be working just fine via Web Interface. My XML port is configured now for 8080 and I also configured the custom ICA connection to use that port as well. Still saying Xen App server is not accepting connections when trying to connect via PNAgent.

Does this sound likely?

Screen shot attached of the Basic settings in IIS for the PNAgent site
PNAgentIIS.jpg
0
 

Author Comment

by:kjs00333
ID: 38832364
Fixed. The issue was session reliability was enabled in the custom ica connection when using xenapp for hosted applications 11.  Any reason why I have to disable this on the custom connections when session reliability is enabled via policy?

When it's enabled, the PN Agent connection gets rejected immediately with "The Xen App server is not accepting connections". When I disable it, it goes through with no issues at all.

I would like session reliability to be enabled if possible.
0
 

Author Closing Comment

by:kjs00333
ID: 38882259
Worked perfectly.
0

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

When rebooting a vCenters 6.0 and try to connect using vSphere Client we get this issue "Invalid URL: The hostname could not parsed." When we get this error we need to do some changes in the vCenter advanced settings to fix the issue.
This article outlines why you need to choose a backup solution that protects your entire environment – including your VMware ESXi and Microsoft Hyper-V virtualization hosts – not just your virtual machines.
Teach the user how to configure vSphere Replication and how to protect and recover VMs Open vSphere Web Client: Verify vsphere Replication is enabled: Enable vSphere Replication for a virtual machine: Verify replicated VM is created: Recover replica…
This tutorial will walk an individual through the steps necessary to enable the VMware\Hyper-V licensed feature of Backup Exec 2012. In addition, how to add a VMware server and configure a backup job. The first step is to acquire the necessary licen…

610 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question