Showing results for 
Search instead for 
Did you mean: 

SAP GUI 720 patch level 8 installation via logon script - little problem

Former Member
0 Kudos

We have set up a SAP Distribution Server - SAP Installation Server

We choose to install SAP GUI 720 via logon scripts and we have already done almost 10 Workstations.

The problem is that sometimes, not always, the user has to disconnect and reconnect himself twice in order to be able to run the command inside the bat file (profile.bat).

This is done automatically, no user intervention.

Sometimes it happen that the first time that the user connect himself to the Windows Domain, the command inside the bat file (profile.bat) is not launched, and no log is generated.

If the user disconnect and reconnect himself one more time, the command is launched and the installation went ok.

Maybe this is related to the fact that we want to upgrade more than 1 workstation at a time.

the command inside the profile.bat file is something like this:

sap_distribution_server\sap_inst_server\setup\NWSAPSetup.exe /silent /package:sapgui_720_patch_level_8_instpack

Do you have any idea?

Please advise.

Thank you very much for your time and support.

Best Regards.

Edited by: Franco Bottani on Oct 4, 2011 2:02 PM

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

We use a batch as follows:

net use
<SERVER>\InstServer\Setup /user:<USER> <PASSWORD> /persistent:no

SERVER\InstServer\Setup\NwSapSetup.exe /install /package="<PACKAGE>"

The net use works well for us.



Former Member
0 Kudos

Ok, let's do the question in another way.

Is it possible to upgrade more than one workstation at a time?

Please advise.

0 Kudos

Hello Franco,

you can definitely start NwSapSetup from more than one host at the same time.

You write: "the user has to disconnect and reconnect himself twice". Does this generate log files from NwSapSetup? If not, it looks more like a problem in your environment. The log file is started, as soon as the process NwSapSetup is actually executed. So if there is none, it was not started. If there is a logfile, you might find an answer there...

Best regards, Klaus-Georg Adams

Former Member
0 Kudos

Hello Klaus, thank you very much for your reply.

There are no logs, the user connect himself to the Windows system but the first time nothing happen.

He has to log off and log in again in order to be able to start the process (via logon script) and now the log is generated and the installation is successful.

The problem is that this scenario in not the same for everybody.

For some users it works perfectly well at the first login.

Maybe I need to investigate more at the AD level.

Thank you again.