Troubleshooting: How do I install ArcFM License Manager in a Citrix environment?
Citrix allows you to have profiles for various combinations of ArcFM Applications. For example, ArcFM with Conduit Manager (or Network Adapter), Designer with Conduit Manager (or Network Adapter), ArcFM alone, Designer alone. You could also restrict access to users in a specific group to prevent anyone from accidentally checking out the wrong license. The following example sets up several profiles that allow users access to ArcFM, Designer, and/or Conduit Manager based on privileges.
- Set up three Citrix groups, one called "Designer" one called "ArcFM" and another called "ConduitManager." The published applications in metaframe are organized into folders "ArcFM" and "Designer." Users who belong to the Citrix Designer group can see the "Designer" folder, which can have specific applications they may use, while users who are "ArcFM" see the "ArcFM" folder in metaframe, which can have specific applications they may use. This is one level of control.
- The applications in those folders have a script file behind them which uses regedit /s to set the MM license registry keys to the appropriate setting based on the context of the app they have chosen to start. This way an Editor who accesses an application in the "Designer" folder will only use a Designer License while an editor who accesses an application in the "ArcFM" folder will use only an ArcFM License.
- Privileges on executing the scripts are based on system permissions. So a user in the ArcFM group cannot access a Designer license because that group does not have privileges to execute the script that would set the designer license keys (designer.cmd).
- In both the ArcFM and Designer scripts, the conduit.reg
file is called. However access to the conduit.reg file should be restricted
to users in the "ConduitManager" Citrix group. If the user is not
part of this group, they may not check out a Conduit Manager license.
If the conduit.reg file fails to execute because of permissions, it
just fails. There is no error message and no user interaction is required.
Using this approach, it does not matter what the user’s roaming profiles, CURRENT_USER keys, or the user’s current desktop admin settings are when they log into metaframe. License management is handled when the user clicks on a particular published application they want to use.
The following scripts are available by contacting Schneider Electric technical support.
"ArcFM.cmd" is a batch file for your Citrix users who are in the "ArcFM" group. It calls the "ArcFM.reg" file to set the user to take out an ArcFM License and also calls the "conduit.reg" file. Permissions on this file must be set so only users in the Citrix group called "ConduitManager" could access it. Finally, it launches ArcMap with your desired license management settings.
"Designer.cmd" is a batch file for your Citrix users who are in the "Designer" group. It calls the "Designer.reg" file to set the user to take out a Designer License and also calls the "conduit.reg" file - but permissions on this file would need to be set so only users in the Citrix group called "ConduitManager" could access it. Finally, it launches ArcMap with your desired license management settings.