JohnEastNevermind. 😳 As it turns out, the tester was using a pair of identical machines with identical MAC address.
But the one question still remains, what, if anything besides the MAC addr do you use to id a system.Thx
Multiple activations issue/question
JohnEastWyatt,Here is how I am untilizing your APIs. During installation, I have a console app verify the product key. I do this with Activate(), and Deactivate(1). If the activate fails, I can prompt the user with the appropriate message. If it succeeds, I continue to install everything and my freshly installed Windows service activates the license immediately. Life is good.
Now, if I attempt to install on a second machine, I expect an in-use failure. I usually get that. BUT, in one case, when I start the installation, again with Activate/Deactivate(1), the product key from the website goes from used/total activations 1/1, to being unused, 0/1. Basically, the second machine succeeded AND it deactivate the license. Not good.Now, (with machine 2 out of the picture ) the first machine, even though it show good Activation of the license, the product key is shown as unused on the web site. Again, not good.
Note that in this case, the two machines are on the same network switch. Just so I am clear, what exactly (or as much info as you want to disclose), do you use to identify a machine? I assume the NIC MAC address.
Thx
JohnEast
Were you using Virtual Machine copies of the exact same "computer"? We have special ways of identifying virtual machines, and we'll have special behavior for these types of computers in the near future. But no, Windows computers aren't ID-ed just by their MAC address -- it's a combination of all their hardware.
JohnEastWyatt,No, these aren't VMs. They are identical hardware, and imaged identically. So at least one of the ID input is the mac address, correct? On one of the machines, we changed the mac address and the behavior is still the same. I will try to reimaging and then change mac address and see if that helps. Does this make sense to you?
Even identical hardware (that is, hardware off the exact same assembly line one right next to the other) will have different Hardware-IDs. What imaging software are you using to duplicated the software? My guess is there's a weird caching bug in that software that we'll have to work around.