Supercharge your Proficy solution! Download a free trial of Proficy Operations Hub, CSense analytics, and more. Explore our Proficy 2024 releases!

Home
Get Started
Get Started Guide
Terminal Server
Getting Started with Remote Desktop Session Host
Before installing Workflow on a Windows^® Server 2008 R2 or computer, you must enable and set up the Windows Remote Desktop Session Host.
Hardware Requirements for Remote Desktop Session Host
The following information describes the recommended hardware requirements for a Remote Desktop Session Host environment.

Workflow IPI
Get Started
- Get Started Guide
  - Installation Requirements
  - Pre-Installation Consideration
  - Installation Procedures
  - Server Clustering Implementation
  - Deploy the Web Task List
  - Log On Overview
  - Post-Installation Configuration
  - Upgrade Workflow
  - Install a Reporting Database
  - Terminal Server
    - Remote Desktop Session Host
      This information is intended for system integrators, IT administrators, and engineers responsible for setting up and optimizing a Workflow Remote Desktop Session Host environment.
    - Remote Desktop Services (Terminal Services)
      With Remote Desktop Services for Microsoft^® Windows^® Server 2008 R2 and Windows^® Server 2012, you can centrally manage and execute Workflow.
    - Getting Started with Remote Desktop Session Host
      Before installing Workflow on a Windows^® Server 2008 R2 or computer, you must enable and set up the Windows Remote Desktop Session Host.
      - Workflow Remote Desktop Session Host Limitations
        The Workflow Remote Desktop Session Host has a number of limitations and assumptions.
      - Hardware Requirements for Remote Desktop Session Host
        The following information describes the recommended hardware requirements for a Remote Desktop Session Host environment.
      - Software Requirements for Remote Desktop Session Host
        Workflow Remote Desktop Session Host requires Workflow and the Windows^® Server 2008 R2 Standard or Enterprise Edition or the Windows^® Server 2012 operating system.
      - Licensing Requirements
        GE Digital recommends that you install your Remote Desktop Session Host on a computer that is not a domain controller. Ensure that you back up the Remote Desktop Session Host licenses regularly to prevent data loss.
      - Enable Windows Server 2008 R2 Remote Desktop Services
        Remote Desktop Services must be enabled on the Windows^® Server 2008 R2 computer that will be used as the Remote Desktop Session Host.
      - Log into a Remote Desktop Session Host from Windows 7
    - Workflow with Windows Remote Desktop Session Host Installation and Configuration
      After enabling Installing Remote Desktop Services and its licensing, you can install and configure Workflow on a Remote Desktop Session Host.
    - Troubleshoot Your Workflow Remote Desktop Session Host Environment
      To successfully troubleshoot your Workflow Remote Desktop Session Host environment, you first need to isolate the source of your problem.
    - Frequently-Asked Questions About Using Workflow with Remote Desktop Session Host
      The following list outlines some of the frequently-asked questions about using Workflow with Remote Desktop Services.
  - ActiveX Task Controls
  - Workflow Task Client
  - Installation Security
  - Troubleshooting Workflow Issues
    This topic describes how to troubleshoot issues that you encounter when working with Workflow.
Tutorials
Orientation
Configure Your Environment
Security
Resource Information and Configuration
Data Administration
Forms and User Displays
Building and Configuring Workflows
eSOP
ActiveX Task Controls
Service Interfaces
Operator Task List in the Workflow Client
Best Practices

Hardware Requirements for Remote Desktop Session Host

The following information describes the recommended hardware requirements for a Remote Desktop Session Host environment.

One 3Ghz CPU for every three clients connected to the Remote Desktop Session Host (minimum)
Note: If the clients are expected to manage high levels of activity, decrease the number of clients per CPU to two.
500MB RAM per client (minimum)