Here's the situation. We use group policy to deploy software packages to computers. Currently in our Visio 2000 group we have about 280 computers. I need to make a small change to the visio 2000 msi. I don't want the existing 280 computes to get the change, cause its only a minor change. However, I would like any new computers added to the Visio 2000 group from this point forward to get the new msi which includes the change. Hope that makes sense.

My question.... Is there a way to make the change to the existing Visio 2000 group, and specify that I only want the change applied to new computers added to the group, and not to change existing computers in the group? I don't think there probably is a way to do this, but thought I'd ask. I could of course just have a second software group with the updated msi, but to keep things neat I would prefer to have only one Visio 2000 software group.
Thanks in advance....
0 Comments   [ - ] Hide Comments


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.
Answer this question or Comment on this question for clarity


Hi Jamie,
if you just change the MSI on the install source it will perform like you want it to. The existing fleet of machines would get the changes only, if you choose "redeploy" on the GPO.
But be carefull and test it first. Because if you change the MSI, you easely break the self repairing functionality, because the the installed software which is looking for it's source does not find it's original MSI file anymore.
Regards, Nick
Answered 10/25/2006 by: nheim
Tenth Degree Black Belt

Please log in to comment
Have in mind that updating the source MSI and a repair triggers in; updated files/registry may be updated and if they depend on other updated resources the repair may not update all changed resources.
Answered 10/26/2006 by: AngelD
Red Belt

Please log in to comment