If you have a large number of users working with SAP and perhaps also changing target systems, you won’t want to manually change the SAP logon configuration (former “saplogon.ini”, since version 7.5 “SAPUILandscape.xml”) on every client but centrally manage it.

To do so, you have to edit the shortcut which is used to open SAP and add the path to the SAPUILandscape.xml as an additional parameter. The complete line might then look like this:

"C:\Program Files (x86)\SAP\FrontEnd\SapGui\saplogon.exe" /LSXML_FILE="C:\Settings\saplogon\SAPUILandscape_<customer>.xml"


  • You can create one shortcut per customer and therefore place numerous different per-customer-links on the user’s desktop.
  • A possibly already existing SAPUILandscape.xml in the user’s profile will be ignored. This also means that users can still have their own custom SAPUILandscapes if they want.
  • The SAPUILandscape.xml is placed ouside the user profile which 1.) prevents users from editing it and 2.) makes it easier for you to deploy using your favorite software deployment solution.

At some point, you might come across connections which require additional lines in the “services” file (C:\Windows\System32\Drivers\etc\services) which look like this:

sapmsp01 3500/tcp

This leads to two possible issues:

  1. You would have to replace the services files via SCCM.
  2. If there is a conflict of several lines in the services file, you’re screwed.

To solve this, you can instead leave the original services file untouched and add the port to the respective line in the SAPUILandscape.xml file like this:

Example before:


Example after:

<Messageserveruuid="12345678-1234-1234-1234-123456789012"name="P01"host="" port="3500"/>

These two possibilities can make a SAP config deployment totally flexible.