We have the following problem. We have an eralier version of a program distributed to about 500 users and it's installed 'per user'. Now we have a new release and for different reasons it will have to be deployed 'per machine'.

The problem is that the users needs to get the new application at just about the same time as the old one is removed. We are usign AD with GP as our distribution engine. From my experiments I have not been able to preform an uninstall of the old 'per user' installation with the 'per machine' installation. The old and the new version of the program doesn't work really well when installed together, so we need to make sure that the old 'per user' installation is removed before thenew 'per machine' installation is installed.

Is there any way of forcing an uninstall of the 'per user' installation without having the user logg on/off?
All ideas or suggestiong are welcome!
0 Comments   [ + ] Show Comments

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.

Answers

0
You could run something in their login scripts to kick off the uninstall. But it won't run with admin rights unless they are admins. The other option would be to create a custom script\package that searches for and deletes any instance of the application from the hard drive. Registry values wouldn't be as easy as they are only loaded when the user logs in.
Answered 02/17/2006 by: yarborg
Blue Belt

Please log in to comment
0
A loginscript isn't a working solution, since the program needs to be installed without any action from the user.

Doing a 'manual' uninstall dosn't seem like a solution either. The application is too complex and the risk of missing some importand parts in the registry seems high.
Answered 02/17/2006 by: wicket
Senior Yellow Belt

Please log in to comment
Answer this question or Comment on this question for clarity