Due to capacity issues, I recently had to upgrade some Windows 2008 R2 Terminal Servers. The replacement servers do not support Server 2008 R2 so here is what i am trying to do. I want to load Windows server 2016 on the new servers as the base OS and then convert the old windows 2008 R2 terminal servers to VM's and run them under hyper-v on windows 2016.
I am able to do all of this and the 2008 R2 VM's run fine on server 2016 hyper-v. They are seen on the network and operate fine. the problem is when a thin client tries to connect, It will not connect to the 2008 R2 VM running on Server 2016. The Terminal server license server is on the domain controller which is a windows server 2008 R2 as well. I can rdp to the 2016 server and to the server 2008 R2 VM no issues. It is just when i try with the thin clients they will not connect. They will still connect to any of the other server 2008 R2 terminal servers still running stand alone. I think it is some sort of licensing issue. I know we are going to have to upgrade the licenses but there are 20+ servers that need upgrading this year so i want to plan it all out first, budget for it and then start the process. The only reason i am doing this now is that i need more seats for thin clients today. We are about to hire 20-30 more staff and we are just about maxed out in capacity on the existing servers. This was meant to be a short term solution until we upgrade the whole environment later this year.
Any input would be helpful