20-11-2023, 11:07 AM
20-11-2023, 03:35 PM
Thats why I never set up any computer with a Microsoft account, go with a Local from the start, and none of the command prompt methods, sometimes after updates MS try again to sign in, but use the exact same method and it makes it go away still using the local account.
Easy as :
When asking to sign in, type no@thankyou.com Password - Anything you want / tap some random keys - it wont be used so no need to remember them, Then it goes OOPS something went wrong - Gives you the option to use a local account / name instead.
If the user wants a MS account thats upto them. Same with Office 365 - while you sign into a MS account with that you click "Microsoft Apps only" ( tiny blue writing bottom left of window) and away you go.
Easy as :
When asking to sign in, type no@thankyou.com Password - Anything you want / tap some random keys - it wont be used so no need to remember them, Then it goes OOPS something went wrong - Gives you the option to use a local account / name instead.
If the user wants a MS account thats upto them. Same with Office 365 - while you sign into a MS account with that you click "Microsoft Apps only" ( tiny blue writing bottom left of window) and away you go.
20-11-2023, 04:01 PM
much the same here, mainly use local accounts. The clients usually end up signing in to MS themselves when prompted.
I must say though, I do feel that the reason against that outweighed 'all' the benefits of using a MS account, well it isn't really a signing into a Microsoft Account issue now is it?
The only real intersection of bitlocker and a MS account is that the key is stored in the MS account. Kind of sounded like he was having a bit of a rant to be honest
Looks like an interesting bug though, discussed a bit here
https://answers.microsoft.com/en-us/wind...8b94da7d41
and
https://answers.microsoft.com/en-us/wind...035139e0c9
Makes me wonder whether it is actually enabling bitlocker or just showing the bitlocker form. Maybe if they had a look at the data it would actually be accessible
I must say though, I do feel that the reason against that outweighed 'all' the benefits of using a MS account, well it isn't really a signing into a Microsoft Account issue now is it?
The only real intersection of bitlocker and a MS account is that the key is stored in the MS account. Kind of sounded like he was having a bit of a rant to be honest
Looks like an interesting bug though, discussed a bit here
https://answers.microsoft.com/en-us/wind...8b94da7d41
and
https://answers.microsoft.com/en-us/wind...035139e0c9
Makes me wonder whether it is actually enabling bitlocker or just showing the bitlocker form. Maybe if they had a look at the data it would actually be accessible
22-11-2023, 11:41 AM
(20-11-2023, 03:35 PM)Wainuitech Wrote: [ -> ]Thats why I never set up any computer with a Microsoft account, go with a Local from the start, and none of the command prompt methods, sometimes after updates MS try again to sign in, but use the exact same method and it makes it go away still using the local account.
Easy as :
When asking to sign in, type no@thankyou.com Password - Anything you want / tap some random keys - it wont be used so no need to remember them, Then it goes OOPS something went wrong - Gives you the option to use a local account / name instead.
If the user wants a MS account thats upto them. Same with Office 365 - while you sign into a MS account with that you click "Microsoft Apps only" ( tiny blue writing bottom left of window) and away you go.
Thats what I end up doing, surprised M$ has not addressed it yet.