<?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: Writable volumes not loaded in App Volumes</title>
    <link>https://communities.vmware.com/t5/App-Volumes/Writable-volumes-not-loaded/m-p/2875266#M8643</link>
    <description>&lt;P&gt;It was related to a fault App Volume Manager. Once the IP list was adjusted, it worked without an issue&lt;/P&gt;</description>
    <pubDate>Fri, 29 Oct 2021 12:10:51 GMT</pubDate>
    <dc:creator>dpaessens</dc:creator>
    <dc:date>2021-10-29T12:10:51Z</dc:date>
    <item>
      <title>Writable volumes not loaded</title>
      <link>https://communities.vmware.com/t5/App-Volumes/Writable-volumes-not-loaded/m-p/2871425#M8629</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;We have a new environment.&lt;/P&gt;&lt;P&gt;Horizon 2012 with App Volumes 4.&lt;/P&gt;&lt;P&gt;When mounting an application volumes everything works fine. We see the application on the desktop and so on.&lt;/P&gt;&lt;P&gt;But once we assign a writable volumes, it stops. We even got a message about the userprofile sevice failed at sign in.&lt;/P&gt;&lt;P&gt;Until then we see the disk attached; but once a re-login happens, we don't see it any more, and very often the user is logged with a temporary profile (like temp). Any ideas?...&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Daniel&lt;/P&gt;</description>
      <pubDate>Mon, 11 Oct 2021 20:49:00 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/App-Volumes/Writable-volumes-not-loaded/m-p/2871425#M8629</guid>
      <dc:creator>dpaessens</dc:creator>
      <dc:date>2021-10-11T20:49:00Z</dc:date>
    </item>
    <item>
      <title>Re: Writable volumes not loaded</title>
      <link>https://communities.vmware.com/t5/App-Volumes/Writable-volumes-not-loaded/m-p/2875266#M8643</link>
      <description>&lt;P&gt;It was related to a fault App Volume Manager. Once the IP list was adjusted, it worked without an issue&lt;/P&gt;</description>
      <pubDate>Fri, 29 Oct 2021 12:10:51 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/App-Volumes/Writable-volumes-not-loaded/m-p/2875266#M8643</guid>
      <dc:creator>dpaessens</dc:creator>
      <dc:date>2021-10-29T12:10:51Z</dc:date>
    </item>
  </channel>
</rss>

