My Windows 7 Test workstation finally updated itself to the latest Version. Rebooted and manually adapted the Network instead of using DHCP. My normal Nethserver is doing DHCP, not the Test-Server yet.
Cool is the fact using VirtIO-Network you get 10 GB/S !!! (At least inside the ProxMox, my ProxMox has only Gigabit LAN!)
So: Testing the Samba AD:
Entering the “Domain Admin” credentials (From the NethServer-Beta)…
And looking good!
Checking groups / permissions:
I created a “normal” User. On the network normal permissions, but on the local machine I want the user to have local Administrator permissions AND of course RemoteDesktop…
-> Feature Wish
Why not have some “Standard” groups, for those who choose AD?
Like remotedesktopusers, domain users, printer admins…
For those using Windows clients, it could help.
Rebooted the PC and testing direct Domain Logins:
RDP as the “normal” User (RDP Settings on my Mac):
And… Login / Permissions from AD perfect!
One small issue I noticed:
The DNS Alias for the AD should be automatically activated (and filled in) as soon as AD is activated!
Actually - even without AD, the server should have it’s defined name entered in as soon as the DNS server is activated. Can Nethserver handle reverse lookups correctly? Even itself? DNSmask can handle that, afaik…
The required info is already there:
additionally, after setting up AD the domain name and DNS is “fixed”, so why not use that info.
These entries I had to do manually:
One of the key requirements of a working AD is DNS working correctly (to be more precise, a working Name to IP resolution is required, but also to tell clients eg which server is the master.).
Printing and other Stuff not yet tested, I will also test Squid performance using the Nethserver, but I’ll wait until I set up the clone my hardware Win7 box.
That way, I’ll actually have three Win7 clients using the Test NethServer, one in Hardware, one on ProxMox and one on Parallels (Mac).
NextCloud using AD:
I can also confirm that NextCloud works well as far as LDAP/AD Integration is concerned:
The image shows the NethServer Admin (Not the NextCloud admin!) with permissions as Admin of NextCloud. The defined groups (eg nextcloud-users) also work as expected!
This isn’t optimal:
This would be a more appropriate setting:
env EDITOR=nano crontab -u apache -e
*/15 * * * * /opt/rh/rh-php56/root/usr/bin/php -f /usr/share/nextcloud/cron.php
CTRL x y
So far, all looks good!
@giacomo and all involved in packaging, testing…