![install sap gui install sap gui](https://image4.slideserve.com/302884/slide4-l.jpg)
Net developer could write enough code to poll for a > PID and kill it – but if you could do that, you wouldn’t be asking the > question... > So, as others have said, to do that you need to execute something that > is wrapping the SAP ‘nwsapsetup.exe /package=x’ command (something like > a. There is no method I know of to abort the > installation process during the “on begin install” execution. The problem with trying to use the > canned scripted sections, is that these are going to occur ALONG with > the installation. 10/10 for effort, commitment, and having your heart in the right place, but 0/10 for pragmatism... 2 Dean Waelz via sap-basis : > Good Day > I understand what you are doing. thats their job?) you are making your own life much harder. In trying to make this easy for your network team (and err. Not cost, no risk, and bandwidth and disk space on client machines is cheap these days – just roll it out to everyone. (some things just break in portal that work fine with one or another GUI flavour) If you *DO* have MS SMS or simialr deployment tool, why not simply use that? You dont pay licence fees to SAP per deployed GUI, nor can unauthorised persons sign on. If you are using several different versions of the SAPGUI, or SAPGUI / EP access, again, you are asking for grief – use one or the other – UAT becomes a nightmare if using multiple different access methods.
![install sap gui install sap gui](http://4.bp.blogspot.com/-Hzyhn5MWqS8/T17k0AwfR0I/AAAAAAAAAB4/lYHm2VuSU1A/s1600/Adobe+photoshop.jpg)
![install sap gui install sap gui](https://cps.unileoben.ac.at/wp/Franka-Desk-1024x511.png)
some comments: If your org does not have a way to deploy, remove, and monitor what packages are on its workstations in the first place, you are in a spot of trouble.