msi on a machine with a vanilla clean build of XP. msi that has not been cleaned up just to check basic functionality of the app.) I found that when it was installed and I clicked a shortcut nothing happened.Īfter a lot of head scratching I got to the bottom of it.
Sap gui 740 windows 10 install#
After capturing the install (with installshield - repackager) and building a dirty MSI (e.g. I have just successfully packaged SAP GUI 7.10 after encountering the same problem as you. Have a look here for more information on creating non-MSI installation.
Sap gui 740 windows 10 update#
This applies only the patch / update stuff there is no need to remove & reinstall the application. I've tailored the VB script to check to see if SAP 7.10 is already installed on the PC, if it is, the install is run but with a "/update" switch. All you need to do is patch the Server Installation folder (using the NwUpdateInstServer.exe tool), upload this back onto the SMS Distribution Points and re-run the advert. It's quite a neat way of doing it as makes patching / upgrading the client really easy. When the install command runs from the VB script it installs SAP onto the PC using the data in the Installation Server folder. The Server Installation is basically a folder containing all the files / folders etc that SAP needs to be installed onto a PC.
I used the SAP method (see file NwCreateInstServer.exe) of creating a "Server Installation" of the software and then using SMS to deply this to machines and a VB script to run the install. I don't know how true the threat was but it was still there. In fact, I was told that if we did use an MSI that SAP wouldn't provide support for the client.
I've recently packaged and deployed SAP 7.10 to more than 3,200 (and rising) machines and the one thing I was told before starting was to NOT repackage it into a MSI.
0 kommentar(er)
