About Overrides
Overrides are a means of customizing the functionality of Hummingbird products. You can apply an override to a single user, a group of users, or to all users. For example, if you create a silent installation override for Exceed and apply this override to a group of users (Admin), Exceed will silently install upon logon for all Admin user group members. For a list of overrides, see Overrides List.
You can customize the following products with overrides once they are installed on the Terminal Server.
Applying Multiple Overrides to One User
Once you create an override, the override is recognized by the per-user installation. In cases where multiple overrides with the same name apply to the same user through different levels (This User, Group, All Users), the per-user installation applies the overrides in the following sequence:
The following scenario is an example of the same override being applied to a user (USSALES\Jim) and to a group (USSALES) to which that user is a member.
The following override applies to the USSALES group:
- HCL_USER_ROOTset to [%USERPROFILE]Products\Exceed
where [%USERPROFILE] represents the path specified by the USERPROFILE environment variable and the following override also applies to USSALES\Jim:
- HCL_USER_ROOTset to [AppDataFolder]Hum
where AppDataFolder represents the path to the user’s Application Data folder.
According to the hierarchy that UsrSetup uses to apply overrides, the individual user override takes precedence over the group override. Therefore, the per-user installation will apply the following override when USSALES\Jim logs in:
- [AppDataFolder]Humfor HCL_USER_ROOT
Informing UsrSetup of Override Changes
After you have created an override, or if you have made changes to one or several, you can increase the Product Level setting to inform UsrSetup that a change has been made.