Provisioning Server 5.6 KMS CMID Issues

After you create your desktop image and set it up for KMS activation, you notice that the CMID does not change no matter how many times you reboot or issue the SLMGR /REARM command. The issue is with the order in which you enable/disable KMS in the File Properties of the vDisk in Provisioning Server. When you start the process of getting an image ready to update, make sure to disable KMS first, then set the mode to Private. After you have updated your image, enable KMS and then set the image to Standard. Now, every reboot an image makes, a new CMID is generated and you are finally able to activate against KMS (granted you meet the minimum requirements).