Hi Alessio, I was also thinking that some screenshots will be more appealing, but there are none because I had 2 constrains.
First all of this was done on the vSphere client and i had a lot of switching back and forward between consoles and second, it is a little difficult to have all this edited and also edit the screens.
I’ll try to add printscreens and also continue the how-to because is not yet finished
still to do - Joining the linux client to AD, but i’m stuck at connecting to LDAP of NS to explore it and joining the machine.
(maybe you can give me some info. because i did not succeded with the docs.)
I agree with you that it had to be split into sections.
I’ve done it in one session and this is why is not so properly formated
I hope the V 1.1 of the document will look better.
Anyway thanks for the comments, this is the stuff that makes things better (constructive points and suggestions for improvement)
Good info… thanks for sharing…
I have this question from so long…may be it sounds silly…
Can we replace Windows AD Server with AD on Linux?
WIll I be able to manage windows machines using this Linux AD server?
If yes, any limitations?
I have Windows server running as AD Server for 300 desktops, just to manage users. With lot of space and RAM. So, I want to replace it with Linux to make that hardware more usable with other apps.
Well managing the AD tree is what i’m trying to do right now.
First I need to be able to connect to LDAP. I’m trying with APACHE Directory studio (Welcome to Apache Directory Studio — Apache Directory) but until now i could not connect to it I miss the information required to connect to LDAP.
So, Ii can’t say for sure that you can manage the computers from SAMBA AD. One thing for sure is that you do not have GPOs like in SAMBA 4 yet
If anyoane has success with connecting to LDAP please share so we can make progress with this HOW-TO
Anyway long instructions are great for us easily copy text in some situations. Hard to find the right pics/text mix
@Ctek Thanks a lot for taking the time to write this. Community’s guides like this one are really demystifying these tasks. It would take me days to find and understand how to do what you explain here, you made it clear. I’ve not yet finished to read it but thank you again for this step-by-step tutorial, you really take us by the hand “come with me, I’ll show you how easy it is” Luv it
Sure, if you need data to copy/paste then I suggest using the discourse code snippet while you are describing an operation by web UI a screenshot fits better.
Hi FenyX, Thank you for your words and I hope that this HOW-TO it helped you.
Please take into account that it is not yet finished due to the lack of time
And also what Stefano (Zamboni) sayed is true. It is a Domain controller as NT not Active Directory.
The question is not if NS sso supports Moodle, but if Moodle supports NS authentication. The answer is yes and can be found in Moodle documentation: https://docs.moodle.org/24/en/Active_Directory
For your 2nd question: just configure 1 interface as green and do not install the firewall/UTM module. You can decide to hand over DHCP and DNS to NethServer instead of the mikrotik router. If you need the proxy service, I would consider a second interface since a single interface can be bypassed. In the case of a second interface you can ‘double nat’ NethServer behind the mikrotik.
I was also thinking that some screenshots will be more appealing, but there are none because I had 2 constrains.
I miss the information required to connect to LDAP.
Luv it
