<?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: AppStack + Windows 10 + VHD in App Volumes</title>
    <link>https://communities.vmware.com/t5/App-Volumes/AppStack-Windows-10-VHD/m-p/1387636#M851</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Boom!&amp;nbsp; I meant to post earlier! Thank you this was the issue.&amp;nbsp; Writables when dynamic don't need "domain computers" read access.&amp;nbsp; AppStacks are treated differently and do.&amp;nbsp; Now my office 365 is up and running!!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 27 Jan 2016 19:43:26 GMT</pubDate>
    <dc:creator>BungeBash</dc:creator>
    <dc:date>2016-01-27T19:43:26Z</dc:date>
    <item>
      <title>AppStack + Windows 10 + VHD</title>
      <link>https://communities.vmware.com/t5/App-Volumes/AppStack-Windows-10-VHD/m-p/1387632#M847</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Trying out AppStacks, and we deploy with VHD. The VHD for AppStacks do not seem to attach in the Operating system.&amp;nbsp; I can manually mount the VHD and the provisioning process starts and the Pop-ups appear.&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Once finalized and assigned to a user the same issue occurs.&amp;nbsp; App Volume Manager says the AppStack is attached, but it is not attached in the OS until I manually do so.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Looking at the System messages I'm getting:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;TABLE class="dataTable" style="margin: 0 auto; font-size: 12px; color: #4d4d4d; font-family: Helvetica, Arial, sans-serif; background-color: #f5f5f5;"&gt;&lt;TBODY&gt;&lt;TR class="odd" style="border-bottom-width: 1px; border-bottom-color: #e0e0e0; background-color: #fafeff;"&gt;&lt;TD style="padding: 7px 10px;"&gt;Jan 26 2016 03:04PM&lt;/TD&gt;&lt;TD style="padding: 7px 10px;"&gt;&lt;P class="break"&gt;Unable to attach "\\server\vols\cloudvolumes\apps\office365.vhd" (Access is denied. &lt;BR /&gt;(error: 5)&lt;/P&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR class="even" style="border-bottom-width: 1px; border-bottom-color: #e0e0e0; background-color: white;"&gt;&lt;TD style="padding: 7px 10px;"&gt;Jan 26 2016 03:02PM&lt;/TD&gt;&lt;TD style="padding: 7px 10px;"&gt;&lt;P class="break"&gt;Unable to attach "\\&lt;SPAN style="color: #4d4d4d; font-family: Helvetica, Arial, sans-serif; font-size: 12px; background-color: #fafeff;"&gt;server&lt;/SPAN&gt;\vols\cloudvolumes\apps\office365.vhd" (Access is denied. &lt;BR /&gt;(error: 5)&lt;/P&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR class="odd" style="border-bottom-width: 1px; border-bottom-color: #e0e0e0; background-color: #fafeff;"&gt;&lt;TD style="padding: 7px 10px;"&gt;Jan 26 2016 02:58PM&lt;/TD&gt;&lt;TD style="padding: 7px 10px;"&gt;&lt;P class="break"&gt;Unable to attach "\\&lt;SPAN style="color: #4d4d4d; font-family: Helvetica, Arial, sans-serif; font-size: 12px; background-color: #fafeff;"&gt;server&lt;/SPAN&gt;\vols\cloudvolumes\apps\office365.vhd" (Access is denied. &lt;BR /&gt;(error: 5)&lt;/P&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR class="even" style="border-bottom-width: 1px; border-bottom-color: #e0e0e0; background-color: white;"&gt;&lt;TD style="padding: 7px 10px;"&gt;Jan 26 2016 02:35PM&lt;/TD&gt;&lt;TD style="padding: 7px 10px;"&gt;&lt;P class="break"&gt;Unable to attach "\\&lt;SPAN style="color: #4d4d4d; font-family: Helvetica, Arial, sans-serif; font-size: 12px; background-color: #fafeff;"&gt;server&lt;/SPAN&gt;\vols\cloudvolumes\apps\office365.vhd" (Access is denied. &lt;BR /&gt;(error: 5)&lt;/P&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;P&gt;Here's the registry from my machine.&amp;nbsp; Not sure why it's showing Hypervisor as vcenter if the app volume manager defines as VHD.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="regsitry.PNG"&gt;&lt;img src="https://communities.vmware.com/t5/image/serverpage/image-id/63844i7FBB3185FE3B735D/image-size/large?v=v2&amp;amp;px=999" role="button" title="regsitry.PNG" alt="regsitry.PNG" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Running App Volumes 2.10 agent and server.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 26 Jan 2016 21:12:01 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/App-Volumes/AppStack-Windows-10-VHD/m-p/1387632#M847</guid>
      <dc:creator>BungeBash</dc:creator>
      <dc:date>2016-01-26T21:12:01Z</dc:date>
    </item>
    <item>
      <title>Re: AppStack + Windows 10 + VHD</title>
      <link>https://communities.vmware.com/t5/App-Volumes/AppStack-Windows-10-VHD/m-p/1387633#M848</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Are you sure you have the permissions on the share set up correctly? see: &lt;A href="http://pubs.vmware.com/appvolumes-210/topic/App-Volumes-User-Documentation/GUID-D402CC33-F3E1-46A6-9999-F0B3D0FB01B4.html" title="http://pubs.vmware.com/appvolumes-210/topic/App-Volumes-User-Documentation/GUID-D402CC33-F3E1-46A6-9999-F0B3D0FB01B4.html"&gt;Configure VHD In-Guest Storage&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 27 Jan 2016 07:09:29 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/App-Volumes/AppStack-Windows-10-VHD/m-p/1387633#M848</guid>
      <dc:creator>VirtualSven</dc:creator>
      <dc:date>2016-01-27T07:09:29Z</dc:date>
    </item>
    <item>
      <title>Re: AppStack + Windows 10 + VHD</title>
      <link>https://communities.vmware.com/t5/App-Volumes/AppStack-Windows-10-VHD/m-p/1387634#M849</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;My thought also.. Looking at the second screenshot everything seeems to be quite allright (other then suggesting using port 443 for traffic between agent and manager &lt;img id="smileyhappy" class="emoticon emoticon-smileyhappy" src="https://communities.vmware.com/i/smilies/16x16_smiley-happy.png" alt="Smiley Happy" title="Smiley Happy" /&gt;).&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 27 Jan 2016 08:26:35 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/App-Volumes/AppStack-Windows-10-VHD/m-p/1387634#M849</guid>
      <dc:creator>Ray_handels</dc:creator>
      <dc:date>2016-01-27T08:26:35Z</dc:date>
    </item>
    <item>
      <title>Re: AppStack + Windows 10 + VHD</title>
      <link>https://communities.vmware.com/t5/App-Volumes/AppStack-Windows-10-VHD/m-p/1387635#M850</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I'll double check that specific folder.&amp;nbsp; I will say the writable volumes mount just fine.&amp;nbsp; I've tested appstacks with and without writable volumes and was getting the same result.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 27 Jan 2016 12:33:41 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/App-Volumes/AppStack-Windows-10-VHD/m-p/1387635#M850</guid>
      <dc:creator>BungeBash</dc:creator>
      <dc:date>2016-01-27T12:33:41Z</dc:date>
    </item>
    <item>
      <title>Re: AppStack + Windows 10 + VHD</title>
      <link>https://communities.vmware.com/t5/App-Volumes/AppStack-Windows-10-VHD/m-p/1387636#M851</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Boom!&amp;nbsp; I meant to post earlier! Thank you this was the issue.&amp;nbsp; Writables when dynamic don't need "domain computers" read access.&amp;nbsp; AppStacks are treated differently and do.&amp;nbsp; Now my office 365 is up and running!!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 27 Jan 2016 19:43:26 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/App-Volumes/AppStack-Windows-10-VHD/m-p/1387636#M851</guid>
      <dc:creator>BungeBash</dc:creator>
      <dc:date>2016-01-27T19:43:26Z</dc:date>
    </item>
  </channel>
</rss>

