I saw this post of yours Repair system critical error but I guess this is solved? Did you install the App Active Directory-compatible Domain Controller and all join scripts are executed? Did you install UCS with the master-role? If you can answer these questions with ‘yes’ and only if you can answer them with ‘yes’ then consider moving forward to the next step:
Why? Freenas is not linux and creating it in the “member server container” will not help. I discussed the roles with you here: Not able to communicate with smb shares from freenas. Point no.5.
“Will not help” means the following: if you chose the role ‘member-server’ you can - after a successful join of freenas - manage shares (that are already created on freenas) over UCS/UMC (domain - shares). So that you are able to assign them as user-directories and so on. If you create a ‘linux computer’ and put it in LDAP ‘member server’ container you can’t.
If you only want to connect to freenas-shares with the user-credentials managed through UCS, then you can leave this consideration aside. I have never tried the ‘linux role’ for freenas but even this should do as long as you don’t run into this:
They should be there, they must be there, they have to be there! (don’t forget the leading
/ which will make it
/etc/univention/ssl/) And as long as you don’t have the right certificates on UCS that you can import to freenas a join from freenas will fail! So there is no need to proceed with any freenas configuration (which is described in several threads here in the forum).