Patching conundrum! Best practice?


Have a client / server application called Trent that has been packaged for the client side as an MSI, apologies in advance as it is a long post.

My issue is the best way forward to update this application as the vendor supplies numerous updates with a very short support life for an update (ie 3 - 4 Months!)

Now the application was packaged without enough input from the Server team with regards to the above so the System files (Trent) and the production database Connection files (Tplive) are in one package.

I have thought about patching the Trent system files from 6.1.3 to 6.5 as the test users need to test the Server update on another connection (Egres) that has been updated to 6.5 on the server side. They require the client side system 6.5 update only at this point.

All well so far (maybe!) but once signed off the production users will need their Trent system files and their Tplive connection files updated to 6.5 at the same time.
I tried creating another patch for the updated connection files against the 6.1.3 connection files but it returns a product cannot be uninstalled!?!

The main problem is the end users that use the Tplive connection need both the system files and the database connection updated at the same time. The testers just need the system files updated and will at a later date require the updated Tplive connection files.

This application will follow the same cycle every update, testers system files get updated they sync their test database with the server, then once signed off the users will need the updated system files and the updated tplive database files when the server is updated.

Should I create a system patch only for the developers and then a separate patch to update the users from 6.1.3 to 6.5 that includes both the system files and database connection, or just uninstall 6.1.3 and send a complete install for 6.5 with a new Product ID?

I just want to make this as neat and simple as possible! Has anyone had experience of such an application with separate system files and database files and of Patching with regards to best practice for changing Product ID's etc?

It will all be delivered by SMS

Suggestions / advice much appreciated :D



0 Comments   [ + ] Show comments

Answers (1)

Posted by: BarryB 14 years ago
Orange Belt

I think what I am going to do is have a seperate system upgrade patch and Full systen / connection files patch. Punt the test users in their own group that recieves only the patch and let them sync the database manually.

Cannot think of any cleaner way to do this. [8|]

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

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login


This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ