Just looking to get some advice on licensing for Remote Desktop.We currently have 1x server 2012 gateway server running connection broker, gateway, licensing and web access.We have 4x server 2012 session host servers just running the session host role.Our academic licensing means that we are able to use server 2016 remote desktop using our campus agreement number. I asked our supplier if I could install the 2016 licensing on our 2012 licensing server, he said this would be fine and it would work with 2016.So I added the license, replaced 2 of the session host servers with 2016, but I am getting errors about no licenses being available and it is going to expire in 120 days.After some Googling I have established that the server running the licensing role needs to be server 2016 also.Although I want to update the session host servers, our gateway server has quite a complex setup and I would prefer to leave it as is for now.
Is it acceptable for me to install the licensing role on one of the 2016 session host servers and add the licensing to this? Will it just work itself out from there?Thanks:).
With RDS services (formerly know as terminal services) there are several roles and licenses involved.You will need Server licenses (OSe licenses), RDS licensing server (OSe license) & RDS CALs.Even if you have SA for your OSe licenses, you will also need to deploy a Server 2016 RDS licensing server and purchase RDS '2016' CALs (You can't use older CALs to access newer Windows Server versions).' Any RDS license server can host licenses from all previous versions of Remote Desktop Services and the current version of Remote Desktop Services. For example, a Windows Server 2016 RDS license server can host licenses from all previous versions of RDS, while a Windows Server 2012 R2 RDS license server can only host licenses up to Windows Server 2012 R2.'
With RDS services (formerly know as terminal services) there are several roles and licenses involved.You will need Server licenses (OSe licenses), RDS licensing server (OSe license) & RDS CALs.Even if you have SA for your OSe licenses, you will also need to deploy a Server 2016 RDS licensing server and purchase RDS '2016' CALs (You can't use older CALs to access newer Windows Server versions).' Any RDS license server can host licenses from all previous versions of Remote Desktop Services and the current version of Remote Desktop Services. For example, a Windows Server 2016 RDS license server can host licenses from all previous versions of RDS, while a Windows Server 2012 R2 RDS license server can only host licenses up to Windows Server 2012 R2.' JitenSh wrote:davidashcroft wrote:I do hope that the screenshot is not one that you have just created today from your environment haha!Copied from the internet, I don't think you have any clue how you respond to somebody's answer.Huh? I was making a joke, I guess you don't have a sense of humor.Thanks everyone though, I will give these ideas a go, I think I should be OK from here though, I just wanted to make sure I wasnt going to cause any sort of issue by having the license server as a session host server also.
Windows Server 2012 Terminal Services Licensing Crack 1
I would prefer to keep doing it this way. Thanks again.