Hi,

I downloaded the zip with the binaries rdpx.v0380.zip but when I extract it I get a message from Microsoft Security Essentials regarding a Medium level threat 'Win32/Uwamson.A!ml'.

Is this a false positive?

After you have edited a RemoteApp, it does not.

Hi Kim,

I cant thank you enough for this amazing piece of software. Its very well written and secured as well. I was just wondering like could you help me display the logged in windows username and the original source ip the connection is comming from in the rdpx cmd? at the moment, it shows very important log, but instead of showing the source Ip it shows my router IP whenever i access from WAN and it would be nice to see the logged in username as well. Please let me know.

Hello,

Could you please help me to hide the main settings icon and app settings icons. I am using this program as the main source for hosting apps with rdpwrapper and we are happy with it. But unfortunately users started playing with the settings and ACL is not strong here. I tried playing with the HTML file, CSS and nothing seems to hide the settings. Also could you please guide me to create my own SSL using letsencrypt or certbox using NGINX. I tried several times and no luck. Much appreciated for your wonderful program and contributions and would highly appreicate your prompt response.

Hi,
Firstly congratulations on a wonderful tool that you have made and launched on GitHub. very helpful.

If I add the machine to a domain, add the RDS Role, connection broker, Add a Remote app collection and then use a published app, I can get the connection to the app (and not the full Remote desktop) exactly like i want it using the syntax below with the hashed password etc..

https://myserver/Myrtille/?__EVENTTARGET=&__EVENTARGUMENT=&server=server&domain=domain[optional]&user=user&passwordHash=passwordHash&program=program[optional]&width=width(px)[optional]&height=height(px)[optional]&connect=Connect%21

But I can avoid all the lengthy setup of RDS role, adding to domain, connection broker etc. and make a simple registry entry to get the remote app defined.

I can just add registry entries for the apps i want to publish - like in the image below.

Now if I call this program that i have manually published using the registry entry using a RDP file (like below)- it works like a charm and notepad from the remote server opens on the local machine as a remote app.

allow desktop composition:i:0
allow font smoothing:i:0
alternate shell:s:rdpinit.exe
devicestoredirect:s:*
disableremoteappcapscheck:i:1
drivestoredirect:s:*
full address:s:192.168.86.149
prompt for credentials on client:i:1
promptcredentialonce:i:0
redirectcomports:i:0
redirectdrives:i:0
remoteapplicationmode:i:1
remoteapplicationname:s:Notepad
remoteapplicationprogram:s:||Notepad
span monitors:i:1
use multimon:i:1

The problem is that if i use the API

https://myserver/Myrtille/?__EVENTTARGET=&__EVENTARGUMENT=&server=server&domain=domain[optional]&user=user&passwordHash=passwordHash&program=program[optional]&width=width(px)[optional]&height=height(px)[optional]&connect=Connect%21

and call the same manually published app (from registry that works using the RDP file) we get a full remote desktop and not the remotely published app.

Any great ideas on this. and if I call this URL in a Chrome window as an app, then I can get the window to resize to the size of the remote app window being published.

Hope you got the idea, Thanks in advance.

Please let me know how I can donate to this program.

Add an MSI installer that will unpack files in Program Files and create a task in the scheduler to autorun the web interface.

It is advisable to add an uninstaller.

Hi,

i'm testing rdpx v0380 on Windows 10 Pro latest updates.

I got everything running, can create new RemoteApps and also see existing ones. However, if i'm trying to start a session in the browser (chrome and ff), the .rdp file is downloaded instead of executed in the browser.

What am I doing wrong here?

I have several accounts without administrator rights. Some of these accounts do not have RDP access and have a very simple password.

I decided to try to log into the Web interface under such an account and was able to edit the RemoteApp list (as if I were an administrator).

Please add a check for user rights so that users without administrator rights can only download RDP files and use the WEB channel.

Currently, you will be notified if the Windows edition detected is Home or Core.

This does not cover all incompatible Windows releases, such as Windows 7 or 8 Professional. I ignored these in the first instance because adding detection for Professional would exclude Windows 10 Professional (which is compatible). Compatibility list.

Need to implement detection of incompatible versions and editions in js/winver.js.

After running the app, Windows Defender instantly flags it as a PUP

Hi all,

I've been trying to connect the Remote Desktop App (macOS) to the server for 2 days but the following error always appears.

App Version: Version 10.6.6 (1883)

Decided to deploy rdpx on ports 80 and 443 via IIS URL Rewriting so as not to disable other IIS based sites.
I used a proxy not for the root, but for /RemoteAppX (RAWeb is hosted in /RemoteApp and functions normally)

web.config from /RemoteAppX:

<?xml version="1.0" encoding="UTF-8"?>
<configuration>
    <system.webServer>
        <rewrite>
            <rules>
                <rule name="ReverseProxyInboundRule1" stopProcessing="true">
                    <match url="(.*)" ignoreCase="true" />
                    <action type="Rewrite" url="http://127.0.0.1:8080/{R:1}" />
                </rule>
            </rules>
        </rewrite>
    </system.webServer>
</configuration>

UPD I found the reason (but not the solution):
Requests are coming in correctly.
In the HTML code of the response, the links go as if the proxy was running from the root directory "/".

I am looking for options for replacing the answer ...

IIS URL Rewriting: https://www.iis.net/downloads/microsoft/url-rewrite

Application request routing: https://www.iis.net/downloads/microsoft/application-request-routing

UPD: You can also suggest alternative solutions on how to get rdpx to work on IIS.