[Windows XP 2003 EXPerience Edition October 2011 64 Bit
Luther Lazaro
We know the important role your PC plays every day for hybrid work, learning, entertainment and gaming, and we are committed to supporting our customers using Windows 10. Today, we are announcing the availability of the Windows 10 2022 Update (also known as Windows 10, version 22H2). Based on customer feedback we are providing a limited scope of new features and functionality delivered via a familiar, fast and reliable update experience. Version 22H2 will continue the recent Windows 10 feature update trend of being delivered in an optimized way using servicing technology.
I have consistently noted that being on the latest version of Windows provides you with the latest features, security improvements and control. We recommend that you update your devices to the latest version of Windows 10 or upgrade eligible devices to Windows 11.
As a reminder, all editions of Windows 10, version 21H1 will reach the end of servicing on Dec. 13, 2022, and we will start initiating updates to the 2022 Update for these devices later this month[2]. Enterprise and Education editions of Windows 10, version 20H2 will reach end of servicing on May 9, 2023. After these dates, devices running versions 20H2 and 21H1 will no longer receive monthly security and quality updates containing protections from the latest security threats.
If you have a Surface Hub 2S, you can migrate it to run the Microsoft Teams Rooms on Windows experience. This enables Surface Hub 2S devices to run the same Windows 11 software platform shipping on new Surface Hub 3 devices.
Begin the migration process via the downloadable Surface Hub 2S OS Migration Launcher - Microsoft Teams Rooms app, which you can install directly on a Surface Hub 2S or remotely via Microsoft Intune or other cloud management tools.
The Migration Launcher app is designed exclusively for Surface Hub 2S devices transitioning from the Windows 10 Team edition operating system to the Microsoft Teams Rooms on Windows experience. It triggers the migration process under specific prerequisite conditions and has no other functionality or user interface.
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, 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.
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:
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.
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 line or console and enter the following commands:
Alternatively, if you don't wish to migrate your Surface Hub 2S, you can purchase the Surface Hub 3 Pack compute cartridge, which lets you swap out your existing Surface Hub 2S cartridge and instantly convert your Surface Hub 2S to a Surface Hub 3. To learn more, see Install and manage Surface Hub 3 Pack.
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.
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.
Once you see the Migration Launcher in the app list, the migration proceeds automatically upon restarting the Windows 10 Team edition OS. You can either manually restart Surface Hub 2S or wait until the system automatically restarts during the default nightly maintenance window.
After this initial restart, do not interfere with the system; even though it may appear nothing is happening and you still see the same experience, the migration proceeds independently after completing all necessary backend processes (including downloading and unzipping the new Teams Rooms on Windows image).
Typical migration time is around 90 minutes from restart after installing the Migration Launcher app, but the length can vary depending on many characteristics, including customer network bandwidth and related factors.
When migration is complete, the device displays the Windows first-time setup program, also known as Out of the Box Experience (OOBE). To learn more, see First-time setup for Surface Hub running Microsoft Teams Rooms on Windows.
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.
Any devices in the group targeted for Migration Launcher app deployment are migrated as soon as the app has deployed. To avoid unintended behavior, we recommend against using Dynamic Groups, and we encourage you to validate that only your intended devices are included in the group you selected.
After you select Manage, the page listing for the Migration Launcher app is displayed. Wait a few moments for the spinner to complete and the Download portion of the resulting page to appear.
Select Dependency app files and choose the blue folder icon to select and upload all three dependencies. The inventory of required files displays a green check box to indicate that you have all the required files uploaded.
Several factors contribute to how long it takes for the app to finish deployment and installation on the target devices, including device power/sleep state, sync cadence/status with Intune, and related factors. Continue to monitor Intune status for indications of successful app deployment.
Once the app is deployed, the next restart initiates migration, which - in this remote deployment scenario - is likely to be the automatic restart as part of the nightly maintenance window. Similar to the manual app deployment scenario, the migration process typically takes about 90 minutes after this restart (but many factors can impact migration time, as explained earlier, with a test example exceeding 5 hours on a slower network). Customers must test and validate sequences relative to their unique infrastructure and management approaches.
If you configured seamless deployment with Autopilot, the Windows first-time setup program automatically proceeds according to the Autopilot configuration you've established. Once complete, you can see the device registered in Intune and appearing online in the Teams Rooms Management Portal. To ensure the device is properly online and visible in the Teams Admin Center, refer to the following section.
After migrating your Surface Hub 2S to the Microsoft Teams Rooms on Windows platform, 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.
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 encounter a WinPE drive error during the migration process, you will need to follow the instructions for manual recovery 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.
When overseeing the migration process on Surface Hub 2S, pay attention to specific events logged by the SurfaceHubMonitor source. Event IDs 6-11 indicate different stages and potential failures in the migration process.
Avoid Frequent Reboots: It's important not to reboot the system unnecessarily during the migration process. Frequent reboots can restart the download process, extending the duration of the migration and potentially leading to repeated "nothing seems to be happening" scenarios. By monitoring these specific events, you can effectively track and troubleshoot the migration process of your Surface Hub 2S.
What does the assessment do that can't be done under standard (limited) user permissions?And if the action(s) that necessitate elevation were allowed to be run by a standard user without elevation, what security risks would that open up?
795a8134c1