Configure Remote ReliaSoft

Remote ReliaSoft allows you to configure SEP to run ReliaSoft desktop applications on one or more remote servers, eliminating the need to install and update software on each client computer. This section describes the minimum requirements for setting up the server(s) and generating a connection file for Remote ReliaSoft.

Requirements

• A Windows server that can be configured with Microsoft Remote Desktop Services (RDS) and RDP RemoteApp, or multiple RDS servers and a “broker” that distributes the requests. When planning your hardware requirements, you can estimate the following typical memory requirements per application per session. For example, a server with 32 GB RAM could support approximately 30 simultaneous ALTA users, or 100 simultaneous Lambda Predict users, and so on.

Application	Estimated Memory Requirement per Session (MB)
ALTA	1000
RGA	1000
Weibull++	900
BlockSim	500
XFMEA	400
RCM++	400
MPC	300
Lambda Predict	300

• Sufficient RDS license seats (purchased from your preferred Microsoft vendor).
• ReliaSoft desktop applications installed and kept up to date on the RDS server(s). Locally hosted licensing is recommended (token-based or floating). If you do not already have a locally hosted license server for ReliaSoft and nCode software, see instructions at https://www.reliasoft.com/locally-hosted-licensing.

Set Up the RDS Server(s) and Create a Connection File

1. Note that this document provides partial instructions focused on the settings that will affect your ability to generate a connection file that can be used within SEP. If you are not familiar with the steps required to install and configure RDS, you may need to consult documentation/support provided by Microsoft.
2. Install the ReliaSoft desktop applications and configure the locally hosted licensing.
3. In the Windows Server Manager, make sure the required RDS roles are installed:

Windows 2016 or 2012	Windows 2008
Remote Desktop Session Host	Remote Desktop Session Host
Remote Desktop Connection Broker	Remote Desktop Services Manager
Remote Desktop Web Access	Remote App Manager

4. In Remote Desktop Session Host, configure your Remote Desktop license (CALs) and any other settings that are appropriate for your implementation.
5. Add the ReliaSoft Launcher as a published RemoteApp program.
   • In Windows 2016 or 2012, in the Windows Server Manager under Remote Desktop Services, create a Session Collection. In the collection, use Publish RemoteApp Programs and follow the wizard. In the Properties window, make sure Parameters is set to Allow any command line parameters.
   • In Windows 2008, follow the wizard in the RemoteApp Manager. Make sure Arguments is set to Unrestricted.
6. Create and save an *.rdp file that contains the connection information for the ReliaSoft Launcher.
   • In Windows 2016 or 2012, open RDWeb (e.g., https://servername/RDWeb) in a web browser (other than Internet Explorer) and save the connection file.
   • In Windows 2008, click the Create .rdp File link in the RemoteApp Manager.

Note: SEP will use the *.rdp file that you provide as a template, and it will add settings that allow the ReliaSoft Launcher to open a specific ReliaSoft application, project and analysis. If your RDS server is configured to use digital certificates, you may need to edit the file (in Notepad or another text editor) before uploading to SEP. Specifically, if a certificate was added to the end of the file, it must be removed.

Enable Remote ReliaSoft

Remote ReliaSoft is now ready to be enabled on the SEP Admin page. (See SEP Admin Page in the SEP help.)