Skip to Content

NetWeaver SAPSetup is SAP’s front-end software deployment tool that deploys SAP GUI for Windows 710, A1S Components, and software by SAP partners like Live Cycle Designer from Adobe, to mention a few. In the CD / download of these products, you will find a SETUP folder that contains the set of SAPSetup distribution and deployment utilities that help you in easy SAP software deployment.


Here is a snapshot of our tools –

SAPSetup Tools - An Introduction


NetWeaver SAPSetup Tools:

NWCreateInstServer: The first tool you need to setup an Installation Server. It’s wizard driven and will configure your windows environment for hosting an installation server and using SAPSetup Tools.


NWUpdateInstServer: Use this tool in the CD / installation-folder of a new front-end component to integrate it into an existing installation server. If the component(s) already exist, it will update them if the source contains a better version thereof.


NWSAPSetupAdmin: The Installation Server administration tool. Strictly for use by administrators, this tool lets you configure installation packages and maintain them, apply patches, configure services, etc. It also supplies alternative ways of importing new products into the installation server, and allows you to delete them.


NWSAPSetup.exe: The workstation installation tool. Start this in user-interactive mode for manual installation or via powerful command-lines to perform silent, unattended deployments.


NWCheckWorkstation: The check-utility that diganosis the health of the Workstation containing installed SAP front-end software. It also produces a CAB-file containing reports and error information, as applicable that you supply to SAP Primary Support if you face problems.


NWSAPSetupDS and NWSAPSetupIS: These implement Local Security Handling that help administrators to allow domain users with non-administrative privileges to install software locally on their workstations using NWSAPSetup.exe. LSH is configurable only via NWSAPSetupAdmin.exe. You never need to call or interact with these two applications directly.

Help Files:

Installation Server Help.chm and Workstation Installer Help.chm should help answer many routine questions that come up. Apart from explaining SAPSetup processes, they feature FAQs that help deal with the most common problems.

To report this post you need to login first.


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

  1. Former Member
    Dear Siddhartha Rao,

    I have two questions I would appreciate Your help with:

    1) Using the installation server I have installed SAPGUI 7.10 Patch 5 on round about 400 workstations. Afterwards it was necessary to replicate the installation server to another server and to remove the old one. Now I have applied SAPGUI Patch 7 to the new installation server. How can I setup the Automatic Workstation Update Service and let the clients get the latest SAPGUI patch from the new server? At the moment they try to get the updates from the old installation source, but the old server does not exist any longer.

    2) speaking of the Automatic Workstation Update Service, if I start NWSapSetup.exe on my installation server, I have only two items in the menu “Services”
    – configure LSH
    – Stop distributing services

    why is the item “configure automatic update” not visible for me? I have checked the prerequisites so far, they are matching my configuration.

    Last but not least I have a litte request: during the setting of LSH, is it possible to set the focus automaticly to the first text area? actualy you have to perform a mouseclick before typing the login-name

    best regards

    1. Former Member Post author
      Hi Alexander,

      Let me answer your questions in reverse order. ๐Ÿ™‚

      >> why is the item “configure automatic update” not visible for me? <<

      This means that the product “SAP Automatic Workstation Update” is not available on your installation server. This was shipped with SAP GUI 710 C2 (and patching C1 wont get this). Please create a new installation server or update an existing one using C2 CD.

      >> How can I setup the Automatic Workstation Update Service and let the clients get the latest SAPGUI patch from the new server? <<

      First create an installation server using C2 (and the latest patch available) and configure it via the Services Menu. Create a package (or modify an existing one) to contain AWU and have this package installed on those workstations where you wish to have this feature in use. Automatic Workstation Update by default will look up the ‘history’ or most-recently-used servers for update-availability. So, changing the server name / address of course is not advisable. What you can do (before installation or update) is to configure “Additional Update Sources” in the AWU Service Configuration dialog. These servers will be looked up on a priority over the ones in the history.

      The documentation (CHM files as well as the SAP FE Installation Guide) should guide you with this feature.

      >> Last but not least I have a litte request: during the setting of LSH, is it possible to set the focus automaticly to the first text area? actualy you have to perform a mouseclick before typing the login-name <<

      Thank you for bringing this to my notice. You are of course right. You get this in SAP GUI 710 PL9 scheduled for release on 25th of July. ๐Ÿ™‚


      1. Steven Glennie
        Hello Sid,

        I noticed your comment regarding “Automatic Workstation Update by default will look up the ‘history’ or most-recently-used servers for update-availability” One of our helpdesks have asked is there a way to check which server / servers the end user PC is registered with?

        Can you advise where this can be found. You mentioned this is held in the history but I cannot see this anywhere.

        Any help on this would be much appreciated

        With regards,

        1. Former Member Post author
          Hi Steven,

          You will find the records of last-used installation servers (network shares) in WkstaUpdater.cfg inside folder %ProgramFiles%\SAP\SAPSetup\Setup\Updater. This is an INI file.


          1. Steven Glennie
            Hi Sid,

            Many thanks for the quick response. We located the file and can see the server name. What we are trying to do is modify this file to point towards another server. The reason for this is that some users have changed locations so we want to avoid these users having to perform updates across the WAN by changing the WkstaUpdater.cfg to point to another server. However the update is still looking towards the original server.

            Any ideas why this may happen? Is there also a registry key set somewhere that is stopping this workaround working?

            Best regards,

            1. Former Member Post author
              Hi Steven,

              The Automatic Workstation Update mechanism uses WkstaUpdater.cfg only. There is no registry key used in finding servers or update availability.

              You need to replace the existing server share’s address with the new one. Also look up NWSAPAutoWorkstationUpdateService.log file to see what the service is doing and if it detects an update.

              Note that you can also configure “Additional Update Sources” via NWSAPSetupAdmin to contain your new server path, save and simply replace the WkstaUpdater.cfg file on the workstations with this newly configured one on the server. Admin-configured servers are taken on a priority over the most-recently-used servers.

              Hope that helped.

              Good luck,

              1. Former Member
                I have  build a GUI installation server to push GUI istallations and updates on worstations
                but when I try executing the command
                \\Lap-bfzlph1\GuiInstall\Setup\NWSapSetup.exe /Product=”SAPGUI710″ /Silent
                It gives and error
                Executing \\Lap-bfzlph1\GuiInstall\Setup\NWSapSetup.exe  /Silent/Install/Product=”SAPGUI710″
                Failure in executing \\Lap-bfzlph1\GuiInstall\Setup\NWSapSetup.exe /Product=”SAPGUI710″ /Silent on DES-760PFC1. Check parameters, credentials and verify if the Windows workstation is running!
                where as using the same credentials I am able to display the windows running process
                Any clues will be helpful
      2. Former Member
        hello Sid,

        >> Please create a new installation server or update an existing one using C2 CD. <<

        it works now as it should. thank´s a lot ๐Ÿ™‚

        >>So, changing the server name / address of course is not advisable.<<

        well, i cannot undo the change of the server name. do i have any possibility to change the server name after setting up a client?

        best regards

        1. Former Member Post author
          >> do i have any possibility to change the server name after setting up a client? <<

          One way is to run a dummy install from the new server and the new server name will be indexed by Automatic Workstation Update.

          (Say, install a new package from the new server that contains components already installed… This will be a dummy run that will record the new path.)

          Alternatively, you can configure “Admin-Configured Servers” via the AWU Configuration window in NWSAPSetupAdmin in the original server.
          This change will be propogated as an update.

          Good luck,

  2. Former Member
    Dear Siddhartha Rao,

    I just installed an installation server Gui for windows 7.10 with download files 50088654_4.ZIP and patch gui710_9-10002995.exe on a french windows server 2003. Everything is OK with this installation and runs well on a workstation with administrator rights.
    When I configure the LSH service for network users without administrator rights, I get this message :
    “Failed to configure Local Security Handling
    L’ID de langue de ressource spécifié ne peut être trouvé dans le fichier image”

    What does that mean ?

    Thanks for advance.

    1. Former Member Post author
      Dear Jean Louis,

      I unfortunately don’t understand French particularly well to be able to decipher that message. Google’s translation tells me this: “The ID language specified resource can be found in the image file” — which doesn’t make sense either.

      So, I would recommend that you please look up this FAQ:
      Troubleshooting FAQ: Why is LSH not working?

      If it doesn’t address the problem, please create a ticket for our primary support: they will need the LOG files from your installation server.


    2. Former Member
      hello Jean Louis,

      we´ve had similar problem here. just make sure there are no LSH-Task running in the background. In other case stop it and try to configure the LSH one more time.


  3. Former Member
    Hello Sid

    I have been trying to use the Installation Server and SMS2003 to deploy the SAP GUI 7.10 to my workstations. I have set up the Installation Server, created the package and it will work from a workstation command line. I then created the Package Definition File and attempted to deploy through SMS2003. I was finally successful in getting it to deploy. However, it is not putting the correct icon onto the desktop for the new version and the old icon no longer works. I have created a batch file which will delete the old icon and copy the new one from the correct folder on to the desktop. I am stuck now at the point of putting these commands into my SAP package on the Installation Server. Can you provide some assistance. I would be fine just running my batch file, or if it is better just scripting the delete and copy in the program itself under On End Install. I have been fighting with this deployment for several weeks and would really like to get it accomplished.

    Thanks for any help you can offer.

    Karen Harbaugh

    1. Former Member
      Hi Karen,
      there should be an icon on the desktop (if saplogon or saplgpad was installed) If this is not the case, you should open a Message at the SAP and provide LOG files to the support people.
      Nevertheless: there is a file called InstallationServerHelp.chm. Go to the section Administering an Installation Server -> Maintaining Installation packages ->
      Configuring Packages and Scripts
      Here you will find script samples, which will help.


  4. Former Member
    Dear Siddhartha Rao,

    We are currently in the process of rolling out GUI 7.10 across Europe. To manage the deployment we are using SMS to send the installation command to the clients so they will then pull from the various deployment points which we have replicated in each country. One of the issues we have got now is that we cannot see easily which machines have been upgraded to the new GUI – is there any mechanism in the deployment point to report back on successful installations, or is there a way that this can be implemented simply?

    Our plan is to regularly patch the GUI as we have a project running which will be running a number of products which are either in ramp-up or very recently released. Given this approach I am expecting pressure to ensure that the GUI is always running at no more than one patch behind current – which is a bit of a change from our traditional implement and forget about it approach!! Again I need to be able to demonstrate to our customers that the client machines have all been patched to the appropriate level before any new solution is brought into production.

    An additional issue (if we didn’t already have enough) is that bandwidth to some of our sites is relatively small and we have to limit the number of machines we upgrade to the new GUI on a given day at a location. Going forward I want to make sure that they don’t all pull any patches on the same day – I know that the update can be configured to control how frequently the update server is checked – is there a recommended way to configure this to minimise the risk of overloading the network but at the same time ensuring that patches are deployed in a timely manner?

    Sorry for such a long query – this is quite a pressure point for us at present and I am keen to get it resolved.



    1. Former Member Post author
      Hi Aden,

      If I remember correctly, the installer supports SMS via the command-line /SMS (please check documentation). This option allows the installer to report the success of the installation / patch / update / uninstall via a MIF file understood by the SMS system.

      As far as ensuring that your update doesn’t happen all at once, please configure your SMS advertisement programs accordingly (the details of which are beyond the scope of the SAP installer).

      Good luck for your deadlines.

      Best Regards,

  5. Former Member
    Hi Sid, great resource here, I plan to look into the self installing packages.  My question is regarding NWEngine functions.  I’d like to echo the time and date to a log file, but nwengine only seems to resolve certain env. variables, for example,
    susername=NwEngine.Variables.ResolveString(“%username%”) work fine but sWinDir=NwEngine.Variables.ResolveString(“%windir%”)
    susername=NwEngine.Variables.ResolveString(“%date%”) does not resolve (blank).  is there a comprehensive list of functions.  Thanks! 
      1. Former Member Post author
        Hi Tina,

        The function “Resolve” usually resolves the most common environment variables. As DATE isn’t a common environment variable, it wont be resolved (you can however use other generic VB Script functions / methods that may allow you to access and expand environment variables and or find the date-time, if the possibility exists).

        Note that the log files themselves contain the DATE and TIME, per line. So, if you wish to resolve the date just for sake of logging it, you could as well use one the LOG functions.

        >> is there a comprehensive list of functions. <<

        In NWSAPSetupAdmin, you can see a list of possible scripting functions via the samples reached through the ‘Configure Packages’ tab. That apart, you can also use all generic VB Script functionalities.

        Best Regards,

        1. Former Member

          You are awesome!  The vbscript function worked:
          Dim MyTime
          MyTime = CStr(Time)   ‘ Return current system time.
          Dim MyDate
          MyDate = CStr(Date)   ‘ MyDate contains the current system date.


  6. Paul McNamara
    Could you clarify the following for me as we are just looking at Installation Server for the first time.
    Assuming Automatic update is on or Logon Pad update is active.
    Scenario: If I have 2 packages eg Power Users and General users. Both have Product ABC.

    I wish to patch Product ABC but I would like to first deploy it only to the Power User group.

    On patching the product on the server will it automatically deploy to both groups?
    If yes (I think it is)is there a way to selectivly deploy patchs to selected package receipients until some initial testing etc is performed without disabling Auto Updates.

    Are there other recommended methods of testing prior to deploying updates?

    Also be interested to hear user experiences with network load if 500 to 600 desktops all find an update at once. (All on a LAN)


  7. Former Member
    Hi Sid,

    Do you have any info on correcting history issue.
    I have tried following Notes:
    Note 931540 – History: repair MDAC installation
    Note 1176026 – History: doesn’t work even after MDAC repair (note 931540)

    can this be corrected with out reinstalling Windows XP software.

    Thanks, have a nice time.


  8. Former Member
    I have to distribute new patches to various organizational units (in fact, different domains).
    The users won’t be able to get updated if they haven’t administrative rights, since I don’t administer the forest (Besides, I didn’t succeed in using the administrative account from the Installation Server).
    Some of the users have administrative rights, but others don’t.
    Some of the workstations have used my Installation Server, but others haven’t.

    Apart from the fact that I can’t manage to install some patches on the server, I am encountering serious issues in applying manually the BI patches to the workstations, so I’m afraid to distribute them automatically:
    – Sometimes, IE (new windows) and Outlook (printing) stop working. I have found out that the solution is to sap register mshtml.tlb… Why does this happen? How can I avoid it previously?
    – Sometimes, the patch doesn’t install, it gives errors, and SAP stops working at all!. What will happen when I distribute the patch? Can I identify problematic workstations in advance with a script?
    I would like to give the chance to IT staff to choose the time of installation or even to rule out the installation server. But it seems impossible: if I patch the server, the clients will start trying to update; if I don’t patch the server, I cannot offer the command-line option (with /update). Is there a solution?
    – Is there a way to distribute a script to uncheck the auto-check for updates?
    – Is there a way to patch only one package but no others?
    – What will happen to the already manually patched stations when I patch the server? Will they know they have the necessary patches and consequently won’t try to re-update? What if I use a new installation server?
    Thanks a lot.

  9. Lieven De Bock
    Dear Sid,

    In the installation manual, the schematic indicates that the LSH-services can be on a different server than the distribution point..

    How do I do this?

    Our ‘distribution’-point is a DFS-feature which synchronizes files over different sites..

    But LSH does not work in this setup
    as the DNS-name of the DFS does not correspond to the servername on which the Distribution-point is hosted.. 

    When addressing the distribution-point using the server-name, the LSH works fine, .. but it interferes with DFS-synchronisation,

    (meaning some files get locked, can’t be synchronized, and after a while the DFS is out of sync)

    So best would be the LSH-services running on a different server seperate from the distribution point.

    This would mean the workstation installation credentials should be coming from a different server, which then redirects the “elevated install user” to the DFS installation-shares for the correct files

    1. Former Member
      Sorry, but with the current version the DS is alwyas with the installation server. this was different with oder versions of sapsetup. I guess the picture was not updated.
      1. Lieven De Bock
        I regret this was taken out, as it would enable the usage of a DFS for storing the installation files, and getting the credentials from elsewhere.

        Maybe someone should correct the picture, as it raises expectations ;-)?

        As requested in blog.. Troubleshooting FAQ: Why is LSH not working?

        I’m assembling OSS Message 816909 / 2010 on component BC-FES-INS
        and collecting all the logs.. I’ll send all infor through shortly




Leave a Reply