Which applications are configured by Desktop Update Agent is managed through On Demand Migration's switch application.

NOTE: Each application can have it own separate switch application task. Each application reconfiguration status is tracked separately for reporting purposes.

NOTE: If required, you can create custom PowerShell scripts that can run before and/or after the desktop application reconfiguration. The option to use a script is set as part of the switch task; however, the script deployment is not done through On Demand Migration. Your administrator needs to deploy the required PowerShell scripts to end user computers to this directory: C:\ProgramData\Quest\DUA\Script\PreScript and C:\ProgramData\Quest\DUA\Script\PostScript. Only a single script should be deployed to each directory. The pre and post configuration scripts can be different, and it is not required to have both. Sample scripts are include here: C:\ProgramData\Quest\DUA\Script\PreScript\quest.sample.pre.ps1 C:\ProgramData\Quest\DUA\Script\PostScript\quest.sample.post.ps1

To configure the switch application task to start the reconfiguration job:

1. Log in to On Demand.
2. Navigate to Migration and select the required project.
3. Select the Desktop Agent tab.
4. Select a user with a successful mail and OneDrive migration.
5. Choose Switch Application. 
6. Under Agent Setup, select the Modern Agent and click Next. If required, you can select to use ‘legacy’ 1.x agents, but you will not have access to new features.
7. Under App Update Scope, select the applications to update and select Next.

   • Ensure Microsoft 365 Office Activation, Outlook Application, Migrate Signature, OneDrive Application and Teams Applications are selected.

8. As of version 2.2.0, you can optionally configure custom scripts to run before and/or after the desktop application reconfiguration. Under PoweShell,select:

   1. Whether to run run the scrip at the start or end of the reconfiguration process or both.

   2. For pre configuration scripts, select whether to proceed with the reconfiguration if the script fails; for post configuration scripts, select whether to proceed with running the script if the reconfiguration fails.

   3. Whether to run the script for every reconfiguration.

   4. Whether to run the script as the local system account or as the logged in user. (If run as the logged in user, they must must be permitted to run scripts, and the PowerShell script execution policy must be set to allow as well.)

9. Under Refresh, you can choose to select to refresh account before running the switch task.
10. Under Custom Domain, you have the option to specify a domain to use for switch application tasks. This is necessary when the DNS domain is moving at the same time as the users but is not being set as the primary SMTP address in the target tenant. When a custom domain is specified, the Desktop Update Agent checks for Switch Tasks matching the user’s current source domain, the user’s current target domain, and the custom domain. This is recommended for domain move scenarios that do not update the target identity.
11. Under Validation, you can choose to Skip mailbox state validation and Skip OneDrive state validation if needed. (This is not normally recommended, except in the case of a Domain Move. However, it may be required if mailbox or OneDrive migration takes place outside of On Demand Migration.)
12. Under Notifications, select to send the email notification (with the required authentication steps for users) to the source or the new target, and select Next.
13. Administrators have the flexibility to decide when they want users to reconfigure their desktop applications. Under Schedule, select when you want the switch application to run, and select Next.
14. Review the Switch Applications Task settings and select Finish.

Once the Switch Applications task is completed, On Demand Migration reports each application reconfiguration status as “Waiting”. This means that the task is pending the user running the Desktop Update Agent. For a complete list of possible states, see Monitoring the Switch Application Status.