Hi,

I have just setup an Exchange 2003 server and am now faced with switching
over our 500+ users from POP3 to Exchange.

This is what I am shooting for:

User logs on and his Outlook profile is switched from the current POP3 to
the new Exchange. Subsequent logons detect that the change has already been
made and therefore no switch is made and the profile is left as is. If the
user logs in to any machine other than there own, Outlook is configured
automaticaly with no intervention.

So far this is where I'm at:

I have created a new CMW file that overwrites the current POP3 profile and
configures the new profile for exchange. I have used group policy to deploy
this at logon.

So far this works just fine in testing. However, after the first logon and
switch has been made to Exchange, any subsequent logons run the script and
the Outlook profile is backed up and overwritten as opposed to the CMW file
determining that Exchange already exits and no change is therefore needed.
Thus after a week of logging on this will create a mess of backups which
arent needed.

My question is: Is there an easy way to prevent this from happening so that
the switch to Exchange is only done if needed?

Second question: Is it possible to have the users current local POP3 PST
file migrate into the new exchange profile when it is created? I doubt it,
but, maybe? Otherwise I have some procedures for users to import there old
personal contacts and calendar manually.

thanks

Look at the Office Resource Kit for deployment tools - also check
http://www.slipstick.com for .prf instructions.

--
Milly Staples [MVP - Outlook]

Post all replies to the group to keep the discussion intact. All
unsolicited mail sent to my personal account will be deleted without
reading.

After furious head scratching, jwmac asked:

| Hi,
|
| I have just setup an Exchange 2003 server and am now faced with
| switching over our 500+ users from POP3 to Exchange.
|
| This is what I am shooting for:
|
| User logs on and his Outlook profile is switched from the current
| POP3 to the new Exchange. Subsequent logons detect that the change
| has already been made and therefore no switch is made and the profile
| is left as is. If the user logs in to any machine other than there
| own, Outlook is configured automaticaly with no intervention.
|
| So far this is where I'm at:
|
| I have created a new CMW file that overwrites the current POP3
| profile and configures the new profile for exchange. I have used
| group policy to deploy this at logon.
|
| So far this works just fine in testing. However, after the first
| logon and switch has been made to Exchange, any subsequent logons run
| the script and the Outlook profile is backed up and overwritten as
| opposed to the CMW file determining that Exchange already exits and
| no change is therefore needed. Thus after a week of logging on this
| will create a mess of backups which arent needed.
|
| My question is: Is there an easy way to prevent this from happening
| so that the switch to Exchange is only done if needed?
|
| Second question: Is it possible to have the users current local POP3
| PST file migrate into the new exchange profile when it is created? I
| doubt it, but, maybe? Otherwise I have some procedures for users to
| import there old personal contacts and calendar manually.
|
| thanks