While the original intent was doubtless noble, hearing the dulcet tones of Microsoft's unloved assistant narrating the setup process can get grating.
Pretty much before its completed the first sentence :-/
Having quietly admitted that an Internet Explorer update had taken an almighty dump in the Windows Sandbox, Microsoft emitted a fresh build of Windows 10 to fix the problem last night. Build 18309 took a bow overnight for fast ring testers and we can confirm that the Windows Sandbox is up and running once again. This is handy …
I recently had to help a person who set up a win10 laptop to sign in with a microsoft account, but then entered the wrong email address. The system let that work, for some reason, but kept asking for an email verification which couldn't happen because that address was not one the user had. Meanwhile, the system for switching the email address would not accept the real one because, according to whatever backend was put on it, that address was not available. I presume by this they meant that someone had already set up a microsoft account with it. The fact that that someone and this someone were the same person did not seem to matter. In the end, we ended up having to create the email account with the typo in it just to get the computer to shut up. So maybe someone could look into making that sign in method functional rather than trying to build what seems like the fifth sign in system for win10.
'both good and bad' - imagine your 4 character PIN number for your smartphone being the only kind of security a company's IT manager can rely on...
After all, how many people use 1234, 0000, the last 4 digits of your taxpayer ID number, or your phone number, or your birthday, or something equally easy to guess? "That's the combination I use on my luggage" "And change the combination on my luggage" (Hail Skroob!)
However, the potential is good as long as there can be 3rd party applications with security token storage that can manage it. I do not want to rely on Micro-shaft slurpware phone applications to do this kind of thing, with hidden "features" that phone home to Redmond. I've been concerned about the whole 'Micro-shaft Logon' thing from its inception, because it automatically has a unique identifier for YOU out on "the cloud", and Micro-shaft already admits in their EULA that they can share that information, and I don't know of any way to STOP them.
But if a 3rd party application, say one WRITTEN BY THE COMPANY, can be use to provide a secure login on any Windows computer in the company, it would be VERY useful for IT managers, wouldn't it?
(I'd consider open-sourcing a framework for one, just for grins, with a 'donate' link, see what happens)
This let's you use a local search and restircts web search to your browser of choice.
Biting the hand that feeds IT © 1998–2019