It seems like your browser didn't download the required fonts. Please revise your security settings and try again.
Barracuda Campus Barracuda Campus

Attention

Starting May 1st, 2018, we will no longer offer the ArchiveOne family of products. This includes all editions of ArchiveOne, ArchiveOne for Files, Max Compression, and Access Security Manager. If you currently hold a maintenance and support contract, you will continue to receive our award-winning support until your contract expires, or until May 1st, 2019, whichever occurs first. The license for ArchiveOne is perpetual; therefore the software may continue to be used independently without any updates or support indefinitely.

Coupled and Uncoupled PSTs Node

  • Last updated on

Use the Coupled PSTs and Uncoupled PSTs nodes to view all data ever discovered about PST files through client based searching, that is, using discovery or policy runs, including information discovered on past runs. The nodes show data found by the AOnePolPSTProc application. For more information, see PST File Processing.

The Coupled PSTs node shows the details of coupled PSTs, that is, PSTs found by checking Outlook's current configured profile. The Uncoupled PSTs node shows the details of uncoupled PSTs, that is, PSTs found by scanning the local hard drive from a configured path. The same PST may appear on both the Coupled PSTs node and the Uncoupled PSTs node. 

When viewing results, each PST is listed including details such as its size. This data is not refreshed, so if you have been running ArchiveOne Admin for awhile, close and restart it to ensure it is up-to-date. 

You can hide PSTs records from the list. If you do so, even if the PST is discovered again, it is not put back into the list. Use this feature to simplify your list of discovered PSTs if there are PSTs you know you are not interested ii, but it does not prevent any other processing on the PST. Right-click on the node, and click Show Hidden PSTs to view hidden PSTs. 

Columns on the Coupled PSTs and Uncoupled PSTs nodes display the PST data size (that is, the size of items in the PST, which is less than the size of the PST file itself), and its initial data size. 

If processing uncoupled PSTs, they must be associated with a mailbox. This is necessary for policy actions such as archive, so that when the PST items are archived, they are stored as though they were from the specified mailbox, so that any user allowed to search into the archive of that mailbox is also allowed to search the PST items. If there is no mailbox associated with a PST, which is the default state when a PST is first discovered, the PST is not processed. To configure a mailbox for a PST, find the PST listed in the Uncoupled PSTs node, right-click the PST, and click Set Mailbox. 

For the PST Processor to process uncoupled PSTs, the user running the PST Processor must have rights to log into the mailboxes associated with the found PSTs. For example, if a PST is going to be associated with mailbox X then the user running the PST Processor has to have rights to log into mailbox X because, the policy action is to move data from the PST into the mailbox. Note that the user running the PST Processor does not need to run as the user associated with the PST, only to have mailbox logon rights for that user. 

When a PST appears on the Uncoupled PSTs node, one of the columns displays a possible candidate as the PST original owner as determined by examining the messages in the PST. Other columns show the confidence level and reason for this confidence. Use this information to associate the PST with a mailbox so that subsequent migration moves the mail from the PST into that mailbox. This data is unavailable unless you have selected the PST Processor configuration option Try to determine the owner of a PST (which may slow down processing).

PST Processor Configuration

The PST Processor configuration dictates how the executable runs and where it searches for PST files. When the PST Processor executable launches on a client machine, it connects to the specified PST Management website and requests its configuration. There is a default configuration which applies to all client machines, unless you define a configuration specifically for that individual client machine based on its hostname. Define a default configuration suitable for the majority of client machines; you can then specify individual client configurations for any machines that require exemption, for example, a file server.

To review or edit the PST Processor configuration, or view the command line to run the PST Processor:

  1. In the ArchiveOne Admin console, right-click on either the Coupled PSTs or Uncoupled PSTs node, and then select PST Processor Configuration.
  2. The PST Processor command line is displayed on the PST Processor Configuration dialog. To review or modify a configuration, select either the specific client machine (if one exists) or the default configuration for machines not listed, and click Edit:
    • Click New to create a new configuration for a specified client machine.
    • ClickRemove to delete a specific client configuration if this is no longer required. The Default configuration is then applied.
  3.  On the Where to Look tab, configure where the PST Processor should search for PSTs:
    1. Select Look for PSTs in the user’s Outlook profile if you want to search for PST files open in Outlook.
    2. Select Look for PSTs in the file system if you want to search on disk for PST files which may not be open in Outlook.
      1. If the All Drives option is selected, system and hidden folders, such as Program files, are excluded.
      2. To define custom locations, select Specified locations, and click Add to type in the required path. for example, D:\UserData. The search is recursive under the specified path; all subfolders are searched. You can add multiple paths in this manner.
  4. On the Time tab:
    • Stall factor introduces a delay of the given number of milliseconds between each processed message. This artificially slows down the program to limits its use of available CPU resources if throttling is required, for example, if run on systems with very limited available system resource. Setting the stall factor to 0 removes any throttling and allows maximum performance.
    • Startup delay introduces a delay of the given number of minutes before the processing begins. This is intended to allow the user time to login and open Outlook before the first time the PST Processor runs processing so that coupled mode can be performed.
  5. On the Start and stop tab you can restrict the absolute running times of the PST Processor.
    • If the PST Processor is launched, it is not allowed to perform any active processing outside of the defined time window and is effectively dormant (even if the process is launched from a login script, for instance).
  6. On the Compaction tab, you can choose to enable the compaction of PST files, if required:
    • PST file typically contain white space. If you are ultimately eliminating the PST files, then it is not necessary to compact them. If the PST files are to be maintained then you can compact them to reclaim storage space.
    • This can only be performed for PSTs connected to Outlook. As this process uses Outlook, it may be inhibited for instance, if Outlook is awaiting user input on a dialog box. 
  7. On the Outlook tab you can specify whether registry keys are to be created which cause Outlook to either disallow users from adding new PSTs, and/or disallow users from making changes to existing PSTs.
    • Barracuda Networks recommends prevent the creation and modification of PST data when processing PST files. This stops users from simply creating new PST files to replace the ones that have been processed by ArchiveOne. You may prefer to control this via Group Policy, but the PST Processor can be used to compliment and reinforce these settings.
    • The Add PSTs to Outlook setting prevents the creation of new PST files. Choose Disable to forcibly prevent users from creating new PST files. Select No change to allow whatever action is currently permitted by Group Policy settings.
    • The Modify PST content setting prevents the modification of existing PST files. Choose Disable to forcibly prevent users from modifying PST data. Select No change to allow whatever action is currently permitted by Group Policy settings. On some versions of Outlook disabling the option to Modify PST content may cause operations on PST messages such as archive or migration to fail.
    • If the PST Processor is run once when Disable is selected, then run subsequently when the No change option is selected, the disable option is still in force until the Enable option is used, Group Policy updates the setting.
  8. On the Miscellaneous tab, you can:
    • Enable show system tray icon to display a system tray icon when PST Processor is running. This allows users to close the application, so is not recommended for general use, but is useful for administrators to interact with the PST Processor, for example, when running manually on file servers.
    • Enable single run. This performs one active processing run and then automatically shuts down the process, rather than continuing the usual active/passive cycle. Use this option when running PST discovery on file servers where you do not want to leave the PST Processor running indefinitely. 
    • Enable Try to determine the owner of a PST. This analyzes the contents of uncoupled PST files, and, based on the most frequent recipient, determines the PST file owner. The determined owner is automatically assigned if the confidence criterion on the PST Threshold setting is satisfied. A PST file must have an owner assigned before you can apply a policy so that ArchiveOne knows who the data belongs to. If this option is disabled, you must manually assign an owner to the uncoupled PST files. 
    • Set the Migration root folder name. This is the name of the root folder in the mailbox for PST data which is migrated into the mailbox.
  9. On the Advanced tab you can specify non-standard options, which are typically necessary only when working with Support.

If you are running multiple instances of the ArchiveOne Admin application, changes made on this node in one instance may not visible on the other instance. If you suspect there have been changes, restart your instance to ensure it has up-to-date data.