<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Html5 on Matt Allford</title><link>https://www.mattallford.com/tags/html5/</link><description>Recent content in Html5 on Matt Allford</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 27 Dec 2019 08:24:38 +0000</lastBuildDate><atom:link href="https://www.mattallford.com/tags/html5/index.xml" rel="self" type="application/rss+xml"/><item><title>VMware VM Clone via HTML5 Client Results in Incorrectly Configured VMDK</title><link>https://www.mattallford.com/vmware-vm-clone-via-html5-client-results-in-incorrectly-configured-vmdk/</link><pubDate>Fri, 27 Dec 2019 08:24:38 +0000</pubDate><guid>https://www.mattallford.com/vmware-vm-clone-via-html5-client-results-in-incorrectly-configured-vmdk/</guid><description>&lt;p&gt;This one is just a quick post regarding an issue I came up against just before Christmas.&lt;/p&gt;
&lt;p&gt;To get straight to the point, I found an issue where in multiple separate environments, when cloning a virtual machine via the VMware vCenter HTML5 Web client interface, if you select the tick box to &amp;ldquo;customize this virtual machine&amp;rsquo;s hardware&amp;rdquo; and change any of the settings of the VM, the cloned virtual machine&amp;rsquo;s VMDK file(s) will be pointed to the VMDK file(s) of the source machine you used for the clone.&lt;/p&gt;</description></item></channel></rss>