<?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>Virtual Desktop Blog</title>
    <link>http://communities.vmware.com/blogs/virtualdesktop</link>
    <description>A blog about VMware Virtual Desktop Infrastructure</description>
    <pubDate>Thu, 12 Jun 2008 14:59:10 GMT</pubDate>
    <generator>Clearspace 1.10.12 (http://jivesoftware.com/products/clearspace/)</generator>
    <dc:date>2008-06-12T14:59:10Z</dc:date>
    <item>
      <title>More clarity on VECD</title>
      <link>http://communities.vmware.com/blogs/virtualdesktop/2008/06/12/more-clarity-on-vecd</link>
      <description>Despite the VECD licensing model having been availalbe for some time now, including a lot of content that explains how it works. It still seems to be plagued with a shroud of mystery.On a weekly basis it seems I get a report or question from a customer or partner that is struggling to get VECD pricing or a clear explanation on how it works. &lt;br /&gt;
&lt;br /&gt;
Recently Microsoft updated some of the VECD content and it appears they have taken another stab at simplifying what is needed when purchasing VECD. They also cover several uses cases detailing how VECD devices should be licensed in several differant scenarios.&lt;br /&gt;
&lt;p /&gt;
Click here for the new &lt;a class="jive-link-external" href="http://download.microsoft.com/download/d/5/f/d5f15b1e-a8e4-4e2c-b85f-d69d3f132cb1/VECD%20Licensing%20Guide.pdf"&gt;Microsoft VECD Quick Reference Guide&lt;/a&gt;   &lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
In addition, Patrick Rouse over at Provision recently went through the trial and tribulations for everyone and collected all of the VECD SKUs the SKUs Patrick's blog entry can be found here - &lt;a class="jive-link-external" href="http://blogs.inside.quest.com/provision/2008/05/29/microsoft-licensing-for-desktop-virtualization/"&gt;Microsoft Licensing Requirements for Desktop Virtualization&lt;/a&gt;</description>
      <category domain="http://communities.vmware.com/blogs/virtualdesktop/tags">vmware_vdi</category>
      <category domain="http://communities.vmware.com/blogs/virtualdesktop/tags">vecd</category>
      <category domain="http://communities.vmware.com/blogs/virtualdesktop/tags">vmware</category>
      <category domain="http://communities.vmware.com/blogs/virtualdesktop/tags">vi3</category>
      <category domain="http://communities.vmware.com/blogs/virtualdesktop/tags">virtualizaiton</category>
      <category domain="http://communities.vmware.com/blogs/virtualdesktop/tags">virtual_desktops</category>
      <category domain="http://communities.vmware.com/blogs/virtualdesktop/tags">vdm_2.1</category>
      <pubDate>Thu, 12 Jun 2008 15:24:00 GMT</pubDate>
      <author>wponder</author>
      <guid>http://communities.vmware.com/blogs/virtualdesktop/2008/06/12/more-clarity-on-vecd</guid>
      <dc:date>2008-06-12T15:24:00Z</dc:date>
      <clearspace:dateToText>1 year, 5 months ago</clearspace:dateToText>
      <clearspace:replyCount>7</clearspace:replyCount>
      <wfw:comment>http://communities.vmware.com/blogs/virtualdesktop/comment/more-clarity-on-vecd</wfw:comment>
      <wfw:commentRss>http://communities.vmware.com/blogs/virtualdesktop/feeds/comments?blogPostID=1853</wfw:commentRss>
    </item>
    <item>
      <title>VMware VDI - Understanding VECD Licensing</title>
      <link>http://communities.vmware.com/blogs/virtualdesktop/2008/01/18/vmware-vdi-understanding-vecd-licensing</link>
      <description>Recently I read a blog explaining some of the early details of VECD. It described VECD as a hidden cost of VDI. There were also some snippets from a FAQ that was released by VMware, shortly after VECD was announced back in April. The blog makes some valid points, but there was one small detail that was not accurate. Not all VECD options require Software Assurance. Licensing Windows Desktop operating systems for use with VMware VDI falls in the top 10 questions I field on a day to day basis. &lt;br /&gt;
&lt;br /&gt;
The initial white paper released explaining VECD. Created more confusion than clarity. I know I read it many times and each time, I came away with a new interpretation. Fortunately I have some close contacts at Microsoft I was able to sync up with, back in September, at VMworld. VECD was top of the list to get clarified. Who better to hear it from the horses mouth. At VMworld Microsoft was handing out a recently completed license brief that had yet to be published on the Microsoft web site. &lt;br /&gt;
&lt;br /&gt;
This license brief as well as my conversation with the owner at Microsoft, went a long way in clarify things for me. Unfortunately,  I failed to share it had posted when it did. I recommend, Anyone interested in better understanding VECD should read this license brief. It covers VECD for SA and VECD.  The document is titled Licensing Vista for Use with Virtual Machine Technologies and can be found on the &lt;a class="jive-link-external" href="http://www.microsoft.com/licensing/resources/volbrief.mspx"&gt;Volume Licensing Briefs&lt;/a&gt; site.</description>
      <category domain="http://communities.vmware.com/blogs/virtualdesktop/tags">vdi</category>
      <category domain="http://communities.vmware.com/blogs/virtualdesktop/tags">virtual_desktops</category>
      <category domain="http://communities.vmware.com/blogs/virtualdesktop/tags">virtualization</category>
      <category domain="http://communities.vmware.com/blogs/virtualdesktop/tags">vecd</category>
      <category domain="http://communities.vmware.com/blogs/virtualdesktop/tags">esx</category>
      <category domain="http://communities.vmware.com/blogs/virtualdesktop/tags">vi3</category>
      <category domain="http://communities.vmware.com/blogs/virtualdesktop/tags">desktop_virtualization</category>
      <pubDate>Sat, 19 Jan 2008 01:58:00 GMT</pubDate>
      <author>wponder</author>
      <guid>http://communities.vmware.com/blogs/virtualdesktop/2008/01/18/vmware-vdi-understanding-vecd-licensing</guid>
      <dc:date>2008-01-19T01:58:00Z</dc:date>
      <clearspace:dateToText>1 year, 10 months ago</clearspace:dateToText>
      <clearspace:replyCount>9</clearspace:replyCount>
      <wfw:comment>http://communities.vmware.com/blogs/virtualdesktop/comment/vmware-vdi-understanding-vecd-licensing</wfw:comment>
      <wfw:commentRss>http://communities.vmware.com/blogs/virtualdesktop/feeds/comments?blogPostID=1408</wfw:commentRss>
    </item>
  </channel>
</rss>

