Question about deployd msi/mst
Hello
We use SCCM to deploy our software. As a policy all in house msi´s are built uncompressed with no cabs.
I need to replace a file in each mst of 2 packages, That can easily be done in orca or wise for new installs.
It´s not a key file, to test I just replaced the file without changing the msi/mst and could run the installation/uninstall without errors and the file was in place and got removed . With SCCM I can just do a simple file copy to the already installed workstations. Would that cause a problem?
Otherwise I have to go the uninstall/install route which is kind of shaky due to the fact that you can not schedule in SCCM and users may be working with the software when the advertisement arrives.
We use SCCM to deploy our software. As a policy all in house msi´s are built uncompressed with no cabs.
I need to replace a file in each mst of 2 packages, That can easily be done in orca or wise for new installs.
It´s not a key file, to test I just replaced the file without changing the msi/mst and could run the installation/uninstall without errors and the file was in place and got removed . With SCCM I can just do a simple file copy to the already installed workstations. Would that cause a problem?
Otherwise I have to go the uninstall/install route which is kind of shaky due to the fact that you can not schedule in SCCM and users may be working with the software when the advertisement arrives.
0 Comments
[ + ] Show comments
Answers (2)
Please log in to answer
Posted by:
anonymous_9363
13 years ago
I wouldn't be happy unless I'd updated the MST and replaced SCCM's and WI's cached copies. You haven't touched the MSI so you can leave that alone.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.