Using Linux AD for Exchange
-
@DustinB3403 said in Moving from Exchange Online Plan 1 to In House Exchange 2016:
@JaredBusch said in Moving from Exchange Online Plan 1 to In House Exchange 2016:
@DustinB3403 said in Moving from Exchange Online Plan 1 to In House Exchange 2016:
If I had my approach, I'd likely use a RedHat as the fileserver (or CentOS), and leave the Exchange services for just that. For the domain functions, use RH or CentOS, maybe Zentyal or some other flavor like that.
Exchange requires AD last I knew. Please show me a guide that gets around that. I could use it (seriously).
I'd have to look around, but I recall seeing a topic where SAMBA4 was used to replace Windows AD, while still using MS Exchange.
AD is AD, so any AD server works with Exchange.
-
@scottalanmiller said in Moving from Exchange Online Plan 1 to In House Exchange 2016:
@DustinB3403 said in Moving from Exchange Online Plan 1 to In House Exchange 2016:
@JaredBusch said in Moving from Exchange Online Plan 1 to In House Exchange 2016:
@DustinB3403 said in Moving from Exchange Online Plan 1 to In House Exchange 2016:
If I had my approach, I'd likely use a RedHat as the fileserver (or CentOS), and leave the Exchange services for just that. For the domain functions, use RH or CentOS, maybe Zentyal or some other flavor like that.
Exchange requires AD last I knew. Please show me a guide that gets around that. I could use it (seriously).
I'd have to look around, but I recall seeing a topic where SAMBA4 was used to replace Windows AD, while still using MS Exchange.
AD is AD, so any AD server works with Exchange.
It was my understanding that SAMBA did not properly support all the extended attributes that Exchange needed.
-
@JaredBusch said in Moving from Exchange Online Plan 1 to In House Exchange 2016:
@DustinB3403 said in Moving from Exchange Online Plan 1 to In House Exchange 2016:
@JaredBusch said in Moving from Exchange Online Plan 1 to In House Exchange 2016:
@DustinB3403 said in Moving from Exchange Online Plan 1 to In House Exchange 2016:
If I had my approach, I'd likely use a RedHat as the fileserver (or CentOS), and leave the Exchange services for just that. For the domain functions, use RH or CentOS, maybe Zentyal or some other flavor like that.
Exchange requires AD last I knew. Please show me a guide that gets around that. I could use it (seriously).
I'd have to look around, but I recall seeing a topic where SAMBA4 was used to replace Windows AD, while still using MS Exchange.
SAMBA4 would be really new and why I did not know it if that is the case. Also replace vs. Greenfield is completely different.
Samba 4 hit production release in 2012. It was heavily used in late beta for a lot of businesses for a year or two before that, people were really passionate about using it and it took like ten years to get to its final release so even some commercial AD replacement products were build on Samba 4 in beta.
NethServer, Zentyal and anyone else offering AD without Windows uses this. This is what Synology uses, too.
-
@JaredBusch said in Moving from Exchange Online Plan 1 to In House Exchange 2016:
@scottalanmiller said in Moving from Exchange Online Plan 1 to In House Exchange 2016:
@DustinB3403 said in Moving from Exchange Online Plan 1 to In House Exchange 2016:
@JaredBusch said in Moving from Exchange Online Plan 1 to In House Exchange 2016:
@DustinB3403 said in Moving from Exchange Online Plan 1 to In House Exchange 2016:
If I had my approach, I'd likely use a RedHat as the fileserver (or CentOS), and leave the Exchange services for just that. For the domain functions, use RH or CentOS, maybe Zentyal or some other flavor like that.
Exchange requires AD last I knew. Please show me a guide that gets around that. I could use it (seriously).
I'd have to look around, but I recall seeing a topic where SAMBA4 was used to replace Windows AD, while still using MS Exchange.
AD is AD, so any AD server works with Exchange.
It was my understanding that SAMBA did not properly support all the extended attributes that Exchange needed.
Schema extensions are disabled by default for protection, but just have to be enabled.
-
@scottalanmiller said in Moving from Exchange Online Plan 1 to In House Exchange 2016:
@JaredBusch said in Moving from Exchange Online Plan 1 to In House Exchange 2016:
@scottalanmiller said in Moving from Exchange Online Plan 1 to In House Exchange 2016:
@DustinB3403 said in Moving from Exchange Online Plan 1 to In House Exchange 2016:
@JaredBusch said in Moving from Exchange Online Plan 1 to In House Exchange 2016:
@DustinB3403 said in Moving from Exchange Online Plan 1 to In House Exchange 2016:
If I had my approach, I'd likely use a RedHat as the fileserver (or CentOS), and leave the Exchange services for just that. For the domain functions, use RH or CentOS, maybe Zentyal or some other flavor like that.
Exchange requires AD last I knew. Please show me a guide that gets around that. I could use it (seriously).
I'd have to look around, but I recall seeing a topic where SAMBA4 was used to replace Windows AD, while still using MS Exchange.
AD is AD, so any AD server works with Exchange.
It was my understanding that SAMBA did not properly support all the extended attributes that Exchange needed.
Schema extensions are disabled by default for protection, but just have to be enabled.
If you are going to keep replying, respond to my flagging of the post for moderation to split the topic.
-
@JaredBusch said in Moving from Exchange Online Plan 1 to In House Exchange 2016:
@scottalanmiller said in Moving from Exchange Online Plan 1 to In House Exchange 2016:
@JaredBusch said in Moving from Exchange Online Plan 1 to In House Exchange 2016:
@scottalanmiller said in Moving from Exchange Online Plan 1 to In House Exchange 2016:
@DustinB3403 said in Moving from Exchange Online Plan 1 to In House Exchange 2016:
@JaredBusch said in Moving from Exchange Online Plan 1 to In House Exchange 2016:
@DustinB3403 said in Moving from Exchange Online Plan 1 to In House Exchange 2016:
If I had my approach, I'd likely use a RedHat as the fileserver (or CentOS), and leave the Exchange services for just that. For the domain functions, use RH or CentOS, maybe Zentyal or some other flavor like that.
Exchange requires AD last I knew. Please show me a guide that gets around that. I could use it (seriously).
I'd have to look around, but I recall seeing a topic where SAMBA4 was used to replace Windows AD, while still using MS Exchange.
AD is AD, so any AD server works with Exchange.
It was my understanding that SAMBA did not properly support all the extended attributes that Exchange needed.
Schema extensions are disabled by default for protection, but just have to be enabled.
If you are going to keep replying, respond to my flagging of the post for moderation to split the topic.
I have no idea where those flags go, they don't show up anywhere for me.
-
minus your reply to the OP after this post, split it here; https://mangolassi.it/post/284280
-
Fork complete
-
-
@scottalanmiller said in Using Linux AD for Exchange:
@JaredBusch said in Moving from Exchange Online Plan 1 to In House Exchange 2016:
@scottalanmiller said in Moving from Exchange Online Plan 1 to In House Exchange 2016:
@DustinB3403 said in Moving from Exchange Online Plan 1 to In House Exchange 2016:
@JaredBusch said in Moving from Exchange Online Plan 1 to In House Exchange 2016:
@DustinB3403 said in Moving from Exchange Online Plan 1 to In House Exchange 2016:
If I had my approach, I'd likely use a RedHat as the fileserver (or CentOS), and leave the Exchange services for just that. For the domain functions, use RH or CentOS, maybe Zentyal or some other flavor like that.
Exchange requires AD last I knew. Please show me a guide that gets around that. I could use it (seriously).
I'd have to look around, but I recall seeing a topic where SAMBA4 was used to replace Windows AD, while still using MS Exchange.
AD is AD, so any AD server works with Exchange.
It was my understanding that SAMBA did not properly support all the extended attributes that Exchange needed.
Schema extensions are disabled by default for protection, but just have to be enabled.
Sounds like a lab project that needs done, because I cannot find any references to this being done.
-
@JaredBusch said in Using Linux AD for Exchange:
@scottalanmiller said in Using Linux AD for Exchange:
@JaredBusch said in Moving from Exchange Online Plan 1 to In House Exchange 2016:
@scottalanmiller said in Moving from Exchange Online Plan 1 to In House Exchange 2016:
@DustinB3403 said in Moving from Exchange Online Plan 1 to In House Exchange 2016:
@JaredBusch said in Moving from Exchange Online Plan 1 to In House Exchange 2016:
@DustinB3403 said in Moving from Exchange Online Plan 1 to In House Exchange 2016:
If I had my approach, I'd likely use a RedHat as the fileserver (or CentOS), and leave the Exchange services for just that. For the domain functions, use RH or CentOS, maybe Zentyal or some other flavor like that.
Exchange requires AD last I knew. Please show me a guide that gets around that. I could use it (seriously).
I'd have to look around, but I recall seeing a topic where SAMBA4 was used to replace Windows AD, while still using MS Exchange.
AD is AD, so any AD server works with Exchange.
It was my understanding that SAMBA did not properly support all the extended attributes that Exchange needed.
Schema extensions are disabled by default for protection, but just have to be enabled.
Sounds like a lab project that needs done, because I cannot find any references to this being done.
It's very uncommon to do because if you are running Exchange, you have already invested in Windows itself, Windows CALs, and Windows support (whether it be knowledge, experience, or whatever.) So the desire to support Exchange on Windows, but not AD, is extremely low.
-
@scottalanmiller But it is what @DustinB3403 is proposing, and what led to this entire thread.
-
@JaredBusch I only said it was possible, not an official recommendation.
-
This sounds like something someone should try in a lab... I just happen to be putting one together. Maybe I can give this a shot tonight.
-
Yea i just got a free server from a returned customer eval. Might have to try somethign like this just to see if it works.
-
Some months ago I tried samba 4 as an AD... In the end I did it with plain linux: zentyal kept chrashing at some automated step. Nethserver was not out.
,I ve abandoned the project when I hit major print server issues. Also rsat was not really full working: I did a lot of cmd line with win10 clients -
I think in many cases, just using a normal Linux server makes more sense. All that GUI and extra stuff tends to be problematic.
-
@scottalanmiller said in Using Linux AD for Exchange:
@magroover said in Moving from Exchange Online Plan 1 to In House Exchange 2016:
@DustinB3403 I've been thinking about investing more time in using CentOS as a premise-based server. I am not whether there are more opportunities for sysadmin or for app development, which has been my more recent role. Managing the actual LOB apps used and customizing, doing reports.
Both, really.
And look at NethServer and Zentyal, they use CentOS as a base but make a lot of the functions easy for SMBs. Going after the SBS concept. I prefer to break things up, but understand why people like this all in one servers.
Zentyal is Ubuntu. ClearOS was the other CentOS based system.
