Caution! This message was sent from outside the University of Manitoba.

Is this an OEM or a retail Win7?  If retail, at least it is re-useable on "another" machine/VM if something goes wrong with your VM and/or real machine experiments, whereas an OEM version cannot be re-used.

Hartmut


On Sun 18 May 2025 at 02:03:59 -05:00, Trevor Cordes <trevor@tecnopolis.ca> wrote:
I'll need to activate my Win7 install in a VirtualBox VM soon.  It's a
legit copy with a legit code, all brand new/unused.

I want to ensure that the VM will work even when the underlying laptop is
upgraded in the future.  Thus I started worrying about CPUID pass-thru,
etc.  I want to be sure I tweak everything now to avoid re-activation in
the future.

What things should I worry about here?  Is there anything more than just
CPUID?

Looks like VB has a difficult way to set CPUID, not in the GUI.  Then the
next question is, what do I set it to?

Does the CPUID provide just a id of the model of CPU, or does it also
include a CPU serial #?  If the latter, then I guess you need to make sure
it's unique for that version of Windows or they may deny activation??

Any other thoughts?  Thanks!
_______________________________________________
Roundtable mailing list -- roundtable@muug.ca
To unsubscribe send an email to roundtable-leave@muug.ca