<?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 on VI3.x recommendations</title>
	<atom:link href="http://virtualfuture.info/2008/07/citrix-on-vi3x-recommendations/feed/" rel="self" type="application/rss+xml" />
	<link>http://virtualfuture.info/2008/07/citrix-on-vi3x-recommendations/</link>
	<description></description>
	<lastBuildDate>Thu, 11 Mar 2010 14:53:50 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: VMware:Citrix on VMware Recommendations &#171; ACC</title>
		<link>http://virtualfuture.info/2008/07/citrix-on-vi3x-recommendations/comment-page-1/#comment-654</link>
		<dc:creator>VMware:Citrix on VMware Recommendations &#171; ACC</dc:creator>
		<pubDate>Sun, 21 Dec 2008 22:02:40 +0000</pubDate>
		<guid isPermaLink="false">http://virtualfuture.info/?p=75#comment-654</guid>
		<description>[...] Many Citrix shops do a good deal of work maintaining multiple images – deploying applications in ‘stovepipe’ configurations…  that is to say, multiple small groups of Citrix servers, each dedicated to a specific set of applications.  Frequently, this is due to largely due to application incompatibility.  However, it results in the Citrix admin being required to maintain several different images for the Citrix farm. Even if the shop has standardized on a single Citrix image, they will not be using the company’s standard application deployment methodology…  Terminal Services is too funky with regards to application deployment, and requires much handholding.  Most Citrix shops has compeletely separate processes for packaging applications for a PC versus a Citrix server. VMware ThinApp (http://www.thinstall.com) can be used to image your applications separately from the Citrix image… In fact, an application that has been packaged with ThinApp on Windows 2003 will work on Terminal Services, Citrix, Windows XP, and Vista, eliminating the need to package that application for the different platforms.  Furthermore, ThinApp includes a ‘sandbox’ to prevent applications from conflicting with each other.  You simply place the packaged application on a file share on the network, accessible to the Citrix servers (or PCs, or both), and you are done.  Your users simply execute the application from the shared directory, and they are off and running.  This results in a win-win for the customer – the ability to package an application once, and use it for either a PC environment or a Citrix environment. Bron: http://virtualfuture.info/2008/07/citrix-on-vi3x-recommendations/ [...]</description>
		<content:encoded><![CDATA[<p>[...] Many Citrix shops do a good deal of work maintaining multiple images – deploying applications in ‘stovepipe’ configurations…  that is to say, multiple small groups of Citrix servers, each dedicated to a specific set of applications.  Frequently, this is due to largely due to application incompatibility.  However, it results in the Citrix admin being required to maintain several different images for the Citrix farm. Even if the shop has standardized on a single Citrix image, they will not be using the company’s standard application deployment methodology…  Terminal Services is too funky with regards to application deployment, and requires much handholding.  Most Citrix shops has compeletely separate processes for packaging applications for a PC versus a Citrix server. VMware ThinApp (<a href="http://www.thinstall.com" rel="nofollow" onclick="pageTracker._trackPageview('/outgoing/www.thinstall.com?referer=');">http://www.thinstall.com</a>) can be used to image your applications separately from the Citrix image… In fact, an application that has been packaged with ThinApp on Windows 2003 will work on Terminal Services, Citrix, Windows XP, and Vista, eliminating the need to package that application for the different platforms.  Furthermore, ThinApp includes a ‘sandbox’ to prevent applications from conflicting with each other.  You simply place the packaged application on a file share on the network, accessible to the Citrix servers (or PCs, or both), and you are done.  Your users simply execute the application from the shared directory, and they are off and running.  This results in a win-win for the customer – the ability to package an application once, and use it for either a PC environment or a Citrix environment. Bron: <a href="http://virtualfuture.info/2008/07/citrix-on-vi3x-recommendations/" rel="nofollow">http://virtualfuture.info/2008/07/citrix-on-vi3x-recommendations/</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Recent Links Tagged With "citrix" - JabberTags</title>
		<link>http://virtualfuture.info/2008/07/citrix-on-vi3x-recommendations/comment-page-1/#comment-530</link>
		<dc:creator>Recent Links Tagged With "citrix" - JabberTags</dc:creator>
		<pubDate>Thu, 23 Oct 2008 08:04:03 +0000</pubDate>
		<guid isPermaLink="false">http://virtualfuture.info/?p=75#comment-530</guid>
		<description>[...] public links &gt;&gt; citrix   Citrix on VI3.x recommendations Saved by hulkimania on Wed 22-10-2008   The Next 5000 Days of the Web Saved by Lurktopia on Sat [...]</description>
		<content:encoded><![CDATA[<p>[...] public links &gt;&gt; citrix   Citrix on VI3.x recommendations Saved by hulkimania on Wed 22-10-2008   The Next 5000 Days of the Web Saved by Lurktopia on Sat [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matthijs Haverink</title>
		<link>http://virtualfuture.info/2008/07/citrix-on-vi3x-recommendations/comment-page-1/#comment-174</link>
		<dc:creator>Matthijs Haverink</dc:creator>
		<pubDate>Thu, 17 Jul 2008 11:08:14 +0000</pubDate>
		<guid isPermaLink="false">http://virtualfuture.info/?p=75#comment-174</guid>
		<description>Hi Dollia,

Assigning 2 vCPU&#039;s isn&#039;t always a guarantee for better performance. You should always analyze that per server installation. At the customer site where I am now we found out that a 1 vCPU VM with SharePoint 2007 performs better then a 2 vCPU VM with SharePoint 2007!</description>
		<content:encoded><![CDATA[<p>Hi Dollia,</p>
<p>Assigning 2 vCPU&#8217;s isn&#8217;t always a guarantee for better performance. You should always analyze that per server installation. At the customer site where I am now we found out that a 1 vCPU VM with SharePoint 2007 performs better then a 2 vCPU VM with SharePoint 2007!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: J House Consulting / Citrix on VI3.x Recommendations</title>
		<link>http://virtualfuture.info/2008/07/citrix-on-vi3x-recommendations/comment-page-1/#comment-171</link>
		<dc:creator>J House Consulting / Citrix on VI3.x Recommendations</dc:creator>
		<pubDate>Sun, 13 Jul 2008 13:24:30 +0000</pubDate>
		<guid isPermaLink="false">http://virtualfuture.info/?p=75#comment-171</guid>
		<description>[...] a pretty good article posted by Sven Huisman on behalf of Verron Martina from VMware: http://virtualfuture.info/2008/07/citrix-on-vi3x-recommendations/   Post a comment &#8212; Trackback URI RSS 2.0 feed for these comments This entry (permalink) was [...]</description>
		<content:encoded><![CDATA[<p>[...] a pretty good article posted by Sven Huisman on behalf of Verron Martina from VMware: <a href="http://virtualfuture.info/2008/07/citrix-on-vi3x-recommendations/" rel="nofollow">http://virtualfuture.info/2008/07/citrix-on-vi3x-recommendations/</a>   Post a comment &mdash; Trackback URI RSS 2.0 feed for these comments This entry (permalink) was [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dollia Sheombar</title>
		<link>http://virtualfuture.info/2008/07/citrix-on-vi3x-recommendations/comment-page-1/#comment-169</link>
		<dc:creator>Dollia Sheombar</dc:creator>
		<pubDate>Thu, 10 Jul 2008 06:41:15 +0000</pubDate>
		<guid isPermaLink="false">http://virtualfuture.info/?p=75#comment-169</guid>
		<description>Nice article Sven,
But why allocate only one vCPU per VM. What is going to happen with that VM if a certain app or process is going to hog the cpu. I always use a minimum of two cpu&#039;s.

Regards,

Dollia Sheombar</description>
		<content:encoded><![CDATA[<p>Nice article Sven,<br />
But why allocate only one vCPU per VM. What is going to happen with that VM if a certain app or process is going to hog the cpu. I always use a minimum of two cpu&#8217;s.</p>
<p>Regards,</p>
<p>Dollia Sheombar</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: VMware: Citrix on VMware Recommendations &#171; ICT-Freak</title>
		<link>http://virtualfuture.info/2008/07/citrix-on-vi3x-recommendations/comment-page-1/#comment-147</link>
		<dc:creator>VMware: Citrix on VMware Recommendations &#171; ICT-Freak</dc:creator>
		<pubDate>Wed, 02 Jul 2008 09:14:54 +0000</pubDate>
		<guid isPermaLink="false">http://virtualfuture.info/?p=75#comment-147</guid>
		<description>[...] Huisman heeft weer een goede post geplaastst op zijn weblog. Verron Martina from VMware dropped me an e-mail with a lot of recommendations for running Citrix [...]

[WORDPRESS HASHCASH] The comment&#039;s server IP (72.232.131.31) doesn&#039;t match the comment&#039;s URL host IP (72.232.101.42) and so is spam.</description>
		<content:encoded><![CDATA[<p>[...] Huisman heeft weer een goede post geplaastst op zijn weblog. Verron Martina from VMware dropped me an e-mail with a lot of recommendations for running Citrix [...]</p>
<p>[WORDPRESS HASHCASH] The comment&#8217;s server IP (72.232.131.31) doesn&#8217;t match the comment&#8217;s URL host IP (72.232.101.42) and so is spam.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Citrix XenApp in combinatie met servervirtualisatie &#171; EarlyBert</title>
		<link>http://virtualfuture.info/2008/07/citrix-on-vi3x-recommendations/comment-page-1/#comment-146</link>
		<dc:creator>Citrix XenApp in combinatie met servervirtualisatie &#171; EarlyBert</dc:creator>
		<pubDate>Tue, 01 Jul 2008 20:31:37 +0000</pubDate>
		<guid isPermaLink="false">http://virtualfuture.info/?p=75#comment-146</guid>
		<description>[...] toch liever de hypervisor van VMware gebruiken in plaats van XenServer, dan heeft Sven Huisman een mooi overzicht gemaakt van aanbevelingen en best practices. Omdat daarbij gebruik gemaakt wordt van multi-core [...]

[WORDPRESS HASHCASH] The comment&#039;s server IP (72.233.69.64) doesn&#039;t match the comment&#039;s URL host IP (76.74.254.125) and so is spam.</description>
		<content:encoded><![CDATA[<p>[...] toch liever de hypervisor van VMware gebruiken in plaats van XenServer, dan heeft Sven Huisman een mooi overzicht gemaakt van aanbevelingen en best practices. Omdat daarbij gebruik gemaakt wordt van multi-core [...]</p>
<p>[WORDPRESS HASHCASH] The comment&#8217;s server IP (72.233.69.64) doesn&#8217;t match the comment&#8217;s URL host IP (76.74.254.125) and so is spam.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matthijs Haverink</title>
		<link>http://virtualfuture.info/2008/07/citrix-on-vi3x-recommendations/comment-page-1/#comment-145</link>
		<dc:creator>Matthijs Haverink</dc:creator>
		<pubDate>Tue, 01 Jul 2008 13:29:12 +0000</pubDate>
		<guid isPermaLink="false">http://virtualfuture.info/?p=75#comment-145</guid>
		<description>Nice stuff Sven, thanx for sharing !</description>
		<content:encoded><![CDATA[<p>Nice stuff Sven, thanx for sharing !</p>
]]></content:encoded>
	</item>
</channel>
</rss>
