Each session has an associated configuration. This is true of sessions initiated by Domain Users, Local Users, Grandfathered Users, and IP Address/Range connections. Each of the session configurations is termed “User – per session” or “User” configuration.
The GSW Configuration GUI Tool allows the administrator to organize the configurations based on Domains, Domain Names, Domain Name Users, Local Users, IP Address Ranges, Grandfathered Users and User Templates. Additionally a default configuration may be specified for different objects.
This provides a powerful user configuration hierarchy that can be traversed and the UTS will apply the appropriate configuration. It is important to understand the configuration hierarchy.
As pointed out above, when a connection is initiated the UTS checks for an existing configuration is in the IP Address/Range objects. If a matching configuration is not found then the UTS determines if the connection is either a Domain User or Local User
If it is a domain user, then the UTS determines if there is a matching Domain User within the matching Domain Name. If not, then the UTS determines if a Default configuration exists for the specific Domain Name. If not, then the UTS determines if there is a Default configuration for All Domain Users. If not then the UTS checks to see if there is a configuration match with Grandfathered User . If there is no match then the UTS checks if there is a Default configuration for All Users, and if there is still no match then the UTS system defaults are used.
Continuing from above if the connection being initiated is not a domain user then the UTS but a local user then the UTS determines if there is a matching Local User configuration. If no match exists, then the UTS determines if a Default configuration exists for all Local Users. If not then the UTS checks for a configuration match with Grandfathered User. If there is no match then the UTS checks if there is a Default configuration for All Users, and if there is still no match then the UTS system defaults are used.
Default configurations may be created for the objects listed in Table 50. You can quickly determine if a default configuration exists for an object by viewing if it has the black circle with a white check in the bottom right of the icon as shown below.
The Domains screen allows you to view quick status information such as how many domains configurations are defined, how many users are defined for each domain. Additionally the administrator may perform right click operations at the Domain level such as adding, deleting domains, creating default configurations etc
The Domain Name screen allows you to view quick status information such as how many user configurations are defined for this domain name. The administrator may also perform right click operations at the Domain Name level such as adding, deleting users for this Domain Name, creating default configurations, etc.
Domain Name - User and Summary
The configuration summary description for a Domain Name User, Local User, Grandfathered User and User Template are the same. Differences are noted in the overview section of each object.
When expanded the Local Users Summary View provides the administrator with the number of Local Users that have a configuration defined, the Local User names and if a default configuration exists for the Local Users object.
Expand each Local User to access their configuration property pages
The Local User Summary provides the administrator with a quick view (on the right side of the display) of most of the Local Users configuration settings. From the User Summary view it is easy to determine which property page to use to edit the configuration setting. Each configuration setting resides within a frame with a label. For example: Logon Script is a label on the frame around the “Home Folder” configuration setting. On the left side of the display is the property page icon with Logon Script as the name. The Home Folder property is available in the Logon Script property page. Simply click on the Logon Script property page to display its properties for editing. There are a few exceptions to this direct association due to screen space but will still be easy to find
Local User - GSW Client Control
Local User - Power Features - Printing
Local User - Power Features - Team Services
Local User - Power Features - Event Logging
Local User - Failure Detection and Recovery
The IP Address/Range Summary View and Specific IP Address/Range provides configuration of:
The association between the logon script and the IP address is specified in the GS_IP_Rt.txt file.
Note: IP Address/Ranges user configurations contain the same property pages as all session users. Each page is described in the Local Users section Note: IP Address/Ranges user configurations contain the same property pages as all session users. Each page is described in the Local Users section
The Grandfathered Summary View and Specific Grandfathered User configuration provides:
Note: Grandfathered Users contain the same property pages as all session users. Each page is described in the Local Users section
The User Templates View and Specific User Templates configuration provides:
Note: User Templates contain the same property pages as all session users. Each page is described in the Local Users section