<div>
Thanks but the problem is that we are going to use thin clients that use the RDP protocol so to carry on using this is there a DNS round robin kind of setup we can use ?
</div>


Thanks but the problem is that we are going to use thin clients that use the RDP protocol so to carry on using this is there a DNS round robin kind of setup we can use ?

<div>
Nope. You'll want to use a thin client that officially supports RDS. There are thin clients running linux and windows embedded capable of reading the published xml feed that rdweb generates. Trying to force a non-supported process (round robin in 2012, for example) will cause licensing and certificate issues so the user experience would suck.
</div>


Nope. You'll want to use a thin client that officially supports RDS. There are thin clients running linux and windows embedded capable of reading the published xml feed that rdweb generates. Trying to force a non-supported process (round robin in 2012, for example) will cause licensing and certificate issues so the user experience would suck.

<div>
<div class="content wysiwyg-content">
Hi all,<br />
<br />
I've created a Microsoft RDS collection using 2 RDS servers that should be load balanced but how do i connect to these via RDP ? I would;ve thought i would connect to the collection name or similar and it would then load balance the users to A server but what address (name) do i use to connect as i've tried the collection name but it doesn't seem to resolve ?<br />
sorry if this is basic.<br />
Thanks
</div>
</div>


Hi all,

I've created a Microsoft RDS collection using 2 RDS servers that should be load balanced but how do i connect to these via RDP ? I would;ve thought i would connect to the collection name or similar and it would then load balance the users to A server but what address (name) do i use to connect as i've tried the collection name but it doesn't seem to resolve ?
sorry if this is basic.
Thanks

how to connecto to an RDS collection

Windows Server 2012 is the server version of Windows 8 and the successor to Windows Server 2008 R2. Windows Server 2012 is the first version of Windows Server to have no support for Itanium-based computers since Windows NT 4.0. Windows Server 2012, now in its second release (Windows Server 2012 Release 2) includes Foundation, Essentials, Standard and Datacenter, and does not support IA-32 or IA-64 processors.