loading Outlook 2003 pst files

[Guest]

I have loaded my Outlook 2003 pst files to my Outlook 2007, however now
Outlook 2007 is extremely slow - is there anything I can do to rectify the
problem?

 

[Henry Craven {SBS-MVP}]

Install the Outlook 2007 Speedup patch ....
Update for Outlook 2007 (KB933493)
http://www.microsoft.com/downloads/...FD-1E09-49B6-9003-C4C47539DF66&displaylang=en

If that doesn't help:
Try unloading it, Creating a new "Clean" .pst file for Outlook 2007 and
then importing all the data from the old pst file.

 

[Brian Tillman]

If that doesn't help:
Try unloading it, Creating a new "Clean" .pst file for Outlook 2007
and then importing all the data from the old pst file.

Importing from a PST is not a good idea.

 

[Henry Craven {SBS-MVP}]

Please explain why.

See my earlier post on this.
I and I daresay thousands of others do this regularly on many tens of
thousands of e'Mail accounts without issue so what are you seeing that we
aren't ?

Granted importing Unicode .psts into No-Unicode (ANSI) Outlook wouldn't be a
good thing to try, but someone sucking recent Outlook data into old -pre
2003- versions of Outlook has got to be pretty rare...

 

[Pat Willener]

Some regular contributors to this newsgroup have been around for many
years. You won't believe how many, many, many times we have seen
subjects like "Exported my PST file and now all my contacts are gone",
or "... all my emails are missing", or ...

In most cases the users did not have any backups or even the original
PST file, and once the deed is done, all is lost. Yes, I have seen your
earlier post, but I still don't see why anybody wants to import a PST
file when it simply can be opened with Outlook. There may be exceptions
such as the filtering you mentioned (which I have never seen before),
but in all other cases using Export or Import just calls for troubles.

 

[Henry Craven {SBS-MVP}]

When the P-2-P / workgroup crowd get their first Exchange Server network
environment you need a fast (and cost effective) method to importing all
those .pst files into Exchange. Exmerge is the preferred tool, but that
isn't always practical and a quick Import while migrating their old profile
works fine. Additionally you can't recover Public Folders from the recovery
Storage Group so copy to .pst and import is the only option.

Obviously due to the nature of the newsgroup you're going to see a lot more
of the issues than I do, but in all honesty I've had extremely little issue
with imports, and not hearing issues from ITs in the SMB Space doing similar
work, and as I say we touch many tens of thousands of .psts annually. Maybe
our clients just accept any "Issues" as part of the transition and so we
don't see/hear of them, although I'm pretty sure they aren't that tolerant
.

I wonder, if it's so broken, why: a. MS don't fix it.and b. Why the Import
from .pst exists.
( but then maybe not as I still consider that Outlook as a proof of concept
has been proven and it is not time to seriously code it

 

[F.H. Muffman]

I wonder, if it's so broken, why: a. MS don't fix it.

Why don't they fix *all* of their bugs? I mean, I'm sure you're not
implying that SBS doesn't have any bugs. Why don't they fix *those* bugs?

Those are rhetorical questions. Don't bother trying to answer them.

The reason why they don't get fixed is because the problems generated by the
bug do not amount to enough support incidents so as to impact the
financials. It all comes down to Severity vs. Priority. It might be a high
severity issue (I'd put it as somewhere between a 1 and a 2 of severity.
There is data loss, but it isn't wholesale data loss. For instance, is
formatting data? All depends on the cojones PM defining the problem and how
hard he wants to push.) but that doesn't necessarily mean it is a high
priority issue. Why could a data loss problem not be a high priority?
Because the requirements of the problem to occur are somewhere the other
side of rare.

High Severity != Must Fix.
High Severity != High Priority.
High Priority == Must Fix.

As for the problems that can happen from Importing, well, I'm sure the list
is around here somewhere. But I'm new around here (just old in general) so
I'll just stick to arguing the facts I do know.

and b. Why the Import from .pst exists.

Beats me. Probably because they haven't removed it. I'd say that's the
likely reason it is still there. Again, if they don't get support calls on
it, they don't know its an issue and how big of an issue it is.

 

[Pat Willener]

Importing to Exchange Server is a different matter; the problem(s) occur
when exporting PST to PST, and/or importing PST from PST. I did a bit of
experimenting a while ago; I did not find any real problems, except that
all folder settings were gone. Sometimes the resulting PST file would be
way bigger than the original, sometimes smaller, which is strange to me.

Why doesn't MS fix it? It is probably many inexperienced users who come
here to look for help after they lost data with some sort of export or
import. They are most likely not to issue a case with MS. They often do
not remember *exactly* what they have done. I think that most of their
problems cannot be reproduced, and therefore are very hard to fix.

This, and the fact that some data is known to be lost, is why people
around here do not recommend Import or Export between PST files.

 

[Henry Craven {SBS-MVP}]

I suppose it's some consolation that the product groups are consistent and
it's a "Microsoft Thing"..

 

[Henry Craven {SBS-MVP}]

Thanks to yourself and the others...
That's what I love about Usenet and why I drop in on different associated
lists... you get a good heads up on issues that you may not have had to deal
with yet.

So fingers crossed..

 

[Brian Tillman]

Please explain why.

Already covered in your other thread.