Clients not Pulling Package from Local Distribution Points
Hello All,
I am a newbee on SAP. I need to deploy SAPGUI 7.10 to some users. I have packaged the the software with NwCreateInstServer.exe as written on Earl's post.
My problem is this: I have a SMS site server and 5 DP. I created a SMS pacakge from the install server package I created thru NWSAPSetupAdmin and distributed to all DPs. The clients at the regional sites with DPs are pulling from the site server. I need to make the clients pull from their DPs. because pulling from the site server took 1 hour for the software to install. I pointed SMS to run this batch file at the program level:
\\Server\Shared folder\NwSapSetup.exe /NoDLG /Package="my package"
Everytime the clients at the regional site try to run the file pointing to the site server which I do not want.
PLEASE HELP IS NEEDED URGENTLY. I am running out of time.
Any suggestions will be highly appreciated.
I am a newbee on SAP. I need to deploy SAPGUI 7.10 to some users. I have packaged the the software with NwCreateInstServer.exe as written on Earl's post.
My problem is this: I have a SMS site server and 5 DP. I created a SMS pacakge from the install server package I created thru NWSAPSetupAdmin and distributed to all DPs. The clients at the regional sites with DPs are pulling from the site server. I need to make the clients pull from their DPs. because pulling from the site server took 1 hour for the software to install. I pointed SMS to run this batch file at the program level:
\\Server\Shared folder\NwSapSetup.exe /NoDLG /Package="my package"
Everytime the clients at the regional site try to run the file pointing to the site server which I do not want.
PLEASE HELP IS NEEDED URGENTLY. I am running out of time.
Any suggestions will be highly appreciated.
0 Comments
[ + ] Show comments
Answers (2)
Please log in to answer
Posted by:
jcarri06
15 years ago
Hi Abassydo,
I'm assuming that you have created a installation package through NWSAPSetupAdmin (We'll call this NWSpackage for ease sake). Then, you used SMS to create an SMS package from the NWSpackage which, through the SMS package creation, you selected all your DPs for it to be replicated, is this correct?
If so, the NWSpackage you created may not be completely standalone and may be trying to go back to the SAP share for installation files. Are you able to connect to a machine in one of your remote sites and try to launch the installation from the local DP share? If it takes a lifetime even when installing it manually from the DP then you know it's going back to the SAP server...which would point to a problem with the NWSpackage.
Hope this steers you in good direction or sparks other possibilities, good luck.
- J
I'm assuming that you have created a installation package through NWSAPSetupAdmin (We'll call this NWSpackage for ease sake). Then, you used SMS to create an SMS package from the NWSpackage which, through the SMS package creation, you selected all your DPs for it to be replicated, is this correct?
If so, the NWSpackage you created may not be completely standalone and may be trying to go back to the SAP share for installation files. Are you able to connect to a machine in one of your remote sites and try to launch the installation from the local DP share? If it takes a lifetime even when installing it manually from the DP then you know it's going back to the SAP server...which would point to a problem with the NWSpackage.
Hope this steers you in good direction or sparks other possibilities, good luck.
- J
Posted by:
lnarayananr
14 years ago
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.