This change in the Remote Desktop configuration scheme renders Windows Server 2012 useless in our environment. Here's my scenario: We have hundreds of standalone servers in service in stores across the country. The counter stations are all ThinClient terminals
connecting through RDP. The servers, for the sake of simplicity, are all configured as "workgroup" as we have no need of a domain in a single server environment. Along comes Windows "Server" 2012. In order to access the Remote Desktop configuration, the server
has to be on a domain. As it is a single server environment, the server also has to be the domain controller. Remote Desktop roles such as the RD Connection Broker can't be installed on the domain controller, so you have to demote the DC in order to install
other integral parts of RD. In order to demote the DC you have to have another DC to maintain access to the domain. Now we're forced to either install two servers per store so that one can be DC and the other can host the RD options, or set up a virtual machine
running on the server just to be a DC for a domain we don't even need. This is ridiculous! There needs to be a way to utilize Remote Desktop configuration tools in a workgroup environment.
↧