SAPGUI & SAP Installation Server

Hi experts,
Currently we build a front end package (single installation) then use SMS to push it out to every computer globally. But recently the packages are getting too big to use SMS.
So we consider the SAP Installation Server as our solution on this issue. But still some questions/concerns here need to give your help- who has used the SAP Installation Server already.
1. Do we need some additional hardware requirements for this installation server? In my simple mind, it's just a software which can be running on Windows server.
2. Do we need licensing considerations for this - SAP Installation Server?
3. I have looked over the SAP installation Server guide, seems we don't need to do any maintenance of this. correct?
4. The last question also it's the important one. .  How does the software delivery for SAPGUI work with SAP Installation Servers that may be decentralized around the globe? We are a global company, so it's impossible that just set up one installation server in headquarters.
Please any experts who has the similar experience give me the answer.
Best regards,
Mimi

Good morning, Mimi - We use SMS in combination with the SAP Frontend Installation Server. I will first answer your questions and then explain what we do.
1. You do not necessarily need a dedicated server strictly for the installation server. You should not install multiple versions of the SAPGui on the same server. For instance, if you have both SAPGui 6.40 and SAPGui 7.10, you would want to use 2 separate servers as the installation servers.
2. There is no additional licensing needed for a SAPGui installation server.
3. The only maintenance required is the application of SAP frontend patches as they become available. The patches are applied to the installation server and then you run an update to get the patches from the installation server to the desktop.
4. It is definitely better that you would not try to have a single installation server for a company with offices around the globe. This will increase your administration somewhat because you will have to manage multiple installation servers (applying patches, etc.). The software distribution mechanism of the installation server is that there are two services, a distribution service and an installation service. These are provided so that a user with non-admin privileges can initiate an update to the SAPGui on their desktop. This is an important consideration, because by default, both SAPGui 6.40 and SAPGui 7.10, when installed on the desktop, have a registry key set that automatically checks when SAPGui is launched to see if the patch level on the desktop is the same as the patch level on the installation server. If not, it initiates an update of the desktop. If the user does not have admin privileges, the update will fail.
The process that we utilize here is that we have one installation server. We duplicate the share where the installation server is installed to all of our SMS servers. We have SMS servers in most of our remote offices, so that when the SAPGui is pushed out, the package is not pushed over the WAN, but instead over the local network in that location, thus making it much faster and reducing the load on the WAN. We then run the SAPSetup command and supply the GUID of the package that we want to push out. We chose not to use the distribution and installation services since we want to be able to make sure that each desktop has the same patch level of the SAPGui. So we used the following scripts to disable the automatic update check:
6.40:
<i>Engine.Context.Log.Write "Event 'SAPGUI640_NONADMIN_OnEndInstall' has been invoked"
     Engine.Shell.SetRegValue "HKLM\SOFTWARE\SAP\SAPSetup\SAPstart\AutoUpdate\SapLgPad.exe", "REG_SZ", "ForceOff"
Engine.Context.Log.Write "Event 'SAPGUI640_NONADMIN_OnEndInstall' has finished"</i>
7.10:
<i>NWEngine.Context.Log.Write "Event 'SAPGUI710_SAPGUI710_NONADMIN_OnEndInstall' has been invoked"
Engine.Shell.SetRegValue "HKLM\SOFTWARE\SAP\SAPSetup\SapStart\AutoUpdate\SapLogon.exe\UpdateMode", "REG_SZ", "ForceOff"
Engine.Shell.SetRegValue "HKLM\SOFTWARE\SAP\SAPSetup\SapStart\AutoUpdate\SapLgPad.exe\UpdateMode", "REG_SZ", "ForceOff"
NWEngine.Context.Log.Write "Event 'SAPGUI710_SAPGUI710_NONADMIN_OnEndInstall' has finished"</i>
We have found this to be a very manageable setup.
I hope this helps. Please let me know if you need more information.

Similar Messages

  • SAP Installation Server & GUI 7.10 Remote Installation

    Hello!
    We have installed an SAP Installation Server (8.1.0.104) with SAP GUI 7.10 (Patch 9) and created a package for SAP GUI. On our old installation server there was a "remote installation" button, but here on the new version, we cannot see it. Have there been some significant changes?
    Thanks for helpful answers!

    I had basically the same question about remote installing the gui.  Here is a response from OSS about it.
    I am sorry but we do not provide a Client Push Installation mechanism.
    but only a method to pull a package from an installation server.
    Using for instance
    <SERVER>\<***>\sapsetup /update /silent
    for a pull scenario.
    As stated in note 507996, tool like SMS can be used but you you use
    the [nw]Sapsetup option
    thanx
    PM1K

  • SAP Installation Server not patching client pc's after patching itself

    Hi
    We have setup Installation Server and used it to deploy SAP GUI successfully to client pc's. We encountered a problem in trying to update the installation server with patch level 22. After the patch SAP reported that numerous files or folders were missing on the installation source. Also the client pc GUI's would then display a message saying that a newer version of the GUI was available and would prompt for a response. "Yes" would appear to reinstall the GUI and would give an error afterwards and a "no" would do nothing, only asking to reinstall the next time round.
    We tried to remove the installation server and reinstall it using a different share name. After removing the old share the client GUI's would no longer prompt but also do not update correctly. We again tried to reinstall the installation server to the old share name and although the clients do not prompt, they also do not update; plus the installation server still shows a patch 22 as being applied!
    Is there any way to roll back the installation server completely (i.e. before the patch level)? If not what could I check to make sure that the installation server at least updates the client GUI's correctly?

    We did some tests again to try piece together what happened. The only thing that seems to have happened is that someone had removed the installation package that the clients were using although we can't be sure if that was the problem.
    We were about to reinstall on the share when we decided to try to update the patch level once more. The strange thing seems that after we patched the Installation Server to level 23 the clients were responding correctly to the IS again! Since then they have been able to update with seemingly no issues.

  • SAPGUI 7.10 Installation Server Patching Problem

    Hello,
    A while back I was having a problem with patching a SAPGUI 710 installation server. A suggestion from the forum was that the version of the SAP Download Manager I was using could be corrupting the patch. So I downloaded and installed the latest SAP Download Manager, downloaded the GUI patch and was then able to apply the GUI patch to the Installation Server. Now I am seeing the same sort of problem with trying to apply the recently released BI and BW patches to the 710 installation server. When I run the SAPSetupAdmin.exe tool, select "Patch Server", browse to the patch and select "Next" to apply the patch, nothing happens. I reinstalled the latest Download Manager, but no luck.
    Any suggestions?
    Thanks,
    Tom Grantham

    Hi All,
    I opened up an OSS message with SAP. The response is below. Changing the extension from EXE to exe fixed the problem.
    Tom.....
    10.07.2007 - 11:41:28 CET    SAP    Reply 
    Dear Mr. Grantham,
    There have been rare reports of the latest download manager not
    resolving the issue. I have just been updated from a development supportcolleague there is a small issue with the patch extensions which
    prohibits NwSapSetupAdmin from applying the patches.
    With the patches that you have currently downloaded could you try
    renaming the extension to lower case only please (.EXE to .exe) and thenapply the patches.
    If the patches still cannot be applied then could you kindly try
    downloading and applying the patches for BW & BI from the SAPmats links
    below:
    BW350GUI710_1_10004473.exe
    https://sapmats-de.sap-ag.de/download/download.
    cgi?id=AC2WQZ8ABBYCGNF3DY0KU7AXXXX3HWGKL5EF9HHR78DRX8MUYM
    BI710_1_10004472.exe
    https://sapmats-de.sap-ag.de/download/download.
    cgi?id=KZGA233QK8LX12CS3CRZHMXZCRU0BDQVIXBVMFIOZT8P5EOU7M

  • Front End Installation Server - Administrator rights on client PC's

    We are using a third party repackaging tool to deploy sapgui to our workstations.  This has proven to be problematic in the past and are now considering the SAP Front End Installation server approach.
    After reveiwing the installation guide we are wondering about how packages are deployed to workstations.  Our users do not have administrator priveleges on thier workstations, so is it still possible to deploy packages from the installation server (either where they "pull" it down, or it is pushed down to them).
    This factor is one reason we are still using the third party repackaging tool because packages can be deployed under a "system" account (via a cleint agent on each PC) - in lieu of each user having administrator privelges on their workstations.
    If the SAP Installation server requires users to have these elevated priveleges it won't be an option for us.  Does anyone else have any experience with the Installation server and users who do not have administrator priveleges?
    Any feedback, directions, or links to additional resources would be greatly appreciated and happily rewarded with positive feedback and reward points
    thanks,
    jeff henke

    Hi Jeff. Try to download the SAPGUI 710 instguid. Go to http://service.sap.com/~form/sapnet?_SHORTKEY=01100035870000614745& in left press on 
    "SAP GUI for Windows" -->  7.10, download this file. In this Guide you can read about :
    Local security handling (LSH) lets users on the network deploy SAP front-end components on
    their front ends using NetWeaver SAPSetup without requiring administrative privileges on
    each front end. Regards.

  • No update of Business Explorer 3.50 and SCM via Installation Server 6.40

    Dear all
    We use SAP Installation Server 6.40 to deploy SAP Front End 6.40 and updates. For new installations, target systems will get the latest version of SAP GUI 6.40 (PL 27), Business Explorer 3.50 (PL 13) and Supply Chain Management add-on (PL 6).
    On existing installations only SAP GUI will be patched resp. updated. Business Explorer 3.50 and Supply Chain Management add-on will not be patched by Installation Server. We have checked this by local installation of patch (patch level 13, your present patch level 4). What is going wrong? Has anyone a hint how I can solve this problem?
    Thanks
    PK

    Hi. I'm think first you need to chek this :
    Viewing the Log
    Use
    You can check the installation by viewing the log file sapsetup.log. The log file can be found in:
    • C:\WINDOWS\ under Windows XP
    • C:\WINNT\ under Windows 2000
    The most recent log has no number. The older logs are numbered. The higher the number, the older the log. Each time new log is generated, each of the log numbers is incremented by 1.
    Procedure
    1. Run saplogvw.exe from the server, to start the SAPSetup Log Viewer.
    2. Enter the path and filename of the log file.
    3. Choose Finish.
    The log file is displayed. Errors are colored red. Warnings are colored blue.
    Also run this in command line
    sapsetup.exe /check
    Regards.
    Edited by: Sergo Beradze on Apr 2, 2008 9:44 PM

  • How to repair a 7.20 Installation Server ?

    hello all,
    i set up an 7.20 SAP Installation Server with PL4. It worked fine last month, no changes were made, but now, if i start NWSapSetupAdmin.exe nothing happens. What possibilities do i have to repair the server or to see which part causes trouble?
    Thanks in advance
    Alexander

    Hello,
    Check log file 'NwSapSetupAdmin.log' in folder C:\Program Files\SAP\SapSetup\LOGs. If log file is not created, check Windows Event Viewer (System events).
    Hope that helps.
    Regards,
    Martin

  • SAPGUI 7.10 patch application to installation server.

    I set up SAPGUI 7.10 Installation server on windows. For 6.40,
    when applying frontend patches, we use to follow the below procedure:
    1) Log into service.sap.com.Click on Downloads.2) Click on support
    packages and patch 3) Click on entry by application group.4) Click on
    SAP Frontend Components 5) Click on SAPGUI for windows 6) Click on
    SAPGUI for windows 6.40 7) Click on win32 and download following
    patches BW 3.5 addon patch, sapgui for windows 6.40 patch and sapsetup
    for sapgui 6.40. 8) Once all the required patches are downloaded, next
    step is to create gui package using those patches. 9)Click on
    SAPADMIN.exe, click on apply patch and the patches are applied in the
    following order Setup patch, gui patch, BW patch. 10) Click on Browse
    and go to the folder where the above patches are located and select the
    patch that should be added to the package and click on open. 11) Then
    click on install.12) Then you can check the version of installed
    patches by click on View--> Server Monitor.
    I would like to know, what is the equivalent procedure for SAPGUI 7.10
    and where can I find document about it?

    Try this guide:
    http://www.id.uzh.ch/dl/sw/sap/SAPGUI/SAP_FE_Instguide_710.pdf

  • SAPGUI Remote Installation - Request to SAP for version 7.10

    Hello
    I've been using SAPGUI Installation Server for some time and was quite pleased with the functionality it provided in version 6.4 that made it possible to push the installation to users. However in a new version (7.10) this feature was removed. Although it is possible to run a remote command using new version you have to know the password of a local administrator on the PC. In version 6.4 no password was necessary to push out the installation.
    I believe it is in our, system administrators, best interest to push SAP to restore that functionality.
    Please share your opinion in this thread. Maybe SAP would make it possible again, once they see it is desired and needed by users.
    Paweł Kryczkowski

    Hello Pawel
    "I believe it is in our, system administrators, best interest to push SAP to restore that functionality."
    That is not necessary.... because you can use the   NWsapsetupadmin.exe ->
    Remote -> Execute Process Remotely
    Please also read the documentation in your Installation server ->  NWsapsetupadmin.exe -> press F1 -> Administering an Installation Server -> Controlling Remote Workstations
    Thats All
    Best regards, Sven

  • Applying BW 3.50 patch 3 for sapgui 7.10 to a installation server

    Hi All
    Im applying a few patches to a 7.10 installation server, everything works fine , except for when applying the BW 3.50 patch 3 for 7.10 GUI to the server .. well applying the patch actually works , but afterwards instead of having only 2 products to choose from on the first hierarchy level (Business Explorer and SAP GUI for Windows 7.10), there is suddenly 6 products instead (SAPGUI for windows 7.10, Engineering client viewer, bw 3.5 addon, kw addon, tweak gui and business explorer).
    The real question is .. before applying the patches, I had a package called "complete" which included both available products, after applying 3.50 bw patch, the original package still contains the same two products, but is that adequate ?? or should a new package be created that includes ALL products available after the patch ?
    Or .... is the original package completely patched ??
    I have never before seen a patch apply additional products to the installation server ....
    /Kim

    Hi Kim Sonny,
    nice to hear from you ....
    Ok, please check the note
    #1131768  and
    #1155445 !
    I recommend you to set up a new installation server with the new compilation 3 CD of
    sapgui 710 ! And for this please look into the note #1266552
    Best Regards,
    Sven
    from primary support gsc austria ....

  • Error while performing SAP Installation in HA Env on Windows Server 2008

    Hello,
    I am performing a SAP Installation in HA Environment on Windows Server 2008. I am at the ASCS installation step.
    As per the guide before installing ASCS there are some activities to be carried out on Failover Cluster Management.
    I have done all the steps except one as per the guide. I am stuck in the Add FileServer Step. In this step the guide says to go to the Dependencies tab and add the cluster disk resource to the dependencies list. It also says to add the Name:Virtual NetworkName to the dependencies list.
    Now in my scenario I have 3 shared drives for SAP and I have added each of them in the dependencies list of the new FileServer. The only problem is how do I add the Name:Virtual NetworkName to this list
    When I continue without giving the Network name the system issues a warning "This resource requires dependencies on instances of the following resource types or classes:Network Name. Not adding these dependencies will prevent the resource from working properly. Do you want to save the current settings anyway"
    If I click on Yes and bring this resource online it fails with this error message
    "The action Bring this resource online did not complete.An error occured while attempting to bring the resource 'SAPECC FileServer online'. The cluster resource could not be brought online by resource monitor."
    My question is how to add the Name:VirtualNetworkName to the dependencies list of the FileServer.
    Regards
    Mitesh Nair

    Hi,
    I have resolved the issue with the help of cluster admin
    Regards
    Mitesh

  • SAP installation guiengine:No GUI server connected;waiting for connection

    Hi All,
    I need one help
    I am trying to install SAP ECC 6 in Redhat Linux 5 and database oracle
    I have installed java 1.4.2_16, I have set the environmental variables also.
    But if I start the SAP installation by executing SAPINST , I am facing the below error
    guiengine: No GUI server connected; waiting for a connection on host welcome, port 21200 to continue with the installation
    I have tried to execute xclock to check it, but its gives the below error
    ERROR: canu2019t open display: welcome:0.0
    I found that before setting the below display environmental variable,  xclock worked good, but after setting the below display environmental variable, I am facing this error
    export DISPLAY=hostname:0.0
    I searched for this error, some people posted that we have to change the display environmental variable like export DISPLAY=:0, set DISPLAY=:0.0,
    I tried it but still facing the same No GUI server connected error.
    I hope it will be a problem with display environmental variable and I have no other clues, please help me, Thanks.
    Thanks,
    Senthil.

    Hi,
    We are trying in my personal laptop, so I have not set any ip addess. Is there any other way like our loop back adapter settings in windows, to configure ip address in Redhat linux 5 in individual machines.
    Also I searched in forums few other people who has already faced the same error. They have set the display environment variable export DISPLAY=ipaddress:0.0 with  ip address but they also has faced the same error and itu2019s not resolved.
    Please help me if there will be any other reason for this error, Thanks.
    Thanks,
    Senthil.

  • SAP XI server installation

    Hi all,
    I want to install SAP XI Server.
    Can it installed with Windows XP as OS.
    Thanks in advance
    Neetu

    Hi neetu,
    check this thread that was raised recently,
    XI Installation Step-by-step procedure
    Regards,
    Bhavesh

  • Connect SAP BO server to domain after the installation.

    Hello,
    I would like to ask if it is fine to connect SAP BO BI 4.x Windows host to the customer domain after the installation of SAP BO.
    I was trying to find answer on this but nowhere is explicitly recommended to connect SAP BO host to domain before the installation.
    My question is related to Windows AD Authentication where two conditions need to be secured:
    1. Windows AD authentication only works if the CMS is run on Windows
    2. These Windows machine must be joined to the appropriate AD domain
    What I found till know is that you can use Windows AD Authentication only when SAP BO server is in domain.
    What is concerning me is that when I start with installation of SAP BO on the server which is not connected to any domain then the installation process is taking during the installation actual hostname of the SAP BO server (e.g. boserver) automatically. There is no requirement or possibility to specify hostname or IP address manually during the installation process. And I assume that connecting SAP BO server to the domain after installation will cause that hostname will change (e.g. to boserver.domain.com).
    So question is if this change will cause any issue for functionality of SAP BO application. If not could you please send me an official statement from SAP Note or any BO Documentation as I was not able to find any.
    Thanks in advance for opinions and answers.
    BR,
    Peter

    Hi Bill,
    thanks for reply. I spoke with couple of my colleagues which are supporting AD and yes I can agree with you that connecting server to the customer domain after the installation of BO can bring some limitation up to Domain policy.
    Best practice in order to prevent possible issues is to join server to the domain before installation.
    Another possible issue can be that some customers are using own naming convention for server's hostname so joining server to the customer domain is conditioned by a change of hostname and this can cause issue with correct functioning of BO application.
    Thanks again for your opinion I really appreciate it.
    Wish you a nice week.
    BR,
    Peter

  • Problem in Domain Server for Cluster SAP installation

    Hello,
    SAP Production Landscape Information :
    SAP Version: ECC 6.0
    OS: Windows 2003
    Database : Oracle 10.2.0.2
    Production Server is in MSCS cluster involving two nodes.
    Also, this is a domain installation and hence user SAPSID and SAPSERVICESID resides on altogether different domain Server.
    Problem:
    OS of u2018Windows domain serveru2019 has crashed. Hence, domain server is almost not usable.
    Restart of it takes several hours. Repair of OS is tried by Microsoft without any success.
    So this has resulted into communication problem between SAP Production server and Domain server. As an effect, restart of production server takes approximately an hour.
    And hence I need some solution to resolve this SAP Server    Domain Server link.
    Logically, following can be solution of this problem,
    1.     If Current SAP Production can be made as Local Installation instead of Domain installation. (Basically, creating users locally and making SAP refer that)
    2.     If above is not feasible then replicating domain server on new hardware and making SAP point to this new domain server.
    However, I am not sure about feasibility and procedures for both of above cases.
    Please let me know your views and any other solution for the same.
    Thanks and Regards,
    Nirav.

    Hi Markus,
    Thanks for your reply.
    Possibility of converting domain installation to local is ruled out as MSCS cluster needs domain.
    As you have rightly mentioned, I do have secondary domain sever.
    For More information:
    1)Domain details for primary server are
        Full computer name : APPL-SERVER.SHREE
        domain            : SHREE
       as secondary server is kept shutdown, details are not available. (I can't run both server running simultaneously)
    2)sqlplus "/as sysdba"
    sql> select username from dba_users;
        TSMSYS
        OPS$SHREE\SAPSERVICEPRD
        OUTLN
        OPS$SHREE\PRDADM
        DIP
        DBSNMP
        SAPPRD
        SYS
        SYSTEM
    3) In the services, mainly users are using SHREE\PRDADM & PASSWORD.
    Client have tried shutting down primary and promoting secondary domain controller. However, after that SAP service were not getting started. But on again starting primary controller,start of SAP services were successful.
    As can be seen in 2nd & 3rd point above,SAP database and  SAP services both refer to name "SHREE" which seems domain name and not to hostname.
    So in this case, when I start secondary domain server (primary is shut down) then as SAP is referring to domain name, SAP's service should start.
    However, that was not the case. SAP Services were not able to get started.
    So, do we have to change anything in SAP as to make it point to secondary domain server.
    Let me know your views.
    Regards,
    Nirav.

Maybe you are looking for