To create the license CAB file
makecab.exe Quest-QAS-GSSAPI-for-SAP.asc license.cab
Note: You may need to download makecab.exe if it is not available on your system.
This creates a file called license.cab.
To deploy Single Sign-on for SAP through Group Policy silently
msiexec /i "qas-sso-for-sap-<version>.msi" TRANSFORMS="qas-sso-for-sap.mst" /qb
To configure the SAP GUI client on Windows XP
The library is located in the folder where you installed Single Sign-on for SAP.
The SAP GUI client should already be installed and configured for normal password-based authentication.
This is the same KPN that was used for the SAP instance profile key snc/identity/as described in Enabling SNC on the SAP server.
You can now click the server name in SAPlogon to log onto the server without being prompted for a user name or password.
Once you have configured the server connection to use SNC, it is now possible to create desktop shortcuts using SAPlogon. Shortcuts normally require a password to either be included with the shortcut (not recommended) or else the user is prompted for a password when the shortcut is activated. With SNC activated, however, it is only necessary to enter an arbitrary shortcut (a single letter will do) in the password field of the shortcut. This shortcut is not actually used for authentication, as the SAP system attempts authentication using GSS-API first.
The use of SNC and shortcuts allows SAP administrators to create desktop icons for users that will launch them directly into specific SAP applications, securely authenticating without the use of passwords.
To configure the SAP GUI client on Windows Vista
The Create New System Entry screen displays:
For example, enter:
Use the same KPN that you used for the SAP instance profile key snc/identity/ as described in Enabling SNC on the SAP server.
The new item you created will now appear on the SAP GUI log on.