Forum Discussion

ChrisATS's avatar
ChrisATS
Level 4
11 years ago

Server Drive PST Migration Issue

Environment: Windows Server 2008 R2, EV 10.0.4.1189  Outlook 2007 SP3 w/EV Outlook add-in 10.0.4.1189

Really excited about PST migration improvements in EV10 SP4.  I did a bunch of testing migrating some small PST files located on a DFS network share. Everthing went smoothly and emails were copied to a folder in my Outlook client.  I rolled this out a few weeks ago to all other clients.  I provisioned the same PST Migation policy that I used for testing to the users and I can't get the files to migrate.  I have the PST Locator, PST Collector Task, and PST Migrator tasks running and scheduled to work during business hours.  I've run the provisioning task to enable all the clients.  My initial thought was that the clients were running an older outlook EV add-in.  So I upgraded them to the latest (10.0.4) plugg-in.  Could it be the PST file size?  I tested on files that were only a few Mb.  The files I'm attempting to migrate are 10-12 Gb.  Does the Migrator task have a problem with such large PST files?  When I refresh 'Files' in 'Store Management' it shows "Ready to copy" and does not change.

Thoughts or suggestions are appreciated.

Enterprise Vault
Information Governance
Windows 7

19 Replies

Sort By
  • Rob_Wilcox1's avatar
    Rob_Wilcox1
    Level 6
    11 years ago

    Failure sure that PSTs on DFS shares won't migrate.  The Directory or Migrator Server processes can't work out 'where' the PST file is really stored, hence can't do anything.

  • RahulG's avatar
    RahulG
    Level 6
    11 years ago

    So are the pst file which are migrating via server driven migration stuck in Ready to copy state or even the client driven migration Pst show the status as Ready to copy ?

    Did the migration of Small PSt file went Fine ?

  • ChrisATS's avatar
    ChrisATS
    Level 4
    11 years ago

    In testing the server driven migration from the DFS worked great.  The user simply needs full access to the file on the DFS.  The feature that I was keen on was the client driven migration which doesn't work from a DFS.  As you decribed that was the exact problem with client driven migration that the locator couldn't find where it was stored.   

  • ChrisATS's avatar
    ChrisATS
    Level 4
    11 years ago

    I tested the server migration under my mailbox and it worked flawlessly.  The service account has full access to the DFS share. 

    I saw a post about using EVPM to do the PST migration.  I created a INI file and run EVPM.exe agaist it but nothing happens.  I followed the example in the utilities guide but nothing.  I'm batting 0.000 today!  I see nothing in the event viewer related PST migration tasks.  

  • Rob_Wilcox1's avatar
    Rob_Wilcox1
    Level 6
    11 years ago

    Please post a copy of your INI file that you used, and the parameters you called it with.

  • ChrisATS's avatar
    ChrisATS
    Level 4
    11 years ago

    Here is the INI file I'm using:

    [Directory]
    DirectoryComputerName= vs-vault
    SiteName = sitename
    [Mailbox]
    LDAPquery = displayName= chrisze
    MailboxDN=/ou=ATS/ou=First Administrative Group/cn=Recipients/cn=chrisze
    ;
    ; Default option settings applicable to all PST migrations
    ;
    [PSTdefaults]
    PSTLanguage = Western European
    ServerComputerName = email.ats-inc.com
    MigrationMode = PROCESS
    MailboxFolder = Imported Archives
    IncludeDeletedItems = true
    CancelMbxAutoArchive = true
    RetentionCategory = ATS Mailbox Retention
    SetPSTHidden = true
    SetPSTReadOnly = true
    ; 
    ; Individual PST migration settings
    ;
    [PST]
    FileName = \\filestore\dfs\users\chrisze\test5.pst
     
    I followed the steps in this TECH67346 to get the MailboxDN.  I've attached a screenshot of the command prompt.
  • ChrisATS's avatar
    ChrisATS
    Level 4
    11 years ago

    Thanks Rob,  Don't know how I didn't stumble upon your blog.  Reading it you didn't use the MailboxDN to specify where to place imported email, you used VaultName instead.  Reading the Utilities guide (10.0.3) I didn't see that as an option, only ArchiveName?

    After discovering EVPM I'm going to create a collection of INI files to import my company PST files.  It seems to be the most organized way to accomplish.

  • Rob_Wilcox1's avatar
    Rob_Wilcox1
    Level 6
    11 years ago

    It has been a long time since I tested it or tried it out.. so try either/or those altneratives.. but definitely 'not' the [mailbox] section.