Running into the following:
Steps to reproduce:
- Create a cloud service (web or worker)
- Set OS family to 5 (Windows Server 2016)
- VM size - any
- Deploy to EU West (probably others too but have not tested)
- RDP into web/worker role and check activation status
AzureSupport on Twitter pointed me to https://blogs.msdn.microsoft.com/mast/2014/12/23/troubleshooting-windows-activation-failures-on-azure-vms/, which did not resolve the issue. I also tried the 2016 keys from https://technet.microsoft.com/en-us/library/dn303421.aspx, to no avail.
Commands executed:
iex "$env:windir\system32\cscript.exe $env:windir\system32\slmgr.vbs /skms kms.core.windows.net:1688"iex "$env:windir\system32\cscript.exe $env:windir\system32\slmgr.vbs /ipk TMJ3Y-NTRTM-FJYXT-T22BY-CWG3J"
iex "$env:windir\system32\cscript.exe $env:windir\system32\slmgr.vbs /ato"
How can my cloud services live a nice, activated life? (preferably without me having to activate them or a startup script havign to activate them...)