Merging changes synced from https://github.com/MicrosoftDocs/Devices-…

…docs-pr (branch live)

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

@@ -49,8 +49,9 @@ Use of the Migration Launcher app on Surface Hub 2S involves significant changes
 - If you're unable to check for Windows updates locally (for example, in remote admin scenarios), you can verify the OS version via Microsoft Intune admin center or other mobile device management (MDM) solutions.
 - You can also check by validating that Windows 10 [*OS Build 19045.4123*](https://support.microsoft.com/help/5034843) or later is present on the system.
 - Validate that your network can handle a **30 GB download**.
-- Ensure the network you're using doesn't have any other firewalls, blockages, or limitations that would otherwise prevent the download and installation of software onto the Surface Hub 2S devices you intend to migrate.
-- Confirm IT allows network access to required sites: ***.devices.microsoft.com** and **download.microsoft.com**. On a separate PC, open a command prompt and enter the following commands:
+- Ensure the network you're using doesn't have any other firewalls, blocks, or limitations that would otherwise prevent the download and installation of software onto the Surface Hub 2S devices you intend to migrate.
+    - After migration, **\*.sls.microsoft.com**, **\*.mp.microsoft.com**, **crl.microsoft.com**, and **`www.microsoft.com/pki/*`** need to be accessible for the devices to activate properly.
+- Confirm IT allows network access to required sites: **\*.devices.microsoft.com** and **download.microsoft.com**. On a separate PC, you can open a command prompt and enter the following commands:
 
     ```cmd
     ping devices.microsoft.com
@@ -288,13 +289,13 @@ When overseeing the migration process on Surface Hub 2S, pay attention to specif
 | **Event ID 6: OS migration process started**             | This event is logged as the first step after the Monitor Service verifies the app's presence and the UEFI version. It signifies the start of the migration process.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
 | **Event ID 7: Failed to verify migration app signature for OS migration** | In a migration, Windows checks the digital signature of the **Surface Hub 2S OS Migration Launcher - Microsoft Teams Rooms** app. Causes of this error include corrupted system files, an outdated or corrupted certificate store, or network issues (if the verification process involves checking with an online certificate authority). To address this problem:<br>- Ensure your current version of Windows is up to date with all the latest patches and updates, as described in the [Prerequisites section](#prerequisites) of this page.<br>- Ensure your internet connection is stable, as the verification process might require contacting external servers. |
 | **Event ID 8: UEFI firmware not updated to support OS migration**| - Confirm that the UEFI version is **699.845.768.0** or later, as described in the [Prerequisites section](#prerequisites) of this page. <br> You can verify the UEFI version via the **Surface app**.|
-| **Event ID 9: Disk space is insufficient for OS migration** | Migration requires a minimum of 30 GB of free space. If this event occurs, delete unnecessary files, uninstall unused applications, or move data to an external storage device.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| **Event ID 9: Disk space is insufficient for OS migration** | Migration requires a minimum of 30 GB of free space. If this event occurs, [use the Teams Rooms on Windows recovery image](#error-during-migration) to complete the migration. |
 | **Event ID 10: OS image download failed**                | If this event occurs, the system attempts the download again. This can lead to a sequence of Event ID 6 followed by Event ID 10 if the issue persists.<br><br>**Common causes:**<br>     - Inability to access the download site.<br>- Connection drops during download, exhausting all retry attempts.<br>- Insufficient disk space or inaccessible file location for the download.<br><br>**Additional notes:**<br>- The system checks for sufficient disk space and the creation of the migration partition at every boot. It fails to download if conditions aren't met.<br>     - Be aware of timing issues. If the download isn't complete before a scheduled or manual reboot, the download restarts, potentially leading to prolonged migration. |
 | **Event ID 11: MTR license key retrieval failed**        | This event occurs after repartitioning and downloading the OS image. If the OS image download isn't successful, the system fails to proceed to the key retrieval stage. |
 
 ### Error during migration
 
-If you encountered a WinPE invalid path error (directing you to this page) during the migration process, you will need to follow the [instructions for manual recovery](surface-hub-recover-reset.md) to complete the migration to the Microsoft Teams Rooms on Windows platform. At that point in the process your Hub 2S is ready to be re-imaged with the **Windows 11 IoT Enterprise with the Microsoft Teams Rooms on Windows experience** recovery image as described in the [Recovery from a USB drive steps](surface-hub-recover-reset.md#recovery-from-a-usb-drive).
+If you encountered a WinPE invalid path error (directing you to this page) during the migration process, or if you encountered Event ID 9 ("Disk space is insufficient"), please follow the [instructions for manual recovery](surface-hub-recover-reset.md) to complete the migration to the Microsoft Teams Rooms on Windows platform. At that point in the process your Hub 2S is ready to be re-imaged with the **Windows 11 IoT Enterprise with the Microsoft Teams Rooms on Windows experience** recovery image as described in the [Recovery from a USB drive steps](surface-hub-recover-reset.md#recovery-from-a-usb-drive).
 
 ## Best practices for a smooth migration