Skip Ribbon Commands
Skip to main content

What is the process for installing the DeploymentPro (legacy) Agent from end user email?

Last Update: 7/21/2017 11:27 AM
This article has been moved to our new Help Center. Please update your bookmarks.


Notice: This Knowledge Base article pertains specifically to the DeploymentPro (legacy) product, and not to the DeploymentPro product that is part of MSPComplete or DeploymentPro for UserActivation.​

What is the process for installing the DeploymentPro (legacy) Agent from end user email?


When installing the DeploymentPro (legacy) agent from end user email, the process is defined by three phases: End User install, Monitoring, and Outlook Configuration.


End User Install:

The install phase begins with the email to the end user. DeploymentPro will send an email to every user in the project. This email contains a unique authentication code as well as a link to download the DeploymentPro Agent. This link will download the install agent called Bootstrap.exe.

When the Bootstrap.exe file is run, it will launch an installer that will complete the following:

  1. Check to see if the user meets the minimum system requirements to run DeploymentPro.
    • If the user's computer does not meet minimum system requirements, the ​installer will stop and display an error.
    • If their computer does meet the requirements, the installer will continue to run.
  2. Download the necessary files for DeploymentPro to the user's temp folder: C:\Users\username\AppData\Local\Temp\UserActivation
    • The download normally takes two to five minutes but, depending on bandwidth speed, it can take longer. The Bootstrap.exe has a timeout function that will stop the download and show an error after one hour.
  3. Once the download completes, there will be a notification in the system tray, and UserActivation will display a dialog box asking for the authentication code that was provided in the user's email.
      • Note: This window can be closed by clicking the red X, but can be reopened by clicking on the icon in the system tray. The process will not continue until the user inputs a valid authentication code. 


Once the installation is completed, users immediately enter the monitoring phase. During this phase, there will be a process running in the background called Guardian. This Guardian process communicates with BitTitan servers to receive instructions about what actions it should take, and doesn't do anything to the end user's computer until the DNS cutover has been processed. Once the DNS cutover has been processed, our UserActivation servers signal to the Guardian processes to create and configure the new mail profile for Office 365. You can monitor who has completed the installation successfully from your Project Dashboard



Once the Configure Outlook button has been clicked on, the OutlookConfigurator.exe file launches on end user machines. This will launch the DeploymentPro Wizard, which will guide the user through the configuration process:

  1. The first page of the wizard provides instructions to the end user, to make sure they complete the entire wizard so that they do not lose access to their email.
  2. The second page of the wizard is the Password page, where users will either create a new password for Office 365 or use an existing password.
  3. The third page of the wizard displays the status of the configuration.
    • If the configuration succeeds, they will move to the final confirmation page.
    • If the automatic configuration fails, the DeploymentPro Wizard will provide the settings that the user will need in order to configure Outlook manually, as well as links to our Knowledge Base articles with detailed, step-by-step instructions to manually create a new Outlook profile.
  4. The last page of the wizard is the confirmation page. This page shows that we have successfully configured a new profile, and instructs the user to restart Outlook.

The Guardian process will stop running once we confirm that the configuration has completed successfully.