Does anyone know how to configure SAP Logon 640 so that the logon pad does not pop-up or appear in the system tray when the GUI is accessed via the enterprise portal?
Help others by sharing your knowledge.
AnswerRequest clarification before answering.
Hi Leticia,
couldn't you use the SAP installation servers for distributing SAP GUI? I would assume that you could also add additional registry keys before running the distribution. Or are there other restrictions that prevent you from doing this?
Best regards,
Christian
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Leticia,
We had the same problem (with the size), it started with a recent compilation of 6.20. We deleted the Adobe folder and all the CAB files. That shrunk it to a reasonable size. The install checks out when we run a SAPSETUP /Check, but SAP recommended against this in a Customer Message.
We use SMS to host the installation, not the SAP Installation Service. It appears (we haven't done a trace to verify) that the CABs are only used by the SAP Installation Service.
Regarding repackaging the installation in Windows Installer, given the complexity of the installation, I don't recommend it and I'm pretty sure that SAP does not recommend it either. We use SMS Installer to do customizations like modifying registry keys, but SAP now has the ability to call scripts in the install to accomplish the same things.
Regards,
John
Hi John,
I noticed that you use SMS to deploy your frontend. I am currently having issues deploying 6.40 c3 with a SAP Installation Server and the pdf file it creates.
How do you have SMS hosting the installation w/o the installation server? We require several modules to be installed (BW,CRM,Outlook, APO/SEM). We would like to install w/o adding another service on the machines.
Any help is appreciated.
Mikio
Hi Mikio,
The process we use to host the installation in SMS is almost identical to setting up a SAP Installation Server. We run ..\GUI\WINDOWS\WIN32\setup.htm from the downloaded compilation and select the Intallation Server Setup Option. Supply a regular file share for the location and copy the files. Cancel out of setting up the distribution service. Then run SAPAdmin from the share and set up your GUI package, adding BW etc. You can optionaly export the PDF and SMS files for the package. We don't use them. We add a wrapper program to call sapsetup with our package like:
sapsetup.exe /p:"KC-Complete" /noDlg
Then import the entire folder into SMS. You can then advertise the wrapper program.
Hope that helps.
John
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.