Implement product key into bios MSDM table of VMware

In my opinion it could be possible. It is practically applicable.Thanks for such a nice stuff.

 

Copy "data.dat" from a previous activated VM to a second VM activates the second VM offline. Even when second VM has different UUID, MAC and some virtual hardware changes (RAM, CPU, soundcard removed).

 

Haven't yet scrutinised the code but slmgr has been updated in 8.1 to check for VM

Code:

               
Private Function IsAVMA(strDescription)
    If InStr(strDescription, "VIRTUAL_MACHINE_ACTIVATION") > 0 Then
        IsAVMA = True
    Else
        IsAVMA = False
    End If
End Function




 If (NOT bKmsClient) AND (NOT bAVMA) Then

                    'Note that we are re-using the UseLicenseURL for the Product Activation
                    'URL for down-level compatibility reasons

                    strUrl = objProduct.ProcessorURL
                    If strUrl <> "" Then
                        LineOut GetResource("L_MsgProcessorCertUrl") & strUrl
                    End If

                    strUrl = objProduct.MachineURL
                    If strUrl <> "" Then
                        LineOut GetResource("L_MsgMachineCertUrl") & strUrl
                    End If

                    strUrl = objProduct.UseLicenseURL
                    If strUrl <> "" Then
                        LineOut GetResource("L_MsgUseLicenseCertUrl") & strUrl
                    End If

                    strUrl = objProduct.ProductKeyURL
                    If strUrl <> "" Then
                        LineOut GetResource("L_MsgPKeyCertUrl") & strUrl
                    End If

                    strUrl = objProduct.ValidationURL
                    If strUrl <> "" Then
                        LineOut GetResource("L_MsgValidationUrl") & strUrl
                    End If

                End If
            End If

 

Right.

But Microsoft do never recognize the multiple VM activations, because with copy "data.dat" the activations works offline.

Just tested with two real PCs: Copy "data.dat" does not activate offline.

 

There is a lot of information that is identical between two VMs. For example, most of the SMBIOS information, including System Manufacturer etc. Maybe that is sufficient. This is all quite surprising though, the check seems too lenient.

 

Most likely something in the Bios or on the motherboard on bootup. It makes the Hardware ID via CPU/MB (i think now graphics card's also heard people getting unactivated with some graphics drivers.)

Anyway when windows boots/installs it does not just read what model of MB and CPU you are using. (if it did this people with the same CPU and MB would be able to use the same key.) There must be a special code embedded into the hardware or bios that it reads to make the unique hardware ID. With the machine being a VM the BIOS it is using will have the same ID on every system or should at least. Although everyone's CPU could be different so this is kind of odd.

My guess is this sort of hidden code is on a hardware level due to people flashing bios images and stuff so would make sense. Meh it might not even be a code just the date the MB was made or first used and model of it combine or something. Hmmmm wonder in the future when/if KMS fails the hardware ID could be emulated on bootup so everyones machine would have the same hardware ID that has the emulator it's a long shot and probably way more complex than its worth and most likely wont work and just slow the system down anyway.. .

 

Did you ever have time for these test?

sebus

 

I would be interested to know how did you manage to arrive to decision as to where put the MSDM table in Vmware BIOS?

Thanks

sebus

 

Thanks, expected that it will take some manual doing. But that is the very fun. Need to get to you an unused OEM key, so you can keep testing...

Need to pick one (tomorrow)

sebus

 

OK - whilst installation you have to enter manually the Windows 8.1 generic product key. Because the installation routine of Windows 8.1 doesn't accept the Windows 8 DM key.

But what happens when you implement the Windows 8.1 generic product key into the BIOS440.ROM MSDM table ? Does the installation routine of Windows 8.1 accept this Windows 8.1 generic key ? OK - for activation you have to substitute the generic key with a regular Windows 8.1 key.

 

You need to login to view this posts content.

 

Probably 8.1 did not recognize the 8.0 OEM key, may be a different story if we installed 8.0... likely it will pick up the key from MSDM then...otherwise like you say, it will just be a 'retail' activation if added later...