Jump to content


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.

Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.


Windows Server 2012 and T5135 thinclients

  • Please log in to reply
1 reply to this topic

#1 PhoenixIT


  • Members
  • 2 posts
  • Local time:07:11 AM

Posted 02 July 2013 - 10:56 PM



We are a Mid-sized charitable organization

that need to setup some users for training on MS Dynamics CRM 2011.


Is it possible to connect T5135s Thin-Client to a Windows Server 2012 Server e.g. with RDP?


If so can you please give an overview how this can be done?


Any advice appreciated :)


We need to setup 8 users and we have plenty of T5135's but very little else in terms of clients.



BC AdBot (Login to Remove)


#2 x64


  • Members
  • 352 posts
  • Gender:Male
  • Location:London UK
  • Local time:06:11 PM

Posted 05 July 2013 - 01:11 PM

Nobody has bitten, so I'll throw some explanations half formed ideas in, incase they are of use. I have no knowedge of how well your T5135s might play with Windows 2012 and only very limited knowledge of a previous version of CRM.

You don't say if the Windows 2012 server is ready doing anything else, for example if it is the CRM server or a spare box that you can be more flexible with.

For a RDP clients, you need to run a remote desktop session host. This would create an operating system instance for each connected user. Were you to do this, then thin client user would end up in a sesssion resembling a Windows 8 desktop. From there that could connect to CRM in the normal manner. Note that this is not a zero cost option, as you would need RDP CALs (and Windows server CALs) for each user or connecting device, in additon for the relevant CRM licences.

Making a server an RDP session host means that you don't want that server instance to be doing do anything else. RDP session hosts should really perform only that role.

If the server is already doing something else but has some spare capacity (CPU, DISK, and Memory), you could install the Hyper-V role. This would allow the server to  run a second instance of WIndows 2012 as a virtual machine, dedicated to being the session host. The windows 2012 licence allows you to run a second server in this way. The thin client would attach to the session host, and launch CRM from the desktop that they end up in.

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users