Ensure Virtual Machine GenerationID does not change over a Shut Down and Start pair of operations
Microsoft invented the VM GenerationID as a means of determining when an important VM transition event has occured. As per Microsoft's paper on the subject, the GenerationID of a guest should not change on restart or migrate operations. This works fine directly on Hyper-V, but an Azure managed VM will see a GenerationID change when the VM is Shut Down then Started (as two separate operations, a single 'Restart' operation does not change the GenerationID). Incidentally, the virtual SMBIOS UUID also changes during this operation, which is wrong too (SMBIOS UUID should change only on a clone operation).
I imagine the existing GenerationID behaviour with Shut Down then Start would negatively impact anyone trying to: run Active Directory Services in an Azure cloud; assign an identity to an Azure VM instance.
Yes, this is good feedback. We are looking at the best way to resolve this.
Hi Corey, How is this investigation progressing? It has now been over four years.
I just ran into the same issue myself and now I'm forced to rebuild DC VM on Azure.
I'm surprised it's been over 3 years since @Corey acknowledgement and no solution has been released yet.
Any update on this?
Our software uses this UUID for tiering/licensing. This UUID regeneration after each VM restart makes it painful to support Azure VMs.