<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Citrix announces XenApp 6!</title>
	<atom:link href="http://virtualfuture.info/2010/03/citrix-announces-xenapp-6/feed/" rel="self" type="application/rss+xml" />
	<link>http://virtualfuture.info/2010/03/citrix-announces-xenapp-6/</link>
	<description></description>
	<lastBuildDate>Sat, 14 Jan 2012 01:44:33 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1</generator>
	<item>
		<title>By: Adam</title>
		<link>http://virtualfuture.info/2010/03/citrix-announces-xenapp-6/comment-page-1/#comment-3307</link>
		<dc:creator>Adam</dc:creator>
		<pubDate>Thu, 22 Jul 2010 15:04:30 +0000</pubDate>
		<guid isPermaLink="false">http://virtualfuture.info/?p=1678#comment-3307</guid>
		<description>One issue with Citrix XenApp 6 is that, unlike previous versions, it doesn’t support mixed server farms (server clusters that contain more than one XenApp and/or Windows server version in the same farm.).  That leaves 3 possible options for upgrading existing XenApp sites:

Option 1: Upgrade all servers to XenApp 6 all at once (since XenApp 6 only runs on Windows Server 2008 R2).  This is not easy to accomplish in a production environment, which can afford little or no downtime. And if you are hosting an application that isn’t very compatible with 64-bit platforms (Windows Server 2008 R2 is 64-bit only) then you’re truly stuck.

Option 2: Create a secondary farm for the XenApp 6 servers; then distribute the clients between the two using a Web interface.  This introduces 3 challenges: (1) Since XenApp 6 has new management consoles and a whole new way of doing configuration and scripting, each farm will need to be managed separately using a different tool-set.  (2) Determining how to properly distribute the clients between each of the two farms requires close monitoring; otherwise users may not be able to connect to the proper farm.  (3) In all likelihood the combined size of both farms will potentially be much larger than a single farm would have been.

Option 3: Switch to Ericom’s PowerTerm WebConnect.  With a three-tier architecture, PowerTerm WebConnect (certified by Microsoft for Windows Server 2008 R2) can support mixed farms containing Windows Server 2003, 2008, 2008 R2 and future versions of Windows as well.  So it can actually be easier, safer and more cost-effective to not only choose this solution over Citrix’s in the first place, but even to upgrade an existing XenApp farm to PowerTerm WebConnect than to XenApp 6!

You can read more and download a free evaluation at:
http://www.ericom.com/citrix_alternative.asp?URL_ID=708

Adam</description>
		<content:encoded><![CDATA[<p>One issue with Citrix XenApp 6 is that, unlike previous versions, it doesn’t support mixed server farms (server clusters that contain more than one XenApp and/or Windows server version in the same farm.).  That leaves 3 possible options for upgrading existing XenApp sites:</p>
<p>Option 1: Upgrade all servers to XenApp 6 all at once (since XenApp 6 only runs on Windows Server 2008 R2).  This is not easy to accomplish in a production environment, which can afford little or no downtime. And if you are hosting an application that isn’t very compatible with 64-bit platforms (Windows Server 2008 R2 is 64-bit only) then you’re truly stuck.</p>
<p>Option 2: Create a secondary farm for the XenApp 6 servers; then distribute the clients between the two using a Web interface.  This introduces 3 challenges: (1) Since XenApp 6 has new management consoles and a whole new way of doing configuration and scripting, each farm will need to be managed separately using a different tool-set.  (2) Determining how to properly distribute the clients between each of the two farms requires close monitoring; otherwise users may not be able to connect to the proper farm.  (3) In all likelihood the combined size of both farms will potentially be much larger than a single farm would have been.</p>
<p>Option 3: Switch to Ericom’s PowerTerm WebConnect.  With a three-tier architecture, PowerTerm WebConnect (certified by Microsoft for Windows Server 2008 R2) can support mixed farms containing Windows Server 2003, 2008, 2008 R2 and future versions of Windows as well.  So it can actually be easier, safer and more cost-effective to not only choose this solution over Citrix’s in the first place, but even to upgrade an existing XenApp farm to PowerTerm WebConnect than to XenApp 6!</p>
<p>You can read more and download a free evaluation at:<br />
<a href="http://www.ericom.com/citrix_alternative.asp?URL_ID=708" rel="nofollow">http://www.ericom.com/citrix_alternative.asp?URL_ID=708</a></p>
<p>Adam</p>
]]></content:encoded>
	</item>
</channel>
</rss>

