Problem configuring client   

We use exchange for intranet email only, mostly so users can access a shared
schedule. External email gets routed through a server outside of our domain.
There is a user who travels, so he has decided he doesn't want to be a part
of the internal system anymore - all emails to him are to go through the
external account.

Outlook was previously configured for him to receive internal email
(external email was accessed via web mail). Now he wants to access the
Exchange emails already sent to him (cached mode was enabled and there is an
.ost file), but not have anything new routed there.

Is it possible to configure Outlook/Exchange so all they do are allow him to
view already existing emails? Does his Exchange account need to be enabled in
order for this to happen?

Thanks very much for any help.

date: Fri, 26 Oct 2007 10:18:02 -0700   author:   Bird Byte

Re: Problem configuring client   

Bird Byte  wrote:
> We use exchange for intranet email only, mostly so users can access a
> shared schedule.

Mind if I ask why? This is always going to be clumsy. You're half in one 
place, half in another - and mixing/matching mail account types in Outlook 
is messy & not recommended. Exchange isn't meant to be used just for shared 
contacts/calendaring - if that's all you needed, there are other options 
available. Search www.slipstick.com.

> External email gets routed through a server outside
> of our domain. There is a user who travels, so he has decided he
> doesn't want to be a part of the internal system anymore - all emails
> to him are to go through the external account.
>
> Outlook was previously configured for him to receive internal email
> (external email was accessed via web mail). Now he wants to access the
> Exchange emails already sent to him (cached mode was enabled and
> there is an .ost file), but not have anything new routed there.
>
> Is it possible to configure Outlook/Exchange so all they do are allow
> him to view already existing emails?

Not really. The OST file is a mirror of the mailbox and shouldn't be used 
unless you're really using Exchange. I'd suggest exporting his mailbox to a 
PST file (use Exmerge on the server) and put it on his laptop.

> Does his Exchange account need
> to be enabled in order for this to happen?

No, not if you do as I suggest.
>
> Thanks very much for any help.

Again, I think you're making things harder for yourself than they have to 
be. Have Exchange handle all your mail as per 
http://www.msexchange.org/tutorials/MF002.html - and have your remote users 
use cached mode&  VPN to reach the Exchange server when out of the office. 
(Or work on an upgrade plan to E2003/2007 so you can use Outlook Anywhere.) 
Your users will get faster mail delivery, you'll be able to centrally scan 
for viruses/spam, use OWA, etc etc etc. The list goes on. Just my $.02.

date: Sat, 27 Oct 2007 14:13:16 -0400   author:   Lanwench [MVP - Exchange]

Re: Problem configuring client   

I'm not setting this up; I am working with something that is already in 
place. Nor am I trying to make things clumsy or harder than they need to be. 
I am trying to clean up an inherited network. Having Exchange handle all mail 
and using cached mode and VPN is not an option for this organization. 

Thank you for the Exmerge suggestion.


"Lanwench [MVP - Exchange]" wrote:

> Bird Byte  wrote:
> > We use exchange for intranet email only, mostly so users can access a
> > shared schedule.
> 
> Mind if I ask why? This is always going to be clumsy. You're half in one 
> place, half in another - and mixing/matching mail account types in Outlook 
> is messy & not recommended. Exchange isn't meant to be used just for shared 
> contacts/calendaring - if that's all you needed, there are other options 
> available. Search www.slipstick.com.
> 
> > External email gets routed through a server outside
> > of our domain. There is a user who travels, so he has decided he
> > doesn't want to be a part of the internal system anymore - all emails
> > to him are to go through the external account.
> >
> > Outlook was previously configured for him to receive internal email
> > (external email was accessed via web mail). Now he wants to access the
> > Exchange emails already sent to him (cached mode was enabled and
> > there is an .ost file), but not have anything new routed there.
> >
> > Is it possible to configure Outlook/Exchange so all they do are allow
> > him to view already existing emails?
> 
> Not really. The OST file is a mirror of the mailbox and shouldn't be used 
> unless you're really using Exchange. I'd suggest exporting his mailbox to a 
> PST file (use Exmerge on the server) and put it on his laptop.
> 
> > Does his Exchange account need
> > to be enabled in order for this to happen?
> 
> No, not if you do as I suggest.
> >
> > Thanks very much for any help.
> 
> Again, I think you're making things harder for yourself than they have to 
> be. Have Exchange handle all your mail as per 
> http://www.msexchange.org/tutorials/MF002.html - and have your remote users 
> use cached mode&  VPN to reach the Exchange server when out of the office. 
> (Or work on an upgrade plan to E2003/2007 so you can use Outlook Anywhere.) 
> Your users will get faster mail delivery, you'll be able to centrally scan 
> for viruses/spam, use OWA, etc etc etc. The list goes on. Just my $.02.
> 
> 
> 
> 
> 
> 
>

date: Sun, 28 Oct 2007 13:07:00 -0700   author:   Bird Byte

Re: Problem configuring client   

Bird Byte  wrote:
> I'm not setting this up; I am working with something that is already
> in place. Nor am I trying to make things clumsy or harder than they
> need to be. I am trying to clean up an inherited network. Having
> Exchange handle all mail and using cached mode and VPN is not an
> option for this organization.

OK - I don't know what you're up against. However, in terms of having a tech 
"cleaning up an inherited network" I would personally expect that to include 
a *real* cleanup - which means getting rid of the POP mail - even if it were 
something you did a little later on.

>
> Thank you for the Exmerge suggestion.

You're most welcome.

>
>
> "Lanwench [MVP - Exchange]" wrote:
>
>> Bird Byte  wrote:
>>> We use exchange for intranet email only, mostly so users can access
>>> a shared schedule.
>>
>> Mind if I ask why? This is always going to be clumsy. You're half in
>> one place, half in another - and mixing/matching mail account types
>> in Outlook is messy & not recommended. Exchange isn't meant to be
>> used just for shared contacts/calendaring - if that's all you
>> needed, there are other options available. Search www.slipstick.com.
>>
>>> External email gets routed through a server outside
>>> of our domain. There is a user who travels, so he has decided he
>>> doesn't want to be a part of the internal system anymore - all
>>> emails to him are to go through the external account.
>>>
>>> Outlook was previously configured for him to receive internal email
>>> (external email was accessed via web mail). Now he wants to access
>>> the Exchange emails already sent to him (cached mode was enabled and
>>> there is an .ost file), but not have anything new routed there.
>>>
>>> Is it possible to configure Outlook/Exchange so all they do are
>>> allow him to view already existing emails?
>>
>> Not really. The OST file is a mirror of the mailbox and shouldn't be
>> used unless you're really using Exchange. I'd suggest exporting his
>> mailbox to a PST file (use Exmerge on the server) and put it on his
>> laptop.
>>
>>> Does his Exchange account need
>>> to be enabled in order for this to happen?
>>
>> No, not if you do as I suggest.
>>>
>>> Thanks very much for any help.
>>
>> Again, I think you're making things harder for yourself than they
>> have to be. Have Exchange handle all your mail as per
>> http://www.msexchange.org/tutorials/MF002.html - and have your
>> remote users use cached mode&  VPN to reach the Exchange server when
>> out of the office. (Or work on an upgrade plan to E2003/2007 so you
>> can use Outlook Anywhere.) Your users will get faster mail delivery,
>> you'll be able to centrally scan for viruses/spam, use OWA, etc etc
>> etc. The list goes on. Just my $.02.

date: Mon, 29 Oct 2007 10:17:20 -0400   author:   Lanwench [MVP - Exchange]