<?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: Appvolumes4 convert VMDK to VHD in App Volumes</title>
    <link>https://communities.vmware.com/t5/App-Volumes/AppCapture-convert-VMDK-to-VHD/m-p/2938642#M9062</link>
    <description>&lt;P&gt;did any body convert appvolumes2.18 vmdk files to VHD files ?&amp;nbsp; Fling tool from vmware only works on Windows 10 not on Windows Server 2016.&lt;/P&gt;</description>
    <pubDate>Wed, 16 Nov 2022 21:05:59 GMT</pubDate>
    <dc:creator>smut5203</dc:creator>
    <dc:date>2022-11-16T21:05:59Z</dc:date>
    <item>
      <title>AppCapture convert VMDK to VHD</title>
      <link>https://communities.vmware.com/t5/App-Volumes/AppCapture-convert-VMDK-to-VHD/m-p/2861616#M8576</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Been trying out the new AppCapture utility provided in App Volumes 2103 but I am having trouble converting vmdk files exported from App Volumes 2012 to VHD format, I get the following output&lt;/P&gt;&lt;P&gt;&amp;nbsp;ERROR: not a valid vmdk file at: C:\packages_files\OfficeE3-flat.vmdk&lt;/P&gt;&lt;P&gt;I was able to convert files that the AppCapture utility created, just not sure if that conversion will work for any vmdk app package?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Also, while I do plan to update our app volumes manager to 2103 later next week, does anyone know if apps packaged with AppCapture will work with app volumes 2012? I don't seem to be able to get the files to appear in app volumes manager but unsure if that's just down to our app volumes manager still being on 2012 or I am making a mistake somewhere..&lt;/P&gt;</description>
      <pubDate>Wed, 11 Aug 2021 13:17:42 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/App-Volumes/AppCapture-convert-VMDK-to-VHD/m-p/2861616#M8576</guid>
      <dc:creator>MattSyme</dc:creator>
      <dc:date>2021-08-11T13:17:42Z</dc:date>
    </item>
    <item>
      <title>Re: AppCapture convert VMDK to VHD</title>
      <link>https://communities.vmware.com/t5/App-Volumes/AppCapture-convert-VMDK-to-VHD/m-p/2863420#M8585</link>
      <description>&lt;P&gt;Hey&amp;nbsp;&lt;SPAN class="UserName lia-user-name lia-user-rank-Contributor lia-component-message-view-widget-author-username"&gt;&lt;A href="https://communities.vmware.com/t5/user/viewprofilepage/user-id/5290524" target="_self"&gt;&lt;SPAN class=""&gt;MattSyme&lt;/SPAN&gt;&lt;/A&gt;,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;I'm attempting the same conversion as well.&amp;nbsp; I received the same error with my App Volume VMDKs pulled directly from the DataStore.&amp;nbsp; I think it's due to the fact that the App Capture tool is designed to work only with Monolithic Sparse VMDKs.&amp;nbsp; I'm about to attempt a dual conversion as such:&lt;/P&gt;&lt;P&gt;1: Convert App Volumes VMDK (and associated -flat vmdk) to a Monolithic Sparse VMDK using the VDiskManager.exe tool included with VMware Workstation and VMware Player (Command: vmware-vdiskmanager.exe -r sourceLocation.vmdk -t 0 targetDestination.vmdk)&lt;/P&gt;&lt;P&gt;2: Convert the resulting VMDK file to VHD with the AppCapture Powershell tools (ConvertTo-AVVhdDisk)&lt;/P&gt;&lt;P&gt;Not yet sure if this will work, but I'll be glad to post results.&lt;/P&gt;</description>
      <pubDate>Tue, 24 Aug 2021 04:56:09 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/App-Volumes/AppCapture-convert-VMDK-to-VHD/m-p/2863420#M8585</guid>
      <dc:creator>Blakerdog</dc:creator>
      <dc:date>2021-08-24T04:56:09Z</dc:date>
    </item>
    <item>
      <title>Re: AppCapture convert VMDK to VHD</title>
      <link>https://communities.vmware.com/t5/App-Volumes/AppCapture-convert-VMDK-to-VHD/m-p/2883427#M8687</link>
      <description>&lt;P&gt;Nope, doesn't work.&lt;/P&gt;&lt;P&gt;I have been following and troubleshooting the same steps but when trying to convert from .vmdk to .vhd I am getting the below error:&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;EM&gt;ERROR: no metadata available in this vmdk disk&lt;/EM&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;EM&gt;ERROR: failed to extract metadata from vmdk while building vhd. Error: 0x0&lt;/EM&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;EM&gt;ERROR: vhd creation failed&lt;/EM&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;not sure how to include the .metadata to the .vmdk file.&lt;/P&gt;</description>
      <pubDate>Tue, 14 Dec 2021 19:59:43 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/App-Volumes/AppCapture-convert-VMDK-to-VHD/m-p/2883427#M8687</guid>
      <dc:creator>mkadouraCITCO</dc:creator>
      <dc:date>2021-12-14T19:59:43Z</dc:date>
    </item>
    <item>
      <title>Re: Appvolumes4 convert VMDK to VHD</title>
      <link>https://communities.vmware.com/t5/App-Volumes/AppCapture-convert-VMDK-to-VHD/m-p/2938642#M9062</link>
      <description>&lt;P&gt;did any body convert appvolumes2.18 vmdk files to VHD files ?&amp;nbsp; Fling tool from vmware only works on Windows 10 not on Windows Server 2016.&lt;/P&gt;</description>
      <pubDate>Wed, 16 Nov 2022 21:05:59 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/App-Volumes/AppCapture-convert-VMDK-to-VHD/m-p/2938642#M9062</guid>
      <dc:creator>smut5203</dc:creator>
      <dc:date>2022-11-16T21:05:59Z</dc:date>
    </item>
  </channel>
</rss>

