Skip Ribbon Commands
Skip to main content

Can DeploymentPro (legacy) configure Outlook for users on a Terminal server?

Last Update: 7/21/2017 11:33 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.​

 

Can DeploymentPro (Legacy) configure Outlook for users on a Terminal or Citrix server?​​​​

Answer:​​​

Yes. DeploymentPro (Legacy) can be used to configure Outlook 2010+ for users on a Terminal or Citrix server. However, the process works slightly differently for Terminal Servers or Citrix users than it does with regular PCs and laptops.

On a desktop or laptop PC, we are able to restart the DeploymentPro (Legacy) gent when the end user starts their machine, so the Agent can be installed at any time ahead of the MX record cutover. After the cutover of the MX records has been performed, click the Configure Outlook trigger in the DeploymentPro (Legacy) dashboard. The Agent on the desktop will monitor our servers looking for the Configure Outlook trigger. Once the trigger has been clicked, the DeploymentPro (Legacy) Wizard will pop up automatically and configure Outlook for Office 365.

 

With a Terminal or Citrix Server, we are unable to restart the DeploymentPro Agent when the user logs off and then logs back on. Therefore, the DeploymentPro agent must be installed after the "Configure Outlook" trigger has been clicked so the DeploymentPro installation and Outlook configuration happen in a single session for the user. The process for a Terminal or Citrix server looks like this:

 

  1. Migrate mailboxes through MigrationWiz.

  2. Create the DeploymentPro (Legacy) Project, and make sure to click the Configure Outlook trigger right away.
    • Note: Email will be sent to end users once "Confirm Project"  is clicked in DeploymentPro (Legacy) , so by the time each end user logs on to their terminal server session, they will install the DeploymentPro (Legacy)  Agent, and the DeploymentPro Wizard will automatically display so they can configure a new profile for Outlook in the same session. 
  3. Quickly point MX records to Office 365 once the "Configure Outlook" trigger in DeploymentPro is clicked, so that by the time DeploymentPro  for UserActivation gets installed and configures Outlook for the end user, email is being routing to Office 365.