M
Marty
We currently use a vb script to write the "UserMicrosoft Exchange Instant
Messaging" key for new users, so messenger is set up automatically for them.
We are going to migrate to Office 2003 (from 2000) and are creating a
standard build, using the Custom Installation Wizard. Can I make my script
redundant, by having the Custom Installation Wizard set this up for the user?
I don't see a setting for this, but you can have the wizard write registry
settings for you. The problem with this is the setting is user specific
(username@ourdomain). I tried using %username%@ourdomain as the setting but
it doesn't get resolved to an actual username. My current plan is to convert
my script to a VB6 exe and call that from the wizard - at least the
customisations will be controlled from a single source (the wizard) and one
less thing will be in the logon script (startup time is a big issue here).
Any better ideas ?
Messaging" key for new users, so messenger is set up automatically for them.
We are going to migrate to Office 2003 (from 2000) and are creating a
standard build, using the Custom Installation Wizard. Can I make my script
redundant, by having the Custom Installation Wizard set this up for the user?
I don't see a setting for this, but you can have the wizard write registry
settings for you. The problem with this is the setting is user specific
(username@ourdomain). I tried using %username%@ourdomain as the setting but
it doesn't get resolved to an actual username. My current plan is to convert
my script to a VB6 exe and call that from the wizard - at least the
customisations will be controlled from a single source (the wizard) and one
less thing will be in the logon script (startup time is a big issue here).
Any better ideas ?