|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 a logon script?
When installing the DeploymentPro Agent from a logon script or through Group Policy, the process is defined by five phases:
- Admin download
- Write the logon script
- Agent gets deployed to users
- Outlook Configuration
1. Admin download:
In order to prepare for running DeploymentPro from a logon script, the admin should complete the following steps:
- Download the DeploymentPro Agent from here. This will download the installer called Bootstrap.exe.
Click on the Start menu and open up the Command Prompt (cmd).
Navigate to the directory that you downloaded Bootstrap.exe into.
This will download both the x86 and x64 versions of DeploymentPro, and will open Windows Explorer to show the result.
- Copy all content to a shared network location that all users can access.
2. Write the logon script:
In order to write the logon script, complete the following steps:
- Open up Notepad and create the following string: \\shared location\Bootstrap.exe Activation Code ?
Note: When using DeploymentPro through MigrationWiz: The Activation code can be accessed in your (DeploymentPro) Project Dashboard after you confirm your project settings.
- The ? attempts to automatically identify the current user's email address to use as a unique identifier for configuration and tracking in the Project Dashboard.
- This email address is matched to the users specified in your project. We use the following methods, in order to detect the users' email address:
- Perform an Active Directory lookup to obtain the user's primary SMTP email address. This works if the machine is joined to a Windows domain.
- Check the current logged in user's User Principal Name (UPN). This works if the current user's UPN is in user@domain format. This is a fallback if previous methods were unable to produce an email address.
- Extract the email address used by the most recent Outlook profile. This is a fallback if previous methods were unable to produce an email address.
- In the string above, replace "\\shared location" with the UNC path to the location where the content of the bootstrap.exe/preinstall setup files were copied to, under the admin download section.
Save as a .bat file.
- Write a logon script that will run this .bat file when each user logs in.
- Before running the logon script, make sure that all of your users have been created in Office 365.
- Make sure that you include a folder exist check within the batch file, to check if the directory %temp%/UserActivation exists. If the directory exists, the script should end processing. If this check is not included, you could experience an issue where the installation process will loop and won't complete successfully. Please review the following Microsoft Support article on how to check if a directory exists: https://support.microsoft.com/en-us/kb/65994.
3. Agent gets deployed to users:
- Once the login scripts runs for each user, the content will be copied down to a local directory on each user's machine.
- Bootstrap.exe will invoke the correct version of DeploymentPro, based on the Outlook architecture (x86 or x64), and pass it the Activation code and email address it received from the login script.
- DeploymentPro will call into BitTitan web services with the Activation code and email address, and kick off the monitoring process.
- Once the install 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 on what actions it should take.
- No actions will be invoked until the Configure Outlook button has been clicked on; or, if using UserActivation product, until after the MX records have been cut over.
Note: When running a project with MigrationWiz, the Configure Outlook button should be clicked on only when you are ready for the profiles to be reconfigured. This is typically done after MX record cutover. More details can be found in KB005391.
- At this time, the BitTitan servers will signal down to the Guardian processes that it is time to create and configure the new Outlook profile for Office 365. The OutlookConfigurator.exe file will then be launched.
- You can then track the status of each user from your Project Dashboard.
5. Outlook Configuration:
Once the Guardian processes receive the signal from the BitTitan servers that the DNS records have been cut over (if using UserActivation), or Configure Outlook button has been clicked on (if using MigrationWiz), it launches the OutlookConfigurator.exe file.
This will launch the DeploymentPro Wizard, which will guide the user through this configuration process:
- 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.
- 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.
- 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 for manually creating a new Outlook profile.
- 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.
Note: Screen shots of the end user experience can be found in KB005457.
Once DeploymentPro is complete and confirmation is received, the Guardian process will end.