Products  | Support & Services  | News & Events  | Partners  | Policies  | Global Sites
Home > Support > Hummingbird Connectivity Products > Exceed >  Terminal Server - Different Configurations for Different Groups Print View   Contact Me
Connectivity Support


Terminal Server - Different Configurations for Different Groups
DISCUSSION

How to install Exceed to WTS with different exceed configuration files for different groups?

RESOLUTION

There are 2 ways to accomplish this: Sconfig and override.ini. In any case the admin must create groups in the override.ini file and add the accounts to each group. Currently we have no UI tool to help here -- it will have to be done manually.

  1. Via sconfig treat this as a normal Admin-Custom install. Create multiple .ins files, one for each group and create a different user directory for each group. The properly customized exceed.cfg file should be placed in the appropriate custom user directory. Then in the override.ini assign the correct sconfig.ins to the group created earlier. All users in that group will then receive the proper exceed.cfg when UsrSetup runs during Login.

  2. You can skip the sconfig method and simply create a different directory for each group and copy a different exceed.cfg into each. Then in the override.ini change the CustomUserDirList override for each group. e.g Group creation in Override.ini: Create 2 directories, SalesUserDir and AccountUserDir under \Userins. Place Sales exceed.cfg in SalesUserDir, Accounting exceed.cfg in AccountUserDir. Add 2 groups to override.ini, and change the CustomUserDirList override for each group. Make sure you add the proper Account names to the Group.XXX sections otherwise the users will not be properly added to the group.

[GroupList]
SalesGroup=1
AccountingGroup=1

[Group.SalesGroup]
SALES\John=1
SALES\Mary=1

[GroupOverride.SalesGroup]
CustomUserDirList=SalesUserDir

[Group.AccountingGroup]
ACC\Jim=1
ACC\Pat=1
ADMIN\assistant=1

[GroupOverride.AccountingGroup]
CustomUserDirList=AccountUserDir

I recommend using the non-sconfig method because it is simpler (2 dirs, 2 file copies, and the same override.ini changes). Then for global changes use the [*] section to override other UsrSetup things.

Note: please install Usrsetup 6.2.0.4 and Xconfig 6.2.0.3 patch to Exceed 6.2 before carrying out the user installation (user login)