Re: Moving pst files from SBS 2003 to 2008

Thank you all for your time and efforts here. Just starting the build now, going to reformat and reinstall SBS 2008 due to the lousy partition Dell created. I want at least 60-80GB on the OS part.

Exporting the users Outlook files to two places, one external HD and also to a local Temp directory. I'm exporting to a .PST file not a CSV so I hope that doesn't make a huge difference. I usually import the entire file and not just the calendar. I think I understand the difference, but if I only open the .pst file then OWA will not be able to see the email and I have some users that only use OWA. Is totally not advisable to import everything?

Once again, I really appreciate this group and your input.

Bobby.

"Ace Fekay [Microsoft Certified Trainer]" <aceman@xxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:OtEqAi%23%23JHA.1608@xxxxxxxxxxxxxxxxxxxxxxx
"Lanwench [MVP - Exchange]" <lanwench@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:uVdctJ%23%

I suggest doing this from the local workstation, not the server (it isn't
supported to access PST files across a network connection) and also suggest
that you never *import* in Outlook. Just open the PST file in the same mail
profile as the mailbox, and select/copy into the mailbox folders. Much more
reliable and doesn't break timestamps, etc.

Note that users trying to reply to a message swhich was ent by another
internal user prior to the PST export, will get NDRs. They'll need to
replace the recipient's address (even if it looks identical).

I should have made that clear to do it within the Outlook profile, and not from the server. After adding the PST to the profile, copy the emails and other items into the mailbox of the profile.

I should also add, if there are calendar items, they need to exported to a file, then imported into the mailbox's calendar. The calendar items can't be simply copied over. The function for import/export is part of Outlook. One would need to select File/Export, select the PST's Calendar, opt to use a Windows CSV file, save it to a location. Then go back to File/Import, select the CSV file from its saved location, and import.

Also Lanwench, that's a good point about the recipient's address, especially if it's a user in the organization, as well as especially if using the Outlook drop-down box feature that allows you to select previously typed in email addresses, when you start typing a letter, the previous names come up. This is the Nickname list file that gets generated from use, and if one had selected a name from the previous GAL (Global Address List - for all internal users), the name even though the display name is different, the X-400 Identifier for the object within Exchange/AD is actually different for the new system, and will generate an NDR if selected. I've done a few migrations, and that's one of the major complaints some of the folks keep calling me about or emailing me asking why is it when I email Jill, a person in our own company, am I getting this undeliverable message? But of course they failed to listen to me when I told them to delete those entries in the Nickname drop-down box list, and simply click the TO: button and select them from the GAL, or start typing a few letters of their name, and hit the CTRL + K buttons for it to search the GAL, select the user from the GAL, and should be good to go! Funny, they still keep emailing me once in a while with such NDR questions to the point I am ready to delete the ".nk2" file that this data is stored in, in the user's profile, but no, I really don't want to do that because they have other external addresses that I know they want/need.

Cheers!

Ace

.

Loading