If you have more than one TS like I do you will want to use a Licensing server. Select your licensing type, I am using Per User To uses this option click 'Tasks' and Edit Deployment Properties' Step 11: Edit Deployment Properties This allows you to share your client TS licenses across all of your terminal servers making it easier to purchase and manage your license needs.
Your licensing server will be contacted, verified and added to the list.Ĭlick OK Step 12: Set Who Can Log into this server Type in the name of your licensing server and hit add.
Test your connectivity out with a regular user account and you should be good to go! Go to System > Remote Settings > Select Users and add the Group or Users who will be allowed to connect to this server Step 13: Verify User ConnectivityĪt this point users should now be able to log into this server. The process as been re-arranged and is very different when compared to previous versions, but once you get a grasp for where things have been moved to it still works very much the same as it always did. I am struggling to understand this new RDS. All we want is to provide the same RDC experience my users had with 2008 Terminal Server. I have followed Molan's tutorial as well as many others and can't get it to work. At this point, I am willing to pay anyone (out of my pocket) to get it done. Here's the issue, my 200+ users in three countries are used to open remote desktop connection on their Windows desktops and connect to which resolved to an NLB cluster of two 2008 R2 servers. #Windows server 2008 r2 remote desktop license crack windows.#Windows server 2008 r2 remote desktop license crack download.#Windows server 2008 r2 remote desktop license crack 64 Bit.#Windows server 2008 r2 remote desktop license crack install.#Windows server 2008 r2 remote desktop license crack how to.
0 kommentar(er)
