Software Deployment

just add the upgrade codes to the upgrade table

Did that - but it doesn't seem to allow me to control the order in which the old MSI's are removed.

Hi ,

Can you explain in detail what you did for upgrade and also let us know what issue you’re facing during upgrade?

AutoCAD must be uninstalled before AutoCAD Language PackWhy? What happens if you don't do that? I can't imagine it would be too much work to make it happen.

ORIGINAL: dannyarya

Hi ,

Can you explain in detail what you did for upgrade and also let us know what issue you’re facing during upgrade?

I added the 2010 MSI's into the Upgrade table of the 2011 transform and changed the sequence of the RemoveExistingProducts action to 1450, which is before the InstallInitialize action. During execution of the 2011 package, the removal of the 2010 MSI's begins, but I need to ensure that the ACAD.MSI must be uninstalled before AcadLP.MSI.

ORIGINAL: VBScab

AutoCAD must be uninstalled before AutoCAD Language PackWhy? What happens if you don't do that? I can't imagine it would be too much work to make it happen.



If the uninstall of the language pack occurs before AutoCAD, it throws an error message on the screen indicating this problem, waits for you to click the OK button and does not perform the uninstall.

I would have thought that it wouldn't have been a big deal, either.

If I can't figure out a solution for the transform to control the uninstall, I'll write a script for SMS to run but I really wanted to have this all wrapped up in a nice little package.


yeah; pun intended.

it throws an error message on the screen indicating this problem...all of which points to that process being controlled by a CA. As such, you could just add an impossible-to-meet condition in order to prevent its execution.

It could conceivably be controlled by AppSearch/LaunchCondition. That is just as simple to circumvent.

sorry; the "must uninstall ACAD first" message is generated by the 2010 Language Pack MSI during its uninstall.

Sssssssssssso.......find out where that message is being generated and bypass it.

Without looking I'd have to say it's a part of the 2010 language pack, which is already installed on the target PC's. Digging into that and developing a way to circumvent it would be much more complicated than running the three “/X” commands in a script – just wanted this to run real smooth!