SAP Configuration Update
The latest SAPgui patch (740p12) includes a change in how connections to backend systems are accessed.
Server-based configuration is now utilized, replacing locally stored information. The server information is cached locally, in case the server is inaccessible for some reason.
Effect on Client
After the process is complete, your connections will be greyed out (not editable, this is normal) and the "Server Configuration File" in SAP GUI options will be changed to this server location.
Group policy is named "CDSS-gpo-SAP-RegEdit-TA99." and is located under Group Policy Objects and should be linkable to other OU's. It deletes 3 local configuration files for SAP and adds 2 registry keys. See report from group policy below for details.
These configuration files will be un-needed or re-cached from the server upon login to SAP after the change
The system Environment Variable SAPLOGON_INI_FILE will be deleted (if present)
The following registry keys will make the SAP client enable local chaching of the server configuration files and tell it where the new configuration file is located
The SAP R3 client can also be reinstalled to complete the update. The installer has been updated on the OIT Software page (https://software.duke.edu/node/168)
No connections appear for the user after completing the connection update
Check for the system environment variable SAPLOGON_INI_FILE
If it exists delete it and then reboot. Connections should appear normally.