Modified CIW, Easiest Way to Re-Deploy???

[Mike]

I rolled out Office 2003 SP2 a few months ago. Now, I realize that I'd
like to make a couple changes:
1. Low priority. Plain text default message format, Outlook as editor.
(I know I can do this with GP and I have, but it's too persistent. I
want the flexibility of telling those HTML freaks how to set their own
HTML default).
2. High priority. I configured a default email account for our POP
provider. We're migrating to Exchange Server now. Rather than create
30 profiles, I'd like to just add the account via CIW.

I was thinkin' the best way might be to push CIW changes through a
logon script or even (gasp) uninstall/reinstall Office.

Suggestions??

Thanks,
Mike


keywords: custom maintenance wizard script CIW office 2003 group policy
GPO re-deploy deploy

 

[Mike]

Best solution I've found: use the Custom Maintenance Wizard (not CIW),
deploying the changes via logonscript.

MS KB Q242216 addresses this. It says that it applies to Office 2000,
but seems to all be applicable to Office 2003.

 

[Mike]

Best solution I've found: use the Custom Maintenance Wizard (not CIW),
deploying the changes via logonscript.

MS KB Q242216 addresses this. It says that it applies to Office 2000,
but seems to all be applicable to Office 2003.

 

[Mike]

Best solution I've found: use the Custom Maintenance Wizard (not CIW),
deploying the changes via logonscript.

MS KB Q242216 addresses this. It says that it applies to Office 2000,
but seems to all be applicable to Office 2003.

 

[Mike]

Best solution I've found: use the Custom Maintenance Wizard (not CIW),
deploying the changes via logonscript.

MS KB Q242216 addresses this. It says that it applies to Office 2000,
but seems to all be applicable to Office 2003.

 

[Mike]

Best solution I've found: use the Custom Maintenance Wizard (not CIW),
deploying the changes via logonscript.

MS KB Q242216 addresses this. It says that it applies to Office 2000,
but seems to all be applicable to Office 2003.

 

[Mike]

Best solution I've found: use the Custom Maintenance Wizard (not CIW),
deploying the changes via logonscript.

MS KB Q242216 addresses this. It says that it applies to Office 2000,
but seems to all be applicable to Office 2003.

 

[Mike]

Best solution I've found: use the Custom Maintenance Wizard (not CIW),
deploying the changes via logonscript.

MS KB Q242216 addresses this. It says that it applies to Office 2000,
but seems to all be applicable to Office 2003.

 

[Mike]

Best solution I've found: use the Custom Maintenance Wizard (not CIW),
deploying the changes via logonscript.

MS KB Q242216 addresses this. It says that it applies to Office 2000,
but seems to all be applicable to Office 2003.