Best Practice for adding packages??

[mmorris]

I have figured out how to add packages but wondering on software that constently updates like adobe reader?

I have a install for current version but not sure how to best structure files and version info for opsi to handle the next update.

Do i save it to a folder called adobe_reader or do i do adobe_reader_11.09

do i put the name the same for the new update and it will overright it or do i add it like a new package and it will list the 2 diffent versions on opsi and i can remove the old one when i uninstall it? I want to just upload the new one and auto update all clients????

do i put the product id the same for all packages like Adobe_reader and just change the product versions like 11.09 this time and next time create a new package the same just with 11.10 for the version and the server will know to overright the old and upgrade clients? Hope this makes sense!

Thanks!

[n.wenselowski]

Hello mmorris,

one software normally has only one package and you only deploy the newest version.
We generally do not recommend to include the version number in the product id.
If a new version needs to be deployed you change only the product version.

If you now have a software where multiple versions may need to be installed or can be installed side by side you it sometimes makes sense to include the version in the product id.
For Adobe Reader you could have a product with the id adobe_reader_10 and another product with the id adobe_reader_11.

I hope this answers your questions.


With kind regards

Niko