"LinkedHelpTopics"="%systemroot%\\help\\tscc.chm" "Description"="Configure Remote Desktop Session Host settings" From a Windows 2008R2 server, copy tsconfig.msc and tsconfig.dll (from and to system32 folder) and load this into registry (also exported from Desktop Session Host Configuration" I've managed to enable TSConfig in Windows 2012 from older Windows 2008R2 TSConfig. This is ridiculous! There needs to be a way to utilize Remote Desktop configuration tools in a workgroup environment. Running on the server just to be a DC for a domain we don't even need. 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 In order to demote the DC you have to have another DC to maintain access to the domain. 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 As it is a single server environment, the server also has to be the domain controller. In order to access the Remote Desktop configuration, the server 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. The counter stations are all ThinClient terminalsĬonnecting through RDP. Here's my scenario: We have hundreds of standalone servers in service in stores across the country. This change in the Remote Desktop configuration scheme renders Windows Server 2012 useless in our environment.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |