Skip to Content
Last modified by Tobias Wintrich on 2025/10/10 13:44
Show last authors
1 {{info}}
2 This HowTo was created and tested with the following versions:
3
4 * Firmware Version x64 13.00 Build 119 
5 * FreeRDP 3.17 13.00 Build 005 
6 * ThinCast 1.1 13.00 Build 015
7 {{/info}}
8
9 {{toc/}}
10
11 ----
12
13 = Server Environment =
14
15 This article was tested with a Windows Server 2022 system configured with various applications shared via RemoteApp.
16
17 {{warning}}
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”**. 
21
22 If this policy is set to **“Disabled”**, it can result in an increased number of visual artifacts within the RemoteApp session.
23 {{/warning}}
24
25 [[image:1760094711652-938.png]]
26
27 = Thincast / FreeRDP Configuration =
28
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.
31
32 {{info}}
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.
35 {{/info}}
36
37 [[image:1760096644329-227.png]]
38
39 {{warning}}
40 When using the **ThinCast Client**, the option **“GFX-Small Cache”** must be enabled.
41 Without this option, the connection will not start.
42 {{/warning}}
43
44 All other connection parameters can be configured as for a standard RDP connection.
45
46 == Alias Mode ==
47
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**.
50
51 [[image:1760095707226-355.png]]
52
53 == Exe Mode ==
54
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**.
58
59 {{info}}
60 **Path Input Note**
61
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. 
64
65 Instead, use an environment variable, for example:
66 **“%HOMEDRIVE%\MyProgram.exe”** 
67
68 Applications located in the System32 directory can be launched without specifying a path.
69 {{/info}}
70
71 **Example entries for Exe mode:**
72
73 * %ProgramFiles%\Windows NT\Accessories\wordpad.exe 
74 * notepad.exe 
75 * %ProgramFiles(x86)%\Microsoft\Edge\Application\msedge.exe 
76
77 The result after connection setup is identical to that of **Alias** mode.
78
79 == Shell Mode ==
80
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.
83
84 The application path can be defined in two ways:
85
86 1. By specifying the full path (as in **“Exe”** mode), or
87 2. By using the alias name prefixed with **“||”**
88
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 
95 * ||msedge
96
97 [[image:1760095922684-297.png]]
98
99 = Black Borders / Transparency in Seamless Mode =
100
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.
104
105 [[image:1760096191902-367.png||height="352" width="500"]]
106
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.