This note will reappear as reference in the following tables.
But New SAPGUI(4.x) has them in windows registry. Old SAPGUI(3.x) had his settings in INI files.
I have been told by SAP support that there is no full documentation for the registry keys for some reasons.General Remarks and Sources Some Statements This could become the official inofficial reference. At the time of creating this document, office was not required to be installed locally on the machine.There is no official reference for all the registry entries SAPGUI makes when being installed or running or one can make to configure the appearance and behaviour of the SAPGUI. variable SAPLOGONINIFILE ignored: 1426178: SAP Logon (Pad): create/distribute server configuration file: 1073779: setting the Frontend Up-/Download Codepage: 38119: SAP Logon: Administration of functions: Popular articles. SAP has some Microsoft Office excel integration. Note: If your SOE or MOE target machines have a lower version of MSXML 4.0 installed locally, you may experience some issues on launch or if you choose to install MSXML4.0 locally. SAP Error Reference (msxml): Failed to load administrator rule file This will also prevent first launch error messages during sequence first launch changes in optimisation. Add Your Comment Cancel reply Indicates Required Field. You would like to launch the SAP LogonPad using this custom ini file. Call SAP Logon Pad with Custom saplogon.ini INI File. Please note that the Msxml4.msi that comes with the vendor installer should not be preinstalled and allowed to be installed by the SapGUISetup.exe during sequencing if you wish to publish the app globally. Call SAP Logon Pad with Custom saplogon.ini INI File.
Local Pre-Requisite Installationįor Windows 7 圆4 the following MSI’s that come with the vendor media should be installed locally on the machine. Preparation of your sequencing machine prior to the actual sequencing process is important to avoid issues during the process and in testing. REQUIREMENTSĪpplication Name: SAP GUI 7.20 with Comp 3Ĭontributor: Geoff Regalado PRE SEQUENCE PREPARATION If you are continuing on from the previous step (SAPGUI Installation Server Part 4 Package Creation), then you have created a Package called Basic with several SAPGUI components in it, and you have installed SAPGUI on your own workstation using the Basic Package.You don’t yet have any entries in SAP Logon, however. The scripting method chosen to incorporate pre-requisite MSI installation using the AppV package is OptionalĬredits: Nicke Källen for his post on overcoming issues with saplogon.exe launch and Excel-in-place issue. May not work if attempting to integrate or enable other SAP products. Once it is set to a value, that location is looked at and if you have mentioned the path in the AppOptions.xml file and saved it then it should pick that value in all sessions and should be visible in the AppOptions.xml file as well. This recipe is based off the successful virtualisation of the “GUI for Windows” feature of the SAP product. Before start doing changes, we need to copy theSAPLOGON.ini file to c:windows, 1.
The following sequencing recipe is for the virtualisation of SAP GUI 7.20 for Windows only with the inclusion of a Comp 3 update and integration of a corporate Saplogon.ini file.