> Migration for Existing Users

A major benefit of the GUI Configuration Tool is that you are not bound to the GUI or the traditional method. The GUI Configuration tool obtains all the configuration data and presents it in a graphical user interface. You can swap back and forth to fit your comfort level.

For those customers that are used to the pre-GUI method of configuration the UTS you have several options

GUI Migration Options

• Continue to use the legacy UTS configuration
  The advantage to using the legacy configuration is that you do not have to change your methods or procedures for configuring the UTS
  Additionally most items the UTS can be configured via SSH and Telnet.
  There are new features that include Domain Names, Grandfathered Users, etc. that can still be fully utilized with the legacy configuration techniques.
• Migrate to the GUI
  The advantage to migrating to the GUI is that you gain all the benefits of the Graphical User Interface including minimal training of new administrators on editing the registry, adding environment variables to scripts etc.
• Use both (but not at the same time)!

Common Questions about Migrating to the UTS GUI Configuration Tool

1. How much effort is it going to require migrating to the GUI?
   Not much at all. The GUI will come up and run out of the box with no changes. All existing users in per session scripts folders will show up as Grandfathered Users. It is recommended that you move the users to either the Local Users or Domain Name Users categories
2. What happens to my Global Logon Script?
   A Global Logon script (specified in the Scripts Root folder), is used as the Default Configuration for the User - per session. See below.
   
3. What if I have both a c_start.bat and a k_start.bat?
   The logon script precedence rules apply if you have both a c_start.bat and a k_start.bat. The c_start.bat is used.
4. Can I go use both the GUI Configuration Tool and the traditional method I have been using for years?
   Yes. You can switch back and forth as you desire (take care not to make edits from both tools simultaneously)
5. Do I have to restart the services after making a change?
   Yes. If it is a Global – per system configuration item
   No. If it is a User – per session configuration item

Logon Script Migration

Logon scripts (Per - Session) created in pre-GUI versions of the UTS will appear under Grandfathered Users in the GUI version. It is recommended to move Grandfathered User configurations to either a Domain User or Local User configuration location.

Example: Move the Grandfathered configuration to a Local User

See question 2 above for Global Logon Script migration.

Registry Setting Migration

Registry settings apply to the Global – per system configuration and as such there is no required migration.

Environment Variable Migration

Environment variable settings apply to the User – per session configuration and show up in as part of the Grandfathered Users configuration. They are migrated as described in the Logon Script Migration

Scripts Folder

Environment variable settings apply to the User – per session configuration and show up in as part of the Grandfathered Users configuration. They are migrated as described in the Logon Script Migration