SAP GUI for Windows Installation Server

[former_member672317]

Hi,

We have went through the frontend installation guide LINK , but still have some questions on the Installation Server.

1. Does the SAPGUI client’s user need admin privileges to the local computer in order to update? (Tried installing silently through a batch script with LSH configured, but it failed ([path to nwsapsetup] /Silent /Package="Basic"))
2. If not, how does the SAPGUI get admin privileges to update the SAPGUI?
3. Can AWUS be configured after the SAPGUI has been deployed?
4. Possible gets updated after every check-in through the AWUS configuration screen?
5. Where do you view the configured AWUS server(s) on a SAPGUI client?
6. How do you test to ensure the AWUS will work?
7. Is the LSH only for the package deployment tool from the installation server manager?
8. Is it possible to modify variables after deployment?
9. Possibly a GPO template?

[andreas_rueger]

Dear Phillip,

1. LSH should allow users without administrative privileges to perform installations/updates. A look at the log file might tell more about why installing failed.
2. SAP GUI does not get admin privileges but NwSapSetup does and it does so via LSH.
3. Yes, it should be possible to install/configure AWUS after the installation of SAP GUI.
4. AWUS usually checks for updates every 24 hours but the interval can be configured. The check for updates happens regardless of a logged-on user.
5. The installation server a workstation has been installed from is stored in the registry at HKLM\SOFTWARE(\WOW6432Node)\SAP\SAP Shared\SAPsourcedir
6. You can test the function of AWUS by updating a package on the server. Every update of a package adds a command for logging something like "Package <PACKAGENAME> has been updated by administrator to version ..." to the "On Update Start" event of the package. This line can be found in the log file NwSapSetup.log on the workstation after the update of the package has taken place.
7. LSH only works for installations from an installation server. The deployment tool can be varied as long as it starts NwSapSetup.exe from the installation server or takes care of elevating privileges by itself.
8. I think most variables can be modified after deployment. I am not sure if that applies to all of them. You might want to test the consequences of modifying a variable after deployment.
9. Not sure what you mean.
   

Best regards
Andreas

[former_member672317]

Hi Andreas,

Thank you for the feedback. We ran into some issues trying to follow your reply:

1. Where are the installation logs located? I assume it is in C:\Program Files\SAP, but without admin access the folder doesn’t exist.
2. Does “every update of the package” mean that using the “Mark as Updated” button will update the package?
3. How can you resolve the “NWSAPSetup was not able to grant you administrator rights” error? I can deploy the software from the server, but when running a batch file \\SERVERNAME\SAPGUI\Setup\NwSapSetup.exe /Silent /Package=Basic it gives the error

[Sriram2009]

Hi Phillip.

1. Yes, it is required administrator privileges or if your are having domain if domain equivalent admin id is required.

2. Create a installer package, through Microsoft SCCM you can deploy for this contact you AD admin.

point number 3 to 9 follow the blogs which will answer your questions

https://blogs.sap.com/2014/05/29/sapgui-installation-server-part-1-getting-started/ https://blogs.sap.com/2014/06/03/sapgui-installation-server-part-2-initial-installation/ https://blogs.sap.com/2014/06/03/sapgui-installation-server-part-3-patching/ https://blogs.sap.com/2014/06/04/sapgui-installation-server-part-5-scripting/ https://blogs.sap.com/2014/06/09/sapgui-installation-server-part-6-lsh-and-distribution/

Regards

SS