I've been to a few network configurations where the small company was
upgrading from a peer-to-peer environment to Small Business Server 2003,
and they wanted to continue to use their Pop3 settings on each
individual client until the server was up and stable.
Personally, if you ask me, I think you should just get yourself some
solid hardware, install SBS and put the peddle to the metal! SBS just
works best in that scenario.
But, for those of you who have trust issues, here is a little tip that
might help out. By default, each time a user logs into their client
computer a script is run to change the default Outlook mail provider to
the Exchange server (SBS in this case).
Don't want this to happen?
No problem, create a DWORD in the registry under
"NoTransportOrder" and set the value to "1" (without quotes).
The next time the user logs on, the transport order won't get changed,
and you may see the following in the logs: "DoOutlookTransportOrder() -
skipping because NoTrasportOrder was set."
The down side of this method is when you do decide to move over to
Exchange (and I strongly suggest you do), you'll have to go and touch
all your clients again.
Why not just configure the pop3 connector on the server instead?
One thing you might consider, and might give you troubles that has recently come to my attention, is if you opted not to install fax (and hence the fax outlook transport is not installed from the server), and set this registry key, then if you ever DID decide to install fax; fax would now be the default profile. This could cause some issues, so just be aware of it.