-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Wed, 7 May 2008, rosenfield.albert@gmail.com wrote:
What I had in mind was more like:
- I install Thunderbird.
- I create an account named <template>.
- I modify TLS and other settings to work better.
- I click magic button.
- Thunderbird creates a new thunderbird_mycfg.exe.
- User downloads and runs thunderbird_mycfg.exe, which installs Thunderbird, asks the user his/her account name and applies the configuration from step (3), and everything magically works.
I'm currently stuck with SeaMonkey, so I don't know if this works for Thunderbird, too.
On shared computers I install Seamonkey "unattendedly", then the Default User gets a profile pointing to a network share, on which every account has a prepared profile. Then I install %ProgramFiles%\mozilla.org\seamonkey\defaults\pref \all.js", which contains proxy settings mostly.
The prepared profile has been prepared by:
I. Create profile template
- Create a fresh profile.
- Fill in all personal data.
- Close SeaMonkey.
- Delete everything from profile, that is automatically recreated and does not contain no personal information.
- Remove many stuff from prefs.js
- Replace personal data in prefs.js with place holders, e.g. %ACCOUNT% %SURNAME% etc.pp.
- Same with other files, e.g. signature.txt
II. Deploy profile template to network home directory
- Copy profile template
- Acquire user data from database
- replace placeholders.
Everything in II. will work for a local user, too, but to actually have the generated profile registered. I had took some steps into the direction by invoking SeaMonkey - so it automatically creates the default profile -, terminate it, the deploy script searches for the actually profile path ("%AppData%\Mozilla\Profile or ~/.mozilla/profile), then overwrites the files with the template ones and replace placeholders and corrects the paths in prefs.js. But it was not worth the time, so I did not made no script.
Bye,
Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFIIqGjVJMDrex4hCIRAoi5AJ91n4karrtH3JvPRgYK7bKMmI0CHQCgsuc2 191MBBhXXAm5mSNKJQ1FYBI= =liwC -----END PGP SIGNATURE-----