Discussion:
Moving .ost file from old to new computers
(too old to reply)
The_professor
2009-02-26 18:24:02 UTC
Permalink
I work in a large organisation that has need to move from .ost files from an
older device being replaced to the new device. We are using XP,
Office/Outlook 2003/ and Exchange 2007. We have recently enabled Cached
Mode, as a part of our upgrade procedure we back up the .ost file from the
old machine to a network share. That .ost file is then copied to the new
machine and the Outlook profile configured to use the copied .ost file. Our
initial testing seem prove this was a workable scenriao. Now, I am seeing
the following error:

"Outlook is using an old copy of your Offline Folder file (.ost). Exit
Outlook, delete the .ost file, and restart Outlook. A new file will be
automatically created the next time you initiate a send/recieve. "

There is a MS article 872930 that describes how the deploy the .oab file for
Cached Mode. I simply want to use a file that is already out there and
contains 98% of the data that the end user needs.

Has anyone tried this before and gotten it to work?
neo [mvp outlook]
2009-02-28 20:07:04 UTC
Permalink
The error message just means that computer you took a copy of the OST from
has started Outlook again and sync'd with Exchange. This destroys the seed
OST that you wanted to use.
Post by The_professor
I work in a large organisation that has need to move from .ost files from an
older device being replaced to the new device. We are using XP,
Office/Outlook 2003/ and Exchange 2007. We have recently enabled Cached
Mode, as a part of our upgrade procedure we back up the .ost file from the
old machine to a network share. That .ost file is then copied to the new
machine and the Outlook profile configured to use the copied .ost file.
Our
initial testing seem prove this was a workable scenriao. Now, I am seeing
"Outlook is using an old copy of your Offline Folder file (.ost). Exit
Outlook, delete the .ost file, and restart Outlook. A new file will be
automatically created the next time you initiate a send/recieve. "
There is a MS article 872930 that describes how the deploy the .oab file for
Cached Mode. I simply want to use a file that is already out there and
contains 98% of the data that the end user needs.
Has anyone tried this before and gotten it to work?
The_professor
2009-03-03 20:45:01 UTC
Permalink
Neo,

Let me see if I understand this correctly;

I backup a user's ost file at 09:00 from computer XP1. Customer reopens
Outlook and continues working. I build computer XP2 and place the .ost file
in the appropriate directory. However, I will receive the error I described
because the customer continued working on the original .ost on computer XP1.
Correct?
Post by neo [mvp outlook]
The error message just means that computer you took a copy of the OST from
has started Outlook again and sync'd with Exchange. This destroys the seed
OST that you wanted to use.
neo [mvp outlook]
2009-03-04 11:53:52 UTC
Permalink
Correct.
Post by The_professor
Neo,
Let me see if I understand this correctly;
I backup a user's ost file at 09:00 from computer XP1. Customer reopens
Outlook and continues working. I build computer XP2 and place the .ost file
in the appropriate directory. However, I will receive the error I described
because the customer continued working on the original .ost on computer XP1.
Correct?
Post by neo [mvp outlook]
The error message just means that computer you took a copy of the OST from
has started Outlook again and sync'd with Exchange. This destroys the seed
OST that you wanted to use.
The_professor
2009-03-04 13:31:01 UTC
Permalink
Thanks for the help, Neo. I am testing and will post the results.
Post by neo [mvp outlook]
Correct.
Post by The_professor
Neo,
Let me see if I understand this correctly;
I backup a user's ost file at 09:00 from computer XP1. Customer reopens
Outlook and continues working. I build computer XP2 and place the .ost file
in the appropriate directory. However, I will receive the error I described
because the customer continued working on the original .ost on computer XP1.
Correct?
Post by neo [mvp outlook]
The error message just means that computer you took a copy of the OST from
has started Outlook again and sync'd with Exchange. This destroys the seed
OST that you wanted to use.
The_professor
2009-03-09 19:14:02 UTC
Permalink
Neo - You are a genius!! Your answer is 100% accurate! After a hours of
running n circles on this issue, this was the answer I was looking for.
Thanks for your help!
Post by The_professor
Thanks for the help, Neo. I am testing and will post the results.
Post by neo [mvp outlook]
Correct.
Post by The_professor
Neo,
Let me see if I understand this correctly;
I backup a user's ost file at 09:00 from computer XP1. Customer reopens
Outlook and continues working. I build computer XP2 and place the .ost file
in the appropriate directory. However, I will receive the error I described
because the customer continued working on the original .ost on computer XP1.
Correct?
Post by neo [mvp outlook]
The error message just means that computer you took a copy of the OST from
has started Outlook again and sync'd with Exchange. This destroys the seed
OST that you wanted to use.
g***@gmail.com
2012-06-22 18:14:13 UTC
Permalink
Post by The_professor
Neo - You are a genius!! Your answer is 100% accurate! After a hours of
running n circles on this issue, this was the answer I was looking for.
Thanks for your help!
Post by The_professor
Thanks for the help, Neo. I am testing and will post the results.
Post by neo [mvp outlook]
Correct.
Post by The_professor
Neo,
Let me see if I understand this correctly;
I backup a user's ost file at 09:00 from computer XP1. Customer reopens
Outlook and continues working. I build computer XP2 and place the .ost file
in the appropriate directory. However, I will receive the error I described
because the customer continued working on the original .ost on computer XP1.
Correct?
Post by neo [mvp outlook]
The error message just means that computer you took a copy of the OST from
has started Outlook again and sync'd with Exchange. This destroys the seed
OST that you wanted to use.
Did you have to resave the old ost?
l***@gmail.com
2013-08-09 05:40:30 UTC
Permalink
The reason why, OLD .ost files cannot be directly move into new devices is that when Outlook is used in Cached Exchange Mode with Exchange server then OST files is created with particular profile. Exchange server encrypts the .ost with same profile only. If old profile is modified then data from ost files will be inaccessible and you will get error messages.

To solve the error and to access old ost file on new system, you are required to convert old ost file to pst file and then import PST files any new computer.

For recovering all data from old ost files PCVITA OST Converter software is the right choice. The software extract entire data (emails, contacts, calendars, notes, lists, tasks etc) from old ost files into Outlook PST files without missing any data value.

Visit the Official Site to Get All Info: http://www.pcvita.com/ost-converter.html
Loading...