Skip to Content
Author's profile photo Matt Fraser

SAPGUI Installation Server Part 3 – Patching

This is the third of a six-part series progressing from initial download, through installation, to configuration of scripted packages for a fine level of workstation control via an SAPGUI Installation Server.  Later in the series I will show how to maintain central control of the SAP Logon configuration, and I will make some recommendations that may help ease the administrator’s burden.


As parts of this process are likely already familiar to many of you, I have broken it up into stages.  Please feel free to jump to the sections most relevant for you.  If you are setting up an Installation Server for the first time, however, I recommend you go back to SAPGUI Installation Server Part 1 – Getting Started and move sequentially through the steps.


In Parts 1 and 2 we downloaded all our required files and installed our Installation Server to a network shared location.  Now it’s time to bring our Installation Server up-to-date with the latest patches.


  1. Getting Started
    1. Includes download of all required files
  2. Initial Installation
  3. Patching (this document)
  4. Package Creation
    1. Includes initial installation of the administrator’s SAPGUI
  5. Scripting
  6. LSH and Distribution


Patch Installation Server


If you are continuing on from the previous step (SAPGUI Installation Server Part 2 – Initial Installation), then the Installation Server Administration Tool will be automatically launched for you when you click Close on the Installation and Update Tool.  If you are returning to this step at a later time, you can launch the tool manually on your workstation by navigating to your server share:

  • \\server\sapgui
    • Setup


From there, execute the program:

  • NwSapSetupAdmin.exe


You will get to know this program very well.  It is important to execute it from the location in your Installation Server share, not from the installation files you previously extracted to your local hard drive.



When you first launch it, you will notice in the title bar that it names the Installation Server that you are working in, so you can confirm that you are in the right place.  You will initially see a list of SAP frontend components that are available on your Installation Server.  Above that are several tool buttons.  Click Patch Server.


The Patch Installation Wizard will open.



Click Next and then click Browse.  A browse window will open.  Navigate to the location where you stored the two patches you downloaded earlier (as part of SAPGUI Installation Server Part 1 – Getting Started), and select the SAPSETUP patch.



Click Open.



Click Next.  The tool will then validate the patch.



If this is an established Installation Server already being used by end users, then you should not proceed during business hours or at a time when users may be installing or updating their SAPGUIs.  If this is the initial configuration of the Installation Server, however, then you are so far the only user.  Click Next.


The tool will close NwSapSetupAdmin and apply the patch.  When it’s finished, you will see a success message.



Leave the checkbox checked and click Close.  The Installation Server Administration Tool will reopen.  You aren’t done patching, however, as so far you have only patched the infrastructure of the server, and not any of the products.  As before, click on Patch Server, then Next.  This time, browse to the GUI Core patch you downloaded earlier.



This time, the patch will take longer to apply.



When the patch is complete, you are once again returned to the Installation Server Administration Tool.  Your Installation Server and the core SAPGUI product are now up-to-date, but in order to make it easier on your end users and yourself, you will now want to create a Package.  That is the subject of the next installment in this series.




Continue on to SAPGUI Installation Server Part 4 – Package Creation.

Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Former Member
      Former Member

      Hello Matt,

      Thank you so much for such a good document.

      I would like to check with you about few things.

      My customer already has around 2k SAP GUI running over windows, fat client and over citrix etc.

      We do not have installation server and looking forward to build one. But is it a good idea now?

      I mean the task is to update the GUI and i am not sure if GUI update server will be good enough for the running environment.

      Please suggest. I will be waiting for your valuable advice. Many thanks!



      Author's profile photo Matt Fraser
      Matt Fraser
      Blog Post Author

      Hi Mohit,

      Yes, I would absolutely recommend an Installation Server for upgrading the existing SAPGUIs already installed. It will make the task significantly easier and less error-prone. In fact, I recently used a newly installed Installation Server for the purpose of upgrading approximately 1,000 existing SAPGUI installations to 7.30, with a mix of 6.40, 7.10, and 7.20 starting releases. You can pretty much follow the same steps I outlined in this blog series.

      The choice you have is whether you want to upgrade-in-place on each existing client, or uninstall and then install a fresh SAPGUI. Upgrade-in-place typically works fine, but if you have a mishmash of different non-standard GUI components installed, then it may be much cleaner to start everyone fresh. This may be especially true if, as seems likely if you don't have an Installation Server now, the existing clients don't have any Packages of components predefined. This is your big opportunity to distribute a more supportable and standardized configuration.

      So, first determine which GUI components you really need, and only put those in your Package. Run a bunch of tests with your scripts. Then choose a pilot group of maybe 50 users willing to be beta-testers, hopefully with a mix of different starting configurations, and run your scripts on them first, then iron out any problems.

      Once you're ready to distribute to all 2,000 users, then you can decide how to load-balance the upgrade (it might be a bit heavy to hit everyone on the same day). You might use logon scripts, or you might push out a link and let people choose the time of their own upgrade (thought my experience is they will tend to choose to simply not do it until forced).



      Author's profile photo Nicolaas Johannes Van Zyl
      Nicolaas Johannes Van Zyl

      It is great that these documents are so detailed and online forgot my usb memory stick at home and can just reference to this online via scn!

      Tx matt!

      Author's profile photo Matt Fraser
      Matt Fraser
      Blog Post Author

      I do that. I've been installing a lot of new systems lately, and I use my SQL Server Installation/Preparation blogs as checklists to make sure I don't forget anything. I just keep them up on a second monitor while doing my work. I have offline checklists for the SAP install / system copy part, too, but I never turned any of that into a blog, as many have already blogged on that process before.