3 ms·

It's easier on Pro, you get a Domain login option which just creates you a local account for you to use to get your machine domain joined, even if you're connec

by Neil44 7y ago

It's easier on Pro, you get a Domain login option which just creates you a local account for you to use to get your machine domain joined, even if you're connected to the internet already. The main reason for me to use local accounts is as an IT professional I'm often setting things up for other people who aren't present at the time. Also if I set a Microsoft account up for someone then in their mind I am usually then the contact for any and all issues around that account forever which creates tension in my customer relationship.

ocdtrekkie 7y ago
This is the source of another huge peeve though: Microsoft's developers have largely forgotten local Windows domains exist, as selecting that the computer belongs to an organization defaults to Azure sign-in, and then dumps you off on creating a normal local account if you say "local domain instead". The OOBE doesn't help with local domain setup at all for no conceivable reason. Similarly, if you look at the new Settings app, it's support for domain PCs is close to nonexistent. Out of disk space, and going to the storage tab? Great, it'll tell you 50 GB of data is used by other users, but you can't see anything about who they are. Need to manage other users? No can do, Settings app doesn't even see domain accounts. You have to go to the legacy Control Panel, System, Advanced Settings, and then User Profiles (a Windows 98 era dialog) to see domain accounts and their local storage use.
- Neil44 7y ago
  Yep it's a pain to go and find your way to the join domain options these days. It certainly shows you the way Microsoft is thinking about these things. Domains with GPOs were a really sweet way to manage everything but MS have realised they can nickel and dime you to replicate the same functionality on a subscription model with Azure ADDS, so bend over boys. All MS's stuff feels half finished these days. I believe they call it 'high feature velocity'.

by Neil44 7y ago

ocdtrekkie 7y ago

This is the source of another huge peeve though: Microsoft's developers have largely forgotten local Windows domains exist, as selecting that the computer belongs to an organization defaults to Azure sign-in, and then dumps you off on creating a normal local account if you say "local domain instead". The OOBE doesn't help with local domain setup at all for no conceivable reason. Similarly, if you look at the new Settings app, it's support for domain PCs is close to nonexistent. Out of disk space, and going to the storage tab? Great, it'll tell you 50 GB of data is used by other users, but you can't see anything about who they are. Need to manage other users? No can do, Settings app doesn't even see domain accounts. You have to go to the legacy Control Panel, System, Advanced Settings, and then User Profiles (a Windows 98 era dialog) to see domain accounts and their local storage use.

Neil44 7y ago
Yep it's a pain to go and find your way to the join domain options these days. It certainly shows you the way Microsoft is thinking about these things. Domains with GPOs were a really sweet way to manage everything but MS have realised they can nickel and dime you to replicate the same functionality on a subscription model with Azure ADDS, so bend over boys. All MS's stuff feels half finished these days. I believe they call it 'high feature velocity'.