You have developed the scripts on your local PC and tested them with a few users. Now you want a large number of users to work with the new masks. The following points should be taken into account:

(1)
Is the latest version of SAP GUI installed on the user workstations?

GuiXT is then automatically up to date, as it comes with the SAP GUI patches. The GuiXT version on the Synactive website may be slightly newer, as it takes some time after a version is released by Synactive for it to become available in the next SAP GUI patch.

In exceptional cases, you can install GuiXT separately on user workstations. In any case, make sure that all users are working with the same version and that this version was also the basis for testing your scripts.

You can add your own files (e.g., guixt.ini) to an SAP GUI installation and distribute them that way; see SAP Note 512040.

(2)
Where do we store the scripts and how do we update them?

In general it makes sense to have a central location for your GuiXT scripts; SAP MIME Repository is useful for this purpose. You might use a network fileserver or http server instead, if this is available and safe. To minimize network load you can activate the GuiXT file cache.

Please ensure that effective protection against unauthorized changes is guaranteed for the central storage of scripts. Otherwise, errors or malicious manipulation could affect the entire user base at the same time. 

The SAP MIME Repository provides all the necessary security functions. Therefore, as a rule, no direct script changes should be made in the production system. Instead, all scripts should be transferred from the development system via the test system to the production system using the regular SAP transport route.

(3)
Define GuiXT profiles for user PCs

To store GuiXT profiles in the windows registry only makes sense if you use a specific tool to update registry entries for all user PCs. Otherwise it is preferable to work with a local guixt.ini that refers to a central ini file. The local ini file then contains the entries  

IgnoreRegistry  Yes
SwitchTo        \\server\.....\guixt.ini  //central ini file

Later on you can simply change profile parameters in your central ini file.

Please observe the following parameters in your local ini files: "StartHidden Yes" to hide the GuiXT window, "IgnoreRegistry Yes" to ignore local profile entries.

In the common case where the central guixt.ini file is stored in the SAP MIME repository, you need to specify the RFC login data. With a generic RFC user, it looks like this:

IgnoreRegistry Yes
StartHidden    Yes
RfcUser        guixtrfc
RfcPasswordEnc MIJFCIGEGMPGPNADBNEKCNLNIGEHLHFDFGHCGKDGNIMAEHJPJNDHGGIFNPDOEMPE
SwitchTo       SAPMR:SAP/BC/BSP/SAP/GUIXT/GUIXT.INI

If you want to perform all RFC accesses in the context of the logged-in user, use the following configuration:

IgnoreRegistry Yes
StartHidden    Yes
RfcUser        *
RfcPassword    *
RfcCurrentClient    *
SwitchTo       SAPMR:SAP/BC/BSP/SAP/GUIXT/GUIXT.INI
 

When using Single Sign On instead of logging in with a user name and password, you must also set the SNC/SSO parameters:

IgnoreRegistry Yes
StartHidden    Yes
RfcUser        *
RfcPassword    *
RfcCurrentClient    *
RfcConnect SNC_MODE=1 SNC_PARTNERNAME="p:CN=&database, O=myCompany, C=XX"
SwitchTo       SAPMR:SAP/BC/BSP/SAP/GUIXT/GUIXT.INI

For more information on SNC/SSO, see Configuration for SNC and SSO