How do you upgrade packages
Hello Everyone
I am wondering what is the most common used way of upgrading a package or appling a patch. Say you have a change to a shortcut of a package and use SMS2003, users that already have the package should receive the change and new users should get immidiately the correct package. Would you use a patch (MSP) or would you created a MSI and make the change to the shorcut, use the upgrade code and distribute this MSI counting on the upgrade principal. And what to do with version numbers?
We are using SMS for some time and now get to the point that we have to upgrade or apply patches to MSi's we have distributed. What is best practise or what is your way of doing this.
Regards,
Robin
I am wondering what is the most common used way of upgrading a package or appling a patch. Say you have a change to a shortcut of a package and use SMS2003, users that already have the package should receive the change and new users should get immidiately the correct package. Would you use a patch (MSP) or would you created a MSI and make the change to the shorcut, use the upgrade code and distribute this MSI counting on the upgrade principal. And what to do with version numbers?
We are using SMS for some time and now get to the point that we have to upgrade or apply patches to MSi's we have distributed. What is best practise or what is your way of doing this.
Regards,
Robin
0 Comments
[ + ] Show comments
Answers (1)
Please log in to answer
Posted by:
francist
17 years ago
All I can tell you is what our 'best practice' is and why.
We use a deployment tool (not SMS) which relies on installation of applications from servers. The applications themselves are 'administratively installed' to the servers and then get installed from the servers to PCs.
This means that any 'patches' would have to be applied to the 'administrative shares' on the servers and then an instruction has to be sent to each PC to effectively 'repair' itself. Believe me.. it's a nightmare.
So our 'best practice' is to always use 'upgrade' packages...
We use a deployment tool (not SMS) which relies on installation of applications from servers. The applications themselves are 'administratively installed' to the servers and then get installed from the servers to PCs.
This means that any 'patches' would have to be applied to the 'administrative shares' on the servers and then an instruction has to be sent to each PC to effectively 'repair' itself. Believe me.. it's a nightmare.
So our 'best practice' is to always use 'upgrade' packages...
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.