Merge pull request #26933 from JoshGer/patch-83

Adding more RS items that cannot be migrated

Author: prmerger-automator[bot]

docs/reporting-services/tools/sample-reporting-services-rs-exe-script-to-copy-content-between-report-servers.md

@@ -3,7 +3,7 @@ title: "Sample Reporting Services rs.exe Script to Copy Content between Report S
 description: Learn how to copy content items and settings from one SQL Server Reporting Services report server to another by using the RS.exe utility to run a Reporting Services RSS script.
 author: maggiesMSFT
 ms.author: maggies
-ms.date: 01/18/2022
+ms.date: 05/01/2023
 ms.service: reporting-services
 ms.subservice: tools
 ms.topic: conceptual
@@ -46,28 +46,34 @@ The script can be used to copy content between report servers of the same mode o
 |Item|Migrated|SharePoint|Description|  
 |----------|--------------|----------------|-----------------|  
 |Passwords|**No**|**No**|Passwords are **NOT** migrated. After content items are migrated, update the credential information on the destination server. For example, data sources with stored credentials.|  
-|My Reports|**No**|**No**|The Native mode "My Reports" feature is based on individual user sign-ins therefore the scripting service does not have access to content in "My Reports" folders for users other than the **-u** parameter used to run the rss script. Also, "My Reports" isn't a feature of [!INCLUDE[ssRSnoversion](../../includes/ssrsnoversion-md.md)] SharePoint mode and items in the folders cannot be copied to a SharePoint environment. Therefore, the script does not copy report items that are in the "My Reports" folders on a source native mode report server<br /><br /> To migrate the content in "My Reports" folders with this script, complete the following steps:<br /><br /> 1.  Create new folder(s) in the web portal. Optionally, you can create folders or subfolders for each user.<br />2.  Sign in as one of the users with "My Reports" content.<br />3.  In the web portal, select the **My Reports** folder.<br />4.  Select the **Details** view for the folder.<br />5.  Select each report that you want to copy.<br />6.  Select **Move** in the web portal toolbar.<br />7.  Select the desired destination folder.<br />8.  Repeat steps 2-7 for each user.<br />9. Run the script.|  
+|My Reports|**No**|**No**|The Native mode "My Reports" feature is based on individual user sign-ins therefore the scripting service doesn't have access to content in "My Reports" folders for users other than the **-u** parameter used to run the rss script. Also, "My Reports" isn't a feature of [!INCLUDE[ssRSnoversion](../../includes/ssrsnoversion-md.md)] SharePoint mode and items in the folders can't be copied to a SharePoint environment. Therefore, the script doesn't copy report items that are in the "My Reports" folders on a source native mode report server<br /><br /> To migrate the content in "My Reports" folders with this script, complete the following steps:<br /><br /> 1.  Create new folder(s) in the web portal. Optionally, you can create folders or subfolders for each user.<br />2.  Sign in as one of the users with "My Reports" content.<br />3.  In the web portal, select the **My Reports** folder.<br />4.  Select the **Details** view for the folder.<br />5.  Select each report that you want to copy.<br />6.  Select **Move** in the web portal toolbar.<br />7.  Select the desired destination folder.<br />8.  Repeat steps 2-7 for each user.<br />9. Run the script.|  
 |History|**No**|**No**||  
 |History settings|Yes|Yes|The history settings are migrated however the history details are NOT migrated.|  
-|Schedules|Yes|Yes|To migrate schedules, it is required that SQL Server Agent is running on the target server. If SQL Server Agent isn't running on the target, you will see an error message similar to this one:<br /><br /> `Migrating schedules: 1 items found. Migrating schedule: theMondaySchedule ... FAILURE:  The SQL Agent service isn't running. This operation requires the SQL Agent service. ---> Microsoft.ReportingServices.Diagnostics.Utilities.SchedulerNotResponding Exception: The SQL Agent service isn't running. This operation requires the SQL Agent service.`|  
-|Roles and system policies|Yes|Yes|By default the script won't copy custom permission schema between servers. The default behavior is the items will be copied to the destination server with the 'inherit parent permissions' flag set to TRUE. If you want the script to copy permissions for individual items, use the SECURITY switch.<br /><br /> If the source and target servers are **not the same report server mode**, for example from native mode to SharePoint mode, and you use the SECURITY switch, the script will attempt to map default roles and groups based on the comparison in the article [Compare Roles and Tasks in Reporting Services to SharePoint Groups and Permissions](../../reporting-services/security/reporting-services-roles-tasks-vs-sharepoint-groups-permissions.md). Custom roles and groups aren't copied to the destination server.<br /><br /> When the script is copying between servers **that are the same mode**, and you use the SECURITY switch, the script will create new roles (native mode) or groups (SharePoint mode) on the destination server.<br /><br /> If a role already exists on the destination server, the script will create a "Failure" message similar to the following, and continue migrating other items. After the script completes, verify that the roles on the destination server are configured to meet your needs. the Migrating roles: 8 items found.<br /><br /> `Migrating role: Browser ... FAILURE: The role 'Browser' already exists and cannot be created. ---> Microsoft.ReportingServices.Diagnostics.Utilities.RoleAlreadyExistsException: The role 'Browser' already exists and cannot be created.`<br /><br /> For more information, see [Grant User Access to a Report Server](../../reporting-services/security/grant-user-access-to-a-report-server.md)<br /><br /> **Note:** if a user that exists on the source server does not exist on the destination server, the script cannot apply role assignments on the destination server, the script cannot apply role assignments, even if the SECURITY switch is used.|  
+|Schedules|Yes|Yes|To migrate schedules, it's required that SQL Server Agent is running on the target server. If SQL Server Agent isn't running on the target, you will see an error message similar to this one:<br /><br /> `Migrating schedules: 1 items found. Migrating schedule: theMondaySchedule ... FAILURE:  The SQL Agent service isn't running. This operation requires the SQL Agent service. ---> Microsoft.ReportingServices.Diagnostics.Utilities.SchedulerNotResponding Exception: The SQL Agent service isn't running. This operation requires the SQL Agent service.`|  
+|Roles and system policies|Yes|Yes|By default the script won't copy custom permission schema between servers. The default behavior is the items will be copied to the destination server with the 'inherit parent permissions' flag set to TRUE. If you want the script to copy permissions for individual items, use the SECURITY switch.<br /><br /> If the source and target servers are **not the same report server mode**, for example from native mode to SharePoint mode, and you use the SECURITY switch, the script will attempt to map default roles and groups based on the comparison in the article [Compare Roles and Tasks in Reporting Services to SharePoint Groups and Permissions](../../reporting-services/security/reporting-services-roles-tasks-vs-sharepoint-groups-permissions.md). Custom roles and groups aren't copied to the destination server.<br /><br /> When the script is copying between servers **that are the same mode**, and you use the SECURITY switch, the script will create new roles (native mode) or groups (SharePoint mode) on the destination server.<br /><br /> If a role already exists on the destination server, the script will create a "Failure" message similar to the following, and continue migrating other items. After the script completes, verify that the roles on the destination server are configured to meet your needs. the Migrating roles: 8 items found.<br /><br /> `Migrating role: Browser ... FAILURE: The role 'Browser' already exists and cannot be created. ---> Microsoft.ReportingServices.Diagnostics.Utilities.RoleAlreadyExistsException: The role 'Browser' already exists and cannot be created.`<br /><br /> For more information, see [Grant User Access to a Report Server](../../reporting-services/security/grant-user-access-to-a-report-server.md)<br /><br /> **Note:** If a user that exists on the source server does not exist on the destination server, the script can't apply role assignments on the destination server, the script can't apply role assignments, even if the SECURITY switch is used.|  
 |Shared data source|Yes|Yes|The script won't overwrite existing items on the target server. If an item on the target server already exists with the same name, you will see an error message similar to this one:<br /><br /> `Migrating DataSource: /Data Sources/Aworks2012_oltp ... FAILURE:The item '/Data Sources/Aworks2012_oltp' already exists. ---> Microsoft.ReportingServices.Diagnostics.Utilities.ItemAlreadyExistsException: The item '/Data Source s/Aworks2012_oltp' already exists.`<br /><br /> Credentials are **NOT** copied over as part of the data source. After content items are migrated, update the credential information on the destination server.|  
 |Shared dataset|Yes|Yes|| 
 |Folder|Yes|Yes|The script won't overwrite existing items on the target server. If an item on the target server already exists with the same name, you will see an error message similar to this one:<br /><br /> `Migrating Folder: /Reports ... FAILURE: The item '/Reports' already exists. ---> Microsoft.ReportingServices.Diagnostics.Utilities.ItemAlreadyExistsException: The item '/Reports' already exists.`|  
 |Report|Yes|Yes|The script won't overwrite existing items on the target server. If an item on the target server already exists with the same name, you will see an error message similar to this one:<br /><br /> `Migrating Report: /Reports/testThe item '/Reports/test' already exists. ---> Microsoft.ReportingServices.Diagnostics.Utilities.ItemAlreadyExistsException: The item '/Reports/test' already exists.`|  
+|Power BI Reports|No|No|**Only available with Power BI Report Server**<br /><br />[Reporting Services PowerShell commands](https://github.com/microsoft/ReportingServicesTools), such as Out-RsRestFolderContent and Write-RsRestFolderContent, may be used as an alternative.|  
 |Parameters|Yes|Yes||  
 |Subscriptions|Yes|Yes||  
 |History Settings|Yes|Yes|The history settings are migrated however the history details are NOT migrated.|  
 |Processing options|Yes|Yes||  
-|Cache refresh options|Yes|Yes|Dependent settings are migrated as part of a catalog item. The following is the sample out of the script as it migrates a report (.rdl) and related settings such as cache refresh options:<br /><br /> -   Migrating parameters for report TitleOnly.rdl 0 items found.<br />-   Migrating subscriptions for report TitleOnly.rdl: 1 items found.<br />-   Migrating subscription Save in \\\server\public\savedreports as TitleOnly ... SUCCESS<br />-   Migrating history settings for report TitleOnly.rdl ... SUCCESS<br />-   Migrating processing options for report TitleOnly.rdl ... 0 items found.<br />-   Migrating cache refresh options for report TitleOnly.rdl ... SUCCESS<br />-   Migrating cache refresh plans for report TitleOnly.rdl: 1 items found.<br />-   Migrating cache refresh plan titleonly_refresh735amM2F ... SUCCESS|  
+|Cache refresh options|Yes|Yes|Dependent settings are migrated as part of a catalog item. The following output is the sample out of the script as it migrates a report (.rdl) and related settings such as cache refresh options:<br /><br /> -   Migrating parameters for report TitleOnly.rdl 0 items found.<br />-   Migrating subscriptions for report TitleOnly.rdl: 1 items found.<br />-   Migrating subscription Save in \\\server\public\savedreports as TitleOnly ... SUCCESS<br />-   Migrating history settings for report TitleOnly.rdl ... SUCCESS<br />-   Migrating processing options for report TitleOnly.rdl ... 0 items found.<br />-   Migrating cache refresh options for report TitleOnly.rdl ... SUCCESS<br />-   Migrating cache refresh plans for report TitleOnly.rdl: 1 items found.<br />-   Migrating cache refresh plan titleonly_refresh735amM2F ... SUCCESS|  
 |Cache refresh plans|Yes|Yes||  
 |Images|Yes|Yes||  
 |Report parts|Yes|Yes||  
+|KPIs|No|No|[Reporting Services PowerShell commands](https://github.com/microsoft/ReportingServicesTools), such as Out-RsRestFolderContent and Write-RsRestFolderContent, may be used as an alternative.|  
+|Mobile Reports|No|No|[Reporting Services PowerShell commands](https://github.com/microsoft/ReportingServicesTools), such as Out-RsRestFolderContent and Write-RsRestFolderContent, may be used as an alternative.|  
+|Excel Workbooks|No|No|**Only available with Power BI Report Server**<br /><br />Using [Reporting Services PowerShell commands](https://github.com/microsoft/ReportingServicesTools), such as Out-RsRestFolderContent and Write-RsRestFolderContent, may be used as an alternative.|  
 
 [!INCLUDE [ssrs-report-parts-deprecated](../../includes/ssrs-report-parts-deprecated.md)]
+
+[!INCLUDE [ssrs-mobile-report-deprecated](../../includes/ssrs-mobile-report-deprecated.md)]
 
 ##  <a name="bkmk_required_permissions"></a> Required permissions  
- The permissions required to read or write items and resources isn't the same for all of the methods used in the script. The following table summarizes the methods used for each item or resource and links to related content. Navigate to the individual article to see the required permissions. For example the ListChildren method topic notes the required permissions of:  
+ The permissions required to read or write items and resources isn't the same for all of the methods used in the script. The following table summarizes the methods used for each item or resource and links to related content. Navigate to the individual article to see the required permissions. For example, the ListChildren method topic notes the required permissions of:  
 
 -   **Native Mode Required Permissions:** ReadProperties on Item  
 
@@ -188,7 +194,7 @@ The script can be used to copy content between report servers of the same mode o
 
     -   `https://servername/reportserver`  
 
-     In SharePoint mode the URL looks like this URL:  
+     In SharePoint mode, the URL looks like this URL:  
 
     -   `https://servername/_vti_bin/reportserver`