Administrators can monitor each user's application reconfiguration status through the On Demand Migration Desktop Agents dashboard.
The possible status states include:
- Empty "-": There is no reconfiguration task assigned to the user.
- Waiting: Reconfiguration tasks have been submitted, waiting for the user to complete the configuration.
- Skipped: User chose to skip the reconfiguration by closing the agent.
- Complete: Reconfiguration has completed.
- Error: An error has occurred during the reconfiguration. Errors are logged and send back to On Demand Migration.
Changing application status manually
It may be necessary to manually set the application status to complete. For example, a user may have chosen to complete their reconfiguration outside of DUA. If this becomes necessary, select the relevant user(s) on the Desktop Agents dashboard. Then choose More and select the Mark as Complete menu option. The Mark as Complete dialog opens. Use the check boxes to choose which apps should be marked as Complete, and then use the Set selected to Complete button to perform the action.
 |
Caution: There is currently no Undo for this action. Be sure that you have selected the correct set of users. |
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 project page:
- From the On Demand Migration Project Page, open Accounts, then choose the Desktop Agents tab. The users' application configuration status should all shown as Completed.
- Click the Devices link in the user detail panel to review the device history information and application configuration status.
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. |
