<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>eGroup &#187; csg</title>
	<atom:link href="http://www.egroup-us.com/tag/csg/feed" rel="self" type="application/rss+xml" />
	<link>http://www.egroup-us.com</link>
	<description>Technology Solutions for Serious Competitors</description>
	<lastBuildDate>Thu, 16 May 2013 18:43:44 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
		<item>
		<title>CITRIX DESIGN BEST PRACTICES</title>
		<link>http://www.egroup-us.com/2009/03/citrix-design-best-practices/</link>
		<comments>http://www.egroup-us.com/2009/03/citrix-design-best-practices/#comments</comments>
		<pubDate>Mon, 23 Mar 2009 15:54:30 +0000</pubDate>
		<dc:creator>Staff</dc:creator>
				<category><![CDATA[Blog On]]></category>
		<category><![CDATA[Citrix]]></category>
		<category><![CDATA[csg]]></category>
		<category><![CDATA[ESX]]></category>
		<category><![CDATA[nlb]]></category>
		<category><![CDATA[presentation server]]></category>
		<category><![CDATA[secure gateway]]></category>
		<category><![CDATA[virtualization]]></category>
		<category><![CDATA[Web Interface]]></category>
		<category><![CDATA[wi]]></category>
		<category><![CDATA[xenapp]]></category>

		<guid isPermaLink="false">http://blogs.eGroup-us.com/?p=495</guid>
		<description><![CDATA[<p>Good Citrix design in its most basic form is simple.  The number one rule is to remove all single points of failure.  This means there should be redundant servers for everything critical.  I consider the Secure Gateway, Web Interface, and XenApp servers critical.  Those are just for Citrix.  The other things to consider are redundant domain [...]</p><p>The post <a href="http://www.egroup-us.com/2009/03/citrix-design-best-practices/">CITRIX DESIGN BEST PRACTICES</a> appeared first on <a href="http://www.egroup-us.com">eGroup</a>.</p>]]></description>
				<content:encoded><![CDATA[<p>Good Citrix design in its most basic form is simple.  The number one rule is to remove all single points of failure.  This means there should be redundant servers for everything critical.  I consider the Secure Gateway, Web Interface, and XenApp servers critical.  Those are just for Citrix.  The other things to consider are redundant domain controllers, Clustered SQL servers, and a file server that is already designed for HA.  The most cost effective way of pulling this off is to use virtualization technoligies like ESX.  My typical small/medium business setup to to virtualize two XenApp servers, and two WI/CSG servers.  The WI/CSG is setup using NLB whereas the XenApp servers just use the standard Load Balancing built into Citrix.  Your SQL server should replicate the DS, there are good artilces on how to do this out there.  That&#8217;s about it, just about any design I do starts with this and is customized for the customer requirements.</p>
<p>The post <a href="http://www.egroup-us.com/2009/03/citrix-design-best-practices/">CITRIX DESIGN BEST PRACTICES</a> appeared first on <a href="http://www.egroup-us.com">eGroup</a>.</p>]]></content:encoded>
			<wfw:commentRss>http://www.egroup-us.com/2009/03/citrix-design-best-practices/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
<!-- WP Super Cache is installed but broken. The path to wp-cache-phase1.php in wp-content/advanced-cache.php must be fixed! -->