-
Notifications
You must be signed in to change notification settings - Fork 3.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enable RemoteApp #13
Comments
Well, RDP Wrapper doesn't provide RemoteApp features officially. If you're wondering about "TerminalServices-RemoteConnectionManager-AllowAppServerMode" policy value, I don't know how it will work in non-server editions. So actually it's not an issue. About Debug Messages, you can try to intercept that function to catch text messages into log file. I tried to do that but the function differs between termsrv releases. To turn it on without hacks, maybe you need to boot Windows in debug mode and attach it to WinDbg. |
Also I updated config file, added more policy values: Just replace old INI file and restart TermService. Maybe it will help. |
And you may try this app: Some users told that it works with RDP Wrapper, see posts #141 and #145: |
Hello, Thank you for your help. As said on DigitalLife forums, RemoteApp is working fine with W7 Ultimate, however it is not working wit Win 7 Pro (or lower edition). By trial and error I can go to these errors in termsrv.dll: Maybe this could help you? |
I researched a bit these things... RemoteApp requires these files: tspubwmi.dll can be installed via RegSvr32 Also rdpinit.exe requires TerminalServices-RemoteApplications-ClientSku-RAILAllowed policy I tried to install it but however not succeeded. |
Also tried to import this registry key: [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\TerminalTypes\eddcc3ce-6e7e-4f4b-8439-3d9ad4c9440f] ...still no success |
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\ConnectionHandler\eddcc3ce-6e7e-4f4b-8439-3d9ad4c9440f] Adding this registry key helped me to get a new session when connecting in RemoteApp mode. |
Hello, Thank you for your time. I will put another program as rdpinit.exe and/or use the Win 7 Ultimate edition. Out of curiosity, how did you find those registry keys? Are they somewhere in termsrv.dll ? Thank you again! |
First of all I compared "Terminal Server" registry keys between Professional and Ultimate editions. Also I researched these updates:
Ok. Feel free to reopen this issue if needed. |
I'm also having some RemoteApp issues with Windows 10 TP2 build 9926. Before the update I was staying with 9874 and everything runs smoothly. Now RemoteApp refuses to start initially, but once a full rdp session is established, it restores functionality. Maybe, I guess they have brought in yet another jmp instruction for us to patch under certain circumstances.. :-D |
Enable RDP -> Programs -> "Start the following program on conection" Regedit: Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services]
"fAllowUnlistedRemotePrograms"=dword:00000001
;"fTurnOffSingleAppMode"=dword:00000000
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Terminal Server\TSAppAllowList]
"HonorLegacySettings"=dword:00000001
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server]
"HonorLegacySettings"=dword:00000001 |
binarymaster, except all things that you mentioned, you have to patch rdpinit.exe (1.7601.17514) with following: |
Windows 10 x64 One Language - RemoteApp is not working (Version 1.6). Can anybody provide working solution for RemoteApp without installing Windows Ultimate? |
Great, great library, thanks! |
@neggenbe maybe sometime. If someone offers a patch for Currently we have some achievements in this thread, but there's not enough to get it fully working. |
ok great, thanks. |
|
@sharo1k I tried to patch the rdpinit.exe with a hex editor, but I don't get it why you have a 2 byte value? |
@trockenasche: |
Could you please give a short summary about the requirements that are required to get remote app working in case of Windows10? I have understood that
Anything else? |
Just for your info. Today I have tried to use the RemoteApp feature of my new clean Windows 10 Pro 64-Bit installation. I haved used the RemoteApp tool from Kim Knight to configure some programe for remote usage (notepad.exe, cmd.exe). I was able to connect to my Windows 10 Pro using the terminal service client that comes with Windows 7 Pro and using the generated RDP file. The was no closing of the connection or similar things. It just works. A single app window shows up on the client. From the CMD.exe window I was able to start other single window apps as well which were not included in the RemoteApp tool list. I had set the host option to allow unlisted apps. I have used Windows 10 Pro 1607 64-Bit German ISO from Microsoft. As license key I have used my Windows 7 Pro (SystemBuilder) key which I have chosen to upgrade to Windows 10 Pro during MS free offer. I had entered the license key AFTER the installation was finished and not right at the beginning (don't know if that matters!). So here in my case there were no modifications necessary! Did MS change something with one of the latest updates? |
RemoteApp is working in Pro/Ent. It is not working with Home/One Language 8 Ноя 2016 г. 20:17 пользователь "chrwick" notifications@github.com
|
@AlexeiScherbakov that is not correct - by default RemoteApp only works on Ent/Ult/Edu versions, not Pro. |
Hm, that is iteresting. I don't know about education version...
30 Ноя 2016 г. 2:13 пользователь "tostercx" <notifications@github.com>
написал:
… @AlexeiScherbakov <https://github.com/AlexeiScherbakov> that is not
correct - by default RemoteApp only works on Ent/Ult/Edu versions, not Pro.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#13 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AIQ7OxM2zUJ3cL5n6p91HylgAjDO5_b4ks5rDLGwgaJpZM4DIAQE>
.
|
Excuse me, it seems most of the comments are focused on non-server Windows OS. My question is, How do I get remote-app functionality on server-2016?
Thanks folks! |
Rdpwrap is only needed on home/one-language versions of windows.
Server systems have this functional by default (2 admin sessions) and with
Remotw Desktop Services(req. terminal server licences). But this server
must be member in domain to enable RemoteApp
6 Дек 2016 г. 15:32 пользователь "Ahmed Kamal" <notifications@github.com>
написал:
… Excuse me, it seems most of the comments are focused on non-server Windows
OS. My question is, How do I get remote-app functionality on server-2016?
- Should I just install rdpwrap+kim's tool ?
- Would trying to install a full RDSH setup, with rdpwrap be a good
idea?
Thanks folks!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#13 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AIQ7OyQ86v5gyEbJ9TF0gAv21J1auCnTks5rFVXwgaJpZM4DIAQE>
.
|
@kim0 try it yourself, maybe it will work out-of-the-box with installed RDP Wrapper. |
I actually played with it, and it seemed to work. The server is a test domain controller, and I was able to connect 5+ users to it concurrently. I also tested the remote-app software recommended in another ticket, which also worked beautifully. So great work folks I guess! I guess the readme should make it clear that it works equally well on server OSs. |
My users are not able to connect after 15 concurrent sessions. |
My users cannot connect after there are 15 simultaneous sessions, how can this problem be solved? my configuration is as follows |
Hello,
I can see in your code that you change some variables for RemoteApp, so I tested RemoteApp on Windows 7 Pro x86 (6.1.7601.18637).
However, this is not working at all.
Full Desktop remote sessions are working fine, but RemoteApp not.
Do you have any idea on how this could work ?
Also, do you know how to activate Debug Messages for termsrv.dll ? I wanted to help you, but I cannot see these Debug Messages with WinDbg...
The text was updated successfully, but these errors were encountered: