noticed the same but we shall see..... keep in mind vamt 3.1 is beta so when Blue and 2012/R2 are RTM'd i'm sure Vamt 3.1 final should have newer or rather RTM pkeyconfigs.
there is nothing wrong with the checker. those keys in the pkeyconfig have the same description and Editionid. i'll pm you the decrypted data.
The checker does not work on XP WEPOS keys There is such known key RJ2DF-*****-*****-*****-P3T4W, but checker gives Profile : NT 5.x Validity: Invalid pidgen.dll from WEPOS is 16,384 bytes version 1.5.1.13 28/01/2005 CRC32: CAD7B47C MD5: 5C659B6D320CFF4BBCE89097E3F353CC SHA-1: 5C2BEAA4197401428236A68C175DD1D55069032A sebus
Janek's UPIDchecker can only check XP/2003 keys as the pidgin.dll from wepos is not embedded in the exe. it is not like a pkeyconfig file that can be used "custom". to check a XPwepos key I presume you would need the older cmdline XPchecker and add the pidgen.dll to it. I don't have the wepos pidgen.dll to check so if you would attach it that would be great.
So what should be the product ID of the virtualized guest server after entering AVMA key?? Will it reflect the same ID of the host??