<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:clearspace="http://www.jivesoftware.com/xmlns/clearspace/rss" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:opensearch="http://a9.com/-/spec/opensearch/1.1/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>IT@Intel Client Blog</title>
    <link>http://communities.intel.com/openport/blogs/client</link>
    <description>Comment Feed for IT@Intel Client Blog</description>
    <pubDate>Tue, 19 Aug 2008 17:19:41 GMT</pubDate>
    <generator>Clearspace 1.7.0 (http://jivesoftware.com/products/clearspace/)</generator>
    <dc:date>2008-08-19T17:19:41Z</dc:date>
    <item>
      <title>RE:&amp;nbsp;Virtualizing the Client PC – A Proof of Concept</title>
      <link>http://communities.intel.com/openport/blogs/client/2008/07/16/virtualizing-the-client-pc-a-proof-of-concept#comments-2489</link>
      <description>Mike - Sorry for the delayed response.  I was fortunate to have had an extended summer vacation.&lt;br /&gt;
&lt;br /&gt;
Traditional thin client models (e.g. terminal services, VHD) are not really viable for most segments within Intel since we are 70/80% mobile platforms and derive significant productivity from mobile usages given our culture of distributed/virtual teams.  Reliable, robust external connectivity is not ubiquitous enough or cheap enough yet to rely exclusively on network-dependent desktop sessions.  In addition, thin client architecture would be a hugely expensive transition for us in that our data center and network infrastructures are designed for distributed client computing.  Finally, since we already need to invest in centralized manageability and service delivery capabilities to reap many of the benefits you describe, it makes more sense for us to begin our transition to the holy grail of virtual containers through application and OS streaming as these are universally applicable across Intel usages.  VHD would be a niche model for us and we can derive the same benefits from app streaming for mobile usages and OS+app streaming for connected desktops.  Ultimately we are looking to improvements in OS streaming technology, hardware virtualization, and other strategies to move us to a virtual container compute model even for mobile usages.&lt;br /&gt;
&lt;br /&gt;
The security considerations I mentioned were not in regards to data storage; rather the concerns were that the usage we were testing envisioned a managed guest on an unmanaged (perhaps user owned) host.  The idea of an unmanaged host raised concerns among our info sec folks that we are still exploring with them.&lt;br /&gt;
&lt;br /&gt;
Usability challenges came down to performance and the fact that some people did not like the "fusion" of host/guest desktops (they preferred a separate window on the host containing the guest desktop).  In addition, the need to patch everything twice (host and guest) presented some loss of productivity.&lt;br /&gt;
&lt;br /&gt;
We're looking forward to continuing work in this space to address the concerns raised by this PoC.  Even since the conclusion of our testing at the end of last year, we've seen big advancements in the products &amp; capabilities we tested in terms of performance, security, manageability, etc.  We also expect that the acquisitions and convergence of the products in this space will result in simplification and improvements on all of the challenges we've identified.&lt;br /&gt;
&lt;br /&gt;
John</description>
      <pubDate>Tue, 19 Aug 2008 17:19:41 GMT</pubDate>
      <author>John Dunlop</author>
      <guid>http://communities.intel.com/openport/blogs/client/2008/07/16/virtualizing-the-client-pc-a-proof-of-concept#comments-2489</guid>
      <dc:date>2008-08-19T17:19:41Z</dc:date>
    </item>
    <item>
      <title>RE:&amp;nbsp;Decentralized or centralized client computing?</title>
      <link>http://communities.intel.com/openport/blogs/client/2008/01/15/decentralized-or-centralized-client-computing#comments-2097</link>
      <description>I don't see the shift going back to completely dumb terminals at the user end or even dumb terminals with a local hard drive.  &lt;br /&gt;
&lt;br /&gt;
There will always be applications that you will want complete control over.  Banking is the big one but purchased media is another. I think the end user wants to retain control over things they pay for.  &lt;br /&gt;
&lt;br /&gt;
Software as a Service and networked applications always carry with them the worry that you may not be able to access what you have been promised.  Take Google Video for example.  They were selling videos with the assurance that you would always have them available and one day they decided that it was not in their corporate best interest to continue offering them.  If your personal consumer data or corporate infrastructure are controlled by another company you will always be dependent upon them in some way which makes many people nervous.</description>
      <pubDate>Wed, 28 May 2008 19:51:13 GMT</pubDate>
      <author>Jon</author>
      <guid>http://communities.intel.com/openport/blogs/client/2008/01/15/decentralized-or-centralized-client-computing#comments-2097</guid>
      <dc:date>2008-05-28T19:51:13Z</dc:date>
    </item>
    <item>
      <title>RE:&amp;nbsp;Virtual Hosted Desktops: Too much of a good thing?</title>
      <link>http://communities.intel.com/openport/blogs/client/2008/02/28/virtual-hosted-desktops-too-much-of-a-good-thing#comments-1730</link>
      <description>I recently helped with some testing to evaluate VHD and how it faired on a few different server configurations.  The results were interesting.  We found exactly what you mention regarding the appropriate workloads.  Some worked well, some did not. &lt;br /&gt;
&lt;br /&gt;
The really interesting thing for me was the fledgling nature of this type of environment.  Virtualization as a technology and industry has not yet evolved in the area of widely accepted test methodologies.  Given the new possibilities you mention, a lot of people are coming up with their own way to evaluate configurations.  Look up &lt;a class="jive-link-external" href="http://www.intel.com/pressroom/archive/releases/20070417gloc1.htm"&gt;vConsolidate&lt;/a&gt;, &lt;a class="jive-link-external" href="http://www.vmware.com/vmtn/resources/573"&gt;VMMark&lt;/a&gt;, and the pending &lt;a class="jive-link-external" href="http://www.spec.org/specvirtualization/"&gt;SPEC Virtualization Benchmark&lt;/a&gt;.  They are a great start at test and benchmark solutions, but they are effectively testing the same thing; Consolidation of workloads onto a single server.  There are many more ways to implement a virtualized environment where these tests do not evaluate.  More maturity in benchmarking and simply having tools to evaluate configurations is necessary.&lt;br /&gt;
&lt;br /&gt;
Defining a workload for the VHD testing I was involved in was simply our definition of a light vs. heavy user load.  It would be interesting to see what Credit Suisse's workloads were and if they truly mimic actual user use cases (I have no reason to believe they wouldn't.)  We checked with other industry leading companies in this area and they effectively did the same.  As example, VMWare also appears to have drawn a line in the sand for testing their VDI solution in this report: &lt;a class="jive-link-external" href="http://www.vmware.com/pdf/vdi_sizing_vi3.pdf"&gt;http://www.vmware.com/pdf/vdi_sizing_vi3.pdf&lt;/a&gt; &lt;br /&gt;
&lt;br /&gt;
My last comment is to reiterate your 'warning' about finding an appropriate use model.  Virtualized environments are not new, but their popularity is certainly refreshed.  As is with most newly popular things, the buzz may exceed delivery in some areas.</description>
      <pubDate>Thu, 28 Feb 2008 16:47:21 GMT</pubDate>
      <author>nongaw</author>
      <guid>http://communities.intel.com/openport/blogs/client/2008/02/28/virtual-hosted-desktops-too-much-of-a-good-thing#comments-1730</guid>
      <dc:date>2008-02-28T16:47:21Z</dc:date>
    </item>
    <item>
      <title>RE:&amp;nbsp;Could Streaming Apps run faster than traditionally installed?</title>
      <link>http://communities.intel.com/openport/blogs/client/2008/02/14/could-streaming-apps-run-faster-than-traditionally-installed#comments-1654</link>
      <description>great post cathy.    do you have any video's on the testing you can share?</description>
      <pubDate>Thu, 14 Feb 2008 15:13:48 GMT</pubDate>
      <author>josh.hilliker</author>
      <guid>http://communities.intel.com/openport/blogs/client/2008/02/14/could-streaming-apps-run-faster-than-traditionally-installed#comments-1654</guid>
      <dc:date>2008-02-14T15:13:48Z</dc:date>
    </item>
    <item>
      <title>RE:&amp;nbsp;Streaming Impact on the Server and Network</title>
      <link>http://communities.intel.com/openport/blogs/client/2008/01/25/streaming-impact-on-the-server-and-network#comments-1564</link>
      <description>Great job Cathy &amp; team, you have a fantastic report here!  This study really illustrates that each of these emerging compute models have varied results on specific workloads.&lt;br /&gt;
&lt;br /&gt;
A quote from the whitepaper "Virtual Hosted Desktop is better suited for standardized applications with relatively static screens, such as data entry. Streaming more efficiently supports multimedia and other&lt;br /&gt;
dynamic applications, including unified communications."&lt;br /&gt;
&lt;br /&gt;
Jason A. Davidson&lt;br /&gt;
&lt;a class="jive-link-external" href="http://www.intel.com/go/emerge"&gt;http://www.intel.com/go/emerge&lt;/a&gt;</description>
      <pubDate>Fri, 25 Jan 2008 18:37:41 GMT</pubDate>
      <author>Jason A. Davidson</author>
      <guid>http://communities.intel.com/openport/blogs/client/2008/01/25/streaming-impact-on-the-server-and-network#comments-1564</guid>
      <dc:date>2008-01-25T18:37:41Z</dc:date>
    </item>
  </channel>
</rss>

