Chat now with support
Chat mit Support

On Demand Migration Current - User Guide

About On Demand Migration Working with On Demand Migration Account Migration Mailbox Migration OneDrive Migration Microsoft Teams Migration Microsoft 365 Groups Migration SharePoint Migration Public Folders Migration Power BI Migration Troubleshooting Finalizing the Migration Appendix A: Using PowerShell Appendix B: How Queuing Works

Provisioning Workspaces

The provisioning task helps you with the following premigration preparations:

  • Automap and provision shared workspaces by source workspace name.
  • Provision shared workspaces that were mapped using the Map from File action.
  • Resolve workspace naming conflicts.
  • Apply permissions to target workspaces based on source permissions.
  • Reprovision workspaces to refresh permissions on target workspaces.
Considerations
  1. After all source-shared workspaces are discovered, you can begin provisioning workspaces in the target tenant using a Workspace Provisioning task.
  2. Workspaces must be provisioned before their contents can be migrated.
  3. Verify that all associated accounts are matched or migrated before creating the provisioning task.
  4. When workspaces are provisioned, the service principal used by ODMPBI in the target tenant will be assigned to the workspace with the Admin role.
  5. If workspaces are to be merged, the Quest service principal or security group created during the setup process in the target tenant must be added to the target workspace with the Admin role before performing provisioning.
  6. The Power BI service requires at least one user account or security group with the Admin role to manage a workspace in the Power BI portal.
  7. If workspace access permissions are changed in the source environment after a workspace is provisioned, you must re-provision the workspace to refresh the permissions on the target workspace.
  8. If a target workspace is deleted in the target environment after it is provisioned, and there is a requirement to recreate or rename the workspace, the Reset Mapping action should be used before processing the provisioning for the workspace again.
  9. Workspaces in the target tenant can take up to 2 hours to become available and for permissions updates to be fully processed in the target tenant after a workspace is provisioned.
Starting a Workspace Provisioning Task
  1. Log in to Quest On Demand and choose an organization if you have multiple organizations.
  2. From the navigation pane, click Migration to open the My Projects list.
  3. Create a new project or open an existing project.
  4. Click Power BI from the project tiles, or click Open from the Power BI tile to open the Power BI migration workspace.
  5. Click the Workspaces tab and select one or more workspaces.
  6. From the Actions menu, click Provision. The New Workspace Provisioning Task wizard starts. Each step is described below:
  7. Provision Options

    Choose from the following options for the processing that the task should complete

    1. Provision workspaces using source workspace name or Map from File – Select this option to preform auto-mapping of the selected workspaces by source name to provision the workspaces in target or to complete provisioning for workspaces that were manually mapped using the Map from file action.

      If a source workspace name does not exist on target, a new workspace will be provisioned with the source name.

      If a workspace has been mapped from file, the target workspace name provided will be used to provision a new workspace or merge with an existing workspace.

      If a source workspace with the same name exists in the target environment, choose from the following options to determine how the task will manage collision handling to resolve naming conflicts:

      • Skip processing, and no changes will be made to the target environment - select this option to prevent a mapping from being performed and skip any processing of permissions for the workspace.
      • Merge with the existing workspace in the target environment - select this option to create a mapping to the target workspace and merge permissions if required.
      • Provision a new workspace in the target environment with the source name and a prefix or suffix - select this option to create a new workspace name based on the text provided. If the new workspace name also already exists it will be skipped.

        TIP: Use Map from file to provision the new workspace with custom name, or to create a custom mapping.

    2. Provision all workspaces with the source name and a prefix or suffix - select this option to rename all workspaces being processed and create new workspaces with the text provided. If the new workspace name already exists it will be skipped.

      TIP: Use this option to bulk archive selected source workspaces into the target environment.

    3. Refresh permissions for previously provisioned workspaces - select this option to re-provision workspaces based on the previously mapped name. This will allow for refreshing permissions on the target workspace in the event of changes to the source workspace permissions. The settings for processing the permissions can be completed on the Permissions step. This option will not create new workspaces.

      TIP: Use the Reset mapping action to remove mappings to previously provisioned workspaces if a new workspace name is required or a workspace was deleted in the target environment and needs to be re-created.

  8. Permissions

    Choose from the following options to determine how permissions are managed:

    1. Default Target Admin User - specify a user account in the target environment that will be set with the Admin role on provisioned workspaces. This account is used to ensure that management access to a workspace in the Power BI portal is not lost.
    2. Set Default Target Admin User as workspace Admin - select this option to apply the Default Target Admin User to provisioned workspaces. If this option is not selected then the Default Target Admin User will not be applied to workspaces and this may result in cases where a target workspace cannot be managed in the Power BI portal post provisioning.

      Choose how the Admin account will be used:

      • Set Always - select this option to always apply the Default Target Admin User permissions during provisioning.
      • Set if no workspace Admin user is mapped - select this option to apply the Default Target Admin User only when there is no other account with the Admin role included in the account mapping.
    3. Set target workspace permissions - select this option to apply permissions from the source workspace to the target workspace using the account mappings. If this option is not selected the provisioning may still apply if the Default Target Admin User is selected.

      Choose how target permissions are set:

      • Add from source - source accounts and groups that are not in the target are added with the source roles. Existing target accounts and groups are not changed.
      • Update from source - source accounts and groups that are not in the target are added with the source roles. Source accounts and groups that are already in the target are changed to the source roles. Target accounts and groups that are not in the source are not changed.
      • Synchronize with source - target accounts and groups are set to the source accounts and groups roles. Target accounts and groups that do not exist in the source are removed.
  9. Schedule
    1. Choose from one of three options to schedule the task. The scheduler will be activated after you complete the task wizard.
      • Run now - task runs immediately.
      • Run later - task must be started manually.
      • Schedule - task will be started at a future date and time entered in the corresponding calendar field.
    2. Click Next.
  10. Summary
    1. Verify the task specifications as described below:
      1. Name - name of the task. The default name is Provision Workspaces. You can specify a custom name.
      2. Provisioning options - indicates the provisioning options selected.
      3. Permissions - indicates the permission options selected.
      4. Scheduled start - date and time when the task will start. Now indicates that the task will start immediately.
    2. Click Back to revise or review a previous step or click Finish to complete the task wizard and start the task as scheduled.
  11. When the task completes, the Workspace State column value of the selected workspaces in the Workspaces list changes to Provisioned, and the.Target Workspace column indicates the mapped Workspace in the target tenant (unless there is a custom mapping, in which case it should remain the same).

 

Migrating Connections

In this topic:

Prerequisites and Considerations

  • Connections can be migrated to the target tenant at any time before performing a Workspace migration.
  • A profile must be assigned to the Connection before it can be migrated.
  • Gateways that are used by Connections:
    • must be matched before migrating a Connection.
    • must be in an Online state for a Connection migration.

Starting a Connections Migration Task

  1. Log in to Quest On Demand and choose an organization if you have set up multiple organizations.
  2. From the navigation pane, click Migration to open the My Projects list.
  3. Create a new project or open an existing project.
  4. From the Power BI tile on the project dashboard click Open. Then select the Connections tab.
  5. Select a Connection that you want to migrate.
  6. Click Migrate in the List View menu. The New Migrate Connections Task wizard starts.

  7. Migration Options
    1. Default Target Admin User - specify the default target admin user to use for any user that has no match on the target. If a default admin user was configured from the project previously, it will automatically appear in this field.
    2. Privacy Level - select a privacy level from the following options:
      • Organizational - Data from a source with an organizational privacy level is considered to contain organizational data. It can be shared with other organizational data sources, but it won't be shared with external data sources.
      • Private - Data from a source with a private privacy level is considered to be highly sensitive. It won't be shared with any other data source, even if they are within the same organizational boundary.
      • Public - Data from a source with a public privacy level can be shared with other data sources without any restrictions. It's assumed that the data at this level doesn't contain sensitive information.
      • None - all data will be migrated regardless of privacy level.
    3. Incremental migration - select this option to migrate modified or missing data. This option is very helpful in subsequent migrations to keep your migrated data synchronized between source and target tenants.
    4. Click Next.
  8. Schedule
    1. Choose from one of three options to schedule the task. The scheduler will be activated after you complete the task wizard.
      • Run now - task runs immediately.
      • Run later - task must be started manually.
      • Schedule - task will be started at a future date and time entered in the corresponding calendar field.
    2. Click Next.
  9. Summary
    1. Verify the task specifications as described below:
      1. Name - name of the task. The default name is Migrate Connections Task. You can specify a custom name.
      2. Default Target Admin User - name of the admin user specified for this task.
      3. Connection privacy level - privacy level selected in the wizard.
      4. Incremental migration - indicates whether or not this option has been selected.
      5. Scheduled start - date and time when the task will start. Now indicates that the task will start immediately.
    2. Click Back to revise or review a previous step or click Finish to complete the task wizard and start the task as scheduled.
  10. When the task completes, the Connection State column in the Connections list is updated.

Reviewing the Connections Migration Task

  1. Open the Tasks tab.
  2. Select the Connections migration task that you want to review.
  3. In the task details pane that opens, the information presented is as described below:
    1. Task Status - current status of the task.
    2. Type - Type of the task. The type is MigrateConnections.
    3. Created - Date and time when the task was created.
    4. Modified - Date and time when the task was last updated.
    5. Last Operation - The action that was most recently performed in this task.
    6. Schedule - Date and time when the task started. Now indicates that the task started immediately after the task was created.
    7. Events (number) - Number indicates the count of events that the task encountered. The values indicate the type of the events and the event count for each type.
    8. Connections (number) - The number of Connections that were selected for migration and the number of Connections passing through the various states from Migrating to Migrated.

Reviewing the Connections Migration Task Events

  1. Open the Tasks tab.
  2. Select the Connections migration task for which you want to review the events.
  3. In the task details pane that opens, click Events (number). The Events tab opens with a filtered list of events for the selected task.
  4. Select an event that you want to review. In the event details pane that opens, the information presented is as described below:
    1. Object - name of the Power BI object if applicable.
    2. Task - Name of the task.
    3. Time - Date and time when the event occurred.
    4. Summary - a descriptive statement about the event if an exception occurs.

Migrating Workspaces

In this topic:

Prerequisites

Any Connections that are required by Reports must be migrated before scheduling a Workspace migration.

The Default Target Admin User configured in your Power BI project, is added to migrated Workspaces to ensure that access to migrated Workspaces is retained if a matching administrator account is not available for a migrated Workspace. We recommend that you retain this for safety.

Considerations

Your target tenant might already host Power BI Workspaces created before the migration. In cases where a Workspace name already exists in the destination, the migration will merge report, semantic model and Workspaces permissions data from the source tenant.

We recommend that you run only one migration task at a time to avoid scheduling delays.

Starting a Migrate Workspaces Task

  1. Log in to Quest On Demand and choose an organization if you have set up multiple organizations.
  2. From the navigation pane, click Migration to open the My Projects list.
  3. Create a new project or open an existing project.
  4. From the Power BI tile on the project dashboard click Open. Then select the Workspaces tab.
  5. Select one or more Workspace that you want to migrate.
  6. Click Migrate in the List View menu. The New Migrate Workspaces Task wizard starts.
  7. Migration Options
    1. Default Target Admin User - specify the default target admin user to use for any user that has no match on the target. If a default admin user was configured from the project previously, it will automatically appear in this field.
    2. Incremental migration - select this option to migrate modified or missing data. This option is very helpful in subsequent migrations to keep your migrated data synchronized between source and target tenants.
    3. Click Next.
  8. Schedule
    1. Choose from one of three options to schedule the task. The scheduler will be activated after you complete the task wizard.
      • Run now - task runs immediately.
      • Run later - task must be started manually.
      • Schedule - task will be started at a future date and time entered in the corresponding calendar field.
      • Priority - select a priority from the dropdown for the objects scheduled for migration with this task . Values are: Highest, High, Medium, Low and Lowest. The default priority is Medium. If the system is busy, the objects are queued (Migration state = Queued). When the system accepts new migration work, objects are taken from the queue based on the assigned priority and age in the queue.
    2. Click Next.
  9. Summary
    1. Verify the task specifications as described below:
      1. Name - name of the task. The default name is Migrate Workspaces Task. You can specify a custom name.
      2. Default Target Admin User - name of the admin user specified for this task.
      3. Incremental migration - indicates whether or not this option has been selected.
      4. Scheduled start - date and time when the task will start. Now indicates that the task will start immediately.
    2. Click Back to revise or review a previous step or click Finish to complete the task wizard and start the task as scheduled.
  10. When the task completes, the Workspace State column in the Workspaces list is updated.

Reviewing the Migrate Workspaces Task

  1. Open the Tasks tab.
  2. Select the Workspace migration task that you want to review.
  3. In the task details pane that opens, the information presented is as described below:
    1. Task Status - current status of the task.
    2. Type - Type of the task. The type is MigrateWorkspaces.
    3. Created - Date and time when the task was created.
    4. Modified - Date and time when the task was last updated.
    5. Last Operation - The action that was most recently performed in this task.
    6. Schedule - Date and time when the task started. Now indicates that the task started immediately after the task was created.
    7. Priority - the priority of this task.
    8. Events (number) - Number indicates the count of events that the task encountered. The values indicate the type of the events and the event count for each type.
    9. Workspaces (number) - The number of Workspaces that were selected for migration and the number of Workspaces passing through the various states from Migrating to Migrated.

Reviewing the Migrate Workspaces Task Events

  1. Open the Tasks tab.
  2. Select the Workspace migration task for which you want to review the events.
  3. In the task details pane that opens, click Events (number). The Events tab opens with a filtered list of events for the selected task.
  4. Select an event that you want to review. In the event details pane that opens, the information presented is as described below:
    1. Object - name of the Power BI object if applicable.
    2. Task - name of the task.
    3. Time - date and time when the event occurred.
    4. Summary - a descriptive statement about the event if an exception occurs.

 

Troubleshooting

Before you contact Quest support is recommended to prepare organization ID, project ID and task ID

To find Task ID and Project ID

In Events grid right click task link in Task Name column and select Copy link address. Copied link contains the Task ID and the Project ID.

To find organization ID

If you are trying to find an existing On Demand organization ID that another users have created, make sure that they have added your email address under Access Control > Administrators.

  1. In case you are Administrator of the organization, click your account in top right corner to open the account related menu.
  2. Click the organization name. You can see Organization ID in Manage Organization dialog.

Special Cases

Table 1: Special Cases

Feature Event Root cause Workaround
Microsoft Teams Migration Cannot find the group '{Group ID}' on the source. Try to check whether the group exists using PowerShell cmdlet 'Get-UnifiedGroup' as described in the documentation Group associated with the team not found

Use the following PowerShell script and the group ID provided by the error message to get the group name:

Install-Module PowerShellGet -Force Install-Module -Name ExchangeOnlineManagement
$UserCredential = Get-Credential
Connect-ExchangeOnline -Credential $UserCredential
Get-UnifiedGroup -Identity "b1552bc6-f932-4ac9-a4f2-24a5d2da2eed" | Format-List DisplayName,Id

If this is a source group, fix your source data before proceed for migration.

If this is a target group, check if this group exists in target. If this group exists, please contact our support. If this group doesn't exist, remove this group associated team from target, and rerun provision and migration.

Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen