Product Documentation

Configuring PST File Import and Export for Exchange 2007

Jun 05, 2015
Updated: 2012-11-27

Configure PST file import and export to enable Services Manager to import and export Exchange 2007 personal store mailboxes using an FTP server.


  • Install the Services Manager Exchange service.
  • FTP server:
    • Running 32-bit Windows Server 2008, with current service packs.
    • Member of a Services Manager domain.
    • Open Exchange ports to the rest of the Exchange organization.
    • Install these components:
      • Exchange Management Tools
      • Microsoft Outlook
      • .NET Framework
      • FTP components and roles of IIS

To configure the FTP server for PST import and export

Important: This procedure applies only to Exchange 2007. The Exchange 2010 server connection that you configure in Services Manager has built-in support for mailbox import and export. Services Manager does not support PST file import and export for Exchange 2003.
  1. In Active Directory, perform the following actions:
    1. Create a new AD user account in the Services Manager system OU called servername_pst.
    2. Grant Full Control permissions of the servername_pst account to the Customers OU.
    3. Add the servername_pst account to the CortexAdmins group.
  2. For the FTP server, perform the following actions:
    1. On the FTP server, create a new folder for use by Services Manager. The default path is C:CortexFTP.
    2. Share the folder as Webhosting and grant Full Control of the share to Everyone.
    3. In the folder properties, on the Security tab, verify that inheritance is disabled and, when prompted, click Add to copy the current permissions to the folder.
    4. Add the domain security group ServiceAdmins HE to the ACL of the folder and grant List Folder Contents permissions.
    5. Add the servername_pst account to the ACL of the folder and grant it Full Control.
  3. Add and configure the FTP site in IIS:
    1. On the FTP server, open the IIS Management Console and then navigate to the Sites container.
    2. Right-click the Sites container, choose Add FTP Site, and configure it.
      • FTP site name: A name such as "CloudPortal Services Manager PST FTP Site"
      • Physical path: The path configured in step 2a above
      • Binding IP Address: An IP address and port or All Available
      • SSL: Allow SSL
      • Authentication: Basic
      • Authorization: Allow access to: Specified roles or user groups
      • Authorization (credentials):domainServiceAdmins HE
      • Authorization: Permissions: Read and Write
    3. Under the Features view, double-click FTP User Isolation, choose FTP home directory configured in Active Directory, and then click Set to specify the credentials for the new AD user account set up in Step 1a. Include the domain with the user name: domainservername_pst
    4. Under the Features view, double-click FTP Authentication, enable Basic Authentication, disable Anonymous Authentication, and then click Edit and set Default domain to the fully-qualified domain name.
  4. Restart the FTP site.

To configure PST file import and export

  1. Assign server roles:
    1. From the main menu, choose Configuration > System Manager > Server Roles and then expand the server to be used for PST import and export. If the server is not listed, go to Configuration > System Manager > Servers and refresh the list.
    2. Under Server Connection Components select Hosted Exchange.
  2. Add a server connection:
    1. From the main menu, choose Configuration > System Manager > Server Connections, select a Location Filter if applicable, click New Connection, and then specify the following information for the Exchange web service.
      Server Role
      Choose Hosted Exchange or Exchange Multi-tenanted.
      Choose the server where the Exchange Web Service is installed.
      Choose the impersonation account for the Exchange service.
      URL Base
      Defaults to /ExchangeWS/HostedExchange.asmx.
      Select http.
      Defaults to 8095. If you change the port here, change it also in the Services Manager Web Service.
      Defaults to 200000 milliseconds.
      Select Mailbox Import/Export.
    2. Click Save.
    3. From the main menu, choose Configuration > System Manager > Server Connections and then click the icon in the Test column for the Exchange server. The icon turns green for a successful connection. A red icon indicates an unsuccessful connection. Mouse over it for information about the failed connection.
  3. Configure service settings:
    1. From the main menu, choose Configuration > System Manager > Service Deployment.
    2. Under Service Filter, select Top Environment Services, and expand Hosted Exchange or Hosted Exchange Multi-tenanted.
    3. Click Service Settings, expand Mailbox Import/Export, and then select the Enabled check box. You can use the default settings for the other properties.
    4. Click Save.
  4. Create a task on the FTP server to start PowerShell for use with PST import and export:
    1. In Windows Server Task Scheduler on the FTP server, create a task with the following settings.
      • Name: CloudPortal PST Import Export PowerShell Start
      • Description: This task automatically starts PowerShell for use with CloudPortal PST Import Export.
      • Security options: Use an account with appropriate privileges, such as an Exchange administrator account who is also a local admin on the PST import/export server. Select Run whether user is logged on or not.
    2. On the Triggers tab, click New and use the default settings.
    3. On the Actions tab, create a new action with the following settings.
      • Action: Start Program
      • Program/script: C:WindowsSystem32WindowsPowerShellversionpowershell.exe
      • Add arguments: -PSConsoleFile "C:Program FilesMicrosoftExchange Serverbinexshell.psc1" -noexit -command ". 'C:Program FilesMicrosoftExchange ServerbinExchange.ps1'"
    4. On the Settings tab, select Allow task to be run on demand, select If the task fails, restart every, and choose 1 minute. Clear any other check boxes and set If the task is already running to Do not start a new instance.
    5. Verify in Task Manager that the PowerShell process started.