Chatta subito con l'assistenza
Chat con il supporto

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

Creating and Assigning Connection Profiles

A connection profile is a named set of credentials that is assigned to discovered Connections before they can be migrated. These credentials are required by Microsoft Power BI to read the source data and create the Connection in the target tenant.

NOTE: Creating a Connection Profile require credentials that are securely stored in the On Demand Migration repository. It is recommended to create a profile when Connections are expected to be migrated. When you complete the Connection migration, you may delete the Connection Profile to remove the credentials from the On Demand Migration repository.

See the On Demand Migration - PowerBI security guide for more information about how On Demand Migration secures sensitive information.

To create profiles

  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 Connection Profiles tab.
  5. Click Create in the List View menu. The Create New Connection Profile Task wizard starts.
  6. Step 1: Connection Profile
    1. Specify the information for the fields described below:
      • User name - unique identifier associated with an individual user permitted to access the connection in the format domain\user.
      • Password - password to verify the identity of the user.
      • Profile name - name of the connection profile. If you use the name of an existing profile, you can modify the profile by selecting the Overwrite existing option.
      • Overwrite existing - select this option to alter a profile with the same name if it exists.
    2. Click Next.
  7. Step 2: 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.
  8. Step 3: Summary
    1. Verify the task specifications as described below:
      1. Name - name of the task. The default name is New Connection Profile. You can specify a custom name.
      2. User name - unique identifier of a user permitted to access the connection.
      3. Profile name - name of the connection profile.
      4. Overwrite existing - indicates whether or not a preexisting profile must be modified if it exists.
      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.

To assign profiles

  1. From the Power BI workspace select the Connections tab.
  2. Select one or more Connections. You can select a Connection that is already assigned if you want to change the profile assigned to the Connection, or you can select an unassigned Connection.
  3. Click Assign Connection Profile in the List View menu. The New Connection Profile Task wizard starts.
  4. Step 1: Connection Profile
    1. Assign an existing connection profile - select this option to assign an existing connection profile.
      • Select a connection profile - click the dropdown and select a connection profile.
    2. Assign a new connection profile - select this option to create and assign a new connection profile. Specify the information for the fields described below:
      • User name - unique identifier associated with an individual user permitted to access the connection in the format domain\user.
      • Password - password to verify the identity of the user.
      • Profile name - name of the connection profile. If you use the name of an existing profile, you can modify the profile by selecting the Overwrite existing option.
      • Overwrite existing - select this option to alter a profile with the same name if it exists.
    3. Click Next.
  5. Step 2: 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.
  6. Step 3: Summary
    1. Verify the task specifications as described below:
      1. Name - name of the task. The default name is Assign Connection Profile. You can specify a custom name.
      2. User name - unique identifier of a user permitted to access the connection.
      3. Profile name - name of the connection profile.
      4. Overwrite existing - indicates whether or not a preexisting profile must be modified if it exists.
      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.
  7. When the task completes, the selected Connections will be assigned to a named profile. The Assigned Connection Profile column value in the List View will be set to the profile name.

Mapping Workspaces

Use this method to map specific Power BI Workspaces from the source to a Power BI Workspace that may or may not exist in the target tenant. If the Workspace exists in the target tenant, it will be merged with the target Workspace and the source data is used to resolve any merge conflicts. If the target Workspace does not exist, a new Workspace will be created.

The CSV file lets you specify the Workspaces that you want to map and ignore the rest. You can then use this file in the New Mapping from File Task wizard to map the Power BI Workspaces from the source to the target tenant.

This is a two-step process as described below:

To create the mapping file:

  1.  Prepare a comma-separated values (CSV) file with the source and target Workspace names.

  2. NOTE:

    • You can download a CSV template when you start the New Mapping from File Task wizard and click Download Example File from the Mapping File step.
    • CSV file names with non-ASCII characters are not supported.
  3. The header row defines the names of the source and target attributes used for mapping. Subsequent rows list the mapping values of the attributes.

    The columns are as follows:

    • Source Workspace Name - unique name of the source Power BI Workspace. The column header is case sensitive.
    • Target Workspace Name - unique name of the Power BI Workspace. The column header is case sensitive. In cases where a mapping is not applied and the Target Workspace does not have a value, the Name of the source Workspace will be used for the migration to the target tenant.
  4. Save the CSV file. You may rename the file if needed.

To upload the mapping file:

  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. From the Actions menu, click More and then select Map from File. The New Mapping from File Task wizard starts.
  6. Step 1: Mapping File
    1. Click Browse and select the CSV mapping file. The selected file name appears next to the Browse button.
    2. Click Next.
  7. Step 2: 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.
  8. Step 2: Summary
    1. Verify the task specifications as described below:
      1. Name - name of the task. The default name is Map Workspaces From File. You can specify a custom name.
      2. 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.
  9. When the task completes, the Target Workspace column in the Workspaces list indicates the mapped Workspace in the target tenant.

Matching and Mapping Gateways

Prerequisites

Gateways must be configured in the target tenant at any time before matching or mapping the Gateways, and migrating any Connections or Workspaces.

There are two ways to match Gateways from the source to a target tenant:

Matching Gateways from the Gateways list

  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 Gateways tab.
  5. Select one or more Gateways that you want to match to a target tenant.
  6. Click Match in the List View menu and then select Match Selected. The New Match Gateways Task wizard starts.
  7. Step 1: 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.
  8. Step 2: Summary
    1. Verify the task specifications as described below:
      1. Name - name of the task. The default name is Match Gateways. You can specify a custom name.
      2. 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.
  9. When the task completes, the Target Gateway column in the Gateways list indicates the matched Gateway in the target tenant.

Mapping Gateways from a file

To match source Gateways to target Gateways with different names, a CSV file is used to indicate the mapping between source and target Gateways, as described below.

To create the mapping file:

  1.  Prepare a comma-separated values (CSV) file with the source and target Gateway names.
  2. The header row defines the names of the source and target attributes used for mapping. Subsequent rows list the mapping values of the attributes.

    The columns are as follows:

    • Name - unique name of the source Gateway. The column header is case sensitive.
    • Target Gateway - unique name of the Gateway in target tenant. The column header is case sensitive.
  3. Save the CSV file. You may rename the file if needed.

To upload the mapping file:

  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 Gateways tab.
  5. Select one or more Gateways that you want to map to a target tenant.
  6. Click Match in the List View menu and then select Map from File. The Import Gateways Matching Task wizard starts.
  7. Step 1: Import Gateways Mapping Options
    1. Click Browse and select the CSV mapping file. The selected file name appears next to the Browse button.
    2. Click Next.
  8. Step 2: 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. Step 2: Summary
    1. Verify the task specifications as described below:
      1. Name - name of the task. The default name is Import Gateways Mapping. You can specify a custom name.
      2. 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 Target Gateway column in the Gateways list indicates the mapped Gateway in the target tenant.

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. Step 1: 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. Step 2: 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. Step 3: 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.
Related Documents

The document was helpful.

Seleziona valutazione

I easily found the information I needed.

Seleziona valutazione