<?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>michaelcolson.com &#187; vdi</title>
	<atom:link href="http://www.michaelcolson.com/category/vdi/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.michaelcolson.com</link>
	<description></description>
	<lastBuildDate>Sat, 06 Mar 2010 14:54:29 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Disable Multimedia Acceleration in XenDesktop</title>
		<link>http://www.michaelcolson.com/2010/01/23/disable-multimedia-acceleration-in-xendesktop/</link>
		<comments>http://www.michaelcolson.com/2010/01/23/disable-multimedia-acceleration-in-xendesktop/#comments</comments>
		<pubDate>Sun, 24 Jan 2010 00:24:07 +0000</pubDate>
		<dc:creator>michael</dc:creator>
				<category><![CDATA[citrix]]></category>
		<category><![CDATA[vdi]]></category>
		<category><![CDATA[xendesktop]]></category>

		<guid isPermaLink="false">http://www.michaelcolson.com/?p=341</guid>
		<description><![CDATA[I recently came across a multimedia application that uses the Indeo codec for its video components.  While this codec is supported by HDX it is only supported when it runs within the context of Windows Media Player, QuickTime, or one of the other supported video players.  This particular application made use of its own player [...]]]></description>
			<content:encoded><![CDATA[<p>I recently came across a multimedia application that uses the Indeo codec for its video components.  While this codec is supported by HDX it is only supported when it runs within the context of Windows Media Player, QuickTime, or one of the other supported video players.  This particular application made use of its own player which prevented the HDX technologies from enhancing the performance of the videos.</p>
<p><span id="more-341"></span>I should point out that this application had been working well from within the LAN when users were connecting with ICA from a WYSE ThinOS based terminal.  However when connecting from a Windows based workstation using a XenApp or XenDesktop plugin the performance suffered.  My first thought was something was different about the way in which the terminal handled multimedia, SpeedScreen, HDX, etc.</p>
<p>Thinking that I could reproduce this I started down the path of trying older clients until I found one that worked.  Then I could read the release notes and try to figure out exactly what was or wasn&#8217;t needed to make this application perform well.  Aside from taking a trip down memory lane by installing some pretty old clients I was never able to make the application perform well from the Windows based workstation.</p>
<p>Now I know that disabling HDX Multimedia Acceleration is just a check box away in XenApp, the same cannot be said for XenDesktop.  The console for XenDesktop 3 does not have anywhere near the number of configuration items as its close relative XenApp 5 does.</p>
<p>Only in the release notes for an updated Virtual Desktop Agent (<a href="http://support.citrix.com/article/CTX122963">CTX122963</a>) did I finally find my answer.</p>
<p><strong>On the virtual desktop:</strong></p>
<p><code><br />
Set the following DWORD to false</code></p>
<p><code>HKLM\SOFTWARE\Citrix\ICA Client\Engine\Lockdown Profiles\All Regions\Lockdown\Virtual Channels\Multimedia\SpeedScreenMMA</code></p>
<p><strong>On the Desktop Delivery Controller:</strong></p>
<ol>
<li>At a command prompt, cd to C:\Program Files\Citrix\Desktop Delivery Controller.</li>
<li>Execute PorticaSetDefaults.exe /o &lt;filename.xml&gt; to create an editable settings XML file.</li>
<li>Open the xml file created in the previous step and locate the <em>SpeedScreen Multimedia</em> section.</li>
<li>Change the entry for &lt;Enabled&gt;<em>true</em>&lt;/Enabled&gt; (default) of the <em>SpeedScreen Multimedia</em> section to &lt;Enabled&gt;<em>false</em>&lt;/Enabled&gt;.</li>
<li>Save your changes.</li>
<li>Reimport the settings using Porticasetdefaults /i. The settings will take effect the next time a Virtual Desktop Controller registers against this Desktop Delivery Controller.</li>
<li>Repeat the previous step on every Desktop Delivery Controller that conducts VDA registrations.</li>
</ol>
]]></content:encoded>
			<wfw:commentRss>http://www.michaelcolson.com/2010/01/23/disable-multimedia-acceleration-in-xendesktop/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>VDI Connection Brokers</title>
		<link>http://www.michaelcolson.com/2007/10/30/vdi-connection-brokers/</link>
		<comments>http://www.michaelcolson.com/2007/10/30/vdi-connection-brokers/#comments</comments>
		<pubDate>Tue, 30 Oct 2007 18:09:21 +0000</pubDate>
		<dc:creator>michael</dc:creator>
				<category><![CDATA[citrix]]></category>
		<category><![CDATA[vdi]]></category>
		<category><![CDATA[vmware]]></category>

		<guid isPermaLink="false">http://www.michaelcolson.com/?p=76</guid>
		<description><![CDATA[There are only a handful of companies that are currently producing a connection broker product.  If you dig through the documentation from HP, IBM, and others they mention this “optional” magical box that serves as the bridge between the client devices and the hypervisors.  Very few of these vendors who are pushing VDI have come [...]]]></description>
			<content:encoded><![CDATA[<p>There are only a handful of companies that are currently producing a connection broker product.  If you dig through the documentation from HP, IBM, and others they mention this “optional” magical box that serves as the bridge between the client devices and the hypervisors.  Very few of these vendors who are pushing VDI have come forward and presented a solid connection broker component, which I would consider to be one of the most critical components of VDI.  I have listed them here for convenience in evaluating end-to-end VDI solutions.</p>
<p><span id="more-76"></span></p>
<p><strong>ChipPC Virtual Desktop Center<br />
</strong><a href="http://www.chippc.com/management/xcalibur-global/index.asp?p=Overview">http://www.chippc.com/management/xcalibur-global/index.asp?p=Overview</a><br />
ChipPC makes a full computer that fits into a wall socket, while that may be an interesting concept, I have doubts about their ability to work with VMware, Microsoft, and others on creating a solid connection broker product.</p>
<p><strong>Citrix Desktop Broker -&gt; Citrix Desktop Server -&gt; Citrix XenDesktop<br />
</strong><a href="http://www.citrix.com/xendesktop">http://www.citrix.com/xendesktop</a><br />
Citrix has what seems to be all of the pieces needed to produce a connection broker product that is head and shoulders above the competition.  They have a very efficient transport protocol (ICA), they have a solid delivery platform (Web Interface, Secure Gateway, Access Gateway), they have figured out load balancing, session management, and the list goes on and on.  However, they have not yet made their connection broker product, which has now undergone two name changes,  utilize all of their existing technologies.  It still remains to be seen what the new release of the XenDesktop product will bring, although after much hype at the recent iForum 2007, the technical preview of the XenDesktop product has been pushed back to the ambiguous “early November.”  There has also been some feuding lately between Citrix and VMware after the recent purchase of XenSource by Citrix which also rasises concerns about the future compatibility of a Citrix connection broker package with VMware or other manufacturer hypervisors.</p>
<p><strong>Dunes Virtual Desktop Orchestrator (VD-O)<br />
</strong><a href="http://www.dunes.ch">http://www.dunes.ch</a><br />
Dunes Technologies was recently acquired by VMware, which I can only assume means that VMware wants to incorporate the Dunes VDI product suite into their own product lineup.  A quick glance around the existing Dunes website reveals that the Desktop Orchestrator (VD-O) product is missing.  Because of this I don’t know that Dunes or its once upon a time VD-Oproduct</p>
<p><strong>LeoStream Virtual Desktop Connection Broker</strong><br />
<a href="http://www.leostream.com/productVHDC.html">http://www.leostream.com/productVHDC.html</a><br />
Currently the LeoStream product only supports the VMware hypervisor.  While this may not be a problem for existing VMware environments it does pose a problem should an alternative hypervisor emerge as a better platform for VDI.  In terms of feature set and scalability the LeoStream product does seem to be one of the current market leaders.  IBM is also referencing the LeoStream product for their VDI architecture.</p>
<p><strong>Propero workspace<br />
</strong><a href="http://www.propero.com">http://www.propero.com</a><br />
Propero was acquired by VMware in April 2007, and the Propero website now redirectes to a VMware page that doesn’t give much insight into what they plan to do with the acquired Propero technology.</p>
<p><strong>Provision Networks Virtual Access Suite (VAS)</strong><br />
<a href="http://www.provisionnetworks.com/solutions/vas/vas.aspx">http://www.provisionnetworks.com/solutions/vas/vas.aspx</a><br />
Provision Networks seems to be one of the only independent (not associated with a hypervisor technology) connection broker manufacturers that really understands what people want in a connection broker.  They support nearly every hypervisor on the market, they have a web interface, they even support the logical pooling of a mixture of virtual and physical machines.  The one thing that I did find alarming was the frequent mention of a Provision Networks VAS client.  This would mean that existing terminals, computers, and other end points that may already have RDP or even ICA clients would need yet another remote connectivity client.</p>
<p><strong>Zeus Virtual Desktop Connection Broker (ZXTM VDB)</strong><br />
<a href="http://www.zeus.com/news/press_articles/070423-001.html">http://www.zeus.com/news/press_articles/070423-001.html</a><br />
Zeus already being a player in the web server, load balancing, and traffic management markets seemed to be a good fit for entering the VDI connection brokering space.  However other than a several month old press release there is no information about the ZXTM VDB product on their website.  Have they discontinued the product?  Will the technology be incorporated into one of the other ZXTM product lines?  Until there is some more information it is hard to consider them a player in the connection broker market.</p>
<table border="0" cellspacing="0" cellpadding="0">
<tbody>
<tr>
<td>ChipPC Virtual Desktop Center</td>
<td>A serious player?</td>
</tr>
<tr>
<td>Citrix XenDesktop</td>
<td>Available?</td>
</tr>
<tr>
<td>Dunes Virtual Desktop Orchestrator (VD-O)</td>
<td>Acquired by VMware</td>
</tr>
<tr>
<td>LeoStream Virtual Desktop Connection Broker</td>
<td> </td>
</tr>
<tr>
<td>Prospero workspace</td>
<td> </td>
</tr>
<tr>
<td>Provision Network Virtual Access Suite (VAS)</td>
<td> </td>
</tr>
<tr>
<td>Zeus Virtaul Desktop Connection Broker (ZXTM VDB)</td>
<td>Discontinued?</td>
</tr>
</tbody>
</table>
<p>In summary if you are evaluating VDI and need a connection broker solution the only two choices available today are the ones from LeoStream and Provision.  Technically the 1.0 version of the Citrix Desktop Server is also available but it is lacking in its feature set and will likely be discontinued in favor of their new XenDesktop product.<br />
If you can afford to wait then it will probably be worth it to see how Citrix improves upon their XenDesktop product and also what VMware decides to do with their recently acquired technologies.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.michaelcolson.com/2007/10/30/vdi-connection-brokers/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
