|
|
|
date: Thu, 24 Jan 2008 07:47:03 -0800,
group: microsoft.public.exchange.clients
back
Re: Moving OST files to another computer - massive mailboxes
Nancy R wrote:
> Hi folks,
>
> I'm not certain this can be done but I need to find out.
>
> We have two remote users who are getting their local computers
> replaced.
>
> Due to security policies we have in place, we were not able to sync
> their Exchange mailbox before the computers were sent out.
>
> They currently use Outlook (one on 2003 and one on 2007) and will be
> moving to Outlook 2007. They are working in cached mode over a slow
> connection.
>
> The both have massive mail boxes and I would like to either move the
> OST from the old machine to the new or to export/import with a PST.
> Doing a resync over the remote connection will take far too long and
> have too big of an impact on our other users.
>
> A long time ago, we successfully did an export/import from a cached
> mailbox with a PST file and did not end up with duplicate messages in
> themailbox but I haven't been able to recreate this minor miracle.
>
> Any suggestions?
>
> TIA,
> Nancy
You can't send them the OST files & expect them to work or even be
accessible - those files are permenantly linked to not only the mailbox, but
also the Outlook profile, in which they were created. I'd have them trigger
the initial sync over a weekend. You can have them set up Outlook to sync
headers only, then full data, so the users can work in the meantime.
Avoid PST files - they won't help you if you want to keep the data
centralized on the server at all, and the mailbox data will actually
increase in size if you dump it out to PST anyway.
date: Thu, 24 Jan 2008 11:06:12 -0500
author: Lanwench [MVP - Exchange]
Re: Moving OST files to another computer - massive mailboxes
Thanks for the help.
We had done this successfully a while ago (halt the sync process immediately
after the user folders were created on the client then import the e-mail from
a PST) but I guess we were just lucky.
Nancy
"Lanwench [MVP - Exchange]" wrote:
> Nancy R wrote:
> > Hi folks,
> >
> > I'm not certain this can be done but I need to find out.
> >
> > We have two remote users who are getting their local computers
> > replaced.
> >
> > Due to security policies we have in place, we were not able to sync
> > their Exchange mailbox before the computers were sent out.
> >
> > They currently use Outlook (one on 2003 and one on 2007) and will be
> > moving to Outlook 2007. They are working in cached mode over a slow
> > connection.
> >
> > The both have massive mail boxes and I would like to either move the
> > OST from the old machine to the new or to export/import with a PST.
> > Doing a resync over the remote connection will take far too long and
> > have too big of an impact on our other users.
> >
> > A long time ago, we successfully did an export/import from a cached
> > mailbox with a PST file and did not end up with duplicate messages in
> > themailbox but I haven't been able to recreate this minor miracle.
> >
> > Any suggestions?
> >
> > TIA,
> > Nancy
>
> You can't send them the OST files & expect them to work or even be
> accessible - those files are permenantly linked to not only the mailbox, but
> also the Outlook profile, in which they were created. I'd have them trigger
> the initial sync over a weekend. You can have them set up Outlook to sync
> headers only, then full data, so the users can work in the meantime.
>
> Avoid PST files - they won't help you if you want to keep the data
> centralized on the server at all, and the mailbox data will actually
> increase in size if you dump it out to PST anyway.
>
>
>
>
date: Thu, 24 Jan 2008 11:54:03 -0800
author: Nancy R
Re: Moving OST files to another computer - massive mailboxes
Nancy R wrote:
> Thanks for the help.
>
> We had done this successfully a while ago (halt the sync process
> immediately after the user folders were created on the client then
> import the e-mail from a PST) but I guess we were just lucky.
I really can't see how this would help you. The PST data would have to be
created from the mailbox and then removed. Then you'd configure an empty
mailbox with an OST file. If they were to copy (never import in Outlook!)
the PST data into Outlook, you'd *still* be syncing a boatload of data
between the client and the server. Oh, and it'd be more data.
>
> Nancy
>
> "Lanwench [MVP - Exchange]" wrote:
>
>> Nancy R wrote:
>>> Hi folks,
>>>
>>> I'm not certain this can be done but I need to find out.
>>>
>>> We have two remote users who are getting their local computers
>>> replaced.
>>>
>>> Due to security policies we have in place, we were not able to sync
>>> their Exchange mailbox before the computers were sent out.
>>>
>>> They currently use Outlook (one on 2003 and one on 2007) and will be
>>> moving to Outlook 2007. They are working in cached mode over a
>>> slow connection.
>>>
>>> The both have massive mail boxes and I would like to either move the
>>> OST from the old machine to the new or to export/import with a PST.
>>> Doing a resync over the remote connection will take far too long and
>>> have too big of an impact on our other users.
>>>
>>> A long time ago, we successfully did an export/import from a cached
>>> mailbox with a PST file and did not end up with duplicate messages
>>> in themailbox but I haven't been able to recreate this minor
>>> miracle.
>>>
>>> Any suggestions?
>>>
>>> TIA,
>>> Nancy
>>
>> You can't send them the OST files & expect them to work or even be
>> accessible - those files are permenantly linked to not only the
>> mailbox, but also the Outlook profile, in which they were created.
>> I'd have them trigger the initial sync over a weekend. You can have
>> them set up Outlook to sync headers only, then full data, so the
>> users can work in the meantime.
>>
>> Avoid PST files - they won't help you if you want to keep the data
>> centralized on the server at all, and the mailbox data will actually
>> increase in size if you dump it out to PST anyway.
date: Thu, 24 Jan 2008 22:55:38 -0500
author: Lanwench [MVP - Exchange]
|
|
