Archived Forums
>Remote Desktop Services [Terminal Services]
Question
-
4
Sign in to vote
Where is the Remote Desktop Session Host Configuration tool in Server 2012 ?
This is an MMC snap-in found on earlier servers, even if RDS is not installed. In Server 2012, even if the Remote Desktop Session Host role is installed, this tool is still not available.
I'm looking for the Server 2012 tool to adjust security settings like TLS authentication, High encryption level, choice of TLS certificate, NLA, etc.
Thanks!
Tuesday, June 19, 2012 4:01 PM
-
9
Sign in to vote
I thought this was the windows server forum. Isn't windows 2012 server a "windows server" any more?The top of the page lists it. I have questions also as to managing a Remote Desktop server and it seems that workgroup instances have been completely left out. Management requires a session collection... but you get this when you open server manager - Remote Desktop Services - Overview - "You are currently logged on as a local administrator on the computer. You must be logged on as a domain user to manange servers and collections." Where isany information for configuring a RDP server to host sessions and RDP client licensing in a stand alone 'Workgroup'environment? Do we have to look at other OS options for hosting our applicationsother than Windows?
Thanks, Dale
Tuesday, November 6, 2012 6:46 PM
-
11
Sign in to vote
This is crazy, I am also trying to configure this on a template server therefore it's not part of a domain. MICROSOFT, what are you thinking with this craziness !
Niamh
- Proposed as answer by Azzuroo Monday, January 7, 2013 6:59 PM
- Unproposed as answer by Azzuroo Monday, January 7, 2013 6:59 PM
Monday, November 26, 2012 2:42 PM
-
2
Sign in to vote
You can install just the Session Host role service and manage it entirely with PowerShell:
//blogs.msdn.com/b/rds/archive/2012/06/28/introduction-to-windows-powershell-scripting-in-windows-server-2012-remote-desktop-services.aspx
You will eventually also need a License Server, which can be installed on the same Session Host or a separate sever entirely.
The RDS GUI management plug-in for Server Manager does require a domain in order to install.
Don Geddes - SR Support Escalation Engineer - Remote Desktop Services - Printing and Imaging
Monday, January 7, 2013 7:41 PM
-
0
Sign in to vote
hey dgedes
thank you!
well than, but now i know what i have to do.
so i think for some project's i can use the RDSH in a workgroup, and i think it is supported.
the thing is, i thought i can outsource all my servers to azure, but now with a server for the active directory and one for the rds it ismore expensive :[
or do you know can i use the azure active directory service for this szenario?//www.windowsazure.com/en-us/home/features/identity/
thank you for your fast answer!
Monday, January 7, 2013 8:07 PM
-
5
Sign in to vote
Azzuroo, the License Mode can be set using the Group Policy Editor/Administrative Templates/Windows Components/Remote Desktop Services/Remote Desktop Session Host/Licensing/Set the remote desktop licensing mode.
There are other RDS settings that can be changed through Group Policy as well. It's not as simple and straight forward as it used to be, but it can be done. Hope this helps!
- Proposed as answer by vashekcz Friday, March 29, 2013 9:34 AM
Thursday, February 21, 2013 3:09 PM
-
4
Sign in to vote
So it appears for all the customers that use RDP in a workgroup environment it has become virtually impossible to host a remote application without also having the overhead ofactive directory. If there is a way to configure a remote app in a workgroup setting I need to know. If power shell and hacking the registry is the only way to manage a workgroup RDP server and you can't publish a remote app, most of our clients will be forced to abandon MS for their small business needs or pay someone elseto manage it for them. Please advise.
Friday, May 24, 2013 5:38 PM
-
15
Sign in to vote
I've managed to enable TSConfig in Windows 2012 from older Windows 2008R2 TSConfig. From a Windows 2008R2 server, copy tsconfig.msc and tsconfig.dll [from and to system32 folder] and load this into registry [also exported from 2008R2]:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MMC\SnapIns\FX:{80aaa290-abd9-9239-7a2d-cf4f67e42128}]
"ApplicationBase"=hex[2]:43,00,3a,00,5c,00,57,00,69,00,6e,00,64,00,6f,00,77,00,\
73,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,00,00
"About"="{00000000-0000-0000-0000-000000000000}"
"VersionStringIndirect"="@C:\\Windows\\System32\\umcRes.dll,-107"
"ProviderStringIndirect"=hex[2]:40,00,43,00,3a,00,5c,00,57,00,69,00,6e,00,64,\
00,6f,00,77,00,73,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,\
5c,00,75,00,6d,00,63,00,52,00,65,00,73,00,2e,00,64,00,6c,00,6c,00,2c,00,2d,\
00,31,00,30,00,32,00,00,00
"SmallFolderBitmapIndirect"=hex[2]:40,00,43,00,3a,00,5c,00,57,00,69,00,6e,00,\
64,00,6f,00,77,00,73,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,\
00,5c,00,75,00,6d,00,63,00,52,00,65,00,73,00,2e,00,64,00,6c,00,6c,00,2c,00,\
2d,00,31,00,32,00,30,00,00,00
"NameString"="Remote Desktop Session Host Configuration"
"HelpTopic"=hex[2]:25,00,73,00,79,00,73,00,74,00,65,00,6d,00,72,00,6f,00,6f,00,\
74,00,25,00,5c,00,68,00,65,00,6c,00,70,00,5c,00,74,00,73,00,63,00,63,00,2e,\
00,63,00,68,00,6d,00,00,00
"AssemblyName"="tsconfig"
"RuntimeVersion"="v2.0.50215"
"Description"="Configure Remote Desktop Session Host settings"
"DescriptionStringIndirect"=hex[2]:40,00,43,00,3a,00,5c,00,57,00,69,00,6e,00,\
64,00,6f,00,77,00,73,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,\
00,5c,00,75,00,6d,00,63,00,52,00,65,00,73,00,2e,00,64,00,6c,00,6c,00,2c,00,\
2d,00,31,00,30,00,31,00,00,00
"LinkedHelpTopics"="%systemroot%\\help\\tscc.chm"
"NameStringIndirect"=hex[2]:40,00,43,00,3a,00,5c,00,57,00,69,00,6e,00,64,00,6f,\
00,77,00,73,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,\
75,00,6d,00,63,00,52,00,65,00,73,00,2e,00,64,00,6c,00,6c,00,2c,00,2d,00,31,\
00,30,00,30,00,00,00
"IconIndirect"=hex[2]:40,00,43,00,3a,00,5c,00,57,00,69,00,6e,00,64,00,6f,00,77,\
00,73,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,75,00,\
6d,00,63,00,52,00,65,00,73,00,2e,00,64,00,6c,00,6c,00,2c,00,2d,00,31,00,31,\
00,30,00,00,00
"FxVersion"="2.0.1.7"
"Type"="Microsoft.TerminalServices.Configuration.SnapIn.TSConfigSnapIn, tsconfig, Version=6.1.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"
"FolderBitmapsColorMask"=dword:00000000
"ModuleName"="tsconfig.dll"
"Provider"="Microsoft Corporation"[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MMC\SnapIns\FX:{80aaa290-abd9-9239-7a2d-cf4f67e42128}\NodeTypes]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MMC\SnapIns\FX:{80aaa290-abd9-9239-7a2d-cf4f67e42128}\NodeTypes\{f86e6446-aaff-11d0-b944-00c04fd8d5b9}]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MMC\SnapIns\FX:{80aaa290-abd9-9239-7a2d-cf4f67e42128}\Standalone]
This Works for my Windows 2012 server, including remote configuration for other Windows 2012 servers, but maybe with some limits[reading tsconfig.msc contents it seems that other snap-inextensions are included, but I've have not exported them]. Be careful, maybe Microsoft doesn't support it ;-]
Regards
- Proposed as answer by Rlo8761 Wednesday, February 19, 2014 5:47 PM
Wednesday, February 19, 2014 11:47 AM
-
6
Sign in to vote
Well, last month our board of directors handed down the final word - meet the penguin. The main reason we are migrating everything away from Microsoft is this Remote Desktop Services fiasco. Every time we turn around there seems to be some new aspect of Remote Desktop that we can't utilize anymore without jumping through several new hoops and using some kind of work around to get past Microsoft's Domain Exclusivity. This will cost you [Microsoft] thousands of Server installations on our part. Oh well. I'm sure you'll make lots of money off of someone else.
- Proposed as answer by Michal Sokolowski Tuesday, September 16, 2014 7:02 PM
Friday, May 2, 2014 2:05 PM
-
0
Sign in to vote
Just found this post after looking for much the same. I do not see where in the GPO you can specify users/groups to be allowed to logoff other sessions. I was using a powershell script to do this, which worked very nicely, until I allowed a group of my support folks access. They don't have the ability to run a simple get-rdusersession without being a local admin on each of my rd hosts. I was hoping to delegate to them the ability to logoff sessions, but if they can't even list the users, well, that seems rather hopeless. :[
mpleaf
Friday, May 30, 2014 9:54 PM
-
2
Sign in to vote
great suggestions here and i agree that this is big fail on the part of microsoft. i am able to manage ***some**** setting of my 2012 R2 RDS session host server [ ExmplSrvA ] remotely from a 2008 r2 server [ExmplSrvB ] via the tsconfig.msc...just connect to the remote 2012 r2 server . From ExmplSrvB open tsconfig.msc right click the root of tree in the gui on the left had side and connect to remote desktop session host server. find /browse your remote server ExmplSrvA or type inExmplSrvA . Course this means that you have to keep around a server 2008R2 or win 7 machine... perhaps the tools installed on win 8.1 would also work ? Still testing this.
- Proposed as answer by mpwar Thursday, July 24, 2014 8:07 PM
- Edited by mpwar Thursday, July 24, 2014 8:27 PM
- Unproposed as answer by mpwar Thursday, July 24, 2014 8:27 PM
Thursday, July 24, 2014 8:01 PM
-
9
Sign in to vote
I was able to successfully restore the administrative console on my Windows 2012 R2 servers by following the "hairy" registry technique posted by E6Sistemes and Rl08761. As far as I can tell, 9 developers from Microsoft up-voted Freek Berson's reply [which should be reported as abuse also, in my opinion] and then a Microsoft forum administrator came along and marked it as the answer. Points should have been given to E6Sistemes and Rl08761 for actually solving the user's problem [and not telling them to get over it].
For the record, in addition to TSADMIN.DLL, TSADMIN.MSC, TSCONFIG.DLL, and TSCONFIG.MSC, I also had to copy over WTS.DLL.
SPMSDN's attempt to scare users away from the real answer [just because it involves a registry script]should also be marked as abuse. The configuration console *needs* to be restored so you can examine and adjust the security configuration of Remote Desktop for Administration. Right??? Freek [?] is over here tell us that we need to have Session Collections now?!? Anyone got a license for that?!? Anyone running out to buy one because of this?!?
I just need to securely configure a way [that will pass a Nessus scan]to remote to my server as an administrator. I think Microsoft has their head in the cloud on this one.The combined registry file looks something like this:
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MMC\SnapIns\FX:{80aaa290-abd9-9239-7a2d-cf4f67e42128}]
"ApplicationBase"=hex[2]:43,00,3a,00,5c,00,57,00,69,00,6e,00,64,00,6f,00,77,00,\
73,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,00,00
"About"="{00000000-0000-0000-0000-000000000000}"
"VersionStringIndirect"="@C:\\Windows\\System32\\umcRes.dll,-107"
"ProviderStringIndirect"=hex[2]:40,00,43,00,3a,00,5c,00,57,00,69,00,6e,00,64,\
00,6f,00,77,00,73,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,\
5c,00,75,00,6d,00,63,00,52,00,65,00,73,00,2e,00,64,00,6c,00,6c,00,2c,00,2d,\
00,31,00,30,00,32,00,00,00
"SmallFolderBitmapIndirect"=hex[2]:40,00,43,00,3a,00,5c,00,57,00,69,00,6e,00,\
64,00,6f,00,77,00,73,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,\
00,5c,00,75,00,6d,00,63,00,52,00,65,00,73,00,2e,00,64,00,6c,00,6c,00,2c,00,\
2d,00,31,00,32,00,30,00,00,00
"NameString"="Remote Desktop Session Host Configuration"
"HelpTopic"=hex[2]:25,00,73,00,79,00,73,00,74,00,65,00,6d,00,72,00,6f,00,6f,00,\
74,00,25,00,5c,00,68,00,65,00,6c,00,70,00,5c,00,74,00,73,00,63,00,63,00,2e,\
00,63,00,68,00,6d,00,00,00
"AssemblyName"="tsconfig"
"RuntimeVersion"="v2.0.50215"
"Description"="Configure Remote Desktop Session Host settings"
"DescriptionStringIndirect"=hex[2]:40,00,43,00,3a,00,5c,00,57,00,69,00,6e,00,\
64,00,6f,00,77,00,73,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,\
00,5c,00,75,00,6d,00,63,00,52,00,65,00,73,00,2e,00,64,00,6c,00,6c,00,2c,00,\
2d,00,31,00,30,00,31,00,00,00
"LinkedHelpTopics"="%systemroot%\\help\\tscc.chm"
"NameStringIndirect"=hex[2]:40,00,43,00,3a,00,5c,00,57,00,69,00,6e,00,64,00,6f,\
00,77,00,73,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,\
75,00,6d,00,63,00,52,00,65,00,73,00,2e,00,64,00,6c,00,6c,00,2c,00,2d,00,31,\
00,30,00,30,00,00,00
"IconIndirect"=hex[2]:40,00,43,00,3a,00,5c,00,57,00,69,00,6e,00,64,00,6f,00,77,\
00,73,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,75,00,\
6d,00,63,00,52,00,65,00,73,00,2e,00,64,00,6c,00,6c,00,2c,00,2d,00,31,00,31,\
00,30,00,00,00
"FxVersion"="2.0.1.7"
"Type"="Microsoft.TerminalServices.Configuration.SnapIn.TSConfigSnapIn, tsconfig, Version=6.1.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"
"FolderBitmapsColorMask"=dword:00000000
"ModuleName"="tsconfig.dll"
"Provider"="Microsoft Corporation"
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MMC\SnapIns\FX:{80aaa290-abd9-9239-7a2d-cf4f67e42128}\NodeTypes]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MMC\SnapIns\FX:{80aaa290-abd9-9239-7a2d-cf4f67e42128}\NodeTypes\{f86e6446-aaff-11d0-b944-00c04fd8d5b9}]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MMC\SnapIns\FX:{80aaa290-abd9-9239-7a2d-cf4f67e42128}\Standalone]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MMC\SnapIns\FX:{3FCE72B6-A31B-43ac-ADDA-120E1E56EB0F}]
"ApplicationBase"=hex[2]:43,00,3a,00,5c,00,57,00,69,00,6e,00,64,00,6f,00,77,00,\
73,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,00,00
"About"="{00000000-0000-0000-0000-000000000000}"
"VersionStringIndirect"="@C:\\Windows\\System32\\umcRes.dll,-106"
"ProviderStringIndirect"=hex[2]:40,00,43,00,3a,00,5c,00,57,00,69,00,6e,00,64,\
00,6f,00,77,00,73,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,\
5c,00,75,00,6d,00,63,00,52,00,65,00,73,00,2e,00,64,00,6c,00,6c,00,2c,00,2d,\
00,31,00,30,00,32,00,00,00
"NameString"="Remote Desktop Services Manager"
"HelpTopic"=hex[2]:25,00,73,00,79,00,73,00,74,00,65,00,6d,00,72,00,6f,00,6f,00,\
74,00,25,00,5c,00,68,00,65,00,6c,00,70,00,5c,00,74,00,73,00,5f,00,6d,00,61,\
00,6e,00,61,00,67,00,65,00,72,00,2e,00,63,00,68,00,6d,00,00,00
"AssemblyName"="tsadmin"
"RuntimeVersion"="v2.0.50215"
"Description"="Manage Remote Desktop Services sessions"
"DescriptionStringIndirect"=hex[2]:40,00,43,00,3a,00,5c,00,57,00,69,00,6e,00,\
64,00,6f,00,77,00,73,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,\
00,5c,00,75,00,6d,00,63,00,52,00,65,00,73,00,2e,00,64,00,6c,00,6c,00,2c,00,\
2d,00,31,00,30,00,34,00,00,00
"LinkedHelpTopics"=hex[2]:25,00,73,00,79,00,73,00,74,00,65,00,6d,00,72,00,6f,\
00,6f,00,74,00,25,00,5c,00,68,00,65,00,6c,00,70,00,5c,00,74,00,73,00,5f,00,\
6d,00,61,00,6e,00,61,00,67,00,65,00,72,00,2e,00,63,00,68,00,6d,00,00,00
"NameStringIndirect"=hex[2]:40,00,43,00,3a,00,5c,00,57,00,69,00,6e,00,64,00,6f,\
00,77,00,73,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,\
75,00,6d,00,63,00,52,00,65,00,73,00,2e,00,64,00,6c,00,6c,00,2c,00,2d,00,31,\
00,30,00,33,00,00,00
"IconIndirect"=hex[2]:40,00,43,00,3a,00,5c,00,57,00,69,00,6e,00,64,00,6f,00,77,\
00,73,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,75,00,\
6d,00,63,00,52,00,65,00,73,00,2e,00,64,00,6c,00,6c,00,2c,00,2d,00,31,00,31,\
00,31,00,00,00
"FxVersion"="2.0.1.7"
"Type"="Microsoft.TerminalServices.Monitor.SnapIn.TSManagerSnapIn, tsadmin, Version=6.1.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"
"FolderBitmapsColorMask"=dword:00000000
"ModuleName"="tsadmin.dll"
"Provider"="Microsoft Corporation"
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MMC\SnapIns\FX:{3FCE72B6-A31B-43ac-ADDA-120E1E56EB0F}\NodeTypes]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MMC\SnapIns\FX:{3FCE72B6-A31B-43ac-ADDA-120E1E56EB0F}\Standalone]=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
- Edited by JeffTheDotNetGuy Thursday, September 4, 2014 7:20 PM code wasn't wrapping; hard to copy and paste
- Proposed as answer by JeffTheDotNetGuy Thursday, September 4, 2014 7:24 PM
Thursday, September 4, 2014 7:18 PM
-
13
Sign in to vote
Hi All
After trawling the internet searcing for answers I finally found it - you need to do the following:
Run gpedit.msc
Local Computer Policy -> Computer Configuration -> Administrative Templates -> Windows Components -> Remote Desktop Services -> Remote Desktop Session Host -> Licensing
"Use the specified RD license servers" = %myservername%
"Set the Remote Desktop licensing mode" = set your desired option
Hope this helps some of you
Richard
- Proposed as answer by Tioust31 Tuesday, October 20, 2015 8:08 AM
Wednesday, June 10, 2015 8:09 PM
-
0
Sign in to vote
That helped me a lot and it worked for me, thank you so much!
Friday, December 4, 2015 9:00 PM
-
0
Sign in to vote
Cheers Richard. Thanks for the share. Easy, safe, no hack.
Perth, Western Australia.... mate :]
Wednesday, April 20, 2016 5:33 AM
-
0
Sign in to vote
Mate! this was the answer I was looking for.
works for Server 2016 as well, installed the remote desktop licencing manager, added cals and then was able to set itself as its own licencing server, and I didn't have to join any domains or require an AD server to do so.
You saved me a headache!
Saturday, November 12, 2016 10:35 PM
-
0
Sign in to vote
Richard,
Thanks, adjusting in gpedit.msc was a lot easier than some of the other solutions on here. Just wish we could mark it as the REAL answer.
Thursday, March 9, 2017 9:36 PM
-
0
Sign in to vote
Just wanted to say this was a very comical read. Hundreds of standalone Windows Servers? I hope everyone here realizes now how ridiculous that sounds.
Tuesday, January 16, 2018 8:47 AM
-
0
Sign in to vote
i am still not rejoicing..
I have a stand-alone DC 2012 R2 with RemoteApps and standard RDS clients connecting to it.
Everything seemed all right while all clients were Windows 7. With the advent of Windows 10 it turned out
that SOME users work perfectly with W7 but get "wrong password" if connection is attempted from a Windows 10 station. I played several days with all possible settings including the above mentioned to no avail. The interesting thing is that the accounts which are bad for Win10 are also bad for WebAccess.
Finally I simply changed the password of a "bad" account and it started to work with Win 10! Then I discovered that it is not just password but the combination of username/password. And finally some combinations proved to be good for Win10 but bad for Win7.
So at this point the only solution in hand for me is to try and find successful combinations for users!
Can anybody shed some light on the phenomenon ?
- Edited by Shlomo Vinishsky Sunday, March 18, 2018 6:43 PM
- Proposed as answer by tridexsteve Thursday, June 28, 2018 4:10 PM
- Unproposed as answer by tridexsteve Thursday, June 28, 2018 4:10 PM
Sunday, March 18, 2018 6:41 PM
-
0
Sign in to vote
If you think server 2012 was bad. Wait till you try to use 2019. The crippling of the Essentials Server edition or the Essentials component is a show stopper for all my clients. 2016 is the end of the road for any MS server recommendation. Not everyone out there wants to run O365. In fact there are companies that don't want to be "online" 24/7, especially to run apps and server OS's.
Staple Bench Computers
Thursday, July 11, 2019 12:51 AM