Outlook 2003 should easily import an OST file

[Guest]

My father accidentally closed the OST file that contained important data and
has been unable to re-connect to the file using OL 2003. I searched the web
and found TONS of forum posts regarding this problem. People are spending up
to $600 on 3rd party programs to convert the OST file to PST just so they can
recover their data. I am amazed at what a widespread problem this has become.

Outlook should not allow a user to so easily lose valuable data. An option
to import OST files should be added to OL, or a utility should be bundled
with office.

Some forums suggest that XP system restore can reconnect the OST file.
Others have resorted to expensive software, or illegal downloading from
Chinese websites of such software. Software companies are basing their whole
business on the process of recovering OL data, and this should not be
happening.

----------------
This post is a suggestion for Microsoft, and Microsoft responds to the
suggestions with the most votes. To vote for this suggestion, click the "I
Agree" button in the message pane. If you do not see the button, follow this
link to open the suggestion in the Microsoft Web-based Newsreader and then
click "I Agree" in the message pane.

http://www.microsoft.com/office/com...28a4&dg=microsoft.public.outlook.installation

 

[BillR - MVP]

OST files are used with Exchange typically in a work environment. Data,
essentially, cannot be "lost" since it resides on the server. A new profile
connecting to the server should allow access to the data.
Cases we see where data is "lost" include those where an employee no longer
has access to the server. Such issues are between the employer or Exchange
provider and the employee / user. Legal questions regarding ownership can
come into play.

Users often have the ability to backup OST files to local PST files.

I don't think you will ever see native support for OST to PST conversion or
import ability partly because of the possible legal issues involved.

 

[Brian Tillman]

My father accidentally closed the OST file that contained important
data and has been unable to re-connect to the file using OL 2003.

OSTs are just reflections of what are contained on the Exchange server
(since the last sync, of course) and can't be "closed" as you call it. You
can certainly delete the account that was using the OST, but recreating that
account should use the same OST as long as it's within the same profile.

 

[Guest]

Thanks for the reply.

In this case, my father was part owner of a company that went out of
business. The server hosting exchange services was wiped and liquidated. I
understand based on your post why MS protects OST files. I guess my point is
that OL makes it too easy for users to accidentally lost access to data that
may otherwise be unrecoverable.

 

[Guest]

I completely agree. There are scenarios in which the locally residing ost
file is your only point of recovery for the users email. For instance I have
been involved in a situation where a new SBS 2003 domain was installed on new
equipment with the same domain name as the old domain. All the users’ data
was dumped to pst files. All except one imported back fine on the new
domain. On one Outlook literally ate the pst file. We still had the ost
file from the old domain profile on the users machine but you can’t import it
directly nor can you convert it without laying out 600 bucks! Ridiculous.

 

[Guest]

The old "Always in the office and hardwired paradigm".

Here is how I find my self in need of a .ost import.

I am currently working in Haiti and will not be returning to Office for
another 2 months. My 4 year old laptop died (burnt out video card) and my
office sent me a new one. It took me a few hours with an external usb drive
cage containing my old hard drive to get back all my other documents
utilities etc...

If I was back at the home office it would be a trivial task ( <1 hour ) to
enter my account information and download all 1.3 GB of email. However on
the availeble internet link going throgh VPN, It should take around 3 months
to download my email.

That is why I need a way to import .ost files.

Now tell me about those legal isues and how using a 3rd party tool is
diferent from using a built in utility to import email.

 

[Hal Hostetler [MVP-P/I]]

No legal issues and no built-in utility, but certainly possible...for a
price.

http://www.payam.com.au/exchangeconverstion-convertosttopsthtml.htm
OST to PST File Conversion Service
http://officerecovery.com/exchange/
ExchangeRecovery (OST2PST)

Hal
--
Hal Hostetler, CPBE -- (e-mail address removed)
Senior Engineer/MIS -- MS MVP- Print /Imaging -- WA7BGX
http://www.kvoa.com -- "When News breaks, we fix it!"
KVOA Television, Tucson, AZ. NBC Channel 4
Still Cadillacin' - www.badnewsbluesband.com

 

[Rahil]

I lost my 6 years e-mails and other stuff, Microsoft products are not
reliable, particularly outlook is the worst.

I switched over to IBM Lotus Notes, it is very cool e-mail client.

Rahil

 

[Peter Foldes]

How in the heck were you able to manage to add to a 3 yr old thread. Just
curious,that's all

--
Peter

Please Reply to Newsgroup for the benefit of others
Requests for assistance by email can not and will not be acknowledged.

I lost my 6 years e-mails and other stuff, Microsoft products are not
reliable, particularly outlook is the worst.

I switched over to IBM Lotus Notes, it is very cool e-mail client.

Rahil

 

[Brian Tillman [MVP - Outlook]]

I lost my 6 years e-mails and other stuff, Microsoft products are not
reliable, particularly outlook is the worst.

I switched over to IBM Lotus Notes, it is very cool e-mail client.

Poor practices can cause you to lose your data no matter what client you use.
Outlook is certainly as reliable as any other large application.