Windows Azure VM - enable RDS Session Host how

After finding out "the hard way", am finding out that the Remote Desktop Services "Session Host" role won't install on the hosted VMs. It's great really, I love spending my time on things like this. Anyway..... Where is the documentation showing how to get this working, and also which "subscriber access licenses" to buy to use?

Funny how the license role DOES install and the RDS CALs DO apply properly. Any information?

I'd like to update this post. For the record, the root cause of my issue was what I still think of as a "sketchy" barrier that was somehow implemented within the operating system to prevent the adding of the "Remote Desktop Services Session Host" role component. In addition, it seems the reason was that Windows Azure previously did not allow RDS to be implemented which is fine but the documentation was less than easy to uncover.

Some posts on the issue, and the very recent change which supposedly means you now CAN use RDS...if you find the right licenses somewhere (CALs not supported).

http:-//blogs.msdn.-com/b/luispanzano/archive/2013/07/15/remote-desktop-services-are-now-allowed-on-windows-azure.aspx

http:-//www.windowsazure.-com/en-us/pricing/licensing-faq/

I still find it quite interesting that within the operating system there is something going on that does not occur when you use your own DVD/ISO to install a "real" Windows server. If there is something extra to block RDS role (only RDS and RMS seem to be taboo on Windows Azure, when else would one expect to have this type of technical barrier), then what other extra "goodies" might there be in the OS?

Also I find it quite humorous and surprising that you marked my own responses to my own post as abuse. "Already reported as abuse". What does that even mean? Sorry if you don't like customers expressing their frustrations publicly, but you make it all too easy and too often. Try understanding the problem and not being in a rush to mark everything as an answer all the time.

Also for the record, on the other hosting provider, the issue does not occur meaning they must be using a different build of the Windows operating system that does not have this "booby trap" to block the install of a feature. I find it quite unsettling that it exists in the first place but as I said it's old news and just wanted to update since I saw your update and making my answer "abuse" hehehe this is too rich.