Import of .PST files to Exchange 2007 Mailbox
Good morning, First of all apologies as I am not an Exchange admin, but I need to provide users access to Outlook Web Access via Citrix. I have the OWA website available to users and they can log in and get access to their mail, however the users have .PST files (which I understand to contain saved mail/personal folders/Callender entries etc) located on their machine. In one test I can update the callendar on the Outlook client and this doesn't update the Callendar if the user then logs into OWA. I would like to integrate all these features into the mailbox on the Exchange 2007 server so the user is working from the "server" copy of their mailbox so all email/callender etc are centralised and there is no need for .PST files. I have looked at the following technet article attempting to integrate the .PST with the mailbox; http://technet.microsoft.com/en-us/library/bb691363(EXCHG.80).aspx I am running Exchange 2007 SP1 x64 so I have installed the Exchange 2007 tools x86 on an XP machine that has Outlook 2007 installed. I am a member of the local admin groups on both servers by virtue of Domain Admins, and I have the Exchange Admin role directly attached to my account. When running the following powershell commands in the Exchange shell Import-Mailbox -Identity someuser@somedomain.com -PSTFolderPath \\Server\Share\someuser.pst I get the following error [07/12/2010 09:44:19] [0] Executing Command: 'Import-Mailbox -Identity someuser@somedomain.com -PSTFolderPath \\server\share\someuser.pst' [07/12/2010 09:44:19] [0] Trying to open registry key 'Software\\Microsoft\\Windows\\CurrentVersion\\App Paths\\OUTLOOK.EXE'. [07/12/2010 09:44:19] [0] The default value of the registry key is 'C:\PROGRA~1\MICROS~2\Office12\OUTLOOK.EXE'. [07/12/2010 09:44:19] [0] The version of Outlook.exe is '12.0.6423.1000'. [07/12/2010 09:44:19] [0] Searching objects "someuser@somedomain.com" of type "ADUser" under the root "$null". [07/12/2010 09:44:19] [0] Previous operation run on global catalog server 'domaincontroller.somedomain.com'. [07/12/2010 09:44:19] [0] Processing object "Someuser AD Path". [07/12/2010 09:44:19] [0] Searching objects "ExchangeServer" of type "Server" under the root "$null". [07/12/2010 09:44:20] [0] Previous operation run on domain controller 'domaincontroller.somedomain.com'. [07/12/2010 09:44:20] [0] Searching objects "MailboxLocation" of type "MailboxDatabase" under the root "$null". [07/12/2010 09:44:20] [0] Previous operation run on domain controller 'domaincontroller.somedomain.com'. [07/12/2010 09:44:22] [0] Ending processing. [07/12/2010 09:44:22] [0] [someuser] The operation has started. [07/12/2010 09:44:22] [0] [someuser] Initializing MAPI, loading library. [07/12/2010 09:44:23] [0] [someuser] Approving object. [07/12/2010 09:44:25] [0] [ERROR] Error was found for Someuser (someuser@somedomain.com) because: Error occurred in the step: Approving object. An unknown error has occurred., error code: -2147221219 [07/12/2010 09:44:25] [0] [testingc] The operation has finished. I have searched around on this error and the only thing I have come up with is http://social.technet.microsoft.com/Forums/en/exchangesvrgeneral/thread/57cebd85-671f-47eb-8777-2afcc8885218 as I only have one Exchange server is this what is giving the error? Any assistance that can ge given will be greatly appreciated. Kind regards, Ryan
December 7th, 2010 5:14am

Any reason why you are still on Exchange 2007 Sp1? We are now on Exchange 2007 SP3. You would be well advised to upgrade. I also wouldn't recommend trying to load the PST files over a network share. That is not only unsupported, but can lead to corruption. Finally, don't use an account with Domain Admin rights, as that will be blocked by Exchange from having the relevant permissions. Create a new user, grant it the rights in Exchange to do the import, but NOT domain admin rights. If you need it to have local admin rights on the workstation that you are doing the import in, that is fine. Have the PST files located locally on the workstation to do the import. Simon.Simon Butler, Exchange MVP Blog | Exchange Resources
Free Windows Admin Tool Kit Click here and download it now
December 7th, 2010 8:48am

Create a new user, grant it the rights in Exchange to do the import, but NOT domain admin rights. If you need it to have local admin rights on the workstation that you are doing the import in, that is fine. Have the PST files located locally on the workstation to do the import. Simon. Simon Butler, Exchange MVP Blog | Exchange Resources Thank you Simon I have set this up but the issue is still the same, using SP1 as I said before im not an Exchange Admin and havent looked at that yet (But I see 2010 has a nice archiving solution!) I have added the account to the admins group on the XP machine and the Exchange Server but get the same error so Domain Admin didn't seem to make the difference. Any other ideas? Regards, Ryan
December 7th, 2010 11:29am

I didn't mention Exchange 2010, just SP3. They are very different. What permissions have you actually granted this account? Being Domain Admin is not enough - a Domain Admin is actually blocked from accessing mailboxes to do the import. Simon.Simon Butler, Exchange MVP Blog | Exchange Resources
Free Windows Admin Tool Kit Click here and download it now
December 7th, 2010 2:57pm

Hi Simon, I have created a new user and this user is a member of both local admin groups on the XP machine (with the Exchange 2007 tools) and the Exchange server. This user is not a domain admin and has full rights to the mailbox, as well as being an Exchange server admin. I still get the same error. As for 2010 I was merely pointing out it had an archive solution since 2007 lacks one :o) Regards, Ryan
December 9th, 2010 4:29pm

As a test, see if Outlook can open one of those accounts when logged in as the user you created. If not, then the permissions are still incorrect. Simon.Simon Butler, Exchange MVP Blog | Exchange Resources
Free Windows Admin Tool Kit Click here and download it now
December 11th, 2010 1:29pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics