I've created a package of Firefox using Admin Studio. The package works great, and uses self-repair when a new user logs in and launches Firefox. In my environment, new user profiles are wiped on a constant basis (we are a college that maintains lab/classroom environments). The self-repair is great for handling our customized Firefox profile, but is there a way to hide the self-repair popup from users?

I suppose I could disable self-repair and try to create a custom action that will handle copying the Firefox profile into the Default User profile, but I really like the self-repair feature. Please advise. Thank you!
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
Basically self-repair popup can't be controlled through your msi, but yes it can be controlled by command-line or by script installation. Explain the way the MSI gets installed on users desktop.

Jeeoo!
Santro
Answered 10/14/2008 by: zipsantro
Purple Belt

Please log in to comment
0
is there a way to hide the self-repair popup from users? Why would you want to? The alternative is to have the user constantly clicking the shortcut because he/she thinks the application isn't loading. Users are univerally stupid and, when presented with no feedback, will just click and click and click and click and...
Answered 10/15/2008 by: VBScab
Red Belt

Please log in to comment
0
ORIGINAL: zipsantro
Basically self-repair popup can't be controlled through your msi, but yes it can be controlled by command-line or by script installation. Explain the way the MSI gets installed on users desktop.


We've been testing it by running msiexec locally, but we will be pushing packages through LANDesk, which more or less does the same thing with MSI packages. LANDesk can also push batch scripts and executables. Can you please expand on how it can be done?

Thanks,
Dan
Answered 10/15/2008 by: danpixley
Senior Yellow Belt

Please log in to comment
0
Basically while pushing, you will be installing the application and silent installation at this point can be easily be done by using command-line "MSIEXEC /i <MSINAME> /qn". But when ever repair gets triggered users will get the pop-up progress bar. To avoid this you might choose below ways according to your standard and requirement and please note that these ways will have some disadvanteges. But if it can be ignored in compare to reapir pop-up then can be implemented easily.

1. Change you shortcut so that it always do a reapir and then launch the application.
[blockquote]
You have concerns in such case as it will take time to launch your application. But if launch of application doesn't depends upon userprofile data, you can launch first and then do a silent repair.[/blockquote]
2. Create a startup shortcut and point to batch file which will repair when ever users logged in.
[blockquote]
This will be appilcable only in case where wiping of user-profile is done at log-off or login. Then you don't have to change the shortcut which launchs your applicaiton. [/blockquote]
I suggest you to go for option 2. Again people have different opinion on these ways, take advice.

Jeeoo!
Santro
Answered 10/15/2008 by: zipsantro
Purple Belt

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