<?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: Manual Upgrade of Writable Volume in App Volumes</title>
    <link>https://communities.vmware.com/t5/App-Volumes/Manual-Upgrade-of-Writable-Volume/m-p/2279044#M1544</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You can pull the VHD out of the ISO under /Hypervisor/In-Guest VHD/yadda yadda, then open it with 7ZIP to pull the wirtable files.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'll run a compare on the VMDK and VHD files (of the same version) and see what happens.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks again!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 03 Jan 2018 14:56:33 GMT</pubDate>
    <dc:creator>fdrietatns</dc:creator>
    <dc:date>2018-01-03T14:56:33Z</dc:date>
    <item>
      <title>Manual Upgrade of Writable Volume</title>
      <link>https://communities.vmware.com/t5/App-Volumes/Manual-Upgrade-of-Writable-Volume/m-p/2279037#M1537</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I am trying to get some instructions.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Current WV 2.11 and I want to test upgrading to 2.12.0.&amp;nbsp; Any idea how I can update just a single WV before I update the rest? &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 12 May 2017 23:22:28 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/App-Volumes/Manual-Upgrade-of-Writable-Volume/m-p/2279037#M1537</guid>
      <dc:creator>michael_borland</dc:creator>
      <dc:date>2017-05-12T23:22:28Z</dc:date>
    </item>
    <item>
      <title>Re: Manual Upgrade of Writable Volume</title>
      <link>https://communities.vmware.com/t5/App-Volumes/Manual-Upgrade-of-Writable-Volume/m-p/2279038#M1538</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;There is no need to upgrade the Writable volume if you upgrade the agent. I would say test with 1 writables after you upgraded the agent and check to see if it works.&lt;/P&gt;&lt;P&gt;Make sure to upgrade to 2.12.1 though, otherwise you could end up with writables that have issues with printers not being attached.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you do want to upgrade for example the snapvol.cfg you can attach it to a basic machines that does not have the Appvolumes agent installed, give the writable a drive letter and edit it from there.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 15 May 2017 06:45:36 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/App-Volumes/Manual-Upgrade-of-Writable-Volume/m-p/2279038#M1538</guid>
      <dc:creator>Ray_handels</dc:creator>
      <dc:date>2017-05-15T06:45:36Z</dc:date>
    </item>
    <item>
      <title>Re: Manual Upgrade of Writable Volume</title>
      <link>https://communities.vmware.com/t5/App-Volumes/Manual-Upgrade-of-Writable-Volume/m-p/2279039#M1539</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks.&amp;nbsp; Actually VMware Support called me back today and gave me the instructions.&amp;nbsp; They described mounting the writable template on a non AVM agent machine (similar to your advice), pull the 6 files off that can be used to upgrade the provisioned WVs.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Funny you say 2.12.1, since that's the problem we've been dealing with recently.&amp;nbsp; The 2.12.1 agent caused massive problems with Office 2016 email attachments (MSI install on master image with KMS) and office doc downloads from the internet.&amp;nbsp; They were being blocked. Somehow the agent was interfering with the Windows Attachment Manager and caused the OS to think they were unsafe.&amp;nbsp; Log off and back on to a pool running 2.12.0 and everything worked fine. Totally weird and frustrating.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We ended up staying with 2.12.1 on the server, but reverted to 2.12.0 agent and WV with 4 exclusions added to the WV sysvol.cfg to fix the printers.&amp;nbsp; All is working fine now, even with AppStacks.&amp;nbsp; VMware claims to fully support this configuration, even on 7.1 (which is our next fun adventure).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Appreciate the reply Ray.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;..mb&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 16 May 2017 23:35:36 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/App-Volumes/Manual-Upgrade-of-Writable-Volume/m-p/2279039#M1539</guid>
      <dc:creator>michael_borland</dc:creator>
      <dc:date>2017-05-16T23:35:36Z</dc:date>
    </item>
    <item>
      <title>Re: Manual Upgrade of Writable Volume</title>
      <link>https://communities.vmware.com/t5/App-Volumes/Manual-Upgrade-of-Writable-Volume/m-p/2279040#M1540</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;So just pull the files off the template and put it in a zip then upload that zip to the writables from the AVM? &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 02 Jan 2018 17:55:27 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/App-Volumes/Manual-Upgrade-of-Writable-Volume/m-p/2279040#M1540</guid>
      <dc:creator>fdrietatns</dc:creator>
      <dc:date>2018-01-02T17:55:27Z</dc:date>
    </item>
    <item>
      <title>Re: Manual Upgrade of Writable Volume</title>
      <link>https://communities.vmware.com/t5/App-Volumes/Manual-Upgrade-of-Writable-Volume/m-p/2279041#M1541</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;If you want to automatically update the writables, yes. But do keep in mind that it will upgrade all writables. It will do this during attachment of the writable. So if a writable is never attached after you upload the zip file into the manager that writable will not be updated.&lt;/P&gt;&lt;P&gt;In this case it was only to change 1 writable manually. I would still suggest attaching it to a machine without the Appvol agent and manually edit it there,&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 03 Jan 2018 07:26:04 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/App-Volumes/Manual-Upgrade-of-Writable-Volume/m-p/2279041#M1541</guid>
      <dc:creator>Ray_handels</dc:creator>
      <dc:date>2018-01-03T07:26:04Z</dc:date>
    </item>
    <item>
      <title>Re: Manual Upgrade of Writable Volume</title>
      <link>https://communities.vmware.com/t5/App-Volumes/Manual-Upgrade-of-Writable-Volume/m-p/2279042#M1542</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks Ray!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I need to do both, one to update/test my custom template and the other to deploy to existing volumes.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Just not all too familiar with the zip process.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As an aside, is the VHD writable files (other than [system]) the same as the vmdk based? I don't particularly want to install the manager to get the template files before the scheduled upgrade. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 03 Jan 2018 14:44:18 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/App-Volumes/Manual-Upgrade-of-Writable-Volume/m-p/2279042#M1542</guid>
      <dc:creator>fdrietatns</dc:creator>
      <dc:date>2018-01-03T14:44:18Z</dc:date>
    </item>
    <item>
      <title>Re: Manual Upgrade of Writable Volume</title>
      <link>https://communities.vmware.com/t5/App-Volumes/Manual-Upgrade-of-Writable-Volume/m-p/2279043#M1543</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;For as far as I know, no. You would need to copy those files there and thus upgrade the manager. I don;t think you could edit the vhd file.&lt;/P&gt;&lt;P&gt;On the other hand you only need the snapvol.cfg, I would say give it a try, it might just work. Make sure to only copy the snapvol.cfg though, just leave the other files.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;EDIT!&lt;/P&gt;&lt;P&gt;Yes you can get the files from that vhd. Just attach the vhd within the manager, give it a drive letter and your good to go.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 03 Jan 2018 14:48:59 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/App-Volumes/Manual-Upgrade-of-Writable-Volume/m-p/2279043#M1543</guid>
      <dc:creator>Ray_handels</dc:creator>
      <dc:date>2018-01-03T14:48:59Z</dc:date>
    </item>
    <item>
      <title>Re: Manual Upgrade of Writable Volume</title>
      <link>https://communities.vmware.com/t5/App-Volumes/Manual-Upgrade-of-Writable-Volume/m-p/2279044#M1544</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You can pull the VHD out of the ISO under /Hypervisor/In-Guest VHD/yadda yadda, then open it with 7ZIP to pull the wirtable files.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'll run a compare on the VMDK and VHD files (of the same version) and see what happens.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks again!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 03 Jan 2018 14:56:33 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/App-Volumes/Manual-Upgrade-of-Writable-Volume/m-p/2279044#M1544</guid>
      <dc:creator>fdrietatns</dc:creator>
      <dc:date>2018-01-03T14:56:33Z</dc:date>
    </item>
  </channel>
</rss>

