Hi, did anyone ever tackle the problem of servicing TheBat in an Active Directory environment? I'm missing options not only to make a rollout without every user having to enter the same account data all over again on every single machine, but also the possibility to set global options, say to configure the editor not to produce or show html mails by default.
Among others, group policy directives like these would help me: No first run -> if set, the first-run-questions (use encryption, create account now etc) -> will not be shown Establish account set to [account name], [server], [username], [pass] -> this account will be present on all workstations (e.g. a -> company-wide "info"-adress, but also a personal account using -> placeholders like username=windowsuser, password to be prompted -> for or hardcoded) Import account from -> import an account from a (ASCII) definition file/template, to -> automatically create the "company default individual user account" Use adress book file -> Addressbook file that will be used, option to be set whether as -> primary (new entrys will be saved in here) or secondary (personal -> AB will take precedence by default) Use OTFE -> Yes/no Distribute certificate -> roll out (install in TheBat and use there as default) a certificate Mail directory standard path -> accounts will be created unter this base folder Perform backup -> if enabled, use the parameters set with this rule to create a -> backup timetable and control where backups will be saved to, if -> disabled, do not make backups (and don't ask for it either) Check for updates, do autoupdate without prompting -> enable/disable update check, and specify where to check updates -> from: A RIT-server or a local server (admins don't necessarily want -> to roll out a new version as soon as it is published, but only when -> they have declared it solid for their network themselves) Editor -> various settings, from word-wrap behaviour to html-handling How about it? I see two ways to realize this: - The much preferred way, both less complicated to the user and a lot safer in operation would be for TheBat to include this mechanism. - The alternative would be fiddling with scripts like the solution that exists for FireFox: A JavaScript file is executed on user login that simply modifies config files and registry entries based on group policy values found. Working, but not exactly foolproof. Any opinions on this proposal? -- Mit freundlichen Grüßen Alto Speckhardt mailto:[EMAIL PROTECTED]
pgpr5jw1vIHvA.pgp
Description: PGP signature
________________________________________________________ Current beta is 3.99.21 | 'Using TBBETA' information: http://www.silverstones.com/thebat/TBUDLInfo.html
