Skip to Content
Last modified by Tobias Wintrich on 2025/10/10 13:46
From version 3.1
edited by Tobias Wintrich
on 2025/10/10 13:41
Change comment: There is no comment for this version
To version 6.1
edited by Tobias Wintrich
on 2025/10/10 13:46
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,8 +1,8 @@
1 1  {{info}}
2 2  This HowTo was created and tested with the following versions:
3 3  
4 -* Firmware Version x64 13.00 Build 119
5 -* FreeRDP 3.17 13.00 Build 005
4 +* Firmware Version x64 13.00 Build 119 
5 +* FreeRDP 3.17 13.00 Build 005 
6 6  * ThinCast 1.1 13.00 Build 015
7 7  {{/info}}
8 8  
... ... @@ -17,7 +17,7 @@
17 17  {{warning}}
18 18  Ensure that the Group Policy setting **“Use advanced RemoteFX graphics for RemoteApp”** under
19 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”**.
20 +is set to either **“Not configured” (default)** or **“Enabled”**. 
21 21  
22 22  If this policy is set to **“Disabled”**, it can result in an increased number of visual artifacts within the RemoteApp session.
23 23  {{/warning}}
... ... @@ -24,7 +24,7 @@
24 24  
25 25  [[image:1760094711652-938.png]]
26 26  
27 -= FreeRDP / ThinCast Configuration =
27 += Thincast / FreeRDP Konfiguration =
28 28  
29 29  In each **connection configuration**, you have three options for launching a RemoteApp.
30 30  For all three options, the corresponding application must first be published on the server for RemoteApp access.
... ... @@ -34,7 +34,7 @@
34 34  This client provides significantly better image quality and greatly reduces visual artifacts.
35 35  {{/info}}
36 36  
37 -[[image:1760095249199-640.png]]
37 +[[image:1760096644329-227.png]]
38 38  
39 39  {{warning}}
40 40  When using the **ThinCast Client**, the option **“GFX-Small Cache”** must be enabled.
... ... @@ -60,10 +60,10 @@
60 60  **Path Input Note**
61 61  
62 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.
63 +Therefore, a path such as **“C:\MyProgram.exe”** will not work. 
64 64  
65 65  Instead, use an environment variable, for example:
66 -**“%HOMEDRIVE%\MyProgram.exe”**
66 +**“%HOMEDRIVE%\MyProgram.exe”** 
67 67  
68 68  Applications located in the System32 directory can be launched without specifying a path.
69 69  {{/info}}
... ... @@ -70,9 +70,9 @@
70 70  
71 71  **Example entries for Exe mode:**
72 72  
73 -* %ProgramFiles%\Windows NT\Accessories\wordpad.exe
74 -* notepad.exe
75 -* %ProgramFiles(x86)%\Microsoft\Edge\Application\msedge.exe
73 +* %ProgramFiles%\Windows NT\Accessories\wordpad.exe 
74 +* notepad.exe 
75 +* %ProgramFiles(x86)%\Microsoft\Edge\Application\msedge.exe 
76 76  
77 77  The result after connection setup is identical to that of **Alias** mode.
78 78  
... ... @@ -82,15 +82,16 @@
82 82  Instead of the Windows Explorer, only the defined application is executed within the session.
83 83  
84 84  The application path can be defined in two ways:
85 +
85 85  1. By specifying the full path (as in **“Exe”** mode), or
86 86  2. By using the alias name prefixed with **“||”**
87 87  
88 88  **Example entries for Shell mode:**
89 89  
90 -* %ProgramFiles%\Windows NT\Accessories\wordpad.exe
91 -* notepad.exe
92 -* %ProgramFiles(x86)%\Microsoft\Edge\Application\msedge.exe
93 -* ||mspaint
91 +* %ProgramFiles%\Windows NT\Accessories\wordpad.exe 
92 +* notepad.exe 
93 +* %ProgramFiles(x86)%\Microsoft\Edge\Application\msedge.exe 
94 +* ||mspaint 
94 94  * ||msedge
95 95  
96 96  [[image:1760095922684-297.png]]
... ... @@ -105,4 +105,3 @@
105 105  
106 106  To enable a compositor, go to **Desktop → Compositor** and set the option to **“XFWM”**.
107 107  The compositor will start immediately after applying the change, and the black borders will disappear.
108 -