UCS vs Ubuntu as fileserver

Hi,
I want to have an AD domain with UCS + 1 fileserver. I’ve already setup the AD domain succesfully and now want to deploy a fileserver for our Windows clients.
I’m wondering what the best (=easiest to setup& maintain) approache would be:

  • setup another UCS server as a managed node
  • setup an Ubuntu server and join this to the AD domain

I’ve read through the Samba4 documentation and found it quite complicated to setup the right idmap backend. I assume if you install another UCS server, this is all configured in the background?
Could you also use a separate disk to have your shares on?

Hi wouter,

Absolutely, go with another UCS and forget the Ubuntu route.
You will have unified user control, same WebUI to manage the shares, while you can have share not only on separate drives but on different machines (visible under the same domain).

Less pain and fragmentation, all with a smooth WebUI.

2 Likes

Absolutely agree with that!

Thanks for your answers. I’ve installed an additional UCS server in the managed node mode, but I’ve noticed samba is not installed on it. When I create a share from my other DC on this server, I cannot access it.

Which app do I need to install in order to be able to serve smb shares from this server?

But being this is a managed node, there is no local LDAP server as pointed by the docs.

I suspect this app should fit this role as file server better?

I guess this must be it. I have never worked with a managed node, all my UCS are domain controllers.

Yes that is the right one.

Indeed, I’ve installed it and I can confirm now it’s working.
FYI: the Active Direcotry compatible Domain controller app is not available on the manage node server, instead the Windows compatible memberserver is available.

One more question: I’ve noticed a default share on this fileserver for each user (i.e. each users only sees his personal shared folder). How can I disable this behaviour?

Not sure if this will work, but you could change settings in the RSAT