<div>
This is very much possible in Windows server 2012 R2. you can add any new server any time.
</div>


This is very much possible in Windows server 2012 R2. you can add any new server any time.

<div>
That was just a typo on my part. We are, in fact, using Server 2012 R2.<br />
<br />
I setup the RDCB with two terminal servers and it works. Are we able to bypass the web access?<br />
<br />
Our users are accustomed to connecting directly from the RDP client. If I try to connect to the connection broker with a domain user, it tries to connect directly to the connection broker and says &quot;This user is not authorized for logon&quot;. However, if I access the server's RDWEB page, it connect to either one of the terminal servers.
</div>


That was just a typo on my part. We are, in fact, using Server 2012 R2.

I setup the RDCB with two terminal servers and it works. Are we able to bypass the web access?

Our users are accustomed to connecting directly from the RDP client. If I try to connect to the connection broker with a domain user, it tries to connect directly to the connection broker and says "This user is not authorized for logon". However, if I access the server's RDWEB page, it connect to either one of the terminal servers.

<div>
<div class="content wysiwyg-content">
We are looking to grow from one 2008 remote desktop services server to two 2012 servers.<br />
<br />
We would like to setup a connection broker but do not have an additional 2012 machine available for a few months.<br />
<br />
1) Can we setup a connection broker on one of the 2012 servers itself? If so, will we be able to move the connection broker to a new server in the future?<br />
<br />
2) Would it be better to setup one terminal server for now until we can purchase a true connection broker then clone?
</div>
</div>


We are looking to grow from one 2008 remote desktop services server to two 2012 servers.

We would like to setup a connection broker but do not have an additional 2012 machine available for a few months.

1) Can we setup a connection broker on one of the 2012 servers itself? If so, will we be able to move the connection broker to a new server in the future?

2) Would it be better to setup one terminal server for now until we can purchase a true connection broker then clone?

Server 2012 Remote Desktop Services Connection Brokering

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.

Windows Server 2012

Remote access may refer to the connection to a data-processing system from a remote location, for example through a virtual private network remote desktop software, terminal emulation, or the activation of features of a business telephone system from outside the business's premises.

Remote Access

The Windows operating systems have distinct methodologies for designing and implementing networks, and have specific systems to accomplish various networking processes, such as Exchange for email, Sharepoint for shared files and programs, and IIS for delivery of web pages. Microsoft also produces server technologies for networked database use, security and virtualization.