 |
 |
Preliminary checks don't look good for GUI 7.x. Appdeploy.com rates it high on the difficulty level. It looks like some people are doing the repackage method using a before/after approach but I personally HATE doing those and usually results vary as for reliability. Considering it's basically a canned install, you COULD just add it to a login script to execute silently and just have it write an arbitrary registry key somewhere when it completes that you can use as a check for the next login to prevent reinstalls. Not ideal, and if you're using Windows 7, the login script won't execute as admin, but it'll work for XP. I'm curious to know what AIS did. Jon Galbreath MCSE/Security+ Systems Administrator International Studies and Programs Helpdesk: 517-884-2148 Ph: 517-884-2144 [log in to unmask] -----Original Message----- From: David Graff [mailto:[log in to unmask]] Sent: Thursday, November 18, 2010 4:28 PM To: [log in to unmask] Subject: [MSUNAG] Deployment of SAP GUI Okay, so in looking at the SAP GUI installer and ways to deploy it, the obvious easy way is the throw the /silent switch on the msusapgui720.exe package which will do everything. But I have to mangle together a script to assign through policy to do it that way, and I would rather go through a straight policy package deployment. Extracting the contents of of that package leaves with a number of support files and the sapguisetup.exe installer. This installer invokes the MSI Installer service to do all the work, so there is a package embedded in there somewhere but I have no idea how to get at it. So does anyone have a brilliant idea on ripping an MSI out of this thing?