/build/static/layout/Breadcrumb_cap_w.png

SAPGUI 6.40 with SMS on more Sites

hi to all,
I've a big problem, with distribution SAPGUI 6.40 on my slow secondary sites.
I'va created my package with SAPADMIN.exe on server1\sapinst (share).
On Primary SMS server was created a package with this configuration:
Package Properties
Data source :
\\server1\sapinst
Program Properties
Setupunattended
command-line: setup\sapsetup.exe /p:"{942B9051-3459-4466-A0E9-0F8FA8E4108F}" /sms /force /NoDlg
and I've replicated this package to all remote distribution servers sms on slow sites.
But when I attempt to distribute SAP on a slow site, distribution start but source is \\server1\sapinst, and the installation is very very slow.
I've found that in sapsetup.cfg is mentioned a dsserver and instserver:

[SAPInstallerSvcFiles]
sapfeiis.exe=SAPSetup Installer Service
sapfeilg.dll=SAPSetup Logging Facility
sapsetup.cfg=SAPSetup Configuration File

[SAPDistribSvcFiles]
sapfeiKr.dll=SAPSetup Installer Kernel
sapfeids.exe=SAPSetup Distribution Service
sapfeilg.dll=SAPSetup Logging Facility
sapfeiut.dll=SAPSetup Utilities Library
sapsetup.cfg=SAPSetup Configuration File

[Proxies]
netsetup.exe=/p
admsetup.exe=/server
setup.exe=%1

[Trace]
Level=3
MaxLogSize=8192

[General]
InstServer=\\server1\sapinst
DsServer=server1

if I delete these lines, installation on clients fail, in sapsetup.log appear that cannot find dsserver.
what can I do to get local distribution server on slow sites?

Thanks
gianluca

0 Comments   [ + ] Show comments

Answers (0)

Be the first to answer this question

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ