Why does this mismatch happen?
As you are upgrading your OS to a newer version or simply chose the wrong (VM Guest Operating Setting) profile to run a different OS.
From Cloud Portal you might see something like this. In this example all virtual machines are running Windows Server 2016, however Cloud portal is showing Microsoft Windows Server 2008
From the vss-cli you might see something like this. Let's proceed to show the virtual machines filtered by name.
vss-cli --columns moref,name,admin,guest_id,guest_full_name,guest_id_run,guest_full_name_run compute vm ls -f name=<NAME_OF_VM>
output:
moref name guest_id guest_full_name guest_id_run guest_full_name_run ------- ------------------ --------------------- -------------------------------------- --------------------- ----------------------------------------------- vm-XXXX <NAME_OF_VM> windows8Server64Guest Microsoft Windows Server 2012 (64-bit) windows9Server64Guest Microsoft Windows Server 2016 or later (64-bit)
The importance of this output is the mismatch between the guest_full_name column and guest_full_name_run. What it means is that you are running Windows Server 2016 with a profile of Windows Server 2012.
How does this affect your environment?
The profile attached to the VM will help to take advantages of the OS features. Windows 2016 won’t take advantage of all the features because is configured with the Windows 2012 profile.
How can you fix the mismatch configuration?
Tun off the Virtual Machine
Configure the right OS, for example (Windows 2012 profile to Windows 2016)
vss-cli compute vm set vm-XXXX os windows9Server64Guest
Turn of the Virtual Machine