On Demand Migration Current - Desktop Update Agent Release Notes

Release History

The following lists the new features, enhancements, and resolved issues by release.

Current Deployment

Desktop Update Agent version 2.5.5
Resolved Issues Issue ID
Additional improvements to OneDrive and Teams account detection. 607362

Previous Deployments

Desktop Update Agent version 2.5.4

January 2026

Resolved Issues Issue ID
Improvements to OneDrive and Teams account detection. 599791
Improvement to interoperability when using the On Demand Migration Active Directory agent to migrate devices. See the 'Device Cutover with Active Directory agent' topic in the Desktop Update Agent User Guide for important considerations. 565780
Desktop Update Agent version 2.5.2

October 2025

Enhancement Issue ID
A new OneDrive Application option on the Switch Applications task instructs the Desktop Update Agent to use the target UPN to reconfigure OneDrive. 440414

Timeout (maximum allowable run time) for pre- and post-configuration scripts increased from two minutes to five minutes.

 569320
Resolved Issues Issue ID
Addressed a change in the behavior of OneDrive starting with build 25.179.0914.0003 where the Sign in to OneDrive dialog would have the Sign in button disabled (grayed out) when launched from DUA. 587364,
587007
Desktop Update Agent version 2.5.1 (Technical Preview)

September 2025

New Features Issue ID

The agent now runs silently in the background and automatically polls On Demand Migration for switch tasks at regular intervals. Users no longer need to manually start the agent; after installation it will automatically start on the next sign-in or reboot, and will open on the desktop to prompt for processing when action is required.

Processing can also be postponed by end users for several minutes or hours, providing greater flexibility.

NOTE: On the Switch Application Task's Schedule tab, the default option has changed from Run Now to Schedule.

Migration administrators should schedule Switch Applications tasks so that they are not run until prerequisite migration project steps have been completed and their help desk is ready to support users, if necessary.

Additionally, migration administrators can now view installed Desktop Update Agent reports directly in the On Demand Migration interface, improving visibility and management of agent deployments.

 440407
A new OneDrive Application option on the Switch Applications task instructs the Desktop Update Agent to use the target UPN to reconfigure OneDrive. 440414
Resolved Issues Issue ID
Improved reliability of OneDrive migration when a restart is required to complete the process. All required data for the restart is saved immediately after a folder rename at restart is requested, preventing an inconsistent OneDrive state if the process is interrupted. 567031
DUA update - Installing when an agent is already present stops the On Demand Desktop Update Agent service, impacting OneDrive reconfiguration and App license reset features. 566232
Two Teams accounts displayed in the Teams Meeting Add-on. 533868
Desktop Update Agent version 2.4.2/2.4.3

September 2025

All resolved issues from the 2.4.2 hotfix and 2.4.3 release are also included in version 2.5.2.

Desktop Update Agent version 2.4.1

December 2024

Enhancement Issue ID
Selection of the Outlook variant (Classic or New) to reconfigure

Desktop Update Agent  needs to close and restart Outlook during the reconfiguration process, Which Outlook variants to reconfigure will be based on the following:

  • If New Outlook and/or Classic Outlook is configured and running when DUA starts, those Outlook variants will be stopped, reconfigured, then restarted.

    • If both variants are configured but only one is running when DUA starts, only the variant that is running will be reconfigured.

  • If neither New nor Classic Outlook is running when DUA starts, DUA will check the user's registry keys for the UseNewOutlook setting to determine which variant the user prefers. Classic Outlook or New Outlook will be reconfigured according to the value of that switch.

    • If the UseNewOutlook registry key is not present, DUA will check the computer for configured Outlook profiles (Classic) and reconfigure Classic Outlook if found.

      DUA will also check the computer for a user account for new Outlook, and reconfigure New Outlook if that account is found.

    		•

      NOTE: Either Outlook variant must be started to complete reconfiguration. In this scenario it is possible that the Desktop Update Agent will start both Outlook variants.

  • If none of these conditions match, Outlook configuration will be skipped.

After the Desktop Update Agent completes, if the Outlook variant that was reconfigured is not the one expected or preferred by the user, a second run can be performed to correct this. The migration administrator can set up a new Switch task for any affected users. The user should ensure their required Outlook variant is running and then manually start the Desktop Update Agent. DUA will then reconfigure that Outlook variant based on the criteria listed above.

 
Resolved Issues Issue ID
Desktop Update Agent detects Outlook configured when the user is only set up for Teams. 521965
Desktop Update Agent does not open and show Outlook Completed when rerun after switching Outlook. 523925
Desktop Update Agent becomes unresponsive when new Outlook is updated from Classic Outlook using the 'Try the new Outlook' switch. 532054
Improved message displayed at the beginning of Desktop Update Agent reconfiguration Spanish edition. 523767
Message displayed at the beginning of Desktop Update Agent reconfiguration is in English in the Spanish edition. 521247
Outlook Reconfiguration - Unable to switch Outlook Classic if it is not running. 527977
Outlook Switch - When Desktop Update Agent is canceled before closing Outlook, the target profile is created but the status is not sent to On Demand Migration. 522344
When Classic and new Outlook co-exist only the Classic Outlook account is updated when Desktop Update Agent is run. 509138
When Teams is open during Desktop Update Agent reconfiguration, “Close Microsoft Teams now” does not reliably close Teams. 531207
Desktop Update Agent version 2.4.0

August 2024

New Feature Issue ID
Support for reconfiguring "New Outlook". 483557
Enhancement Issue ID
Addressed minor code quality issues identified by code analysis tools. 509214

Logging enhancements:

  • User interface enhanced to display agent log state when log requested.

  • "Error" relating to a PowerShell script changed to a"Warning" to better reflect the issue.

  • "PackageName" and "PublisherID" not displayed in the logs when searching for Installed Packages.

 493210 501627 509031
Updates to support Microsoft libraries. 497711
Resolved Issues Issue ID
DUA does not recognize Teams as configured at the end of the Teams reconfiguration step and continues to wait. 519973
Office activation is a trial license when switching between Microsoft Outlook and Office. 492780

Localization issues (Spanish and German):

  • Some messages are not shown in correct language.

  • Link displayed for more information in an article of OneDrive in Windows Spanish edition opens the German edition.

  • "Next' button name updated to follow the instructions of the wizard in Spanish edition.

  • When the preconfiguration script has errors, the retry button “Reintentar” is not spelled correctly.

 498306 498467 498860 501388
Desktop Update Agent version 2.3.1

May 2024

Enhancement Issue ID
Microsoft Entra ID (formerly Azure Active Directory) joined accounts can be reconfigured with the new Teams application. 488317
Microsoft.Identity.Client updated to the latest version. 489105
Resolved Issues Issue ID
Error when trying to switch Teams: Access is denied. 486189
No profiles after switching Outlook using the Remove Original Profile option. 485688
When Teams fails, the guidance is to "Press Retry to try again", but the dialog does not contain a Retry button. 486187
Unhandled exception is displayed when DUA is installed on a computer where Microsoft Office is not installed. 487570
Improve error message if the switch application task is configured to update Outlook on a computer that does not have Outlook installed. 490427
Desktop Update Agent version 2.3.0

March 2024

Enhancement Issue ID

Accessibility improvements:

  • Enabled keyboard (tab) navigation to the Options button ('cog' or 'gear' icon).

  • Provided accessibility text on the Options icon for screen reader to explain the purpose .

  • Fixed a navigation issue where the profile selection combobox would lose focus unexpectedly when changing selection.

  • Provided accessibility text on the profile selection combobox to explain the purpose.

 471574
The Desktop Update Agent can now reconfigure the new Microsoft Teams application. 479017
Resolved Issues Issue ID
Corrected OneDrive setup issue where end user could be incorrectly prompted to choose a new OneDrive folder location during 'PreserveExisting' reconfiguration 460174
Error when Outlook profile is not found. 478671
Corrected minor localization issues. 472691
Desktop Update Agent version 2.2.2

January 2024

Enhancement Issue ID
The Desktop Update Agent now allows the underlying .NET Framework to choose the best TLS version available in Windows. TLS 1.3 will be used where it is available. 462429
The agent now logs the On Demand Migration endpoint that it will contact. This will help identify misconfigurations related to tokens and the different processing regions. 459448
Agent enhanced to support use of the Desktop Update Agent with On Demand Migration Hybrid Exchange. 464123
Resolved Issues Issue ID
If an incorrect passphrase is entered in the agent installer, a warning is issued and the installation will not complete. This avoids a situation where the agent would be installed, but no token would be stored. 446216
When switching multiple profiles on one computer, the status for the PowerShell Script steps could incorrectly reflect a previous run. The status now resets correctly for each profile. 449831

In some domain move scenarios involving a vanity domain, the Desktop Update Agent is unable to locate the source profile, because the source email and User Principal Name known to On Demand Migration will have changed as part of the move process.

In this situation, the Desktop Update Agent may try to create a new profile using another discovered email address, which may result in an incorrectly configured user profile. As a result, Outlook might not be able to start and will report that the current set of folders cannot be opened.

This change also resolves a OneDrive issue related to the same scenario.

 464126
Added digital signatures to the Microsoft-derived scripts included with the Desktop Update Agent, which are used in the Office 365 application licensing step. 467724

Incident response management

Quest Operations and Quest Support have procedures in place to monitor the health of the system and ensure

any degradation of the service is promptly identified and resolved. On Demand relies on Azure and AWS

infrastructure and as such, is subject to the possible disruption of these services. You can view the following

status pages:

System requirements

Before you begin a migration project and agent deployment, ensure that your systems meet the following minimum requirements.

General Requirements
  • Client has been licensed for On Demand Migration.
  • Access to a Global Administrator account for each Microsoft 365 tenant.
  • Disable policies that prevent Outlook Profile, OneDrive for Business, and Microsoft Teams application changes or creation.
  • If applicable, users have been provided new or temporary password for the account in the new target destination Microsoft 365 tenant.
  • Source and target users have matching attribute values to identify and pair objects together for mailbox and OneDrive content synchronization.

TIP: Try Password Sync for On Demand Migration Active Directory to keep your migrated hybrid users synchronized so when they are moved, they keep their existing password.

License Requirements

Before starting a migration, each target user account must be licensed for each application that will be reconfigured using Desktop Update Agent. The following licenses are required:

  • Exchange Online if configuring Outlook profiles.
  • SharePoint Online if configuring the OneDrive for Business application.
  • Microsoft Teams if configuring the Microsoft Teams application.

NOTE: On Demand Migration can automatically assign these licenses to target user accounts during the email and OneDrive migration process.

Software Requirements

NOTE: If OneDrive for Business, Microsoft Teams, Outlook, or Office are not installed on the workstation, those applications will be skipped and not impact any other applications present during the reconfiguration.

The minimum version requirements for software installed on user’s workstations:

  • Windows 11, or Windows 10 with a valid Microsoft Windows Extended Support Update (ESU) license
  • .NET 4.7.2 or higher
  • Outlook 2016 (32-bit or 64-bit) or higher. The Outlook client must also conform to the Microsoft version requirements for the applicable Exchange target version.
  • OneDrive for Business (Most recent updates recommended)
  • Microsoft Teams
  • Microsoft 365 Apps (Office Click-to-Run Version Only)

NOTE:

  • Microsoft Office Professional Plus is not supported for Office license reset.

  • LTSC versions of Windows and/or Office are not tested or supported by DUA.

Network Requirements

The minimum network requirements to run Desktop Update Agent:

NOTE: During this process, the Outlook Profile will be copied to a new Profile directed to the target account. Due to this configuration, a new OST download will occur based on each user's current cache settings, if enabled. To avoid network congestion try disabling or curtailing the cache settings to a lower amount of data then slowly increase it as needed. This can be accomplished through policies.

Supported Authentication

On Demand Migration Desktop Update Agent supports environments that use:

  • Active Directory Federation Services (AD FS)
  • Single Sign On (SSO) with mixed authentication modes, such as:
    • Modern Authentication (ADAL)
    • Forms Authentication
    • Windows Integrated Authentication

FAQs

The following is a list of frequently asked questions for On Demand Migration Desktop Update Agent.

  • Question: Does DUA support multiple accounts in a single Outlook profile?

    Answer: Currently DUA does not support reconfiguring Outlook when multiple mailbox accounts are associated with a single profile. Each additional mailbox must be added manually.

  • Question: Does DUA support non-Microsoft accounts, such as Gmail accounts, when reconfiguring Outlook?

    Answer: DUA does not support non-Microsoft accounts when reconfiguring Outlook. Such accounts must be added manually after reconfiguration.

  • Question: Does DUA support Shared Computer Licensing, also known as Shared Computer Activation (SCA)?

    Answer: Microsoft 365 App License reset and Microsoft Classic Teams configurations will be skipped if the computer is configured for "Shared Computer Licensing".

  • Question: Does DUA support Virtual Desktop Infrastructure (VDI) solutions, such as Citrix?

    Answer: The Desktop Update Agent is not tested in VDI environments, so support is not offered for using DUA in VDI. DUA has been successfully tested with Microsoft Remote Desktop Services (RDS).

  • Question: How does DUA preserve the OneDrive folder and why was my source folder renamed?

    Answer: Microsoft OneDrive for Business automatically sets the local folder name as “OneDrive – [OrganizationName]” where OrganizationName is the tenant organization name. This is the default folder name format cannot be changed.

    To preserve the source OneDrive local folder, DUA must disconnect the source account and rename the folder based on the target tenant’s organization name. For example, if the target tenant’s Organization Name is XYZCorp, the folder will be renamed to “OneDrive – XYZCorp”.

  • Question: Will the end-user’s synchronized local SharePoint folders be preserved when the Preserve Source OneDrive Folder option is enabled?

    Answer: Users must re-sync their local SharePoint folders after DUA has disconnected the source OneDrive account and added the target OneDrive account on their workstation. 

    Local SharePoint folder syncs connected to the source OneDrive account are not preserved.

    The migration administrator must validate that SharePoint migrations are completed successfully to ensure users have access to the target tenant’s SharePoint sites.

  • Question: What happens if several Switch Application tasks have been created? For example, can we create separate tasks for each type of application?
    Answer: Desktop Update Agent acts on the most recent switch task. Previously created tasks are not processed by the agent.

  • Question: Where are the Desktop Update Agent logs located?
    Answer: Desktop Update Agent logs are stored locally in C:\Users\USERPROFILE\AppData\Roaming\Quest Software Inc\On Demand Migration Desktop Update Agent\.
    Starting with DUA 3.0, agent logs can be uploaded automatically to On Demand Migration if the organization settings allow it, where they will be retained for a maximum of 30 days.

  • Question: What does the agent log entry "PowerShell scripts are restricted or disabled on this computer" mean? Is it a problem?
    Answer: Desktop Update Agent tries to run a PowerShell script to determine if the computer is Domain Joined. This is primarily a concern for Classic Teams reconfiguration. As Classic Teams has reached the end of availability, this warning message can be ignored. Note that when extending DUA with PowerShell scripts, those scripts need appropriate permissions to execute.

  • Question: Desktop Update Agent cannot retrieve my user email address information when running, and the DUA agent log reports a message similar to "AADSTS500021: Access to 'Quest' tenant is denied." How can I fix this?
    Answer: Desktop Update Agent needs to communicate with the On Demand Migration API to perform the application reconfiguration, and the API is secured by Microsoft Entra ID through a Quest Software tenant. If your network restricts access to Azure Active Directorty tenants, DUA cannot find the user's email information, and the DUA agent log reports a message similar to "AADSTS500021: Access to 'Quest' tenant is denied.". Ensure that the Quest tenant "quest.com"/91c369b5-1c9e-439c-989c-1867ec606603 is added to the permitted tenant list. Additional details related to Tenant Restriction Configuration can be found in Microsoft documentation. 

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating