Skip to Content
Last modified by Tobias Wintrich on 2025/10/10 13:46
Hide last authors
tobias 3.2 1 {{info}}
Tobias Wintrich 30.3 2 This HowTo was created and tested with the following versions:
tobias 3.2 3
Tobias Wintrich 30.3 4 * Firmware Version x64 13.00 Build 119 
5 * FreeRDP 3.17 13.00 Build 005 
Tobias Wintrich 28.1 6 * ThinCast 1.1 13.00 Build 015
tobias 3.2 7 {{/info}}
8
Tobias Wintrich 16.1 9 {{toc/}}
10
Tobias Wintrich 17.1 11 ----
12
Tobias Wintrich 30.3 13 = Server Environment =
tobias 3.2 14
Tobias Wintrich 30.3 15 This article was tested with a Windows Server 2022 system configured with various applications shared via RemoteApp.
tobias 3.2 16
Tobias Wintrich 27.1 17 {{warning}}
Tobias Wintrich 30.3 18 Ensure that the Group Policy setting **“Use advanced RemoteFX graphics for RemoteApp”** under
19 **Computer Configuration** → **Administrative Templates** → **Windows Components** → **Remote Desktop Services** → **Remote Desktop Session Host** → **Remote Session Environment**
20 is set to either **“Not configured” (default)** or **“Enabled”**. 
Tobias Wintrich 28.1 21
Tobias Wintrich 30.3 22 If this policy is set to **“Disabled”**, it can result in an increased number of visual artifacts within the RemoteApp session.
Tobias Wintrich 27.1 23 {{/warning}}
tobias 3.2 24
Tobias Wintrich 27.1 25 [[image:1760094711652-938.png]]
tobias 3.2 26
Tobias Wintrich 30.3 27 = Thincast / FreeRDP Configuration =
tobias 3.2 28
Tobias Wintrich 30.3 29 In each **connection configuration**, you have three options for launching a RemoteApp.
30 For all three options, the corresponding application must first be published on the server for RemoteApp access.
Tobias Wintrich 27.1 31
32 {{info}}
Tobias Wintrich 30.3 33 When using the **“Alias”** or **“Exe”** modes, it is strongly recommended to use the **ThinCast Client**.
34 This client provides significantly better image quality and greatly reduces visual artifacts.
Tobias Wintrich 27.1 35 {{/info}}
36
Tobias Wintrich 30.3 37 [[image:1760096644329-227.png]]
Tobias Wintrich 27.1 38
Tobias Wintrich 13.1 39 {{warning}}
Tobias Wintrich 30.3 40 When using the **ThinCast Client**, the option **“GFX-Small Cache”** must be enabled.
41 Without this option, the connection will not start.
Tobias Wintrich 13.1 42 {{/warning}}
tobias 3.2 43
Tobias Wintrich 30.3 44 All other connection parameters can be configured as for a standard RDP connection.
tobias 3.2 45
Tobias Wintrich 30.3 46 == Alias Mode ==
tobias 3.2 47
Tobias Wintrich 30.3 48 In **“Alias”** mode, enter the alias name of the published application in the **“RemoteApp Path/Alias/Shell”** field according to the server configuration.
49 The client will then connect to the application in **seamless mode**.
tobias 3.2 50
Tobias Wintrich 27.1 51 [[image:1760095707226-355.png]]
rangee rangee 8.1 52
Tobias Wintrich 30.3 53 == Exe Mode ==
tobias 3.2 54
Tobias Wintrich 30.3 55 In **“Exe”** mode, enter the application to be launched in the **“RemoteApp Path/Alias/Shell”** field.
56 If required, you can also specify the full path.
57 The client will start the application in **seamless mode**.
tobias 3.2 58
Tobias Wintrich 13.1 59 {{info}}
Tobias Wintrich 30.3 60 **Path Input Note**
tobias 3.2 61
Tobias Wintrich 30.3 62 When using the **ThinCast Client** or **FreeRDP**, the application path must **not contain a colon (:)**.
63 Therefore, a path such as **“C:\MyProgram.exe”** will not work. 
tobias 3.2 64
Tobias Wintrich 30.3 65 Instead, use an environment variable, for example:
66 **“%HOMEDRIVE%\MyProgram.exe”** 
Tobias Wintrich 28.1 67
Tobias Wintrich 30.3 68 Applications located in the System32 directory can be launched without specifying a path.
Tobias Wintrich 13.1 69 {{/info}}
tobias 3.2 70
Tobias Wintrich 30.3 71 **Example entries for Exe mode:**
tobias 3.2 72
Tobias Wintrich 30.3 73 * %ProgramFiles%\Windows NT\Accessories\wordpad.exe 
74 * notepad.exe 
75 * %ProgramFiles(x86)%\Microsoft\Edge\Application\msedge.exe 
tobias 3.2 76
Tobias Wintrich 30.3 77 The result after connection setup is identical to that of **Alias** mode.
rangee rangee 8.1 78
Tobias Wintrich 30.3 79 == Shell Mode ==
rangee rangee 8.1 80
Tobias Wintrich 30.3 81 In **“Shell”** mode, the published application is started in its own session against a black background.
82 Instead of the Windows Explorer, only the defined application is executed within the session.
tobias 3.2 83
Tobias Wintrich 30.3 84 The application path can be defined in two ways:
tobias 3.2 85
Tobias Wintrich 30.3 86 1. By specifying the full path (as in **“Exe”** mode), or
87 2. By using the alias name prefixed with **“||”**
tobias 3.2 88
Tobias Wintrich 30.3 89 **Example entries for Shell mode:**
90
91 * %ProgramFiles%\Windows NT\Accessories\wordpad.exe 
92 * notepad.exe 
93 * %ProgramFiles(x86)%\Microsoft\Edge\Application\msedge.exe 
94 * ||mspaint 
Tobias Wintrich 27.1 95 * ||msedge
tobias 3.2 96
Tobias Wintrich 27.1 97 [[image:1760095922684-297.png]]
98
Tobias Wintrich 30.3 99 = Black Borders / Transparency in Seamless Mode =
Tobias Wintrich 27.1 100
Tobias Wintrich 30.3 101 When running a session in **“Exe”** or **“Alias”** mode in **seamless mode**, black borders may appear around the published applications.
102 This occurs because RangeeOS runs **without a compositor** by default.
103 A compositor is required to correctly render transparency effects, such as window shadows.
Tobias Wintrich 27.1 104
105 [[image:1760096191902-367.png||height="352" width="500"]]
106
Tobias Wintrich 30.3 107 To enable a compositor, go to **Desktop → Compositor** and set the option to **“XFWM”**.
108 The compositor will start immediately after applying the change, and the black borders will disappear.