If you want to deploy SAP 710 / 720 client in your organization you can find several posts on this blog by clicking on the SAP category.

Basically not much has changed for this version 730.

The following points however might need clarification:

1. No more automatic updates by default if you don’t manage them yourself.

The 710 and 720 versions were installing components for automatic updating of the client. This caused problems when the logged on user did not have admin rights, so I provided a script to disable this functionality.

By default version 730 won’t prompt you to update the software.

Note that the funcionality to manage updates from the server with a service locally installed on each computer during the client deployment is still present.

2. when adding additional packages to the server It is safer to use the NwUpdateInstServer.exe that is part of the new package itself instead of trying to import the package from the server instance (I actually never succeeded to update the server in this way, but it worked when launched from the package itself.)

3. A new feature that you might use is to add your company logo to SAP console.

see SAP Note 1669254 for more information

In order to do this you need to copy the image file and set some registry keys. This can easily be accomplished through the use of Sap Scripting at the end of the installation.

Here is a script I used and the explanations for the settings:

If “%WOW64MODE%” = “true” Then * checks if the system 64 bits (this variable is being used by the sap installer)

strDstFile = “c:\Program Files (x86)\SAP\FrontEnd\Sapgui\icon.gif”          *sets file path for 64 bits system

strRegFile = “HKLM\SOFTWARE\Wow6432Node\SAP\General\Appearance\BrandingImage”   * sets reg path for 64 bits system

strRegFile2 = “HKLM\SOFTWARE\Wow6432Node\SAP\General\Appearance\UseBrandingImage”


strDstFile = “c:\Program Files\SAP\FrontEnd\Sapgui\icon.gif”      * those are default paths for file system and regitry on 32 bits systems

strRegFile = “HKLM\SOFTWARE\SAP\General\Appearance\BrandingImage”

strRegFile2 = “HKLM\SOFTWARE\SAP\General\Appearance\UseBrandingImage”

end if

strSrcFile = NwEngine.Variables.ResolveString(“%SapSrcDir%\icons\icon.gif”)  * this is the source for the icon file

If NwEngine.Shell.FileExist( strSrcFile ) Then

NwEngine.Shell.CopyFile strSrcFile, strDstFile

End If

NwEngine.Shell.SetRegValue strRegFile, “REG_SZ”, strDstFile

NwEngine.Shell.SetRegValue strRegFile2, “REG_DWORD”, “1”    * sets the client to use the branding as defined (you can also let the user change the icon – see SAP Note 1669254)

Here is a screenshot of the source files with the icons folder so you know where to put the files.

You will note also the custom folder that contains specific saplogon.ini and will be deployed without the need for additional scripting.

4. One more feature that might be interesting is the ability to set different schemes for different connections, so you could have a scheme for production and another one for test/development.