Chat now with support
Chat with Support

Migration Manager for PSTs Enterprise Edition 7.2 - Administrator Guide

Azure Node

An Azure Node is a special node used in migrations to cloud based targets. Azure nodes can be used in a migration by itself or in support of geographically centric resource allocation for a multi-site organization. Azure Nodes are nodes deployed to Microsoft’s Azure service to act as the intended centralization target, processing, and ingestion nodes for a configured location. Azure Nodes can be used to minimize the footprint required to scale an environment out or to enable small businesses to leverage Migration Manager for PSTs by reducing the initial hardware requirements of the solution.

Content Scanning

One of the largest challenges in PST migration projects is accurately determining ownership of a PST file. Most PST files have ownership identified within the Discovery process for Migration Manager for PSTs. PST files identified by a Share Scanner, or by a user as not belonging to them, require some special analysis. Migration Manager for PSTs's Content Scanner is used to scan PST files marked as “Ownerless,” or those files located on specific fileservers. It can provide more information to help determine ownership association based on the contents of the file. Files processed by the Content Scanner can have the most common sender and most common recipient recorded and taken into consideration when determining PST file ownership. This attribute is also evaluated against a user's proxy addresses to ensure account migration history is taken into consideration when evaluating ownership.

Centralized Uploads

The Central Upload Agent (CUA) is a component frequently utilized in a Migration Manager for PSTs environment. The primary role of the CUA is to upload files stored on centralized repositories more rapidly without having to use a workstation's Migration Agent.

In a traditional migration situation without a CUA, remotely stored PST files would be queued for BITS transfer using a user’s Migration Agent to facilitate the upload request.

When a CUA is deployed, and the environment is appropriately configured, files on remote file servers are uploaded by a nearby CUA rather than connecting back through the workstation.

Forced Migrations

If an environment has a CUA installed, configured, and running with sufficient permissions, it can be used to facilitate Forced Migration requests. A Forced Migration utilizes the CUA to connect to a user’s local machine and copy the eligible PST file over the administrative share on their local system. This enables a user to have their files uploaded without having to go through BITS or even a Migration Agent. This feature is useful for Migration Agents struggling to complete an upload or as a means to migrate users who are rarely connected to the domain.

Related Documents