Wrapper for changing paths on the fly ?
Hi guys,
I need a tool for changing paths on the fly, after the msiexec call is started.
For example, I start a batchfile thru SMS, in the batchfile there are a lot of msiexec calls and this msiexec calls start msi packages on a specifig path.
But on some PC´s the path should be a different one (for every msiexec call, also all dependence packagerepairs from other products)
I know i can change the sourcepath keys in the registry and adjust the path with some logic variables in the batchfile. But this have to be done every time and I also have to change it back after the installation.
Does there exist a wrapper or something else ?
A program that runs parallel with the msiexec process and changes all the paths in the calls....(Hmmm sounds a little bit like a virus.....)
I have a dream.......but maybe it will com true ;-)
thanks
frueh
I need a tool for changing paths on the fly, after the msiexec call is started.
For example, I start a batchfile thru SMS, in the batchfile there are a lot of msiexec calls and this msiexec calls start msi packages on a specifig path.
But on some PC´s the path should be a different one (for every msiexec call, also all dependence packagerepairs from other products)
I know i can change the sourcepath keys in the registry and adjust the path with some logic variables in the batchfile. But this have to be done every time and I also have to change it back after the installation.
Does there exist a wrapper or something else ?
A program that runs parallel with the msiexec process and changes all the paths in the calls....(Hmmm sounds a little bit like a virus.....)
I have a dream.......but maybe it will com true ;-)
thanks
frueh
0 Comments
[ + ] Show comments
Answers (4)
Please log in to answer
Posted by:
AngelD
15 years ago
You could use the SOURCELIST property to add more source paths.
As it's a public property you could provided that to the command line during msiexec execution.
As it's a public property you could provided that to the command line during msiexec execution.
Posted by:
fruehlein
15 years ago
You could use the SOURCELIST property to add more source paths.
As it's a public property you could provided that to the command line during msiexec execution.
ORIGINAL: AngelD
You could use the SOURCELIST property to add more source paths.
As it's a public property you could provided that to the command line during msiexec execution.
Thanks
Yes, but only for the current installed product and not for other affected products.
Our installation will start thru SMS from a share and prompt the user to put in a CD or USB device (if available) with the installation files. And in this case the driveletters can change every time and all affected products must also change the path every time. (We can´t use download and execute, because of very slow connections with a lot of users and not enough harddisk space.)
Posted by:
AngelD
15 years ago
Then I guess you could just create a vbscript/jscript with the info below that you could execute through SMS.
How to programmatically update the source list for an installed Windows Installer package
http://support.microsoft.com/kb/297168
How to programmatically update the source list for an installed Windows Installer package
http://support.microsoft.com/kb/297168
Posted by:
fruehlein
15 years ago
Thank You,
That really helps and is the first step i n the right direction.
I will try it and post my experiences here.
That really helps and is the first step i n the right direction.
I will try it and post my experiences here.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.