SAP SAP GUI

Version: 6
Views: 6.5k  |  Created: 07/30/2002

Average Rating: 0
SAP GUI has 1 inventory records, 3 Questions, 0 Blogs and 1 links. Please help add to this by sharing more!

Deployment Tips (12)

Most Common Setup Type
Not Determined
Average Package Difficulty Rating
Rated 1 / 5 (Very Easy) based on 2 ratings
Most Commonly Reported Deployment Method
Vendor Provided Command Line (switch driven)
or cancel
121
Command Line

To install (silent) SAPGui 6.20 by using a package made with sapadmin.exe take the following commandline: CD:\GUI\WINDOWS\WIN32\setup\SAPSetup.exe /p:"Package-Name"

Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment
120
Command Line
This is the uninstall

"C:\WINNT\SAPwksta\setup\sapsetup.exe" /uninstall /SILENT

For the install to work correctly via SDO edit the XML file guisetup.xml and take out the systemupdate.msi excute. then run the systemupdate.msi afterreboot.
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment
120
Command Line
To install (SMS silent) SAPGui 6.20 by using a package made with sapadmin.exe take the following commandline:

CD:\GUI\WINDOWS\WIN32\setup\SAPSetup.exe /p:"Package-Name" /sms /install /silent
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment
120
Note
I don't think repackaging a good idea - a lot of work adding merge modules, fixing dll's issues, etc. I created a suiteable package, selecting only the needed options, using the :CD\WIN32\setup\SapAdmin.exe. Then, I used the command lines to deploy:

sapsetup.exe /silent /p:"my_custom_package_name" /install /sms

After all, you can, by the same way, use a command line to install the needed SAP GUI upgrades, using the sapsetup.exe:

SAPSETUP.EXE /Patch:"%PathToPatch%\SEM31A.EXE
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment
120
Command Line
SAP 46D - SAP 6.20
To Uninstall: We use:
rmdir /q /s %windir%\SAPwksta
\\SERVER\SHARE\SAPGUI620P58\setup\sapsweep.exe /all /delsubdirs /delregkeys /EmptyRB /y

Once this is run, we then call SAPSETUP in a similar manner described above.

Also in the workstations local SERVICES file we add a service:

sapmsPRD 3600/tcp
The port number will change for your particular installation.
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment
119
Note
Open the SAPAdmin.exe in the CD:\GUI\WINDOWS\WIN32\setup\.
Make a suiteable Package.
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment
119
Note

I repackaged SAP GUI 6.4 Compilation3 using WISE Package studio. I added the merge modules that were recognized by the capture. After compiling my package, I had a problem with the install stating that "setup requires Internet Explorer version 5.0.2314.0 or above." The machine actually had version 6+. I found the issue to be in the SQLBase.msm merge module. I found the solution fixing the merge module and it fixed the package. See the link under the links section for the fix.

Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment
118
Command Line
You can use also the /SILENT Switch:

%ProgramFilesDir%\SAPPC\NetInst\SAPSETUP.EXE" /Patch:"%PathToPatch%\SEM31A.EXE" /SILENT
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment
118
Note
No problems using AdminStudio 7.5's Repackager I took a simple two step snapshot approach which worked fine. Brief summary:
1- Took Repackager 1st snapshot of clean system
2- Installed SAP GUI 6.2 and two EXEs (SAP GUI upgrades) specified by my org's SAP techinical team (one of which entailed a reboot)
3- Took 2nd snapshot, culled resulting IRP of extraneous stuff, created ISM then my MSI and did one final tweak to my MSI:

I added our in-house custom SAPLOGON.INI file, which I wanted to put into the User Profile (as we intend to deploy as a user-assigned app and we have a few different versions of that INI file). In order for the SAP Logon Pad to reference that INI (by default the SAP GUI only looks in Windows directory) I created a new User Environment Variable named SAPLOGON_INI_FILE (SAP GUI looks for this environment variable's value before defaulting to Windows dir for the INI) and set its value to [%APPDATA]\SAP\SAPLOGON.INI
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment
118
Note
I was doing SAP GUI 6.40 installation yesterday:

I repackaged the original installation of the product by Wise Packages Studio 5.6. It went without any problems and at the end it asked for several Merge Modules, which I confirmed. The compiled installation worked fine on clean Windows, the installed application worked nicely.

Unfortunatelly when I tried to install the application to my own computer, it failed. In event log I found it had problem with registering C:\Windows\System32\msxml4.dll. Probably the reason was that MSXML4 packae was already installed on my machine (by another application), but no matter I quickly found a solution.

I deleted all three dll's
Windows\System32\msxml4*.dll
from the installation and added MSXML4 merge module provided by Wise (for which it did not ask for when I run the Setup Capture, don't know why).

Now the installation works fine, not only on clean Windows, but also on all other computers in our company.

And finally, of course I made a small MST transform which adds the SAPLOGON.INI entries to the package, so the client installs directly with the configuration to our SAP servers ready.
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment
117
Command Line
SAP introduced a new method for applying patches automatically in GUI 6.10:

Download the patches from service.sap.com, put the EXE files on the network and call

%ProgramFilesDir%\SAPPC\NetInst\SAPSETUP.EXE" /Patch:"%PathToPatch%\SEM31A.EXE"

This will update a local installation of the SAP GUI.
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment
0
Note

SAP GUI deployment 7.30

If you are combining BW 3.5 to the GUI 7.30, please remember that BW only supports Office 2010. in Office 2013, BW analyzer will break with a VB error that doesnt support Excel 2013. 

what we provided is just the GUI, no BW, and BW provided via Citrix.

Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment

Inventory Records (1)

View inventory records anonymously contributed by opt-in users of the K1000 Systems Management Appliance.

Versions

SAP GUI

Version

6

Questions & Answers (3)

Questions & Answers related to SAP SAP GUI

2
ANSWERS
3
ANSWERS
1
ANSWERS

Blogs (0)

Blog posts related to SAP SAP GUI

Reviews (0)

Reviews related to SAP SAP GUI