POP3 and Exchange Server Client co-exist

[Jack]

We currently have Exchange 2000 server and Outlook 2002 POP3 clients in our
office. We're planning to convert these POP3 clients into "Exchange Server
clients" so they can take the advantage of collaboration features in the
Exchange. I have two questions for the set up:

1) Exchange client will use local OST file to sync with the Exchange. Can
the data in PST file be imported into OST file so the PST file can be
removed?
2) Can our staffs still be able to use POP3 with PST file at home to
retrieve emails and co-exist with their office's Exchange Server client
account? If so, should the "remove message from server in xx days" check
box should be disabled from the POP3 setup at home?

Thanks,
-jack

 

[Lanwench [MVP - Exchange]]

We currently have Exchange 2000 server and Outlook 2002 POP3 clients
in our office. We're planning to convert these POP3 clients into
"Exchange Server clients" so they can take the advantage of
collaboration features in the Exchange. I have two questions for the
set up:

1) Exchange client will use local OST file to sync with the Exchange.
Can the data in PST file be imported into OST file so the PST file
can be removed?

Import the PST files into the mailboxes & then sync to OSTs. Be careful
about PST file sizes, tho - make sure they don't exceed your mailbox quotas
(which you should set on the mailbox store level). Why does everyone need an
OST file, btw? They're generally used for laptops, home computers, etc -

2) Can our staffs still be able to use POP3 with PST file at home to
retrieve emails and co-exist with their office's Exchange Server
client account? If so, should the "remove message from server in xx
days" check box should be disabled from the POP3 setup at home?

Actually, it's usually "leave a copy of messages on server" - and you have
to tick it. However, I don't recommend that you open up POP like this- it's
inevitable that at some point a client will forget to tick that box & poof -
the mail is removed from the server. Have them use OWA instead when outside
the office & everything stays in one place -plus they can use more features.
If that isn't an option, at least use IMAP instead of POP.

 

[Jack]

Thanks for the reply, Lanwench. Please read in-line reply:

"Lanwench [MVP - Exchange]"

Import the PST files into the mailboxes & then sync to OSTs. Be careful
about PST file sizes, tho - make sure they don't exceed your mailbox quotas
(which you should set on the mailbox store level). Why does everyone need an
OST file, btw? They're generally used for laptops, home computers, etc -

We have concern when server is down there'll be no access to the message
store or if the messages get deleted by accident on the server...we're worry
the single point of failure could interrupt the daily operation. With the
OST file, people can continue checking their received messages, contact, or
calendar when server is off-line. I'm new to the "Exchange Server Client"
setup, but does this make sense to you or is there a better way to achieve
this?

Actually, it's usually "leave a copy of messages on server" - and you have
to tick it. However, I don't recommend that you open up POP like this- it's
inevitable that at some point a client will forget to tick that box & poof -
the mail is removed from the server. Have them use OWA instead when outside
the office & everything stays in one place -plus they can use more features.
If that isn't an option, at least use IMAP instead of POP.

Good point! We'll use either IMAP or OWA from remote then. Thanks for your
input! -jack

 

[Lanwench [MVP - Exchange]]

Thanks for the reply, Lanwench. Please read in-line reply:

"Lanwench [MVP - Exchange]"

Import the PST files into the mailboxes & then sync to OSTs. Be
careful about PST file sizes, tho - make sure they don't exceed your
mailbox quotas (which you should set on the mailbox store level).
Why does everyone need an OST file, btw? They're generally used for
laptops, home computers, etc -

We have concern when server is down there'll be no access to the
message store or if the messages get deleted by accident on the
server...

Your server really ought to be built so well that it doesn't go down
regularly, and maintenance should be done after hours. - you can use OSTs if
you like, but note that unless you use OL2003 in cached mode, the server
interruption won't be transparent to the user. Also, any deletions will of
course be reflected in the OST file, so that doesn't save you much.
Use Deleted Item Retention so users can get back what they want. I usually
set it for 30 days on the store - but much depends on how many users, how
big your mailbox quotas are, whether you're using Enterprise or Standard,
etc

we're worry the single point of failure could interrupt the
daily operation. With the OST file, people can continue checking
their received messages, contact, or calendar when server is
off-line.

How are they going to get their mail when the server is unavailable? Don't
use POP in your clients - host all your mail on the Exchange server. See
http://www.msexchange.org/tutorials/MF002 for help with hosting your
Internet mail directly on the server. For backup, it's good to have your ISP
or someone else to whom you pay a nominal annual fee (such as dyndns.org)
set up to queue up mail when your server is down - you put their server in
your public DNS as a lower priority (higher cost) MX record so that they can
queue and automatically retry delivery for you for X days.

I'm new to the "Exchange Server Client" setup, but does
this make sense to you or is there a better way to achieve this?

If you haven't set up AD/Exchange before, you might want to get a consultant
to come in and do the setup and show you how to do the regular admin stuff,
to make sure you're set up right....

Good point! We'll use either IMAP or OWA from remote then. Thanks
for your input! -jack

No problem Note in the future that it isn't necessary to crosspost to so
many groups - pick two or three relevant groups. A lot of people sub to the
same groups.