Access to a single program / remote app

To continue you need at least one app license. Have you already activated one?

If you have already connected your server in oneclick™ and want to publish it as a Remote App or single application, make sure to configure all relevant settings in advance for optimal delivery.

If you want to create a Remote App (for example, from a Windows 10 environment), we recommend using the RemoteApp Tool by Kimmknight for a straightforward and efficient setup.

1. Click on the + Icon to create a new app configuration.
2. Select the app license you want to use for this configuration and click Next. Keep in mind that a group license (Pay-Per-Use) can only be assigned to groups later. Individual licenses (Pay-Per-License) can later only be assigned to individual users. You can recognize a group license by the ∞ sign under Availability.
3. In the next step you can select the appropriate configuration type (Single Program) for accessing your resources.
4. Select the destination pool to whose destinations you want to connect to and click Next. Note that you can only access the destinations in a pool you picked that supports the protocol you are about to select in the next step.
5. In the next step change the settings for access.

   • Assign a name for your configuration which you can relate to your destinations.

   • Optionally you can customize connection settings for special use cases (e.g. for using a gateway server).

   • If you set the encryption method to TLS or RDP, you can start the remote app without entering your user data. Your login information is then entered directly via the Windows login window.

   • You can optionally enter an Active Directory domain. If you select “TLS” as the encryption method here, an Active Directory domain must be entered!

   • The option “Allow user to change destination” is enabled by default. If you do not want your users to change the destination independently, disable the corresponding toggle. If you are unsure, you can also restrict the permission later.

   • Entering login data from a user is disabled at default at app started.

     • In this case, you as the administrator must store the credentials for the destination in the step App Instances or you may assign the app to Professional users only, with the option to edit app settings on the tile.
     • For users who should enter their data themselves, we recommend to allow entering the login data when starting the app and saving it, if necessary.
     • Optionally, you can enable the system to keep the login data in an app instance or on the desk tile when switching the destination. This prevents the data from being deleted from the fields when switching.

   • You can optionally customize the settings for using. Here you define how the image of your destination system is transferred, which keyboard layout is used and whether the user is allowed to change these settings independently.

   • Choose whether you want to start a Remote App or perform a remote start of an unlisted program.

     • Enter the alias of the Remote App. Make sure to insert the following two dashes in front of the name: ||
     • Optionally, you can provide the path and command line parameters as well.

   • Select policies if you want to provide extra security for access to apps with this app configuration.

   • For Professional users, you can color customize the tile on the Unified Workspace, change the label and set the icon.

     • You can choose which controls are displayed on the tile. The following controls can be displayed depending on the type of connection: If you do not want the user to be able to use the gear: Edit app settings, make sure to prohibit the "Change password" on the linked remote desktop.
     • Decide whether the name of the destination should also be displayed on the tile.

   • Click on Save. The configuration is now created.

6. Create an app instance for all users who should have access.
7. Note that you give your users few hints for minimizing when using the Remote App.