none
pst capture Console

    Question

  • Hi All,

     

    I've Installed Pst Capture Console. I would like to import a pst file into a mailbox in Exchange Online.

    In Tools\Settings\Online Connection, the check password & connectivity is OK.
    In a New Cloud Import List, i've selected a local pst file. For this pst file, I would like to select a mailbox by clicking on "Set mailbox" but... the Pst Capture Console doesn't retrieve the Exchange online mailboxes.

    What's wrong?

     

    Pst Capture Tools is installed on a Windows 7 Enterprise.

    Monday, February 06, 2012 1:37 AM

All replies

  • Hi,

    What is the version of your Exchange Server? Office365?

    I recommend you to post the issue in office365 forum to get better help.

    http://community.office365.com/en-us/f/default.aspx

    PST, Time to Walk the Plank

    http://blogs.technet.com/b/exchange/archive/2012/01/30/pst-time-to-walk-the-plank.aspx

    Microsoft Exchange PST Capture

    http://technet.microsoft.com/en-us/library/hh781036.aspx


    Xiu Zhang

    TechNet Community Support

    Tuesday, February 07, 2012 9:23 AM
  • Give it 10-15 minutes, it should populate - if it is still hasn't come up, please post relevant portion of the logs from %programdata%\microsoft\exchange\pst capture
    Thursday, February 09, 2012 7:59 PM
  • I let it sit for about 2 hours and it finally came up with the first 1000 or so mailboxes. However I have 20,000+ mailboxes on Office 365 and there doesn't seem to be any way to select one beside the first 1000. This this is bug?
    Friday, February 10, 2012 1:00 PM
  • Especially in medium to large environments the ingestion is just part of the needed workflow.

    We have published an interessting Whitepaper related to PST Migrations to Exchange 2010.

    http://www.quadrotech-it.com/files/FlightDeck-Exchange_2010-WhitePaper.pdf

    Happy reading :-)

    Peter

    Sunday, February 12, 2012 9:08 AM
  • +1 Elijah

    This is the problem I encouter

    Monday, February 13, 2012 7:39 AM
  • This is the content of my log:

    10:36:27.109|Verbose|MailboxGetter       |7  |AdHarvester: Mailbox harvest success - got 0 boxes
    10:36:27.356|Warn   |BposInfo            |7  |No BPOS username set
    10:36:56.491|Verbose|MSOnline365Helper   |7  |CreateSession :  Called
    10:36:57.713|Warn   |MSOnline365Helper   |7  |CreateSession: Bpos credentials not set - cannot create Office365 PS Session
    10:36:57.716|Verbose|MSOnline365Helper   |7  |DisposeSession : Called

    But in Tools\Settings, I've connectivity test is OK. So I don't understand....

    Monday, February 13, 2012 7:43 AM
  • I'm in the same environment as Elijah and I am seeing the exact behavior he described.

    Are there any updates on this?

    Tuesday, February 14, 2012 7:36 PM
  • Elijah -

    For online only, I'm looking to see if there is a workaround for this.  When get-mailbox runs, the default is to specify only the first 1,000 objects.  If you have -unlimited specified, it will return the entire result set.  I will track this issue internally.

    For on-prem, this does not appear to be an issue. 

    Ankur

    Wednesday, February 15, 2012 8:57 PM

  • As indicated by Peter, if you have multiple thousands of PSTs to migrate, you have more than ingestion to worry about.

    1. You'll need to manage upload out of hours to minimize network impact.

    2. The sheer bulk of data to be transferred will take a long old time.

    3. Keeping track of progress, any failures etc, over this time period will be challenging to say the least.

    See also Tony Redmonds latest blog in which he resonates with these kind of issues.

    http://www.windowsitpro.com/blog/tony-redmonds-exchange-unwashed-50/office-365/pst-capture-142229

    Friday, February 17, 2012 3:43 PM
  • We've got an Exchange 2003 server that is on crap hardware and is basically on dialup network speed so we're going to use ExMerge to dump the PSTs and then take them on external drive to our FIOS connection offsite and dump them into our new Office365 account.  I'm doing some testing with old PSTs and I can't get PST Capture to connect to the Office 365 account.

    I've setup the online connection section and it connects...then manually added a test PST and clicked set mailbox, but it's empty.

    Running Windows 7 64, Outlook 64...but the machine is stand alone and not attached to any domain.  I can't pull the server since it's also their file server...and figured that there'd be an easier way to dump 20 x 5GB PSTs into their new Office365 accounts.

    Is there a hack to get around the member domain issue?...and is that the main problem?

    Thanks,

    Dan


    Thursday, March 22, 2012 6:36 AM
  • Ankur,

    Has there been any resolution to this?  We've seen the same problem.

    Sunday, June 03, 2012 3:28 PM
  • I have the same issue. I had to wait over an hour for the mailbox selection to populate, and I only have 3 in my 365 account! I am trying to test this tool to use it in a migration to 365, but I do not understand why it takes so long to query the Online Exchange server for a user list!
    • Proposed as answer by Jetze Mellema Thursday, February 21, 2013 12:45 PM
    • Unproposed as answer by Jetze Mellema Thursday, February 21, 2013 12:45 PM
    Monday, June 04, 2012 6:56 PM
  • Elijah -

    For online only, I'm looking to see if there is a workaround for this.  When get-mailbox runs, the default is to specify only the first 1,000 objects.  If you have -unlimited specified, it will return the entire result set.  I will track this issue internally.

    For on-prem, this does not appear to be an issue. 

    Ankur

    PST Capture 2.0 has been released, this version no longer has the 1000 Mailbox limit: http://support.microsoft.com/kb/2815301/en-us

    Did my post help? Please use "Vote As Helpful", "Mark as answer" or "Propose as answer". Thank you!

    Thursday, February 21, 2013 12:46 PM