サポートと今すぐチャット
サポートとのチャット

On Demand Migration Current - Desktop Update Agent User Guide

Extending DUA with PowerShell scripts

If required, you can create custom PowerShell scripts to run before and/or after the desktop application reconfiguration.

  • The Desktop Update Agent will wait a maximum of two minutes for any script to complete.

  • The option to use a script is set as part of the switch task; however, for security and compliance reasons, the script deployment is not done through On Demand Migration.

  • Project administrators need to deploy the required PowerShell scripts to end user computers to these directories: 
    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

NOTE: The Quest-provided sample scripts will be ignored if DUA finds any other PowerShell script in the same directory.

Using the Desktop Update Agent

Running Desktop Update Agent

This section describes the process followed by users to run Desktop Update Agent to reconfigure their applications.

NOTE:

  • The applications to be reconfigured by Desktop Update Agent are set by the migration administrator as part of the migration project.
  • After each application has been reconfigured, users may be prompted to enter Microsoft 365 account passwords and select Allow my organization to manage my device or No sign in to this app only.

  • To reconfigure Microsoft 365 App License and Microsoft Classic Teams, command prompt script processing must be enabled.

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

  • For Microsoft 365 App License reconfigurations: On some versions of Windows, Managed Device options (such as Azure Joined, Hybrid Azure Joined, or workplace joined) are not supported. This is a Microsoft limitation.

  • For Classic Teams reconfigurations: For Managed Device options (such as Azure Joined, Hybrid Azure Joined, or workplace joined), the Teams step may report success, but users may still be signed in to source. This is a Microsoft limitation.

To run the Desktop Update Agent:

  1. From the Start menu, expand the Quest folder, and click the On Demand Migration Desktop Update Agent.
  2. On the Configure Desktop Application dialog, select the Profile to migrate (if more than one eligible profile is present) and click Start.
    1. If applicable, close any opened Office application and restart it to complete the license activation and click Next to reconfigure the next application.

    2. If Outlook has been migrated, users are prompted to close Microsoft Outlook if it is currently running. The agent starts the reconfiguration and opens Outlook after target account profile is created and click Next to reconfigure Microsoft 365 App License Reset.

      NOTE: If OneDrive is also being processed, Outlook will not be opened until the Desktop Update Agent has completed all steps.
    3. If OneDrive has been migrated, the agent opens the OneDrive client once it has been reconfigured and click Next to reconfigure the next application.

      • To add a new target and retain OneDrive file locations when reconfiguring a OneDrive application, enable the Add new target OneDrive account preserving existing local folders and disconnect the source account option.

      • To simply add a new target OneDrive file location enable the Add new target OneDrive account and local folders (requires downloading) option. After successful authentication with Microsoft 365 tenant, OneDrive prompts users to configure the target tenant OneDrive account and provide a local folder where the OneDrive content will be synchronized. Note: The source OneDrive account is not removed by the agent.

        NOTE: The computer may have to be restarted to allow the OneDrive folder to be renamed. Once restarted, the agent will open again to process any remaining steps. If this is required, you can select to either restart the computer immediately or have the rename triggered on the next restart.

    4. If Teams has been migrated, users are prompted to exit and quit Teams. The agent reconfigures the Teams client with the target account and opens it after the process completes.
  3. If required, click the gear icon and select Logs to review the updates.

Validating application reconfiguration

Once Desktop Update Agent has been run, administrators can verify that applications have been reconfigured properly for all users.

To validate application reconfiguration results from On Demand Migration, see Validating application reconfiguration from On Demand Migration

To validate application reconfiguration on workstations:

  1. Open Outlook. Users may be prompted to enter their Microsoft 365 account password and also asked to Allow my organization to manage my device or No, sign in to this app only.
  2. Sign in with the target Microsoft 365 account. Click Sign in.
  3. Enter user target account email address and click Next.
  4. Accept the Microsoft license agreement.
  5. Choose File | Office Account in Outlook. Review the license information and confirm that the Microsoft 365 App license has been reconfigured to the target account.
  6. Open Teams and validate that the user is signed into the target tenant.
  7. Open OneDrive and validate that the target OneDrive account has been added.

    • For OneDrive applications, if the “Add new target OneDrive account preserving existing local folders and disconnect the source account” option was selected, verify that the OneDrive local folders and version history information are preserved.

関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択