Installing SAP Gui 6.4 via SMS 2003
Hi,
i packed SAP Gui via sapadmin including 3 updates.
I created a package and an advertisment. The Package is advertist at the client. The client
manually run the install and some time later the status in the system management is
Last run .... successfull. But theres no installatiion files unter Program Files\SAP....
the command in sms is: setup\sapsetup.exe /p:"{35A0675B-BD3F-434C-A5AF-29233E101D01}" /sms
source directory of the package: D:\Packages\SAP\PRES1\GUI\WINDOWS\WIN32
I have no idea what goes wrong. when i connect a share on the client to the sms server sap gui setup
and call it like sapsetup.exe /p:"{35A0675B-BD3F-434C-A5AF-29233E101D01}" it will be installed on the
client.
Iam not sure if the problem is on the sap package or on the config on my SMS 2003 Server.
Any ideas from you guys ?
thanks,
Marcus
i packed SAP Gui via sapadmin including 3 updates.
I created a package and an advertisment. The Package is advertist at the client. The client
manually run the install and some time later the status in the system management is
Last run .... successfull. But theres no installatiion files unter Program Files\SAP....
the command in sms is: setup\sapsetup.exe /p:"{35A0675B-BD3F-434C-A5AF-29233E101D01}" /sms
source directory of the package: D:\Packages\SAP\PRES1\GUI\WINDOWS\WIN32
I have no idea what goes wrong. when i connect a share on the client to the sms server sap gui setup
and call it like sapsetup.exe /p:"{35A0675B-BD3F-434C-A5AF-29233E101D01}" it will be installed on the
client.
Iam not sure if the problem is on the sap package or on the config on my SMS 2003 Server.
Any ideas from you guys ?
thanks,
Marcus
0 Comments
[ + ] Show comments
Answers (6)
Please log in to answer
Posted by:
travelfreak
18 years ago
Hi,
iam one step ahead: changed the command line to
setup\sapsetup.exe /p:"{35A0675B-BD3F-434C-A5AF-29233E101D01}" /sms /install /silent
and the package will install.
When installation is finished and ill open SAP Logon it appears:
a newer version of SAPLogon.exe is available on the installation source. Would you like to run the update first?
If i click no, SAP Gui starts. If i click yes it appears: All installed components are current. Do you wnat to
override the existing installation and install all components again?
When start SAP Logon next time it come again? Any ideas what went wrong ?
cheers,
Marcus
iam one step ahead: changed the command line to
setup\sapsetup.exe /p:"{35A0675B-BD3F-434C-A5AF-29233E101D01}" /sms /install /silent
and the package will install.
When installation is finished and ill open SAP Logon it appears:
a newer version of SAPLogon.exe is available on the installation source. Would you like to run the update first?
If i click no, SAP Gui starts. If i click yes it appears: All installed components are current. Do you wnat to
override the existing installation and install all components again?
When start SAP Logon next time it come again? Any ideas what went wrong ?
cheers,
Marcus
Posted by:
froggzy
18 years ago
Posted by:
brpo
18 years ago
Posted by:
sallysil
17 years ago
Hello guys,
I want to distribute SAPGUI 640 using Microsoft SMS 2003.
I instaled SAPAdmin and I generated the .pdf and .sms files, but when I tried to
import the .pdf file in the SMS Server using the Create Package from
Definition Wizard, the system shows the following error
message: "Invalid Package Definition File".
Do you know what solution is required to solve this inconvenience?
Best regards,
Sandra
I want to distribute SAPGUI 640 using Microsoft SMS 2003.
I instaled SAPAdmin and I generated the .pdf and .sms files, but when I tried to
import the .pdf file in the SMS Server using the Create Package from
Definition Wizard, the system shows the following error
message: "Invalid Package Definition File".
Do you know what solution is required to solve this inconvenience?
Best regards,
Sandra
Posted by:
brpo
17 years ago
Hi,
you are right, but do not worry about it, as this is just plain text file to import the command line.
you can just edit it if you like to see the settings used and recreated them yourself.
You can use the package name instead of the cryptic reference numbers, also do not reboot the computer as this is not required.
Also pay attention to the fact that with version 640, autoupdates are set on by default, which could not be what you want for keeping your installation base at the same level everywhere.
Brgds
bruno
you are right, but do not worry about it, as this is just plain text file to import the command line.
you can just edit it if you like to see the settings used and recreated them yourself.
You can use the package name instead of the cryptic reference numbers, also do not reboot the computer as this is not required.
Also pay attention to the fact that with version 640, autoupdates are set on by default, which could not be what you want for keeping your installation base at the same level everywhere.
Brgds
bruno
Posted by:
alphaboy
15 years ago
Hello all.
I have create an SAP7.10 package using the NWSETUPADMIN.EXE. The problem is using SMS to launch the package. If I use the following command in a .bat file it works fine...\\Server\Shared folder\NwSapSetup.exe /NoDLG /Package="my package" I get a progress bar with no user intervention. If I run this in SMS it runs a successful silent install with no progess bar. I would like to have a progress bar visable with no user intervention. Any halp on the command line for SMS? I thought it should be the same as the working .bat file?
Regards
Paul
I have create an SAP7.10 package using the NWSETUPADMIN.EXE. The problem is using SMS to launch the package. If I use the following command in a .bat file it works fine...\\Server\Shared folder\NwSapSetup.exe /NoDLG /Package="my package" I get a progress bar with no user intervention. If I run this in SMS it runs a successful silent install with no progess bar. I would like to have a progress bar visable with no user intervention. Any halp on the command line for SMS? I thought it should be the same as the working .bat file?
Regards
Paul
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.