Terminal Server Installation
1. Check Access to the Add-In
To set up the add-in the user must have access to the add-in (xll file). For example: \\yourserver\addins\
2. Check Registry Settings
Furthermore, a registry entry must be set in “HKEY_CURRENT_USER”.
The following key contains the path to the add-in:
There can be one or more “OPEN” keys OPENx= / R “<path_to_.xll>”
See example: “OPENx” in the above key may have one or more “OPEN” key values.
One for each add-in. The following count applies:
e.g.: OPEN = Path to add-in 1 OPEN1 = Path to add-in 2 OPEN2 = Path to add-in 3 you can put the add-in in a different place that every user has access to,
then every user has to set the registry entry in which this path is referenced.
Create a new <<“String / Zeichenfolge”>>
<…path to …\AnalyticsGate_x64.xll>
If the .xll file is in the path „C:\Users\%USERNAME%\AppData\Roaming\Microsoft\AddIns“ – then an indication without a path is enough.
If the add-in is on a different path, it must be specified as well (for example, “C:\QlikShare\Add-Ins”)
3. Check Office Versions
- Office 2013 → 15.0 “HKEY_CURRENT_USER\Software\Microsoft\Office\15.0\Excel\Options”
- Office 2016 and newer → 16.0 “HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Excel\Options”
4. Create a New Group Policy
If no add-in is registered yet, the value (string) “OPEN” must be created. If one or more add-ins already exist, a value (string) “OPEN1 … etc. OPENx” must be created, with x beeing the next number to use (for example, “OPEN4” if Sense Excel is the 4th add-in)
Update a version:
Our add-in carries the version number in its name. This can be unfavorable for you: if you want to provide the users with a new version, you always have to adjust the registry.
Therefore, the version number part of the file name and the registry entry can be removed:
“AnalyticsGate_x64.xll” or “AnalyticsGate_x86.xll”
This has the consequence that the registry entry only needs to be set once, and to update the add-ins only the xll must be overwritten via copy and paste.