You are distributing SAPGUI for Windows 7.30 (this series does not pertain to SAPGUI for Java or SAPGUI for HTML (aka WEBGUI)).SAP Service Marketplace: SAP’s customer support website, typically accessed via (customer S-user logon required).saplogon.ini: A configuration settings file for SAP Logon, usually stored locally on the end user’s workstation, but which can be stored centrally for shared access.
LSH (Local Security Handling): An optional feature of the Installation Server which allows users without local Administrator privileges to their workstations to install SAPGUI.Package Event Script: Customizable scripts which run at the beginning or end of an installation, uninstallation, or update of SAPGUI.Package: A set of SAPGUI components, often with associated scripted actions, preconfigured for ease of installation and administration.SAPGUI Distribution Service: A service running on the Installation Server utilized for Local Security Handling (LSH see below).
I will show how to maintain central control of the SAP Logon configuration, and I will make some recommendations that may help ease the administrator’s burden.Īs parts of this process are likely already familiar to many of you, I have broken it up into stages. In this six-part series I will take you from the initial download, through the installation, to the configuration of scripted packages for a fine level of workstation control. The SAPGUI Installation Server has a number of features to help the system administrator achieve these goals. Managing a large landscape of SAP Frontend clients requires a central location from which to maintain configurations as well as push updates, upgrades, and the initial distribution.