Overview:
In order to optimise the system speed and responsiveness we recommend either using the application directly on the server or publishing the application only to the users desktop. This manual is for reference purposes. Individual setups may differ depending on the existing IT landscape.
1. Set Up RemoteApp Program on the RDS Server
Install Remote Desktop Services (RDS):
Install the necessary RDS roles on your server, such as Remote Desktop Session Host and Remote Desktop Connection Broker.
2. Publish the Application
2.1. Open the Server Manager on the RDS server.
2.2. Go to Remote Desktop Services -> Collections.
2.3. Select the collection where you want to publish the application.
2.4. Click on Tasks and select Publish RemoteApp Programs.
2.5. Manually navigate to the UNC path of OPTO.exe which will be the directory where Opto is.
3. Generate the RDP File
Once the application is published as a RemoteApp, you can generate an RDP file for users to access it.
3.1. Open Server Manager on the RDS server.
3.2. Navigate to Remote Desktop Services -> Collections.
3.3. Select the collection where your RemoteApp is published.
3.4. Click on the RemoteApp Programs tab.
3.5. Find the RemoteApp program (your executable) that you want to create an RDP file for.
3.6. Right-click the RemoteApp and select Create .rdp File.
4. Configure and Save RDP File
When you create the RDP file, you’ll have the option to configure several settings:
Specify a Location to Save the RDP File:
Choose a folder on your server or network share where the RDP file will be saved.
Customize the RDP File Settings:
4.1. Remote Desktop Gateway Settings: If using an RD Gateway, configure the gateway settings in the RDP file.
4.2. Security Settings: Customize the security settings, such as authentication level.
4.3. Other RDP Settings: You can also configure additional settings like screen resolution, local resource redirection (e.g., printers, drives), and more.
4.4. Save the RDP File: Once configured, save the RDP file. This file can now be distributed to users.
5. Distribute the RDP File to Users
Now that you have the RDP file, you can distribute it to users in several ways:
Email: Send the RDP file as an attachment in an email.
Network Share: Place the RDP file on a network share where users can access it.
Group Policy: Use Group Policy to automatically place the RDP file on users’ desktops.
Company Intranet: Host the RDP file on a company intranet page where users can download it.
6. User Access
Users can access the RemoteApp by double-clicking the RDP file. This will open a connection to the RDS server, and the published application will launch as if it were running locally on their desktop.
7. Example RDP File Content
If you need to manually create or edit the RDP file, it might look something like this:
redirectclipboard:i:1
redirectprinters:i:1
redirectcomports:i:0
redirectsmartcards:i:1
devicestoredirect:s:*
drivestoredirect:s:*
workspace id:s:YOUR_WORKSPACE_ID
loadbalanceinfo:s:tsv://MS Terminal Services Plugin.1.YOUR_COLLECTION_NAME
remoteapplicationmode:i:1
alternate shell:s:||YOUR_APP_ALIAS
remoteapplicationprogram:s:||YOUR_APP_ALIAS
remoteapplicationname:s:Your App Name
remoteapplicationcmdline:s:full address:s:YOUR_RDS_SERVER_NAME
YOUR_WORKSPACE_ID: Replace with your workspace ID if applicable.
YOUR_COLLECTION_NAME: The name of the collection where the app is published.
YOUR_APP_ALIAS: The alias you defined when you published the app.
YOUR_RDS_SERVER_NAME: The name of the RDS server.
This file can then be saved with a `.rdp` extension and used by users to access the RemoteApp.
Opto Software Pty Ltd Created: 12/08/24
