<html><head></head><body>I don't know how to get the uuid from hardware either, but your further explanation of why this workaround works helps. <br>
-- <br>
Sent from my phone. Please excuse my brevity.<br><br><div class="gmail_quote">On May 17, 2016 7:38:02 AM PDT, Rod Roark <rod@sunsetsystems.com> wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre class="k9mail">If I knew how to retrieve the original UUID I would... but it turns out <br />that is not necessary. The install works with whatever UUID is in the <br />VM and can be activated via smartphone. However if you then clone the <br />VM without making sure the UUID is preserved, the resulting VM has to be <br />activated again... too many of those and they are bound to get difficult <br />about it.<br /><br />On 05/17/2016 07:23 AM, Jeff Newmiller wrote:<br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;"> The procedure appears to never retrieve the hardware UUID from your <br /> bare metal install. If you are trying to transition from a license <br /> associated with your existing windows install, wouldn't you want to <br /> continue using that uuid? Without it, wouldn't you need to buy at <br /> least one new license?<br /> -- <br /> Sent from my phone. Please excuse my brevity.<br
/></blockquote>[original post omitted]<br /><hr /><br />vox mailing list<br />vox@lists.lugod.org<br /><a href="http://lists.lugod.org/mailman/listinfo/vox">http://lists.lugod.org/mailman/listinfo/vox</a><br /></pre></blockquote></div></body></html>