Windows 11 22H2 is almost here. Is it ready for the enterprise?
- Reference: 1655980029
- News link: https://www.theregister.co.uk/2022/06/23/windows_11_22h2_is_almost/
- Source link:
[1]Windows 11 launched in October 2021 with some controversial changes. The first was a considerably reduced list of compatible hardware (compared to its predecessor, Windows 10). The second was a redesigned user interface that seemed pretty much guaranteed to enrage customers still smarting from the Start Menu fiasco of Windows 8 and 8.1.
But hey, the window corners were rounded (sometimes) and you didn't really care about the fact that a right-click on the taskbar no longer gave a task manager options, did you?
[2]
It is fair to say that the operating system has not been a roaring success for Microsoft (as [3]evidenced by OS usage stats – despite the company bravely insisting the uptake has been excellent), but it is early days and enterprises were always likely to steer clear until the first major update (even without the draconian hardware requirements, which rendered large portions of companies' existing hardware fleets obsolete).
Windows 11 in detail: Incremental upgrade spoilt by onerous system requirements and usability mis-steps [4]READ MORE
With the shift of the code to the Release Preview channel of the Windows Insider program, and its arrival on Windows Update for Business, a release is looming. The question is, considering Microsoft's drip-feeding of minor updates since release: What is new this time around?
The good news, for enterprises at least, is that the answer is not that much. At least, not much that is likely to frighten the horses. However, that means there is also not much to tempt the holdouts.
Start Menu
While the hardware requirements (for a recent CPU and TPM hardware) remain in place, despite a [5]slightly embarrassing emission earlier this month where it appears somebody at the company's Redmond HQ forgot to switch on the CPU check, the controversial new Start Menu has been updated. Apps can now be pinned into folders and it is possible to see either more apps or stick with the recommendation view.
[6]
`Folders in the Start Menu (Click to enlarge)
Unfortunately, functionality taken for granted by Windows 10 fans remains missing in action: dragging and dropping remains severely limited and third party options (such as [7]Stardock's Start11 ) are needed to restore some of what Microsoft has decided you don't need in Windows 11.
The upshot for enterprises is that users will still need retraining before venturing near the user interface – for reasons known only to Microsoft.
[8]
[9]
As well as updates to the Start Menu itself, Microsoft has also added some gestures for touchscreen users – swipe up to display the start menu, swipe left to show all apps and swipe right to return to pinned apps. It's an improvement, but all feels like window-dressing compared to the complaints of users missing the days of Windows 10.
Other user interface changes include window snapping improvements and something distinctly cosmetic in the form of a volume control to dispense with some of the last vestiges of the Windows 8 era.
Energy efficiency
The Windows team has already overhauled the veteran [10]Task Manager application (the changes are mostly cosmetic), although the efficiency mode that can be turned on for processes will be of interest to administrators looking ways of conserving energy without resorting to actually suspending background processes.
Similarly, Windows 11 22H2 will also try to install its updates when the local electricity supply is coming from renewable sources, assuming it has access to data feeds with that information. From an enterprise standpoint, one would hope that an administrator has an organization's fleet under sufficient control.
Security
One of Microsoft's justifications for its hardware compatibility list was security, and lurking in Windows 11 is [11]Smart App Control to stop users running untrusted or unsigned applications (although you'll need a fresh install of Windows 11 to use it – after all, an existing install could already be compromised) and an improved Windows Sandbox with ARM64 support.
Perhaps more significant on the security front is the final stripping away of SMB1 support (the Home edition is the last to have the protocol removed.) Sure, administrators can pop support back into the platform, but this is likely as good an excuse as any to finally rid an organization of devices that still depend on it.
[12]
Slightly more worrying for consumers, however, is that users will require a Microsoft account in order to set up a Windows 11 system. Enterprises and schools will not be affected (since users will already have an account with their organizations) but the change could come as a shock for users accustomed to running locally.
[13]Apple update approach 'not realistic' in enterprise, but login 'shim' gets thumbsup
[14]Microsoft readies Windows Autopatch to free admins from dealing with its fixes
[15]If you're using older, vulnerable Cisco small biz routers, throw them out
[16]Open source 'Office' options keep Microsoft running faster than ever
[17]What if ransomware evolved to hit IoT in the enterprise?
Other useful tweaks in the security administration arena include some new Mobile Device Management (MDM) policies to further control devices, as well as support for [18]Discovery of Designated Resolvers (DDR.)
Accessibility
Finally, there are improvements both in the Narrator (with new voices for the text to speech) and Live Captions, to caption audio coming out of the PC; handy not just for those hearing disabilities, but anyone struggling to focus on audio (although the functionality is English-only for the time being).
Microsoft has not confirmed the arrival date for the second coming of Windows 11. The release is not the big bang of some versions, a reflection of the update mechanism for Windows 11, but still irons out some of the rougher edges.
Administrators have been given more control over the operating system, but for organizations looking at the looming cut-off for Windows 10 support, some training is still going to be required – as well as an explanation for why what might have worked in Windows 10 doesn't work in Windows 11.
And the team at Redmond may not yet be done. A refreshed [19]File Explorer – replete with tabs – recently turned up in the Windows Insider Beta Channel (although has yet to make it as far as Release Preview.)
[20]
Coming soon to Windows 11? (Click to enlarge)
Ultimately, Windows 11 22H2 is likely to be the version that enterprises sticking with the Windows world will adopt. The operating system has had a year in which to stabilize and pretty much any new device will be able to run it without falling at Microsoft's hardware hurdles. And, perhaps most importantly, there is little to cause alarm (at least, not since the initial release.)
Which is, lets face it, just how administrators like it. ®
Get our [21]Tech Resources
[1] https://www.theregister.com/2021/10/05/windows_11/
[2] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/oses&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=2&c=2YrSOJhT9Rm-hnFBHN2mvnAAAAIQ&t=ct%3Dns%26unitnum%3D2%26raptor%3Dcondor%26pos%3Dtop%26test%3D0
[3] https://www.theregister.com/2022/04/28/adduplex_windows_11/
[4] https://www.theregister.com/2021/10/05/windows_11_in_detail/
[5] https://www.theregister.com/2022/06/09/windows_11_requirements/
[6] https://regmedia.co.uk/2022/06/22/windows_11_start_menu_folders.jpg
[7] https://www.theregister.com/2022/01/26/openshell_windows_11/
[8] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/oses&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44YrSOJhT9Rm-hnFBHN2mvnAAAAIQ&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0
[9] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/oses&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=3&c=33YrSOJhT9Rm-hnFBHN2mvnAAAAIQ&t=ct%3Dns%26unitnum%3D3%26raptor%3Deagle%26pos%3Dmid%26test%3D0
[10] https://www.theregister.com/2022/06/10/microsoft_tabs_file_explorer/
[11] https://www.microsoft.com/security/blog/2022/04/05/new-security-features-for-windows-11-will-help-protect-hybrid-work/
[12] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/oses&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44YrSOJhT9Rm-hnFBHN2mvnAAAAIQ&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0
[13] https://www.theregister.com/2022/06/20/jumpcloud_survey/
[14] https://www.theregister.com/2022/06/17/autopatch/
[15] https://www.theregister.com/2022/06/16/cisco_critical_patches/
[16] https://www.theregister.com/2022/06/13/open_source_office_suites/
[17] https://www.theregister.com/2022/06/01/ransomware_iot_devices/
[18] https://techcommunity.microsoft.com/t5/networking-blog/making-doh-discoverable-introducing-ddr/ba-p/2887289
[19] https://www.theregister.com/2022/06/10/microsoft_tabs_file_explorer/
[20] https://regmedia.co.uk/2022/06/22/windows_11_file_explorer_tabs.jpg
[21] https://whitepapers.theregister.com/
Re: Local account
I knew about this with the home version, but the articule implies that it's also the case with the pro / enterprise versions in the new release. Can anyone confirm? A very bad idea if so - there are a number of circumstances where I need to set up work computers with local accounts.
Re: Local account
I have just this week had to rebuild a machine, so clean install from media, not an upgrade, and wasn't given the option to have a local account. We do all have 'windows' accounts, but it's a pain having to link new devices to a 365 account, before you can join it to the domain, instead of just using a local account.
We are in the process of deploying a load of new hardware anyway, as it is time for a refresh, (laptops and some desktops), so we are taking advantage of that to phase a rollout of 11.
So far, very few issues. Some of our users are extremely technophobic, and many of them haven't even noticed the change, so I'm not sure what kind of people the article is expecting to need to retrain to use a slightly different GUI.
The biggest annoyance for us so far has been that 11 was delivered as an 'update' so the users are able to do it without our interaction. Fortunately very few have (so far).
Re: Local account
Is this the current pro / enerprise version of W11? If so then there definitely is an option, although they make it difficult to find!
We manage most of our computers through either WSUS or Intune, both of which allow us to hold the machines at W10 and the W11 update isn't offered. There are a few standalone ones, but fortunately most of them don't meet the W11 hardware requirements!
Re: Local account
Is there any point reminding them that despite not liking Microsoft's decision - you haven't gone away.
I haven't heard of any major enterprises jumping ship so they can continue to use their existing hardware fleet. The message to Microsoft is they can upset you in so many ways for there own benefit without losing market - except, perhaps against ChromeOS in education.
Enterprises escaping the Microsoft trap is hard and expensive in the short term. Probably harder and more expensive as time goes by. Few will take the certain pain now for any future benefit elsewhere.
Significant shift in Windows share of the corporate desktop will only come when new disruptors with no Windows heritage grow to become significant global corporations. But then these will probably be using server AI apps to displace the need for any wetware driven desktop. Hence windows can maintain its share of a declining market while trying to grab that cloud based server market to maintain and even enhance revenues.
Re: Local account
Can't say for sure if this will go away in the update, but at least on the current Win11, you can create a local user once you've installed and then just ignore the other account, or use it as the backup admin account. It's an extra couple of steps, but if you're already ripping out the ethernet cable, you're clearly motivated enough to do this.
MS dropping peripherals support - AGAIN
They've B***DY gone and done it again!
My move to Linux a decade ago was triggered by MS dropping support for (1) a large format - 1.5 metre roll feed - technical drawing printer which we used for CAD output, AND, simultaneously, (2) my personal Minolta 35 mm film scanner. Neither were supported in a Win 8 environment, but, believe it or not, both worked still perfectly in an Ubuntu environment, with the manufacturers producing Linux drivers. We were talking about £ 000s of kit here, not something to be casually replaced.
About 3 years ago (I'm now retired) my Minolta scanner died, and after some research I replaced it with an Epson V600 - not quite as good as the Minolta for film scanning, but still good enough for my needs, and properly supported by Epson with Linux drivers (plus Vuescan for Linux systems as well). I still work with an ex-colleague who also uses a V600, but in a Win 10 environment. He has just been told that the Win 11 upgrade he is being pushed to install will NOT support his Epson scanner. "advice" is to get a new machine that Win 11 will play nice with - at least £650! What are MS playing at? This is modern kit, not a relic of the dark ages.
We have arranged a visit when I will see just how much of his kit will play nice in Linux - it is all looking good on paper so far - and will probably end up with me moving him onto Mint 20.3.
It is bad enough having MS trying to "own" your whole machine, but he is determined to make sure that they do not get to own his whole budget as well!
Re: MS dropping peripherals support - AGAIN
Kinda sounds like the device maker stopped updating their drivers for Windows. For you the end result is the same, but it's not really something Microsoft has control over. You can yell and scream at Microsoft all day, but it's kind of like yelling at a goldfish for losing a foot race.
Re: MS dropping peripherals support - AGAIN
"but it's not really something Microsoft has control over"
Depends on whether or not the problem is caused by changes MS have made to the way drivers interact with the system - in theory, so long as you can still physically connect the peripheral to the PC, then it ought to be possible to continue using the original drivers to drive said peripheral so long as the OS lets you, because the hardware hasn't changed, the original drivers haven't changed, so the only thing left that could change and break stuff is the OS. At which point the ball would very definitely be back in MS's court.
Problems can also arise due to MS messing around with how Windows deals with new devices when they're first connected, which can make it harder than it ought to be to even attempt to install older drivers - when I tried connecting my old Canon Pixma inkjet to my new W11 laptop, as soon as I plugged in the USB cable (noting that at this point I hadn't tried to pre-install any of the old Canon drivers I still had lying around), 11 was automatically enumerating it as being something other than a printer rather than simply deciding, as it ought to have done, that it actually had no idea what it was I'd plugged in and leaving it listed as an unknown device in need of manual driver installation. You know, a bit like how older versions of Windows used to behave when new stuff got connected. Again, that's on MS and MS alone.
"users will still need retraining before venturing near the user interface – for reasons known only to Microsoft"
It's not just MS - this is a recurring theme with many UI redesigns across a variety of products from different companies. Seems to be a case of UI designers in general not being content until they've changed things sufficiently that the users *have* to pay attention to the changes one way or another, rather than simply continuing to use the new UI without giving it a second thought...
*scene cross-fades to a design studio somewhere in central London*
"I say Tarquin, the latest focus group study shows our users are able to navigate the new UI almost as quickly as the old one, am I reading this report correctly?"
"I know Lavinia, I know, something's gone terribly wrong here, what can we do to make their lives miserable again?"
"What ho Tarqs, Lavvie, wouldn't it be a splendid wheeze if we, you know, just move *everything*?"
"And change the colours to be less contrasty whilst we're at it?"
"What about removing some of the visual cues users rely on to know which parts of the UI can be interacted with?"
"My god, I think we've got it! Quick, get those changes pushed into production - no, skip the test phase, this is TOO important to delay - and away to the wine bar we go for a celebratory drinkie-poos"
*credits roll*
Yes yes, I know, hideous stereotyping of graphics design people there. But you know what, after suffering the effects of their handiwork in various products I use on a daily basis over the past few years, my ability to be nice to them is practically exhausted, and I now regard them as fair game for whatever levels of ridicule and scorn get thrown their way by users fed up beyond our capacity to cope as we struggle with UI design changes that offer so much less than they take away.
WTF?
Similarly, Windows 11 22H2 will also try to install its updates when the local electricity supply is coming from renewable sources, assuming it has access to data feeds with that information.
So of all the potential improvements possible for an MS OS, it wasted carbon on virtue signalling?
It's a huge assumption given AFAIK that information doesn't exist, and there aren't really any plans (other than maybe marketing) to supply that data. 'Smart' meters don't do it, they're just there to allow 'demand management'.
Even if the data were available, it'd lead to interesting situations. So-
http://www.gridwatch.templar.co.uk/index.php
Wind has been low due to the err.. weather. So MS issues a critical update, power manager sees you're running on gas, and postpones the update. On the other hand, I guess MS could collect a lot of detailed power supply and usage data. Given the current energy crisis, that could be rather valuable.
I'm committed either way
I just got a shiny new 12th Gen i7 system, so I'm committed to the Win11 ecosystem like it or not. I'd probably see a pretty significant performance decrease and lose access to the primary selling point of the 12th gen Core chips. Guess it's a good thing I really don't mind most of the changes to Win11. I actually like some of the file manager changes, like putting cut/copy/paste/delete functions as easier to access buttons at the top of the right-click menu. I wish they'd add the functionality for it to remember which virtual desktop it was on when being restored, but I only tend to reboot to install updates, so minor annoyance. The rest doesn't really bother me. I was using the Ctrl-Shift-Esc keyboard shortcut to get the task manager for so long I never even noticed the option in the taskbar until seeing El Reg mention it. I almost never use the start menu, having trained myself to use the search function which has come a long ways since Win8. A lot of people might be happier pinning Windows Tools to their start menu.
What I want to see more of, however, is Microsoft ripping out elements that have been around since the NT 3.1 days and put in native WinUI 3 replacements. I'm not a fan of the current visual style, but once you have everything running on the same graphics API you could add in functionality akin to GTK+ themes to change the visual appearance without messing with underlying functionality.
What is it with people ?
Rather than move to another platform, they stay with the one they dislike and think whining and wishing it better will make it so.
Almost the same way people would rather vote Tory in the hope they change than prompt the change by voting for someone ( anyone !!!) else.
Local account
"Slightly more worrying for consumers, however, is that users will require a Microsoft account in order to set up a Windows 11 system."
A workaround that once worked, no longer works for 11 Home. My workaround was after the first restart to disconnect the ethernet cable; if you had WiFi only, do not check the box to automatically connect. Being the morally bankrupt people that they are, Microsoft took that away in 11 Home. Still haven't tested it in 11 Pro. Still, the "net user" commands still work to create a local account.
I suggest everyone here continually send Microsoft negative feedback about forcing people to use a Microsoft account. I repeatedly do this, and always say it is high priority. Furthermore, I do not use language that would cause it to go straight to the bin. But I do make it a strong point to tell them how morally wrong this is, and there is no ethical justification for it. All of need to spam Microsoft's feedback about this.