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:
https://github.com/binarymaster/rdpwrap/blob/master/res/rdpwrap.ini

Just replace old INI file and restart TermService. Maybe it will help.

And you may try this app:
http://www.kimknight.net/remoteapptool

Some users told that it works with RDP Wrapper, see posts #141 and #145:
http://forums.mydigitallife.info/threads/55935?p=977269

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:
GetInstanceOfRemoteConnectionManager
CConnectionEx::ProcessData
FindConnectionHandler failed: 0x800710d8 in CRCMConnDispatchManager::HandleConnection

Maybe this could help you?

I researched a bit these things...

RemoteApp requires these files:
%SystemRoot%\system32\rdpinit.exe
%SystemRoot%\system32\rdpshell.exe
%SystemRoot%\system32\TSErrRedir.dll
%SystemRoot%\system32\tspubwmi.dll
%SystemRoot%\system32\wbem\tsallow.mof
%SystemRoot%\system32\spp\tokens\ppdlic\terminalservices-remoteapplications-clientsku-ppdlic.xrm-ms

tspubwmi.dll can be installed via RegSvr32
tsallow.mof can be installed via mofcomp

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]
"Name"="Remote Applications Terminal"
"SessionSource"=dword:00000001

...still no success
I only know that the "problem" is somewhere inside termsrv.dll

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\ConnectionHandler\eddcc3ce-6e7e-4f4b-8439-3d9ad4c9440f]
"CLSID"="2be8bdbb-be09-499d-9a4b-4637e09ae00b"
"Description"="Default Connection Handler"
"Name"="Default Connection Handler"
"fAcceptConnection"=dword:00000001

Adding this registry key helped me to get a new session when connecting in RemoteApp mode.
But rdpinit.exe was not started and session closed immediately.

Hello,

Thank you for your time. I will put another program as rdpinit.exe and/or use the Win 7 Ultimate edition.
For me, you can close this issue.

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:

• KB961742 (turns on RemoteApp on Windows XP)
• KB961741 (on Windows Vista)

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:
0000568E: 04 01
0000568F: 40 00
00005691: 80 00
This is return value of checking ...ClientSku-RAILAllowed policy. Assuming that policy is missing.

Windows 10 x64 One Language - RemoteApp is not working (Version 1.6).
RDP working normally

Can anybody provide working solution for RemoteApp without installing Windows Ultimate?

Great, great library, thanks!
Will RemoteApp be supported officially sometime?

@neggenbe maybe sometime.

If someone offers a patch for termsrv, which overcomes this issue, I'll implement it in the wrapper and for each possible version in INI file.

Currently we have some achievements in this thread, but there's not enough to get it fully working.

ok great, thanks.
Another topic - Is there any discussion about conflicts with Windows licence terms and so on?

Another topic - Is there any discussion about conflicts with Windows licence terms and so on?

#26

@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?
Shouldn't it 1 byte value to change in HEX? Or am I wrong?

@trockenasche:
these are old byte->new byte. This is return value of function which checks for TerminalServices-.....-RAILAllowed policy. With this patch, the function retruns 0x01 instead of 0x80004004

Could you please give a short summary about the requirements that are required to get remote app working in case of Windows10?
What registry keys are required? What DLLs/EXEs need to be modified?

I have understood that

• termsrv.dll needs the usual treatment to allow multiple connections or connections at all.
• rdpinit.exe needs the above patch to override the police check for TerminalServices-RemoteApplications-ClientSku-RAILAllowed. above patch
• registry addition frmo above

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?
My version is 10.0.14393. I am on the slow update ring. So no INSIDER preview builds, but all updates installed.

RemoteApp is working in Pro/Ent. It is not working with Home/One Language
(like RDP itself)

8 Ноя 2016 г. 20:17 пользователь "chrwick" [email protected]
написал:

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 for me there is was no patching necessary!

Did MS change something with the latest updates?

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#13 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AIQ7O8WGELYtjFkxFaNRpMPNNtIEif1Rks5q8K7DgaJpZM4DIAQE
.

@AlexeiScherbakov that is not correct - by default RemoteApp only works on Ent/Ult/Edu versions, not Pro.

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!

@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
Wrapper ver. 1.5.0.0
Service ver. 10.0.18362.657