[On demand] Windows 10 EOS: Myths, misconceptions, and FAQs
Support for Windows 10 and other Microsoft products will end on October 14, 2025. Get tips to help you prepare your organization to navigate these milestones. Watch Windows 10 EOS: Myths, misconceptions, and FAQs – now on demand – and join the conversation at https://aka.ms/EndOfSupportFAQs. To help you learn more, here are the links referenced in the session: Products affected by End of Support in 2025 Windows 10 (Non-LTSC) Office 2016 | 2019 Exchange Server 2016 | 2019 Visio 2016 | 2019 Project 2016 | 2019 Skype for Business Server 2015 | 2019 Also, monitor Windows Release Health, for updated information as it becomes available. Leverage Day 1 with Windows 11: A Quick Tour to inform your users on how to get the most out of their new Windows 11 desktop Where to start with your Windows 10 upgrade Windows deployment documentation | Microsoft Learn If you qualify for FastTrack benefits, our FastTrack resources can help you in your journey For more free technical skilling on the latest in Windows, Windows in the cloud, and Microsoft Intune, view the full Microsoft Technical Takeoff session list.
Outlook 365: Duplicate conference room names showing under locations
We recently changed our conference room names and since that time, we've noticed that some of our users are seeing multiple entries for conference rooms. When the users attempt to select the room on the location tab or required tab, they are seeing duplicates of the same rooms. This is only happening when the users are selecting the room from the location tab. If they go to Room Finder, there is only one instance of the room. The issue of course is that most people just use location and do not go into Room Finder as it creates an extra step. I have looked at multiple sites on this and the solution they quote involves changing the registry, but we don't have the registry option that these solutions point out. We also don't want to have to manually do a registry change for every individual having this issue. Has anyone come across this and if so, how did you resolve it? one more thing, we are also experiencing this in Outlook web.Windows 10 21H2 and Windows 11 21H2 both show up as "2009" release
I'm not real sure where to post this, so will try here. I have noticed that for both Windows 10 - 21H2 and Windows 11 - 21H2, the "ReleaseID" value in the Registry is incorrectly shown as "2009". (We are using Windows 10/11 Enterprise.) This is located at this key in the registry: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion We rely on inventorying this value to determine which computers have which "Feature Update" installed, and therefore, which computers we still need to update. Has Microsoft migrated away from using this value to indicate which Feature Update is installed? Do we need to change our approach to look at the "DisplayVersion" instead of the "ReleaseID"? Or some other value in the registry? Also, Windows 11 has another issue. In the same registry key location, the "ProductName" value is listed as "Windows 10 Enterprise", which of course is incorrect. Are others seeing these same results with these items? Anyone heard if Microsoft has plans to fix these issues?
