/build/static/layout/Breadcrumb_cap_w.png
11/04/2009 2187 views
Hello all.

I'm interested to know how people have solved the problem with settings and files which needs to be created for each new user in their profile/registry for first time they use the program. It is possible to do with MSI using rather complex registry/filekey + duplicate file and msi self repair combination, but that is so complex that if I try to explain it to someone else they do not understand it and I get my brains into knot.

So: how do you do those things? Any easy way to do it? Custom action based on file/registrykeypath?

Timo Pietilä
0 Comments   [ + ] Show comments

Comments


Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

All Answers

0
The easiest method I know is using Active Setup key.
Answered 11/04/2009 by: jinxngoblins
Senior Yellow Belt

0
Add below registry, in your package. After Installation, whenever user will log-inn for the 1st time, your application will get repaired with favous, and that perticular user will get settings.


REGEDIT4
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Active Setup\Installed Components\[ProductCode]]
"StubPath"="msiexec /favous [ProductCode]"
"Version"="1.0.0"
Answered 11/04/2009 by: Yaduveer
Orange Senior Belt

0
and that perticular user will get settings. ...which you will need to have added to HKCU in the MSI.
Answered 11/04/2009 by: VBScab
Red Belt

0
Active Setup works only at first login. I would rather have it work immediately after program has been installed, because it is not guaranteed that user logs out and in in next week or so after installation has happened. Othervise I would use Active Setup as it is, like all of you have said, easy method of creating those settings / fixing missing files.

So: any other "easy" ways to do that?
Answered 11/04/2009 by: TimoP
Orange Belt

0
If the user is logged in and you go for a per machine installation, I guess he is sure to have the settings under his account. If you want the settings for any other user, the logged in user has to log off anyway.
Answered 11/04/2009 by: jinxngoblins
Senior Yellow Belt

0
Not when you install using distribution system that installs with system rights. I can't install all 10k+ machines by hand, can't afford to pay for all those adidas-shoes [:)]
Answered 11/04/2009 by: TimoP
Orange Belt

0
So...you're installing per-machine.

Go for an advertised entry-point, whose "parent" feature is a child of another (I tend to call this feature 'CurrentUser') which contains the HKCU junk.As soon as the e/p is triggered (e.g. a shortcut is double-clicked), the package "repairs" and will write the appropriate registry entries and/or files.
Answered 11/04/2009 by: VBScab
Red Belt

0
That's basically what I have done. [:)] You managed to wrap that explanation in very short sentence. Impressive.
Answered 11/04/2009 by: TimoP
Orange Belt

0
Check out John McFadyen's blog on Windows Live. He has a ton of stuff about advertised e/p, self-healing/repair and general WI stuff. I'd post a link for you if my current client didn't block Windows Live...
Answered 11/04/2009 by: VBScab
Red Belt