Skip to Content

NetWeaver SAPSetup deploys SAP GUI for Windows 710, A1S Components, NetWeaver Business Client, software from Adobe and many other desktop components. With this version of the installer that is available starting January 2007, SAP provides you with a unified mechanism to make the distribution of these components easy and use a unified process in dealing with SAP software deployment.

So, in other words, NetWeaver SAPSetup (NW SAPSetup) is a multi-product deployment tool. It allows you (the administrator) to create an installation server that works as a central point for SAP client software distribution, add new components to it in course of time and distribute them.

Recommended pre-read:

Hope you’ve read the post on NetWeaver SAPSetup Tools and Utilities…?   


  • You have the CD / downloaded package of one of the above mentioned SAP front-end components that you wish to install on client computers in your local network.
  • To configure packages, you need to have the .NET Framework version 1.1 SP1 installed to use NWSAPSetupAdmin.exe.
  • All steps below need administrative privileges on the computer on which they are performed.

Process in brief:

Step 1: Create an Installation Server using NWCreateInstServer.exe

Step 2 (optional): Create installation packages using NWSAPSetupAdmin.exe

Step 3: Install software on end-user workstations from this installation server using NWSASPSetup.exe via the installation server network path.

Setting up SAP software distribution landscape
















All SAPSetup tools mentioned can be located in the SETUP folder of your CD / download / Installation Server.    

Process in detail:

Step 1: Creating an installation server

An installation server is a storage for SAP front-end components that you wish to distribute on end-user workstations. To create an installation server, simply run NWCreateInstServer.exe, and let the wizard guide you through the process.

  • When supplying a physical folder path for the installation server, ensure that it is shared with write access to you (administrator) and read access for the users on the domain. This ensures that the users cannot tamper the contents of the server.
  • When NWCreateInstServer is done, it will automatically start NWUpdateInstServer.exe to update this new (but empty) installation server with the SAP components available at the source (CD or Download folder).
  • When the update process is completed, NWSAPSetupAdmin will be automatically started (if you have .NET Framework 1.1 installed) to help you view the contents of the server and re-configure it.


Step 2 (optional): Configuring packages for installation

As such an installation server with an SAP front-end component like SAP GUI for Windows 710 is complete and ready for distribution. You would configure packages if you wish to –

  • Choose and simplify the selection of components for users (for example: create a package for HR employees containing components you know that they need to install).
  • Configure installation parameters (say like installation folder path) for components.
  • Use the freedom to change the package at a later stage and let the installer (NWSAPSetup.exe) update workstations with the newer versions of the package – hence installing components that are newly a part of it, or uninstall those taken off via a simple command-line.

If none of these criteria interest you, and you wish to install the front-end software, skip this section and jump to the next part.

The process of creating packages is pretty simple and wizard driven –

  • Start NWSAPSetupAdmin.exe (if done creating a new server, this would have been automatically started).
  • Click the “New Package” toolbar button or press CTRL + N.
  • Follow the wizard… Select the components you wish to install with this package.
  • Click Finish when done.

You can configure the package’s installation parameters (component folder paths, etc) in the Configure Packages tab, via the link titled ‘Configure Parameters’.


Step 3: Installing software on end-user workstations using NWSAPSetup.exe

Method A (Manual Installation):

  • Start NWSAPSetup.exe from the SETUP folder of the installation server. Click ‘Next’ to view avail
  • If you followed optional Step 2 above, switch to Package View, select the package you wish to install and click next.
  • Else, select components you wish to install and click next.
  • If you selected a package, there is nothing more to be configured as configuration was done in Step 2, else you may be asked for installation parameters like folder path, etc – depending on your selection of components.

Method B (Command-line based unattended installation):

To install the full version of a product (say SAP GUI for Windows 710) available on the installation server, simply run command-line:


        \InstallationServerPathSetupNWSAPSetup.exe /Product=”SAPGUI710″ /Silent


To install multiple products (say A and B), execute:


        \InstallationServerPathSetupNWSAPSetup.exe /Product=”A+B” /Silent


To install a package created using Step 2 above:


        \InstallationServerPathSetupNWSAPSetup.exe /Package=”Package Command-Line Name” /Silent


You can get the command-line names for the package or the product being installed via NWSAPSetupAdmin.exe (in fact, the entire command-line string that I display above.).

To report this post you need to login first.


You must be Logged on to comment or reply to a post.

  1. Former Member

    Due to slow connections, we plan to have a SAP Gui Installation server in every contry.

    Do we have to install and upgrade all SAP Gui Installation servers manually.

    Or is is possible to have one central SAP Gui Installation server and the replacate all changes to more decentral SAP Gui installation servers.

    Best regards
    René Agerskov

    1. Former Member Post author

      Dear Mr Agerskov,C:\MasterInstServer\Setup\NwCreateInstServer.exe /ServerPath=”
      RemotePC\WriteShare\RemoteInstServer” /Silent<br/><br/>…So, every time you update your master installation server, simply delete the contents of the installation server network share in your remote locations and either have the master server copied, or have it re-created using the above command-line.<br/><br/>Hope that answered your question.<br/><br/>Best Regards,<br/>Siddhartha

      1. Former Member

        Dear Siddhartha<br/><br/>Thank you for the answer, I have replicated the server and installed from it. Works fine.<br/><br/>But I’m still not sure about the front-end clients, how they are updated with new patches. <br/><br/>If I use:
        MasterInstServer\Setup\nwsapsetup.exe /update /silent<br/>Will the update be sent from the MasterInstServer even though it’s installed from a RemoteInstServer.<br/>I’m asking, because it’s easier to have one script<br/>     <br/>If I use:
        RemoteInstServer\Setup\nwsapsetup.exe /update /silent<br/>Will the update be sent from the RemoteInstServer even though it’s installed from a MasterInstServer.<br/>I’m asking, because we install the clients central.<br/><br/>So the question is  more, if we have to update from the same InstServer that it was installed from.<br/><br/><br/>And another question<br/>It’s called an Replicated Installation Server. But I see it more as a file share.<br/>If I use Robocopy to have
        MasterInstServer and
        RemoteInstServer synkron, then I never have to run the command to replicate the server. Is that possible?René

  2. Former Member

    We are using the same schenario in our company i.e. one central setup server and then replicate it to the local shares in each country. However I have a problem with the amount of data that needs to be replicated (over 500MB for the inst server and two installed products).

    Considering that the package thay I have defined uses only a small subset of the comonents for these products, is there anyway to extract and replicate the requred file to reduce amount of WAN traffic? My assumption was that this feature will become available in patch 6. I installed patch 6 today but could not find such option.

    Many thanks,

    1. Former Member Post author
      Hi Masoud,

      We are currently developing a feature by which you would be able to convert a package into a self-extracting installer.

      You cannot make an installation server using this self-extracting installer, but you can deploy the package successfully on workstations.

      We can supply you with a beta-version of this tool (it is still under final test-stages) and you could let us know if it serves your purpose.

      Best Regards,

    2. Former Member Post author
      To be more specific: this self-extracting installer in a sense meets your criteria very well. It contains only those files that the package needs for deployment. Secondly, as it is a single-file that needs to be transferred across the network, the copy-mechanism will be quicker and a lot more reliable.


  3. Former Member
    Dear Sid,

    While SAPGUI Upgrade from 640 to 710, I have the DVD from SAP which has patch level 0. For the patch, do I need to just deploy the patch or install 710_0 and then deploy the patch.


    1. Former Member Post author
      Hi SN,

      In general, to upgrade workstations from GUI 640 to 710, please follow these steps:

      1. Create an installation server using nwcreateinstserver.exe from the DVD containing SAP GUI for Windows 710 Compilation 1 (or you can take Compilation 2 which is already available).

      2. Use NWSAPSetupAdmin.exe to apply the latest GUI patch on this installation server.

      3. Install SAP software from this patched installation server / network share using nwsapsetup.exe.

      The commandline for silent installation would be:
      nwsapsetup.exe /silent

      Note that a patch is an incremental change / correction / improvement containing only a certain set of files that belong to a product, and not all its files. Hence, one cannot apply a SAP GUI patch without first installing a GUI compilation.

      Best Wishes,


Leave a Reply