I have an application that is distributed with sms on a per-user basis (as soon as possible). This was required as a must for the end-users.

The msi package consists of 2 executables and some current-user registry keys.
So no advertised shortcuts. (user requirement [X(])

The problem arrises when user2 logs on to a machine where user1 has logged on before. Both of them are member of the group on which the package is advertised.
Because user1 allready installed the package SMS doesn't install the package for user2 and de CU-keys are not repaired.

So, i want a repair of the msi.
Because i cannot use a advertised shortcut, i have to search for another solution to initialize the repair.

The executables installed on the machine are started from a word-macro. Can i make an executable/file in my msi-package advertised?
0 Comments   [ - ] Hide 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.
Answer this question or Comment on this question for clarity


mickman....have a look here and see if this solution helps you out

Answered 01/07/2005 by: MSIMaker
Second Degree Black Belt

Please log in to comment
Thanx, i found that discussion earlier.

That could work. But i was wondering if i could use a file as an entry point for starting a repair.
Answered 01/07/2005 by: mickman
Orange Belt

Please log in to comment