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


Please log in to comment

Community Chosen Answer

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.
Answered 05/27/2011 by: VBScab
Red Belt

Please log in to comment
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.


Thanks, I will do that.
Answered 05/27/2011 by: admaai
Orange Senior Belt

Please log in to comment
Answer this question or Comment on this question for clarity