Skip Ribbon Commands
Skip to main content

Why has the DeploymentPro (legacy) wizard not displayed automatically?

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

Why has the DeploymentPro (legacy) wizard not displayed automatically?



If the "Configure Outlook" trigger in the DeploymentPro dashboard has been clicked, and the DeploymentPro agent is not popping up on the end users' desktops, there are a few reasons why this might happen:

  1. The agent may not have checked back in with our servers yet. The desktop agent checks in every half-hour. Check how long it has been since the Configure Outlook button in the User Interface was pressed, and make sure that each user has waited a half-hour, based on when they last logged on or installed the agent.
  2. The DeploymentPro.exe is enabled as a startup application by default. So when the user reboots the machine and the "Configure Outlook" trigger has been pushed, the next time they log on, the agent will check in with our servers and the wizard should display. There are a few cases where this will not happen:
    • Terminal servers. If the end users are logging into a terminal server desktop, we do not have the ability to edit the registry to enable DeploymentPro as a startup application, and the admin needs to follow the instructions here to change the workflow:  KB004824.  
    • Something else is keeping DeploymentPro from editing the registry. The issue needs to be escalated to Support.