Page tree
Skip to end of metadata
Go to start of metadata


This Wiki Page describes how to package and distribute SAP front end components on Windows using SAP Netweaver SAPSetup (NW SAPSetup) - SAP Installation Server Administration Tool.


SAP’s Front-End Software Deployment Tool – Netweaver SAPSetup not only allows direct installations from distribution media, but also an Installation Server based deployment mechanism that helps distribute SAP Front-End Software to workstations over a network and also using Microsoft SCCM  to deploy the large number of users. 

General Features of NW SAPSetup:

  • Fully-featured installation, uninstallation, update, repair, and patch functions for SAP front end components:
    • Front end components are available from an installation server or a distribution medium such as a DVD.
    • Install new SAP front end components, uninstall existing ones, and update the remaining components in one cycle.
  • Easier and more reliable handling of SAP front end components by using installation servers:
    • Wizard-driven user interfaces let you manage the installation server easily.
    • You can customize the installation of packages by programming events that support Visual Basic (VB) scripting.
    • With NW SAPSetup you can manage multiple SAP front-end components that are deployed on the front ends.
    • Maintain nearly all Windows-based SAP front end components on a single installation server.
    • Integrate additional SAP front end components into an existing installation server, such as Import Product.
    • Deploy multiple SAP front end components on workstations using a single command.
    • Easily manage the installation server with wizard-driven user interfaces.
    • Local Security Handling (LSH), when configured, lets you deploy SAP front end components on workstations without requiring administrator privileges on all machines.
    • Whenever installed SAP front end components or packages change on the installation server, the automatic workstation update service (AWUS) will, once configured, automatically update the workstations and reboot them if necessary.
    • Easier handling of multiple SAP front end components by configuration of installation packages – by implementing script events, you can customize and extend the installation of such packages.
    • Controlling workstations remotely helps you to remotely access and control workstations on which you have administrator privileges. You can collect remote log files, execute processes remotely, and list remote processes.
    • The directory for the creation of the installation server is configured automatically. By default, it is made NULL-session accessible. It can be shared automatically on the network for everyone to read.
    • If NwSapSetup.exe is started from a batch file, the return code can be caught by the environment variable %ErrorLevel%.

New Tools and Utilities 

  • NWCreateInstServer: Installation Server Creation Wizard Driven Tool that helps in creating a basic Installation Server and configures.NET Security to administer it over a network path.
  • NWUpdateInstServer: Installation Server Update Wizard Driven Tool is used to update an Installation Server with SAP Front-End Components. This utility will also automatically update older versions existing on an Installation Server by newer ones.
  • NWSAPSetupAdmin: Installation Server Administration Wizard Driven Tool that helps in maintaining and configuring an Installation Server, creating packages, importing products, apply patches etc.  Administrators can create a Package Definition File to deploy the package using like Microsoft SCCM.
  • NWSAPSetup: Front-End Installation Tool is used to install SAP Front-End Components available on the Installation Server on a Workstation, to update an installation or to perform un-installations.  Administrator can install manually or using command lines to perform the installation silently and unattended deployments
  • NWCheckWorkstation: This utility is used to diagnose the health of the Workstation containing installed SAP front-end components. It creates a CAB-file with the error information. If required, you supply the logs to the SAP Product Support.
  • NWSAPSetupDS: This tool allows you to configure (Local Security Handling) that helps administrators to allow domain users with non-administrative privileges to install software locally on their workstations.

Hardware and Software Requirements

Make sure in advance that your system meets the following requirements:

The host for server-based installations must meet the following conditions:

  • Accessible to all users at all times, even after the installation is complete. This is required for maintenance purposes such as the distribution of patches.
  • Have broadband network connection for high throughput
  • Have sufficiently free disk space for all SAP front end components
  • Use a Windows server as operating system

SAPSetup 9.0 Notes

It is important that you read the following SAP Notes before you start the installation. These SAP Notes contain the most recent information about the installation, as well as corrections to the installation documentation.

1587566 - Installation problems with NwSapSetup Version 9.0

1583967 - Release Information Note for SAPSetup 9.0

On the Installation Server:

  • The Installation Server can be configured to manage and hold many SAP Front-End Components.
  • The "Import Product" feature allows the Administrator to bring new SAP Front-End Components into an existing Installation Server for distribution over the Network.
  • The "Export Product" feature allows the export of an SAP Front-End Component from one Installation Server to another.
  • Packages can be configured to contain and deploy multiple SAP Front-End Components.

On the Workstation:

  • This one installer is capable of managing multiple SAP Front-End Components deployed on the Workstations.
  • With the new installer, it is possible to install new components, uninstall existing ones and update the rest in one cycle.
  • It features the installation and maintenance of multiple SAP Front-End Components on the Workstation using a single command-line.

Installing Packages Using the Logon Script

To automate the installation of SAP front end components on a large number of workstations, insert a command line into the logon scripts of the users. This enables you to start the installation of SAP front end components or a package when the user logs on.


The SAP front end components (especially SAP GUI) should not be running when you perform the following procedure, as SAPSetup might require a reboot to complete the installation if program files are in use.


To automatically install a package when a user logs on, add the following command to the user’s logon script:

\\<server>\<shared directory>\Setup\NwSapSetup.exe /package:“<package command line name>“ /nodlg

When you start this command for the first time on a workstation, SAPSetup installs the specified package. With every following logon, SAPSetup will check for updates of this package on the installation server.

 Command Line Parameters





Does not display a user interface.
When using /silent, you must specify a product name, a package name, or /update


Shows only the progress dialog.
Displays no other user interface. You can use it instead of /silent.
If using /nodlg, you must specify a product name, a package name, or /update.


Overwrites all files, registry keys and other artifacts installed by SAPSetup, regardless whether they exist or not. Even files with a newer file version are overwritten.
SAP files are uninstalled even if their shared DLL counter is not zero.


Make sure that an installation with the tag <OnceTag> runs exactly once on a workstation. The tag <OnceTag> is stored in the Windows registry and never deleted by SAPSetup. If an installation with the same tag is started again, it will do nothing and return 0 instantly.


Uninstalls SAP front end components installed by SAPSetup.
To uninstall all SAP front end components, add  “/all”
To uninstall a specific product or package instead, add  /Product="Product Command Line Name" or, respectively /Package=”Package Command Line Name"
Works only with /nodlg or /silent


Runs the installer in product mode.
You cannot switch to Package View.


Runs the installer in package mode.
You cannot switch to Product View.

/product:"<product cmd name>"

Only the specified product is processed. Other products are not displayed on the selection dialog.
You can specify several products by concatenating their names with a plus sign (+).

/package:"<package cmd name>"

Only the specified package is processed. Other packages are not displayed on the selection dialog. You can specify several products by concatenating their names with a plus sign (+).


Updates installed SAP front end components.
To update all installed packages available on the installation server, add /Package
To update a specific product or package instead, add /Product="Product Command Line Name" or, respectively /Package="Package Command Line Name"
Works only with /nodlg or /silent


Skips the check whether the WTS server is in installation mode. Only provide this if the check does not work correctly; in this case, open a message on component BC-FES-INS for a bug report.


Restarts the workstation automatically when the installation is complete.
Use in combination with /package or /product after /silent or /nodlg.
\NwSapSetup.exe /silent /product="SAPGUI710" /ForceWindowsRestart

/SMS:["<package cmd name>"]

Creates a status file named "Package Name.MIF" in the %temp% directory that indicates the success or failure of the process.
Typically used by software distribution systems such as SMS to determine the success or failure of a remote installation (advertised package installation).


Repairs all installed SAP front end components.
For further information, see section Repairing Installed SAP Front End Components


Usually, only those SAP front end components that are also available on the installation source are displayed in the selection dialog. With this switch, all installed SAP front end components are displayed and can be uninstalled.

Single File Installer


Provides help on command line parameters



Does not display a user interface. Returns the
same return values as NwSapSetup.exe. For
further information, see section Return Codes.

SAP GUI Installation on a Workstation from an Installation Server

The installation process from an installation server is flexible, easy, and customizable. It makes maintenance easier in any phase of the distribution process, for example, when applying patches.

When installing SAP front end components with server-based workstation installation:

The following options are available:

● Without user interaction (unattended)

● With user interaction (attended), where the user has the following options:

○ Select from installation packages that the administrator has configured

○ Select from a complete list of SAP front end components available on the installation server

Process Flow

The following figure shows how the installation with an installation server works.

With an installation server, the administrator can group various SAP front end components together as installation packages relevant for certain employee roles. The administrator can also specify which package particular users should receive, or offer a variety of packages and allow the user to choose the most appropriate one.

Important SAP Notes for SAP GUI 7.30

sapnote_0000026417_SAP GUI Resources_Hardware and software.pdf

sapnote_0000038119_SAP Logon_Administration of functions.pdf

sapnote_0000066971_Supported SAP GUI platforms.pdf

sapnote_0000147519_Maintenance strategy_deadlines for SAP GUI.pdf

sapnote_0000166130_SAP front end_Delivery and compatibility.pdf

sapnote_0000328723_GUI default settings during installation.pdf

sapnote_0000508649_Diagnosis of frontend installation problems.pdf

sapnote_0000535308_How to apply a SAP Front End patch.pdf

sapnote_0001053737_Expected release dates for SAP GUI for Windows & ITS Patches.pdf

sapnote_0001085218_NetWeaver 7.x BW Frontend Patch Delivery Schedule.pdf

sapnote_0001144671_New SAP Installer for SAPGUI for Windows 7.10.pdf

sapnote_0001169612_Cannot start NWSAPSetupAdmin over a network path.pdf

sapnote_0001397000_SAP GUI for Windows Security Execution of SAPShortcuts.pdf

sapnote_0001414580_Jaws & SAP GUI configuration.pdf

sapnote_0001426178_SAP Logon (Pad) create and distribute server configuration file.pdf

sapnote_0001442028_SAP GUI for Windows_No support for Office 2010 64bit.pdf

sapnote_0001583967_Release Information Note for SAPSetup 9.0.pdf

sapnote_0001587566_Installation problems with SapSetup Version 9.0.pdf

sapnote_0001588323_SAP GUI for HTML cannot be started (NW Basis 7.30).pdf

sapnote_0001652770_BI 7.x in 730 DVD1-BI client tools - contents & versions.pdf

sapnote_0001669254_SAP GUI 7.30_Branding image in titlebar.pdf

sapnote_0001670678_730_New Features.pdf

sapnote_0001685221_SAP Logon_maintain system entry without sapmsg.ini and service file.pdf

sapnote_0001702037_BW 7.x Frontend in GUI 730 - First Customer Shipment.pdf

sapnote_0001710864_SAP Logon 7.30_possibility to disable views via registry.pdf

sapnote_0001726742_SAPBWNews NW 7.x BW Add-On Frontend Patch 300 - GUI 7.30.pdf

sapnote_0001796138_SAPBWNews NW 7.x BW Add-On Frontend Patch 201 - GUI 7.30.pdf

sapnote_0001797599_RRMX for BEx Analyzer 3X is not supported with SAP GUI 730.pdf

Log Files

Log files are maintained under %ProgramFiles%\Sap\SAPSetup\Logs


Log File

Error File










NwSapSetup.exe – Single File Installer



Return Codes

The following table describes the return codes for NwSapSetup.exe

Return Codes



Process ended without detected errors


Another instance of SAPSetup is running


LSH failed


SAPSetup started on WTS without administrator privileges


WTS is not in install mode


An error occurred in COM


General error


Installation canceled by user


Invalid patch


Installation engine registration failed


Invalid XML files


Reboot is recommended


Reboot was forced


Error report created


Error report created and reboot recommended


Error report created and reboot forced

Software Download Links (SMP Login Required)

SAP GUI 7.30 for Windows

SAP GUI 7.30 for JAVA

Patch Download Links (SMP Login Required)

SAP GUI Patches for Windows

SAP GUI Patches for JAVA


SAPSetup 9.0 Patches

SAP GUI 7.30 Patches and Relevant Notes


  1. Please reach out to me if you have additional questions or comments.

    Also be sure to follow me to get the latest updates on future upgrades and modifications.

  2. Former Member

    Looking for SAP GUI Server 7.40 Script for "Single File Installation" that includes applying core patch and updating %AppData%\SAP\Common\saplogon.ini.  Just updated my server with SapSetup patch 79.  Adding this script to"strSrcFile   = "\\<PATH\to\Configfiles>\saplogon.ini" strDstFile   = "%AppData%\SAP\Common\saplogon.ini" NwEngine.Shell.CopyFile strSrcFile, strDstFile  to the On Update End isn't updating the saplogon.ini file on the desktop.  Any ideas?





    Dan Mead