Substitutes for Active Directory and Windows Server
-
@JaredBusch said in Substitutes for Active Directory and Windows Server:
@scottalanmiller said in Substitutes for Active Directory and Windows Server:
You can turn those things off, of course.
Do this.
@scottalanmiller said in [Substitutes for Active Directory and Windows Server]
Or just use CentOS, Fedora, openSuse, Ubuntu, etc. as your Samba 4 base OS. Even FreeBSD is an option.
I would not do that. That requires more advanced knowledge of the pieces needed. Uunless the OP desires to learn those skills, doing things this way would be a waste of time when there are solid products available.
If I could maintain it 8 hours a day 7 days a week, then I would totally build it from scratch. Something that could be fun to do.
However, I can only maintain it from a distance and fleetingly, so having something that is tried and true, offers a solid community and has a time saving front end is what I would need in order to keep them up and running smoothly.
I'll give NethServer a go, since it seems to check the boxes I need.
-
NethServer would run in XenServer without issue, correct?
-
@jrc It should be hypervisor agnostic.
-
@jrc said in Substitutes for Active Directory and Windows Server:
NethServer would run in XenServer without issue, correct?
Just an OS. It's CentOS underneath.
-
@scottalanmiller said in Substitutes for Active Directory and Windows Server:
NethServer is the place to look first. And they are active here in the forum.
Thanks for mentioning us, I'm still here. Just mention me or @nethserver
All things I just read here about NethServer are correct, it's worth noting that- NethServer is extremely modular, you can add just what you need and nothing more
- if you can install CentOS 7 you can install NethServer 7, period
- NethServer avoids learning all those skills and saves your time. You can do almost everything by webui
I hope it helps.
-
@alefattorini Thanks for jumping in.
-
@jrc said in Substitutes for Active Directory and Windows Server:
Hmm, the problem with the pre-built ones you mentioned is that they come with a ton of things that won't be needed. There is no reason for it to handle email, or web filtering among other things. AD, DNS and File Server is all they need.
I assume the non-needed services can be turned off so that they do not consume any resources?As mentioned by @alefattorini, NethServer is extremely modular. If you just need the DC, there's no need to install/activate firewall, email, VPN, etc. Though you can also install the backup for the just-in-case scenario.
For help in installation and/or configuration, head out to the community forum, developers are there as well to lend their helping hand.
-
Hi,
Can Samba4 be used to push .msi packages to AD clients ? like I do on my Windows Group Policy management?
-
@msff-amman-Itofficer said in Substitutes for Active Directory and Windows Server:
Hi,
Can Samba4 be used to push .msi packages to AD clients ? like I do on my Windows Group Policy management?
I believe so... You'll still need a Windows workstation with rsat installed to configure the group policies.
-
@msff-amman-Itofficer said in Substitutes for Active Directory and Windows Server:
Hi,
Can Samba4 be used to push .msi packages to AD clients ? like I do on my Windows Group Policy management?
Yes. The only push mechanism is Group Policy and that works just the same.
-
I would not recommend Zentyal however is like the SBS of Linux AD with Email. I would prefer Ubuntu or something of the like as noted above on previous comments.
-
@Eltolargo said in Substitutes for Active Directory and Windows Server:
I would not recommend Zentyal however is like the SBS of Linux AD with Email. I would prefer Ubuntu or something of the like as noted above on previous comments.
That is opposite the stated goal. A single box to handle it all. The advantage to these distributions is that they do not require an all or nothing approach like SBS did. Instead, you turn on only the features you want.
-
@JaredBusch said in Substitutes for Active Directory and Windows Server:
gle box to handle it all. The advantage to these distributions is that they do not require an all or nothing approach like SBS did. Instead, you turn on only the features you want.
that's true I am not a fan of having too many roles in one server.
-
@Eltolargo said in Substitutes for Active Directory and Windows Server:
@JaredBusch said in Substitutes for Active Directory and Windows Server:
gle box to handle it all. The advantage to these distributions is that they do not require an all or nothing approach like SBS did. Instead, you turn on only the features you want.
that's true I am not a fan of having too many roles in one server.
AD/DNS/DHCP are all pretty normal to be on a single server.
-
@JaredBusch we agree on that no questions about it. I meant having email, firewall, Ad/DNS, DHCP, file server and VPN in one server that is a lot.
-
@Eltolargo said in Substitutes for Active Directory and Windows Server:
@JaredBusch we agree on that no questions about it. I meant having email, firewall, Ad/DNS, DHCP, file server and VPN in one server that is a lot.
@Eltolargo you're not forced to do it. You can install a module on a server and another module on another one sharing the userbase. NethServer can join another remote NethServer using LDAP or AD
Scenario:- NethServer1: firewall with VPN, Proxy, ecc..
- NethServer2: mailserver, personal cloud and fileserver
NethServer1 joins NethServer2 so you can use NethServer2 users/groups for authenticated proxy or VPN users
That's just a pretty simple example. -
@Eltolargo said in Substitutes for Active Directory and Windows Server:
@JaredBusch we agree on that no questions about it. I meant having email, firewall, Ad/DNS, DHCP, file server and VPN in one server that is a lot.
I agree, too. Keep that stuff separate. Especially if you are dealing with Linux, you don't have a licensing issue making you want to smoosh them all together.
-
@alefattorini said in Substitutes for Active Directory and Windows Server:
u're not forced to do it. You can install a module on a server and another module on another sharing the userbase. NethServer can join another remote NethServer using LDAP or AD
Scenario:NethServer1: firewall with VPN, Proxy, ecc..
NethServer2: mailserver, personal cloud and fileserverNethServer1 joins NethServer2 so you can use NethServer2 users/groups for authenticated proxy or VPN users
That's just a pretty simple example.Oh yeah, I agree with NethServer, I was just saying about Zentyal. I have used it in the past and not a big fan. I just came too late to the post so sorry
