• Not Answered

Workstation is not running a Remote Client operating system. V14.3 Server 2016

I setup all my servers. I setup up my terminal servers as operator station as remote client server.  I downloaded the terminal servers. Then I set them up for to have remote client functionality. I exported this configuration file and ran workstation config on the terminal servers.

I try to download the terminal servers and get the following

1-ERROR: DO NOT DOWNLOAD WORKSTATION
Doing so will cause this workstation to become un-configured.

This workstation is not running a Remote Client operating system or the Terminal Service is not installed.....

I installed the remote desktop services (terminal service) according to how we set up all our machines in the past and checked against the KBA for Server 2016 and it was done the same. I also logged into a different plant and checked all the settings there... Exactly the same as far as anything we ever change.  Is there an issue with version 14.3 where Remote Desktop Services has to be installed prior to installing DeltaV?  This would be a new revelation.

Thanks

6 Replies

  • Installation of Remote Desktop role has always been a prerequisite to installing DeltaV software for the Remote Client.

    v14 BOL:

    v11 BOL:

    As far as I can remember, RDS or Terminal Server always required to be installed prior to installing DeltaV.

    Andre Dicaire

  • In reply to Andre Dicaire:

    The Terminal Server, now called RD server, is configured as a Workstation, and licensed as a Base Station (not Operator Station). the individual RDP sessions are licensed according to need (view only, Zero Span, full Span, Engineering etc.)

    I always get caught on this, but be sure you assign the required plant areas to each Client Session to get write access privileges in DeltaV. :-)

    Andre Dicaire

  • In reply to Andre Dicaire:

    Okay, let me clarify. We do enable the roles and features prior to DeltaV. I was referrring to the licensing and a few other settings. So, that shouldn't be our issue.
  • In reply to TreyB:

    A new feature in Server 2016 is that even though you add the RD Server role the services associated with it are set to Disabled (maybe not all of the time but frequently).  Check your Remote Desktop services to make sure they aren't disabled.  Should be 4 services set as shown below:

  • In reply to Scott Thompson:

    yep, those are all running
  • to expand on the problem. . . I have noticed that in RDP Licensing Diagnoser it showed all other servers as being not available... I reran workstation configuration with the terminal servers set up for remote client functionality. This fixed that issue on the terminal servers, however, the original problem with not being able to download remains. My Proplus and AS still have all the other servers showing as not available/no connectivity. There are not changes I made to the configuration for the Proplus or the AS, but I decided to try running workstation configuration again on them but that did not resolve the Diagnoser issue on these.