Replicating Auto-Connection Details on Terminal Server Profiles

Replicating Auto-Connection Details on Terminal Server Profiles

Problem:

You are trying to replicate the auto-connection details on load balanced terminal servers or across multiple user profiles without requiring to send out all the details to the users.

Solution:

  1. Configure the auto-connection on an Administrators user profile.
  2. Copy the folder that contains the user.config file : C:\Users\[username]\AppData\Local\Alchemex_(Pty)_Ltd\
  3. Copy that folder to the user's profile you would like to populate with the connection credentials.

The user’s will no longer need to enter the connection credentials.


    • Related Articles

    • Understanding Intelligence Reporting on Terminal Servers

      Intelligence Reporting licensing can be tricky, especially given the different license types and the possible network configurations. In this tip we’re going to look at the case of Citrix and or Terminal Server environments and consider the different ...
    • Using Velixo Reports in Citrix/Terminal Server enviroments

      Overview  This is a best practices guide for installing and configuring Velixo Reports in a Citrix or Terminal Server environment. The document applies to standalone Citrix/Terminal servers and to Citrix server farms. MSI-Based Installation ...
    • Testing Connections and Troubleshooting Connection Errors

      OVERVIEW One of the main functions of the Sage Intelligence software is to connect to a data source(s) and retrieve data; these connections are made through the appropriate ODBC driver(s). Because of this reliance on the ODBC drivers, errors can ...
    • Working with connections in Intelligence Reporting

      Creating New Database Connection A Data Connection holds the relevant connection information to connect to a supported ODBC or OLEDB compliant data source. This data connection object is then used for all connections to this data source. By adding a ...
    • Sharing Report Shortcuts using Intelligence Reporting

      Problem When you create a report shortcut, it creates and points to a file within the AppData directory of the user that created the shortcut, which in turn points to the BICore.exe on the machine. When another user tries to run the report shortcut, ...