<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Provisioning AppStacks, applications installed in D: Drive in App Volumes</title>
    <link>https://communities.vmware.com/t5/App-Volumes/Provisioning-AppStacks-applications-installed-in-D-Drive/m-p/2739380#M8051</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;During AppStack provisioning, the VMDK disk is attached as a symbolic link within Windows as part of the existing C drive. Not sure if there is a way to change this behavior to D drive (unless manually doing it).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Recommended to install the application on C drive so that the capture is redirected to the AppStack correctly.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 11 Jun 2018 10:44:36 GMT</pubDate>
    <dc:creator>Lakshman</dc:creator>
    <dc:date>2018-06-11T10:44:36Z</dc:date>
    <item>
      <title>Provisioning AppStacks, applications installed in D: Drive</title>
      <link>https://communities.vmware.com/t5/App-Volumes/Provisioning-AppStacks-applications-installed-in-D-Drive/m-p/2739379#M8050</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;While working with appstacks and a provisioning machine with C: and &lt;img class="lia-deferred-image lia-image-emoji" src="https://communities.vmware.com/html/@22FFD2A936F58A2FA3C1A2EFC87CEC55/emoticons/1f627.png" alt=":anguished_face:" title=":anguished_face:" /&gt; drives, is there a way to have applications installed in the &lt;img class="lia-deferred-image lia-image-emoji" src="https://communities.vmware.com/html/@22FFD2A936F58A2FA3C1A2EFC87CEC55/emoticons/1f627.png" alt=":anguished_face:" title=":anguished_face:" /&gt; drive and being captured correctly for provision?&lt;/P&gt;&lt;P&gt;Or the installation must always be done in C: drive?&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 11 Jun 2018 09:09:31 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/App-Volumes/Provisioning-AppStacks-applications-installed-in-D-Drive/m-p/2739379#M8050</guid>
      <dc:creator>ocomes</dc:creator>
      <dc:date>2018-06-11T09:09:31Z</dc:date>
    </item>
    <item>
      <title>Re: Provisioning AppStacks, applications installed in D: Drive</title>
      <link>https://communities.vmware.com/t5/App-Volumes/Provisioning-AppStacks-applications-installed-in-D-Drive/m-p/2739380#M8051</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;During AppStack provisioning, the VMDK disk is attached as a symbolic link within Windows as part of the existing C drive. Not sure if there is a way to change this behavior to D drive (unless manually doing it).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Recommended to install the application on C drive so that the capture is redirected to the AppStack correctly.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 11 Jun 2018 10:44:36 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/App-Volumes/Provisioning-AppStacks-applications-installed-in-D-Drive/m-p/2739380#M8051</guid>
      <dc:creator>Lakshman</dc:creator>
      <dc:date>2018-06-11T10:44:36Z</dc:date>
    </item>
  </channel>
</rss>

