Migrating to Exchange 2003

Migrating to Exchange 2003 - cached mode

Hoping that I can get some assistance from the community on this one as I've 
been scratching my head for the past couple of days.  We acquired a company 
and they are hosting their Exchange with an outside firm.  We want to bring 
them inhouse into our domain, however their hosting provider won't allow us 
to run exmerge to bring data over - hosted solution.  All employees run 
cached mode with Outlook 2003, while we do not run cached.  Furthermore, 
there are a great number of users who have large mailboxes; over 1GB in size.

Everything that I'm seeing out there says that having the users change 
exchange servers while in cached mode will equal a loss of email.  Exporting 
mail won't work as they would be exporting large amounts over the wire and 
this, for some, would take all day -- not the fastest internet connection.  
So my question truly falls back to cached mode and whether pointing them to a 
new Exchange server/new user account will allow their mail to sync back to 
the server.

My first thought is no and that they will have to export their email, 
connect to the new server and then import mail.  Is that the concensus?  
We're trying to make this migration as painless as possible, but truly cannot 
see anything other than a chaotic outcome.  Any insight would be much 
appreciated.

-- 
Terrance Bush

date: Fri, 20 Jun 2008 21:33:00 -0700 author: Terrance Bush

Re: Migrating to Exchange 2003 - cached mode

Hi,

You will need to export the cached mail to a pst file (or similar) in order 
to bring the data to a new server.

The cached file (.ost) is linked to a mailbox and can't connect to another 
mailbox.

Leif

"Terrance Bush"  skrev i meddelelsen 
news:BD262B68-738A-4E3E-8B16-2E69B256D5AE@microsoft.com...
> Hoping that I can get some assistance from the community on this one as 
> I've
> been scratching my head for the past couple of days.  We acquired a 
> company
> and they are hosting their Exchange with an outside firm.  We want to 
> bring
> them inhouse into our domain, however their hosting provider won't allow 
> us
> to run exmerge to bring data over - hosted solution.  All employees run
> cached mode with Outlook 2003, while we do not run cached.  Furthermore,
> there are a great number of users who have large mailboxes; over 1GB in 
> size.
>
> Everything that I'm seeing out there says that having the users change
> exchange servers while in cached mode will equal a loss of email. 
> Exporting
> mail won't work as they would be exporting large amounts over the wire and
> this, for some, would take all day -- not the fastest internet connection.
> So my question truly falls back to cached mode and whether pointing them 
> to a
> new Exchange server/new user account will allow their mail to sync back to
> the server.
>
> My first thought is no and that they will have to export their email,
> connect to the new server and then import mail.  Is that the concensus?
> We're trying to make this migration as painless as possible, but truly 
> cannot
> see anything other than a chaotic outcome.  Any insight would be much
> appreciated.
>
> -- 
> Terrance Bush

date: Sat, 21 Jun 2008 13:27:26 +0200 author: Leif Pedersen [ MVP]

Re: Migrating to Exchange 2003 - cached mode

I would tend to agree. I played out a similar scenario in my lab and it 
didn't work.



"Leif Pedersen [ MVP]"  wrote in message 
news:471D79D5-4D4F-4BDD-B5B9-CCE68709C99C@microsoft.com...
> Hi,
>
> You will need to export the cached mail to a pst file (or similar) in 
> order to bring the data to a new server.
>
> The cached file (.ost) is linked to a mailbox and can't connect to another 
> mailbox.
>
> Leif
>
> "Terrance Bush"  skrev i meddelelsen 
> news:BD262B68-738A-4E3E-8B16-2E69B256D5AE@microsoft.com...
>> Hoping that I can get some assistance from the community on this one as 
>> I've
>> been scratching my head for the past couple of days.  We acquired a 
>> company
>> and they are hosting their Exchange with an outside firm.  We want to 
>> bring
>> them inhouse into our domain, however their hosting provider won't allow 
>> us
>> to run exmerge to bring data over - hosted solution.  All employees run
>> cached mode with Outlook 2003, while we do not run cached.  Furthermore,
>> there are a great number of users who have large mailboxes; over 1GB in 
>> size.
>>
>> Everything that I'm seeing out there says that having the users change
>> exchange servers while in cached mode will equal a loss of email. 
>> Exporting
>> mail won't work as they would be exporting large amounts over the wire 
>> and
>> this, for some, would take all day -- not the fastest internet 
>> connection.
>> So my question truly falls back to cached mode and whether pointing them 
>> to a
>> new Exchange server/new user account will allow their mail to sync back 
>> to
>> the server.
>>
>> My first thought is no and that they will have to export their email,
>> connect to the new server and then import mail.  Is that the concensus?
>> We're trying to make this migration as painless as possible, but truly 
>> cannot
>> see anything other than a chaotic outcome.  Any insight would be much
>> appreciated.
>>
>> -- 
>> Terrance Bush
>

date: Sat, 21 Jun 2008 05:01:21 -0700 author: Martin Blackstone

Re: Migrating to Exchange 2003 - cached mode

Martin Blackstone  wrote:
> I would tend to agree. I played out a similar scenario in my lab and
> it didn't work.

I concur.

To the OP:

Export to PST

then

Open the PST file in the new profile (connected to your own 
server/mailboxes) and do not *import* using Outlook- instead, select what 
you want to copy in, and use edit | copy to (or rt-click/drag/drop/copy). 
Importing can often cause problems.

Or exmerge the data back in.
>
>
>
> "Leif Pedersen [ MVP]"  wrote in
> message news:471D79D5-4D4F-4BDD-B5B9-CCE68709C99C@microsoft.com...
>> Hi,
>>
>> You will need to export the cached mail to a pst file (or similar) in
>> order to bring the data to a new server.
>>
>> The cached file (.ost) is linked to a mailbox and can't connect to
>> another mailbox.
>>
>> Leif
>>
>> "Terrance Bush"  skrev i meddelelsen
>> news:BD262B68-738A-4E3E-8B16-2E69B256D5AE@microsoft.com...
>>> Hoping that I can get some assistance from the community on this
>>> one as I've
>>> been scratching my head for the past couple of days.  We acquired a
>>> company
>>> and they are hosting their Exchange with an outside firm.  We want
>>> to bring
>>> them inhouse into our domain, however their hosting provider won't
>>> allow us
>>> to run exmerge to bring data over - hosted solution.  All employees
>>> run cached mode with Outlook 2003, while we do not run cached. 
>>> Furthermore, there are a great number of users who have large
>>> mailboxes; over 1GB in size.
>>>
>>> Everything that I'm seeing out there says that having the users
>>> change exchange servers while in cached mode will equal a loss of
>>> email. Exporting
>>> mail won't work as they would be exporting large amounts over the
>>> wire and
>>> this, for some, would take all day -- not the fastest internet
>>> connection.
>>> So my question truly falls back to cached mode and whether pointing
>>> them to a
>>> new Exchange server/new user account will allow their mail to sync
>>> back to
>>> the server.
>>>
>>> My first thought is no and that they will have to export their
>>> email, connect to the new server and then import mail.  Is that the
>>> concensus? We're trying to make this migration as painless as
>>> possible, but truly cannot
>>> see anything other than a chaotic outcome.  Any insight would be
>>> much appreciated.
>>>
>>> --
>>> Terrance Bush

date: Fri, 4 Jul 2008 10:55:54 -0400 author: Lanwench [MVP - Exchange]

Re: Migrating to Exchange 2003 - cached mode

"Lanwench [MVP - Exchange]" 
 wrote in message 
news:OI2$tYe3IHA.4332@TK2MSFTNGP06.phx.gbl...
> Martin Blackstone  wrote:
>> I would tend to agree. I played out a similar scenario in my lab and
>> it didn't work.
>
> I concur.
>

You cant concur. Only I am allowed to concur. That's why they call me Capt 
Concur.

date: Fri, 4 Jul 2008 08:03:43 -0700 author: Martin Blackstone [MVP]

Re: Migrating to Exchange 2003 - cached mode

Martin Blackstone [MVP]  wrote:
> "Lanwench [MVP - Exchange]"
>  wrote in
> message news:OI2$tYe3IHA.4332@TK2MSFTNGP06.phx.gbl...
>> Martin Blackstone  wrote:
>>> I would tend to agree. I played out a similar scenario in my lab and
>>> it didn't work.
>>
>> I concur.
>>
>
> You cant concur. Only I am allowed to concur. That's why they call me
> Capt Concur.

I can cur.

date: Sun, 6 Jul 2008 13:01:54 -0400 author: Lanwench [MVP - Exchange]

Re: Migrating to Exchange 2003 - cached mode

"Lanwench [MVP - Exchange]" 
 wrote in message 
news:upZl$n43IHA.3384@TK2MSFTNGP04.phx.gbl...
> Martin Blackstone [MVP]  wrote:
>> "Lanwench [MVP - Exchange]"
>>  wrote in
>> message news:OI2$tYe3IHA.4332@TK2MSFTNGP06.phx.gbl...
>>> Martin Blackstone  wrote:
>>>> I would tend to agree. I played out a similar scenario in my lab and
>>>> it didn't work.
>>>
>>> I concur.
>>>
>>
>> You cant concur. Only I am allowed to concur. That's why they call me
>> Capt Concur.
>
> I can cur.
>
Ed is Curspice

date: Sun, 6 Jul 2008 11:21:30 -0700 author: Martin Blackstone [MVP]

Re: Migrating to Exchange 2003 - cached mode

Martin Blackstone [MVP]  wrote:
> "Lanwench [MVP - Exchange]"
>  wrote in
> message news:upZl$n43IHA.3384@TK2MSFTNGP04.phx.gbl...
>> Martin Blackstone [MVP]  wrote:
>>> "Lanwench [MVP - Exchange]"
>>>  wrote in
>>> message news:OI2$tYe3IHA.4332@TK2MSFTNGP06.phx.gbl...
>>>> Martin Blackstone  wrote:
>>>>> I would tend to agree. I played out a similar scenario in my lab
>>>>> and it didn't work.
>>>>
>>>> I concur.
>>>>
>>>
>>> You cant concur. Only I am allowed to concur. That's why they call
>>> me Capt Concur.
>>
>> I can cur.
>>
> Ed is Curspice

Andi is Hospice.

date: Mon, 7 Jul 2008 12:39:24 -0400 author: Lanwench [MVP - Exchange]