Table of Contents

Installing to a terminal server

TYLER MONROE Updated by TYLER MONROE

When attempting to install any CFS software to a Windows server with Remote Desktop Services (formerly Terminal Services), additional prerequisites are required due to the more complicated permissions associated with this type of network.

CFS does not support installation of our products on terminal servers. Use at your own risk.

Requirements

  1. You must be licensed for the Network version of any CFS software to be able to install it to a Windows server.
  2. You must have access to a server running Windows Server 2016 or later with Terminal Services licensed and enabled.
  3. You must have a Network share that is accessible by all RDP users to store the program's shared database.
    1. If using a mapped drive to point to the database, make sure that all user accounts have the drive letter mapped.
It is possible, however not recommended to keep the database on the local (C:) drive of the RDP server. This will require custom modifications to the permissions on the CFSLib folder. Users (or 'Remote Desktop Users') must have Read, Write, and Modify permissions.

Procedure

TaxTools WorkShop

Follow the procedure outlined in the TaxTools WorkShop Installation Instructions. When installing to a terminal server, the procedure differs from the linked instructions in the following ways:

  1. Perform the installation from the administrator account while logged directly into the server. This will ensure that your changes propagate to all RDP user accounts correctly.

All Other Programs

Follow the procedure outlined in the How do I perform a network installation? When installing to a terminal server, the procedure differs from the linked instructions in the following ways:

  1. Perform the installation from the administrator account while logged directly into the server. This will ensure that your changes propagate to all RDP user accounts correctly.
  2. After installation, ensure that the appropriate user groups have Read, Write, and Modify permissions to the destination location chosen during installation, as well as C:\CFSLib on the server.
Since permissions vary based on your specific network configuration, it is not always sufficient to provide these permissions to the 'Users' group.

Troubleshooting

Error 75 or Error 3050

This error is usually related to incorrect permissions on the CFSLib folder on the network share, but could also be caused by security software running on the server. Try running the program as administrator. Does this fix the issue?

  • If yes, double-check the permissions for the CFSLib directory. All RDP users need to have 'Modify' permissions. Depending on your specific network configuration, RDP users might not be added to 'users' group by default. Add or adjust permissions as required. Check C:\CFSLib as well as the network share.
  • If no, it is more likely that our software is unable to access the directory due to interference from other software on the server. Check any installed antivirus and/or security software on the server, and add exclusions for your CFS software if necessary.

TTW freezing on launch

  1. Check the version of Windows Server that is currently installed on your server. TaxTools WorkShop requires the Microsoft WebView2 runtime which is only compatible with Windows Server 2016 or later.
  2. If you are using a compatible version of Windows Server, follow the instructions in our TaxTools WorkShop freezes on startup article.

'Path not found' error on launch

The program may appear to open correctly, but upon launch displays a message that says 'Path not found.'

Make sure that the shared data directory (as specified during installation) exists and is accessible to RDP users. If using a mapped drive to access the data directory, make sure all user accounts have the drive letter mapped.

'Missing Shortcut' error when trying to launch the program from the desktop shortcut.

If on the RDP user's desktop, the program icon does not display correctly and gives the following error when trying to launch the program, then the current user account is unable to access the shared database location. If you used a mapped drive for the program location during installation, make sure all user accounts have the drive letter mapped

How did we do?

Installing in demo mode

Manual installation of a specific program from a CD

Contact