![]() ![]() ![]() Clock was winded back automatically because of synchronization with time server or with host of virtual machine by more than a day.Clock was winded back manually by more than a day.A virtual machine was reverted to a snapshot that includes licenses.Only after the reboot, Windows detects the cloning that changes its internal IDs and in consequence the UMN3. A snapshot of a virtual machine in running state is started after cloning of the virtual machine (cloning can be long time back!!!) and then rebooted.A virtual machine that includes licenses was cloned (moving of the virtual machine does not change UMN3).Only after the reboot, Windows detects the cloning that changes the MAC address and in consequence the UMN2. Virtual network adapter configuration was changed (manually or automatically by the hypervisor, e.g.Primary network adapter changed after adding of further network cards.For 'Hyper-V' VMs there exist MAC address assignment configuration that is by default set to dynamic but it must be static! For VMware moving of the vmx configuration file changes also the MAC address even when moved on same host in different folder. MAC address has been changed automatically or manually.Attempt to cheat or tampering by a hacker.Anchor information in registry got changed/manipulated (maybe registry cleaner was used).Attempt to cheat or tampering by a hacker (copied Trusted Storage files to another machine).Disk encryption software is used that changed track 0 information and corrupted anchor information.This is especially a problem for floating licenses as server trusted storage files are always opened by vendor daemon. ![]() Windows was not properly shutdown (crashed, blue screen, power outage) last time.The following situations could cause an untrusted license: ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |