FAQ on Desktop Update Agent
1. How long is the DUA token valid?
The DUA Authentication Token by default valid for 1 year.
2. Does DUA support multiple accounts in a single Outlook profile?
Currently, the Desktop Update Agent (DUA) does not support reconfiguring Outlook when multiple mailbox accounts are associated with a single profile. Each additional mailbox must be added manually.
3. How does DUA preserve the OneDrive folder and why was my source folder renamed?
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”.
4. Will the end-user’s synchronized local SharePoint folders be preserved when the Preserve Source OneDrive Folder option is enabled?
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 succesfully to ensure users have access to the target tenant’s SharePoint sites.
5. What happens if several Switch Tasks have been created? For example, can we create separate tasks for each type of application?
Desktop Update Agent acts on the most recent switch task. Previously created tasks are not processed by the agent.
6. How do I silently deploy Desktop Update Agent using a Command Line script?
To deploy DUA using a command line, use the following procedure:
7. 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?
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.
8 . What is the minimum custom role required to view templates or using template during the execution of a 'Switch Application' task Had assigned DUA only role?
Receive an error message: "Access Denied: Insufficient permissions to access. "
Sample screenshot FAQ8
For the custom Migration role for the DUA Switch task, the following permissions must be selected.
1) "ViewProjects0," With "All Selected"
Sample screenshot FAQ8-1
2) "Run Provision and migration tasks", With "Accounts" selected
Sample screenshot FAQ8-2
3) "Manage Desktop Update Agent", with "Desktop Update Agent" selected
Sample screenshot FAQ8-3
9 . 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?
Refer to DUA FAQ here, 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.
