Autodesk DWG True View 2013 Package is repairing when launching for standard user.
Hi All,
We want to install autodesk dwg true view 2013 silently. Its working fine after installation. but we do not want it to repair when it is being launched 1st time for standard user. This is the thing which is not required by client.
Does any 1 has any solution or script for this.
Also we do not to use active setup process.
Many Thanks,
Atul
Answers (2)
The repair behaviour is by design: it is installing user-level data (files and/or registry data). It's a one-off hit, too, so why inhibit it?
If you really must then in Application Packager-speak, you need to replace the advertised shortcuts with non-advertised ones.
Comments:
-
Hi VBScab,
Thanks for your reply.
We have done that also....We have set value as NO for advertising shortcut
But still its repairing.
Please suggest any other solution if any.
Thanks - atul2651 11 years ago-
You misunderstand. We're not talking about not advertising the features but changing the advertised shortcuts to non-advertised.
I repeat, however, that this is a bad idea unless you have some other method for distributing user settings and, given that the only other practical method is Active Setup, how are you proposing to do that?
Best find a decent packager. - anonymous_9363 11 years ago
Default msi behaviour is to install the userspecifics for each new user. You can work arround the 'problem' with activesetup (microsoft's solution to trigger installation of the usersettings at logon making the action less visible to the user)
How to enable activesetup is documented on ITninja. pretty easy.
You can always make basic shortcuts as advised but the application might show strange behaviour because user-components will not be installled. Repair even then still be triggerd by file-association (double-click on file) or some COM actions.
You can even clean the setup of user-components. This will get rid of the repair as well. Might result in application failures.
Therefore: use active setup.
Comments:
-
>Default msi behaviour is to install the userspecifics for each new user.
Er...no, it isn't. - anonymous_9363 11 years ago-
Lets see, on the msi's I work with the following happens: Advertised entrypoint selected (shortcut, fileaccociation or com-class) results in the relevant msi component being triggered, system checks for feature, checks for components in feature, checks for feature tree, checks components in feature tree. If it finds components with missing key-files (like HKCU or userdata repair or 'self-healing'is triggered.
What's your default behaviour? - EVEEN 11 years ago-
That only works if the feature tree is arranged so that the feature containing the advertised entry-point is a child of the feature containing the user data and that that parent feature has a KeyPath set.
It is in no way a default behaviour. It has to be 'engineered'. - anonymous_9363 11 years ago -
Hi VBScab, couldn't respond directly to your answer. Must be anti-topic-flooding.
Yes you have a point. You can create a setup design that has entry points that do not repair user settings. In this case though that would be quite weird. So I went directly into "vendor intended for this to happen by using msi standard functionality"-mode. Still think he should go for active setup as a solution though. Slows the first logon after the install but doesn't bother the user with scary screens... (like autodesk users are easily scared)
If he goes for the option of using non-advertised shortcuts let's make him clear up the file associations as well. They still link the extensions to the component of the exe. And have him go through COM as well. Just hope he then has a good ESD solution for the usersettings. - EVEEN 11 years ago
