Script for deployment
Hello here is an issue. I need to deploy a package via SMS, since it is a client install and the shortcut is network location my SMS distribution has been a failure with it not been able to locate the network drive.
The package however installs great locally.
Now what I am thinking is tocreate a script that would copy my .MSI files to the user computer's TEMP folder and iniciate the installation from there using a batch file.
Can anyone help me with the script!!
Thanks
su.deep
The package however installs great locally.
Now what I am thinking is to
Can anyone help me with the script!!
Thanks
su.deep
0 Comments
[ + ] Show comments
Answers (1)
Please log in to answer
Posted by:
anonymous_9363
15 years ago
- You would perhaps have been better off posting a request for a script in the 'Scripting' forum;
- There are thousands of scripts available for download for copying files and creating processes (which is all that needs to happen, after all). Google for 'VBScript file copy' and 'VBScript create process'.
Once you have those, a combination script will be simple to create.
BTW, I think we already established in the 'Package Development' forum that the work-around required to make network-located shortcuts work was to use a public property for the shortcut location (and perhaps the Working Directory, too) and then edit the Shortcut table using those properties. http://itninja.com/question/msi-for-sms-2003-secondary-server-installation?6&mpage=1&key=ꤎ You responded that the solution had worked, yet now you're seeking some horrendous lash-up as an alternative. I don't get it...
- There are thousands of scripts available for download for copying files and creating processes (which is all that needs to happen, after all). Google for 'VBScript file copy' and 'VBScript create process'.
Once you have those, a combination script will be simple to create.
BTW, I think we already established in the 'Package Development' forum that the work-around required to make network-located shortcuts work was to use a public property for the shortcut location (and perhaps the Working Directory, too) and then edit the Shortcut table using those properties. http://itninja.com/question/msi-for-sms-2003-secondary-server-installation?6&mpage=1&key=ꤎ You responded that the solution had worked, yet now you're seeking some horrendous lash-up as an alternative. I don't get it...
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
