<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Vdi on The IT Hollow</title>
    <link>https://theithollow.com/tags/vdi/</link>
    <description>Recent content in Vdi on The IT Hollow</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 08 Oct 2012 14:00:29 +0000</lastBuildDate>
    <atom:link href="https://theithollow.com/tags/vdi/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Microsoft Licensing with VMware View Composer</title>
      <link>https://theithollow.com/2012/10/08/microsoft-licensing-with-vmware-view-composer/</link>
      <pubDate>Mon, 08 Oct 2012 14:00:29 +0000</pubDate>
      <guid>https://theithollow.com/2012/10/08/microsoft-licensing-with-vmware-view-composer/</guid>
      <description>&lt;p&gt;I know the subject of Microsoft licensing makes most administrators want to crawl under a desk and hide when the topic comes up, but it&amp;rsquo;s important to understand a few things if you&amp;rsquo;re going to be standing up a VMware View deployment, or any VDI project.&lt;/p&gt;
&lt;p&gt;During the install of a Windows 7 operating system you of course have to enter a license key.  Once the OS has been installed and booted up, it needs to activate.  Product activation is necessary so that Microsoft can make sure that the software is only installed on the number of PCs that were licensed to use it.  This product activation can be done via a network connection or via telephone.  When you enter your assigned volume license keys during installation you have two types of keys that you can enter:&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
