Merge pull request #2123 from MicrosoftDocs/main

publish main to live, 11/15/2024, 3:30 pm PT

surface-hub/includes/hub-mtr-scope.md

@@ -8,4 +8,5 @@ ms.topic: include
 
 ## Scope
 
-This article applies to [new Surface Hub 3 devices](/surface-hub/surface-hub-3-whats-new), Surface Hub 2S devices [upgraded with the Surface Hub 3 Compute Cartridge](/surface-hub/install-manage-surface-hub-3-pack) and Surface Hub 2S devices [software-migrated to the Teams Rooms on Windows platform](/surface-hub/surface-hub-2s-migrate-to-mtr-w).
+> [!NOTE]
+> This article applies to [new Surface Hub 3 devices](/surface-hub/surface-hub-3-whats-new), Surface Hub 2S devices [upgraded with the Surface Hub 3 Compute Cartridge](/surface-hub/install-manage-surface-hub-3-pack) and Surface Hub 2S devices [software-migrated to the Teams Rooms on Windows platform](/surface-hub/surface-hub-2s-migrate-to-mtr-w).

surface-hub/install-manage-surface-hub-3-compute-cartridge.md

@@ -17,7 +17,7 @@ appliesto:
 
 # Install and manage Surface Hub 3 Compute Cartridge
 
-Enjoy the first all-in-one Teams Rooms board running on Windows by seamlessly updating your Surface Hub 2S to Microsoft Teams Rooms with the Surface Hub 3 Compute Cartridge, (formerly Surface Hub 3 Pack). To place an order, contact your [Surface device reseller](https://www.microsoft.com/surface/business/where-to-buy-microsoft-surface#DEVICESRESELLERS).
+Enjoy the first all-in-one Teams Rooms board running on Windows by seamlessly updating your Surface Hub 2S to Microsoft Teams Rooms with the Surface Hub 3 Compute Cartridge (formerly Surface Hub 3 Pack). To place an order, contact your [Surface device reseller](https://www.microsoft.com/surface/business/where-to-buy-microsoft-surface#DEVICESRESELLERS).
 
 ## Install Surface Hub 3 Compute Cartridge
 
@@ -28,7 +28,7 @@ Enjoy the first all-in-one Teams Rooms board running on Windows by seamlessly up
 > [!TIP]
 > You may need to restart the device and continue to check for available updates. Ensure the Surface Hub 2S's update history shows **Microsoft Corporation - System Hardware Update - 5/24/2023** or a **System Hardware Update** with any newer date (for example, 3/1/2024).
 
-- An account with admin privileges. You'll need to reset the device if you don't know your username or admin password. For more information, see [Reset and recovery for Surface Hub 2S](/surface-hub/surface-hub-2s-recover-reset).
+- An account with admin privileges. You need to reset the device if you don't know your username or admin password. For more information, see [Reset and recovery for Surface Hub 2S](/surface-hub/surface-hub-2s-recover-reset).
 - A resource account with a [supported Microsoft Teams Rooms license](/microsoftteams/rooms/rooms-licensing).
 
 > [!NOTE]
@@ -56,37 +56,64 @@ Review the following demo and follow the instructions on this page.
 
 4. Slide the Surface Hub 3 Compute Cartridge into your Surface Hub.
 5. Fasten the locking screw and slide the cover into place. Power on your new Surface Hub 3.  
-6. To complete setup, refer to the following articles:
+6. Complete your setup with guidance from the following articles:
 
 - [First-time setup for Surface Hub running Microsoft Teams Rooms on Windows](first-run-program-surface-hub-3.md).
 - [Security best practices for Surface Hubs running Microsoft Teams Rooms on Windows](surface-hub-3-security.md)
 
-## Manage Surface Hub 3 
+## Manage Surface Hub 3
 
-If you manage Surface Hub 2S via Microsoft Intune or another mobile device management (MDM) provider, remove the device before installing Surface Pack 3.
+This section provides guidance on initial management steps for Teams Admin Center and Microsoft Intune or mobile device management (MDM) provider.
 
-1. Sign into Microsoft Intune admin center, go to **Devices > All devices**,  and select your Surface Hub 2S.
-2. Select **Delete**.
+### Manual removal of upgraded Surface Hub devices from Teams Admin Center (Surface Hubs Legacy tab)
 
-  ![Screenshot that shows removal of Surface Hub 2S from Intune.](images/remove-hub2s-from-intune.png).
+After upgrading your Surface Hub 2S with the Surface Hub 3 Compute Cartridge, you need to manually remove the device listing from the "Surface Hubs (Legacy)" section of Teams Admin Center. This will thereafter enable the device to show up properly under the "Teams Rooms on Windows" section and enable accurate device management.
+
+1. **Navigate to Teams Admin Center**:
+   - Open your web browser and go to the [Teams Admin Center](https://admin.teams.microsoft.com).
+   - Sign in with your admin credentials.
+2. **Access the Surface Hubs (Legacy) Tab**:
+   - In the Teams Admin Center, select  **Teams devices** > **Surface Hubs (Legacy)**.
+3. **Manually remove the upgraded device**:
+   - Locate the row corresponding to the upgraded Surface Hub device and select the device.
+   - Select **Remove** to manually remove the device's row from the list.
+4. **Verification**:
+   - Refresh the page or navigate away and then back to the **Surface Hubs (Legacy)** tab to ensure that the device has been successfully removed.
+   - Verify that the upgraded device is now correctly managed under the appropriate tab for Teams Rooms devices, if applicable. This may take up to 12 hours to happen, but will happen automatically.
+
+### Manual cleanup of stale Intune device records for upgraded Surface Hub devices
+
+If you registered a Surface Hub 2S with Intune or other MDM provider before upgrading it with a Surface Hub 3 Compute Cartridge, you might encounter a "stale" device record. This situation occurs when the original device object in Intune remains, even after a new record is created for the Teams Rooms platform.
+
+Although this stale record doesn't interfere with Intune-based management of the upgraded Surface Hub device, we recommend removal of these outdated entries to maintain directory cleanliness.
+
+1. **Access** [Microsoft Intune Admin Center](https://intune.microsoft.com/): Sign in with your admin credentials.
+2. **Navigate to Devices**: Use the left-hand navigation pane and select the **Devices** tab.
+3. **Locate All Devices**: Within the **Overview** section, select **All devices** to view the entire list of managed devices.
+4. **Identify and select the stale device object**: Look for the device object that needs removal. You can identify the stale entry based on your established device naming conventions. Typically, the stale record displays an OS build number of 19045, indicative of the Windows 10 Team edition.
+
+   > [!NOTE]
+   > Pay close attention to the OS build numbers to accurately distinguish between pre-upgrade and post-upgrade device records.
+
+5. **Delete the stale record**: On the selected device object’s page, navigate to the top menu and select **Delete** to remove the stale device record from Intune.
 
 ## Surface Hub 2S Recycle Program
 
-The Surface Hub 3 Compute Cartridge packaging allows you to return your old Surface Hub 2S cartridge to Microsoft for recycling. To participate, [remove the hard drive](#required-removal-of-hard-drive--corporate-data) from the cartridge to protect your sensitive data and [request a pre-paid shipping label](#request-a-pre-paid-shipping-label). 
+The Surface Hub 3 Compute Cartridge packaging allows you to return your old Surface Hub 2S cartridge to Microsoft for recycling. To participate, [remove the hard drive](#required-removal-of-hard-drive--corporate-data) from the cartridge to protect your sensitive data and [request a prepaid shipping label](#request-a-prepaid-shipping-label). 
 
 ### Required removal of hard drive & corporate data
 
 Before recycling your Surface Hub 2S cartridge, first remove the hard drive and delete any corporate data.
 
-1. You'll need the compute cartridge and a screwdriver.
+1. You need the compute cartridge and a screwdriver.
 
 ![Screenshot that shows compute cartridge and screwdriver.](images/surface-hub-2s-repack-7.png)
 
 2. Remove the cover screw and the cover from the compute cartridge and then remove the solid state drive (SSD).
 
 ![Screenshot that shows removal of cover screw and cover from the compute cartridge and removal of solid state drive (SSD).](images/surface-hub-2s-repack-8.png)
 
-### Request a pre-paid shipping label
+### Request a prepaid shipping label
 
 Select your country/region and follow the instructions to obtain a shipping label. If you upgraded to the Surface Hub 3 Compute Cartridge, you can use its original packaging to ship the Surface Hub 2S cartridge for recycling. 
 

surface-hub/surface-hub-2s-migrate-to-mtr-w.md

@@ -25,7 +25,7 @@ Begin the migration process via the downloadable **Surface Hub 2S OS Migration L
 > The Migration Launcher app is available exclusively to facilitate migration of Surface Hub 2S devices from the Windows 10 Team edition operating system to the Microsoft Teams Rooms on Windows experience. The presence of this app triggers the migration process under specific [prerequisite conditions](#prerequisites) and the app itself has no functionality or user interface.
 
 > [!TIP]
-> Customers can take advantage of streamlined remotely driven deployment after migrating their Surface Hub 2S devices to the Microsoft Teams on Windows platform. As announced at [Enterprise Connect 2024](https://techcommunity.microsoft.com/t5/surface-it-pro-blog/surface-hub-support-coming-for-windows-autopilot/ba-p/3977848), support for Windows Autopilot and Auto-login of Teams Rooms on Windows is now broadly available in Public Preview. Learn more in [Deploy Surface Hub with Windows Autopilot & Auto-login of Teams Rooms](surface-hub-autopilot.md).
+> Customers can take advantage of streamlined remotely driven deployment after migrating their Surface Hub 2S devices to the Microsoft Teams on Windows platform. As announced at [Enterprise Connect 2024](https://techcommunity.microsoft.com/t5/surface-it-pro-blog/surface-hub-support-coming-for-windows-autopilot/ba-p/3977848), support for Windows Autopilot and Autologin of Teams Rooms on Windows is now broadly available in Public Preview. Learn more in [Deploy Surface Hub with Windows Autopilot & Autologin of Teams Rooms](surface-hub-autopilot.md).
 
 ### Migration Launcher app deletes OS and data
 
@@ -35,7 +35,7 @@ Begin the migration process via the downloadable **Surface Hub 2S OS Migration L
 Use of the Migration Launcher app on Surface Hub 2S involves significant changes to the operating system and stored data. Here are key points to understand before proceeding with the migration process:
 
 - **Removes the Windows 10 Team edition OS:** Migration completely eliminates the Windows 10 Team edition operating system preinstalled on the Surface Hub 2S.
-- **Requires consent for data and configuration removal:** By installing and initiating the Migration Launcher app on a Surface Hub 2S, you agree to the complete removal of the Windows 10 Team edition OS. This includes uninstalling and erasing all accounts, data, and existing configurations.
+- **Requires consent for data and configuration removal:** By installing and initiating the Migration Launcher app on a Surface Hub 2S, you agree to the complete removal of the Windows 10 Team edition OS. This process includes uninstalling and erasing all accounts, data, and existing configurations.
 - **Excludes first-generation Surface Hubs:** The Microsoft Teams Rooms on Windows experience and the Migration Launcher app don't support or affect first-generation Surface Hubs (Surface Hub v1).
 - **Requires significant download and storage space:** The migration process necessitates downloading approximately 30 GB of data and needs sufficient on-system storage to establish a temporary partition.
 - **Increases energy consumption:** Switching to the Microsoft Teams Rooms on Windows experience leads to higher energy usage due to adjustments in sleep state and power management settings.
@@ -68,14 +68,14 @@ Use of the Migration Launcher app on Surface Hub 2S involves significant changes
 > [!NOTE]
 > Support for Windows 10 Team edition on Surface Hub, based on Windows 10 version 22H2, is scheduled to end on October 14, 2025.
 
-## Optional: Streamline post-migration deployment with Windows Autopilot and Teams Rooms Auto-Login
+## Optional: Streamline post-migration deployment with Windows Autopilot and Teams Rooms Autologin
 
-Whether you initiate the migration process manually on a Surface Hub 2S or remotely via Intune, it's advantageous to set the stage for the device to autonomously complete its deployment post-migration, utilizing Windows Autopilot in conjunction with Auto-Login of Teams Rooms. This approach is particularly beneficial for customers triggering migration remotely, as it facilitates a fully remote, end-to-end process spanning migration to the Teams Rooms on Windows experience to the subsequent deployment within your organization.
+Whether you initiate the migration process manually on a Surface Hub 2S or remotely via Intune, it's advantageous to set the stage for the device to autonomously complete its deployment post-migration, utilizing Windows Autopilot in conjunction with Autologin of Teams Rooms. This approach is beneficial for customers triggering migration remotely, as it facilitates a fully remote, end-to-end process spanning migration to the Teams Rooms on Windows experience to the subsequent deployment within your organization.
 
-For detailed guidance on enrolling your Surface Hub in Autopilot and Auto-login of Teams Rooms, see [Deploy Surface Hub with Windows Autopilot & Auto-login of Teams Rooms](surface-hub-autopilot.md).
+For detailed guidance on enrolling your Surface Hub in Autopilot and Autologin of Teams Rooms, see [Deploy Surface Hub with Windows Autopilot & Autologin of Teams Rooms](surface-hub-autopilot.md).
 
 > [!TIP]
-> For an optimal experience, it's recommended to configure Autopilot and Auto-login of Teams Rooms before starting the migration process. This preparation ensures that seamless deployment is primed and ready to begin when migration is complete.
+> For an optimal experience, it's recommended to configure Autopilot and Autologin of Teams Rooms before starting the migration process. This preparation ensures that seamless deployment is primed and ready to begin when migration is complete.
 
 ## Install Migration Launcher app to trigger a migration
 
@@ -105,7 +105,7 @@ Choose one of the following options:
 ## Remotely install Migration Launcher app via Intune
 
 > [!TIP]
-> If you are remotely triggering migration with the following steps, you may wish to consider setting up seamless post-migration deployment as well. To learn more, see the earlier section on this page: [Streamline post-migration deployment with Windows Autopilot and Teams Rooms Auto-Login](#optional-streamline-post-migration-deployment-with-windows-autopilot-and-teams-rooms-auto-login).
+> If you are remotely triggering migration with the following steps, you may wish to consider setting up seamless post-migration deployment as well. To learn more, see the earlier section on this page: [Streamline post-migration deployment with Windows Autopilot and Teams Rooms Autologin](#optional-streamline-post-migration-deployment-with-windows-autopilot-and-teams-rooms-autologin)
 
 ### Summary
 
@@ -238,7 +238,9 @@ After migrating your Surface Hub 2S to the Microsoft Teams Rooms on Windows plat
 
 ## Manual cleanup of stale Intune device objects for migrated Surface Hub devices
 
-If you've previously registered a Surface Hub 2S in Intune before transitioning it to the Microsoft Teams Rooms on Windows platform, you'll likely encounter what's referred to as a "stale" device record. This occurs when the original device object in Intune remains unchanged, even as a new device record is generated post-migration to the Teams Rooms platform. Although this stale record does not interfere with the Intune-based management of the now-migrated device, it's advisable to remove these outdated entries to maintain optimal directory cleanliness.
+If you registered a Surface Hub 2S with Intune before transitioning it to the Microsoft Teams Rooms on Windows platform, you might encounter a "stale" device record. This situation occurs when the original device object in Intune remains unchanged, even after a new record is created for the Teams Rooms platform.
+
+Although this stale record doesn't interfere with Intune-based management of the migrated Surface Hub device, we recommend removal of these outdated entries to maintain directory cleanliness.
 
 1. **Access** [Microsoft Intune Admin Center](https://intune.microsoft.com/): Sign in with your admin credentials.
 2. **Navigate to Devices**: Use the left-hand navigation pane and select the **Devices** tab.