Large network of Windows machines without AD - GO!
-
@coliver said in Large network of Windows machines without AD - GO!:
@Dashrender said in Large network of Windows machines without AD - GO!:
What about situations where users roam from computer to computer?
This can be accomplished in a number of ways. Configuration Management, or create the user account with Powershell.
How are you proposing using powershell? or Configuration management? I assume CM is a third party tool - say salt, and you're pushing configs via that? OK I can see that. Powershell can do this as well, but I really don't like the idea of opening powershell ports on the machine - I like the agent based solution instead.
-
@coliver said in Large network of Windows machines without AD - GO!:
@Dashrender said in Large network of Windows machines without AD - GO!:
What about mapping network resources like printers and fileshares?
You can do this with just local accounts.
OK sure, but then I have to know the passwords to all of those accounts so I can make matching ones on the server - or, they end up with different creds for logon vs resource use. I.E. no SSO like you get with AD and Windows resources, so user experience could be lessened - and before you say - but you don't need to do it everything - you only need to do it the first time they attach to the resource.. yeah I know that.
-
You dont really need AAD, though.
You could ditch AD and just get SSO like Okta or Jumpcloud.
-
Would something like Zentyal be appropriate?
-
@Dashrender said in Large network of Windows machines without AD - GO!:
How do you manage and get knowledge that systems are updated?
How do you do it with AD? AD doesn't do any management on its own, nor does it report on this. This is good stuff to have, but awkward to answer in a "how do we ditch X" when you are then asking about Y.
-
@Dashrender said in Large network of Windows machines without AD - GO!:
What user accounts are on the machine - and how do they get there?
Local users. For most large environments, that's one user per machine. So Salt or Ansible is easy, as is manually creating when the system is set up. Nothing complicated normally needed.
If you have a lot of roaming or shared machines, then Ansible or Salt or similar is a great way to handle that.
-
@Dashrender said in Large network of Windows machines without AD - GO!:
Do you have a single admin level account pre-setup on every machine?
For desktops, generally. Depends on your security needs. One controlled by Ansible/Salt makes this secure and easy. But making a unique one for each machine is an option, too, if you want to jump way beyond the security that AD would normally give you. Or push out loads of admin accounts for every admin user. Loads of options depending on your needs.
With Ansible/Salt... do you even need an admin account?
-
@Dashrender said in Large network of Windows machines without AD - GO!:
@coliver said in Large network of Windows machines without AD - GO!:
@Dashrender said in Large network of Windows machines without AD - GO!:
Do you have a single admin level account pre-setup on every machine?
You should be doing this anyway.
Well, you get this through normal AD, and I've only ever used an AAD account to add machines to AAD, and that user does then get local admin, but beyond that....
Not local accounts. And with AD, we always have local, too, because AD tends to be fragile.
-
@Dashrender said in Large network of Windows machines without AD - GO!:
@coliver said in Large network of Windows machines without AD - GO!:
@Dashrender said in Large network of Windows machines without AD - GO!:
What about mapping network resources like printers and fileshares?
You can do this with just local accounts.
OK sure, but then I have to know the passwords to all of those accounts so I can make matching ones on the server - or, they end up with different creds for logon vs resource use. I.E. no SSO like you get with AD and Windows resources, so user experience could be lessened - and before you say - but you don't need to do it everything - you only need to do it the first time they attach to the resource.. yeah I know that.
Maybe at initial creation, but not for them to use them. This isn't an actual problem. Centralized passwords are totally possible without you knowing them or using AD.
-
@notverypunny said in Large network of Windows machines without AD - GO!:
Would something like Zentyal be appropriate?
Just a package of Samba 4 which is just a third party AD. So this is just another way of saying to use Samba, which is another way of saying "keep AD."
If the question is "how can I more affordably do AD", then Zentyal is a great AD distro. But if the question is "how do I ditch AD", Zentyal isn't ditching it at all.
-
@scottalanmiller said in Large network of Windows machines without AD - GO!:
@Dashrender said in Large network of Windows machines without AD - GO!:
How do you manage and get knowledge that systems are updated?
How do you do it with AD? AD doesn't do any management on its own, nor does it report on this. This is good stuff to have, but awkward to answer in a "how do we ditch X" when you are then asking about Y.
/sigh.. yeah, you're right.
Let me rephrase - using all of the tools that come along with Standard Windows Licensing, and typcially seen deployed in an AD environment - how would you do these things without AD/Windows Server/etc.
-
@scottalanmiller said in Large network of Windows machines without AD - GO!:
@Dashrender said in Large network of Windows machines without AD - GO!:
@coliver said in Large network of Windows machines without AD - GO!:
@Dashrender said in Large network of Windows machines without AD - GO!:
Do you have a single admin level account pre-setup on every machine?
You should be doing this anyway.
Well, you get this through normal AD, and I've only ever used an AAD account to add machines to AAD, and that user does then get local admin, but beyond that....
Not local accounts. And with AD, we always have local, too, because AD tends to be fragile.
I haven't failed back to a local account for an AD joined computer in I don't know how long - probably more than 8 years. And if that happened today - I'm not sure I'd do it at all - I'd just wipe and reload.
-
@scottalanmiller said in Large network of Windows machines without AD - GO!:
@notverypunny said in Large network of Windows machines without AD - GO!:
Would something like Zentyal be appropriate?
Just a package of Samba 4 which is just a third party AD. So this is just another way of saying to use Samba, which is another way of saying "keep AD."
If the question is "how can I more affordably do AD", then Zentyal is a great AD distro. But if the question is "how do I ditch AD", Zentyal isn't ditching it at all.
Great point - and one I have been waiting for someone to make.
So - which is really better way to go? Ditch it altogether and try a LANless solution, or AD alternative?
-
@Dashrender said in Large network of Windows machines without AD - GO!:
@scottalanmiller said in Large network of Windows machines without AD - GO!:
@Dashrender said in Large network of Windows machines without AD - GO!:
How do you manage and get knowledge that systems are updated?
How do you do it with AD? AD doesn't do any management on its own, nor does it report on this. This is good stuff to have, but awkward to answer in a "how do we ditch X" when you are then asking about Y.
/sigh.. yeah, you're right.
Let me rephrase - using all of the tools that come along with Standard Windows Licensing, and typcially seen deployed in an AD environment - how would you do these things without AD/Windows Server/etc.
That's a very different question. Nothing wrong with moving away from Windows, just it's very different than moving away from AD.
Now, really, Windows doesn't come with much in that vein, either. Group Policy is weak and non-deterministic, only marginally qualifying as "management". WSUS has gotten so bad, it's almost a stumbling block to updates.
All of Group Policy and WSUS functions (other than local caching) can pretty easily be replaced deterministically with something like Salt or Ansible. Even if you have AD, they'd be the way I'd want to tackle those problems.
-
@Dashrender said in Large network of Windows machines without AD - GO!:
@scottalanmiller said in Large network of Windows machines without AD - GO!:
@Dashrender said in Large network of Windows machines without AD - GO!:
@coliver said in Large network of Windows machines without AD - GO!:
@Dashrender said in Large network of Windows machines without AD - GO!:
Do you have a single admin level account pre-setup on every machine?
You should be doing this anyway.
Well, you get this through normal AD, and I've only ever used an AAD account to add machines to AAD, and that user does then get local admin, but beyond that....
Not local accounts. And with AD, we always have local, too, because AD tends to be fragile.
I haven't failed back to a local account for an AD joined computer in I don't know how long - probably more than 8 years. And if that happened today - I'm not sure I'd do it at all - I'd just wipe and reload.
We do it very often. Small environments, AD is a huge problem.
-
@Dashrender said in Large network of Windows machines without AD - GO!:
So - which is really better way to go? Ditch it altogether and try a LANless solution, or AD alternative?
Really depends. Basically it's LAN-centric vs LANless (LAN-agnostic.) Samba 4 will pretty much give you all the AD features you normally use, plus GPO and the like, but not WSUS, for free. But it becomes only a cost savings, not a change of approach. You are tied to the LAN, whether local or VPN extended, and have all of the headache that that brings still. But you can do things in a traditional way.
-
@Dashrender said in Large network of Windows machines without AD - GO!:
@marcinozga said in Large network of Windows machines without AD - GO!:
Intune is $6/user/month, so at 200 users you're looking at $14,400 annually. Windows Server 2019 Standard license is $800 and $8000 for user CALs, or $0 is you go with Samba.
and you didn't include the AAD license. yeah that shit is hella expensive!!! and a major reason why on prem AD continues to stick around.
It's way less than having an extra IT Admin / engineer hanging around to set up and manage all the SAMBA, Ansible, on-prem, etc., crap involved in taking care of every single point.
It's all ready to go built in management, administration, app deployment / user management / policy / compliance / reporting / updating, LANless/Global/distributed/mobile, such a huge damn list of things all ready to go, that'd you'll end up needing anyways, no building from the ground up. A basic 200-user setup for all the things would be minimal.
It's not a simple "oh just install ansible and samba". That will take a ton of work to build the entire environment unless you use something like others mentioned like Zentyal if you really want to keep the on-prem mindset going.
For 200 users, you would just need one person to set it up.
You could use ansible or something, but I'm telling you that'd be a huge PITA for a full Windows environment. I wouldn't got the on-prem or SAMBA route.
-
@Obsolesce said in Large network of Windows machines without AD - GO!:
It's way less than having an extra IT Admin / engineer hanging around to set up and manage all the SAMBA, Ansible, on-prem, etc., crap involved in taking care of every single point.
Except you don't need one hanging around for that stuff. If you don't have the skills in house, farm that out to an MSP for one time cost way less than the cost of AAD or whatever. Yes, it requires more expertise than many other solutions, but like most things in IT... the higher the expertise needed, the lower the overall cost.
Once Samba, Ansible, etc. is up and running (and you don't need it on premises at all) you've got a near zero cost, easily to maintain infrastructure.
-
@Obsolesce said in Large network of Windows machines without AD - GO!:
You could use ansible or something, but I'm telling you that'd be a huge PITA for a full Windows environment. I wouldn't got the on-prem or SAMBA route.
What does on prem have to do with any of it? Other than AAD being off prem only (unless you use Azure for your desktops, then it is on prem) all solutions (AD, Samba, State) are both on or off prem and work the same either way.
-
@Obsolesce said in Large network of Windows machines without AD - GO!:
It's all ready to go built in management, administration, app deployment / user management / policy / compliance / reporting / updating, LANless/Global/distributed/mobile, such a huge damn list of things all ready to go, that'd you'll end up needing anyways, no building from the ground up. A basic 200-user setup for all the things would be minimal.
I've seen shops do AAD and have it have so many problems that it cost them too much in IT labor time and moved away because it was the opposite of easy or "out of the box." Not that that is normal, but just saying that it's magic and easy and doesn't require IT or knowing what you are doing or whatever isn't the case. It might require less, but at a staggering cost. For less than the cost of AAD you can have your department outsourced and everything handled for you. So somewhere, the math doesn't add up. It would only be "expensive" if trying to do it with resources that can't handle it (like how underpowered cars aren't fuel efficient because the engine is working too hard.)
