If you're sticking with Outlook 2000 for now, the CIW is useful just for
creating .prf files. Your only choice is to use newprof and modprof with a
..prf file. Once you migrate to Office 2003, you'll have other options.
--
Sue Mosher, Outlook MVP
Author of
Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers
http://www.outlookcode.com/jumpstart.aspx
"Bryan Linton" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> I'm trying to migrate our organization from our 3rd party POP mail server
> to
> Exchange 2003. Here's some background:
>
> - We'll upgrade to Office 2003 next year, but for now we need to continue
> using Office 2000.
> - Our workstations are currently running unmanaged installations of Office
> 2000.
> - Outlook is configured on each workstation to use our POP mail server.
>
> I want to bring Office into a managed state by deploying a customized
> software installation package via GPO. I want this package, when
> deployed,
> to replace or modify a user's current Outlook profile so that the
> resulting
> profile is configured for exchange instead POP email.
>
> Using the CIW, I've created a package for this and have been testing it.
> It's working correctly for new users, but I'm hitting a snag with existing
> users. If a new user logs into Windows (i.e., a user who has never logged
> into that workstation before) and launches Outlook, Outlook has been
> correctly configured to use exchange for that user. If a user with an
> existing profile logs in and launches Outlook, their existing profile has
> not been altered; it's still congifured to use POP email. I chose the
> option to "Overwrite existing profile" in the CIW, but it seems to have no
> effect.
>
> I've researched newprof.exe and modifyprof.exe, but it's not clear if or
> how
> these tools integrate with the Custom Installation Wizard, or how exactly
> they can be used to solve my problem.
>
> Any help appreciated; thanks in advance.
>
>