​Introduction

DeploymentPro (legacy version) is a lightweight agent that quickly and easily configures Microsoft Outlook to send and receive email from Office 365, and copies over the users' current Outlook settings.

DeploymentPro (legacy version) does the following:

  1. Creates a new mail profile
  2. Configures the new profile to send and receive email from Office 365Sets the new profile as the default mail profile
  3. Allows the user to set their Office 365 password
  4. Attaches any existing PSTs from the current default mail profile
  5. Copies over the signatures from the current default mail profile
  6. Copies over autocompletes from the current default mail profile
  7. When migrating to Office 365, we bypass internal Autodiscover settings for the Profile configuration. When migrating to On-Premises, we will auto-detect the Destination AutoDiscover URL and Certificate Principal name.​

This video provides a full walk-through of the legacy version of the DeploymentPro product.

 

 

Note: There may be differences between the user interface shown in this video and the user interface in MSPComplete. We are continually improving the user experience to make our platform more intuitive and easier to use.

Related Articles

Checklist

Use this checklist as a guideline to help you plan and complete your migration to Office 365 (other Destinations will be very similar), when using MigrationWiz in conjunction with DeploymentPro.

DeploymentPro has the following prerequisites:

  1. Destination type must equal Microsoft Office 365
  2. Admin credentials on Office 365 are required.

Pre-migration:

  1. Provision users in Office365.
  2. Create and Configure a mailbox Project.
  3. Associate all of your mailboxes to the mailbox project. Mailboxes can be created manually through the MigrationWiz portal, or by importing a csv formatted spreadsheet (downloadable through your MigrationWiz portal), or, if you have admin credentials at the Source, by using our Autodiscover tool to import the users. If your Office 365 addresses are in a different format from the Source addresses, amend these by either individually (by clicking on the pencil icon on the right of each mailbox), or by editing the CSV file with the correct Destination email addresses, prior to importing.
  4. Perform a free trial migration. (Optional; if used, this will verify credentials, create the mailbox folder structure and migrate a small number of items into each folder. When the full migration begins, it will then keep this structure and begin where the trial ended).
  5. Migrate the largest mailbox using MigrationWiz to perform a speed test (optional). This requires a mailbox license to be purchased.
  6. Calculate and size migration (optional).
  7. Notify users that their mailboxes will be moving to a new system.
  8. Purchase migration licenses. Note: The purchase licenses interface is accessed by clicking on the $ icon at the top right of your MigrationWiz portal.

One week before cutover:

  1. Notify users that the migration is imminent.
  2. Verify mailbox access by submitting mailboxes for migration using Verify Credentials.
  3. Perform initial migration pass. Follow the directions in KB004691 for this. Note: The most popular strategy to follow is the Pre-Stage Migration strategy. If you are performing a Big Bang Migration (this is only recommended for small migrations), this step is not required.
  4. Click on the DeploymentPro link in your MigrationWiz portal and finalize the list of users in DeploymentPro.
  5. Set your DeploymentPro install location (options include: via email from your shared local network location, via email from BitTitan servers, or via Group Policy), and customize the emails, password settings, and specify a logo/tagline. Note: The quickest and easiest method to follow is via email from BitTitan servers.
  6. Confirm DeploymentPro install location settings. Note: If the install method is via email, then this triggers an email to end users containing the install instructions for the DeploymentPro agent.
  7. If install method is via email, users receive the email and install the agent. If install method is via Group Policy, it will be a silent install.

One day before cutover:

  1. Notify users that the migration will occur tomorrow.

Day of migration:

  1. Cutover mail flow to new system. Change MX records to point to Office 365. The DNS information can be obtained from your Office 365 admin portal. Note: If migrating only a subset of users, set up mailbox forwarding/co-existence.
  2. Wait for cutover information to propagate.
    • Wait for the forwarding duration to complete (If performing a coexistence migration).
    • Wait for the TTL expiration of MX records (you can look up TTL by using MX Toolbox).
  3. Initiate the migration (or delta migration if you have previously performed an initial pass).
  4. Within your DeploymentPro portal, click on the Configure Outlook button (when the user is logged on they will see a pop-up which guides them through the setup of their Outlook profile).

Day after migration:

  1. Perform a delta migration to pick up any residual mail. This is optional, but recommended since it will migrate any lingering email that was still routed to the old Source email platform).
  2. Notify users that the migration is complete.
  3. Check if any mailboxes have migration errors and perform the error resolution steps described with each error. Note: To migrate failed items, submit mailboxes for migration using the mode: Retry Mailbox Migration Errors.