Need scripts for sapgui 7.5

[former_member604313]

Hello Matt

First off, this is a great tutorial that you made. I was able to get everything going expect for this scripiting part. I think it is because these scripts are designed for 7.3 version. Would you happen to have full scripts for 7.5 deployment? If you do or anyone else have suggestions, I would appreciate it.

Thank you

Mario

[Stefan-Schnell]

Hello Mario,

welcome in the SAP Community.

I assume you mean the blog SAPGUI Installation Server Part 5 – Scripting from matt.fraser

Please use the member tag and a link to the post for your future questions.

Thanks and best regards
Stefan

[Matt_Fraser]

Hi Mario,

I just replied to your comment on the blog post, but now I see you've repeated this here as a question (which is a good way to go about it). So, I'll just repeat what I wrote over on your blog comment, so there's no need for anyone to keep going back and forth:

First, my apologies for a late reply. I’ve been away from the office for the past three weeks and have just returned today.

Since I wrote this blog series, we have upgraded our environment to use SAPGUI 7.40, but we haven’t yet made the leap to 7.50 (despite 7.40 no longer being in support). I can say that with only minor tweaks everything I wrote here still works in 7.40, but I’m aware that with 7.50 the .xml and .ini configuration file landscape changes somewhat. So, I would imagine that some adjustment to the procedure for managing config files will be necessary.

Nevertheless, you should still be able to utilize a central configuration file (or set of files) on a network share that your users can all access, as I describe here. This should avoid the necessity of copying any files over to their workstations, which can indeed become problematic for local access permissions, version control, etc.

Does it make a difference if the install script is launched by someone with local Administrator permissions vs someone without? If so, then something about the Local Security Handling may not be correctly configured (perhaps a mistyped password in the LSH setup in the NwSapSetupAdmin tool).

You should be able to find troubleshooting hints in log files on the workstation at C:\Program Files (x86)\SAP\SapSetup\LOGs.

Cheers,
Matt

[former_member604313]

Matt

thank you for your reply. I was able to configure everything except the scripts for the .ini and .xml files. I am fine with either having them on a shared drive or to copy to the users profile. Here is where I am now and kind of stuck

When a standard user logs in, the script should run. I tested this on a computer that doesn't have sap, and it worked like a charm. I tested it on a computer that has sap 7.4 and it didn't run or upgrade. I have sap gui 7.5 configure correctly by following your guide. So when a user logs in and has 7.4, isn't Nwsapsaetup.exe supposed to run anyways and upgrade from 7.4 to 7.5? Here is the what is in the .cmd file created to run at logon.

\\servername\sapgui\Setup\NwSapSetup.exe /Silent /Product="SAPGUI"

Also a guide on how to setup the scripts for 7.5 for the .xml and .ini files would be greatly appreciated. Thank for the help. You can also e-mail me marioa@dakotaprovisions.com

Thank you again

Mario.

[Matt_Fraser]

@marioazar,

If you look in NwSapSetupAdmin, you'll see that there are different script possibilities for Installation vs Update, so one definite possibility for why the script doesn't run if SAPGUI already exists on the workstation is a missing On Update End script.

Another, perhaps stronger, possibility is that your existing SAPGUI workstations were installed with a different package name than the package that you're trying to update them to, i.e. the package you have configured on your Installation Server. For instance, if you originally installed the 7.40 guis with a package called gui740, and now you are trying to install with a package called gui750, that isn't going to work. The existing SAPGUIs are going to look for updates to the same package they already have installed, and from the same Installation Server they previously used. So, it's important to use the same Installation Server and to apply the upgrade to the same server package.

Cheers,
Matt