Reini

@limetech this request wasn't considered within 15 month. What do I have to do to get attention here? Please respond.

No. Only with the described manual changes, it's possible to get it to work - including AD authentication - without any issues.

I was hoping to get this "Feature Requests", which was already implemented in the past, reactivated in the actual 6.10.x Version. But after 15 month, nothing happens. So, I still need to using "User Scripts" to get the /etc/samba/smb-shares.conf manipulated. This is not good, really "☹️"

@limetech, some news on this? Please give some feedback. Thanks.

Dear unRAID Team, Some news on this?

Hi Tom, First of all many thanks. With theses settings above, it work perfectly. Because of the positive result, we wish that the feature will be re-enabled in ADS environments. Please see my Feature Request Re-enabling macOS interoperability and Time Machine based GUI settings if SMB Settings "Enable SMB" is set to "Yes (Active Directory)". Best regards, Reini

If SMB Settings "Enable SMB" is set to "Yes (Active Directory)", which means "AD join status" is "Joined", then the setting "Enhanced macOS interoperability" setting to "Yes" and the "SMB Security Settings" at "Export" setting to "Yes/TimeMachine" doesn't work for using it on Apples Time Machine. (AFP is also extremely instabil in Active Directory Services (ADS) for more (4+) Macs doing Time Machine Backups. If good luck, then it works some weeks. Next is unRAID's note: "Please note that AFP is deprecated, please use SMB instead.". This will prevent from using AFP - but it's OK.) At the moment, the only way to get SMB based Time Machine backup running in ADS environments with more Mac-Users is to add these lines to "Samba extra configuration:" This must be done, because if "Enable SMB" is set to "Yes (Active Directory)", all "macOS interoperability" settings will be ignored from unRAID OS - so far as I remember from Tom (cause of ADS problems in the past). With the quoted settings above, we are running SMB based Time Machine backups in an ADS environment long time without any issues. But there is one problem, because these settings are global, the option "fruit:time machine = yes" and "fruit:time machine max size = 4T" is valid for ALL shares. If Macs are connecting to any other share, the share limit is 4TByte for ALL shares. Leaving the option "fruit:time machine max size = 4T" is not an option, because Time Machine is taking ALL available storage. So, please re-enable the "macOS interoperability" and TimeMachine based GUI settings if ADS is active (SECURITY="ads" in /boot/config/ident.cfg) to prevent from manual adding "Samba extra configurations". Thanks in advance.

OK, but basically this feature is already implemented and internally disabled if ADS is active. It just needs to re-enable it again. Anyhow, I posted it at the Feature Request section. Thanks.

Hi, if at SMB Settings "Enable SMB" is set to "Yes (Active Directory)" which means "AD join status" is "Joined", then the setting "Enhanced macOS interoperability" setting "Yes" and the "SMB Security Settings" at "Export" set to "Yes/TimeMachine" doesn't work for using it on Apples Time Machine. AFP is also extremely instabil in Active Directory Services (ADS) for more (4+) Macs doing Time Machine Backups. If good luck, then it works some weeks. Next is unRAID's note: "Please note that AFP is deprecated, please use SMB instead.". This will prevent from using AFP - but it's OK. The only way to get SMB based Time Machine backup running in ADS environments with more Mac-Users is to add these lines to "Samba extra configuration:" This must be done, because if "Enable SMB" is set to "Yes (Active Directory)", all "macOS interoperability" settings will be ignored from unRAID OS - so far as I remember from Tom (cause of ADS problems in the past). With the settings above, we are running SMB based Time Machine backups in an ADS environment long time without any issues. But there is one problem, because these settings are global, the option "fruit:time machine = yes" and "fruit:time machine max size = 4T" is valid for ALL shares. If Macs are connecting to any share, the share limit is 4TByte for ALL shares. Leaving the option "fruit:time machine max size = 4T" is not an option, because Time Machine is taking ALL available storage. So, my wish is that the "macOS interoperability" and TimeMachine based GUI settings won't be ignored if ADS is active (SECURITY="ads" in /boot/config/ident.cfg). Is there a quick and easy way to make this happen or is there any possibility / timeline / roadmap until when it could be happen? Thanks in advance.

And you also need this the following in addition at the affected share section (not at [global]): fruit:time machine = yes Otherwise you won't see the affected share at Apple's Time Machine. But this can't be done at "Settings/SMB/Samba extra configuration" I assume !?

Have you configured unRAID-SMB with joining to an Active Directory domain controller ?

If this works well, the it would be great to know the right settings. On the other side, I read "Note: AFP is now deprecated and macOS users are encouraged to use SMB only." at: So, AFP don't run stable and the SMB-Share isn't visible in Time Machine wile ADS is enabled, hmmm ...

Same problem for me. It seems that the "Time Machine support via SMB" is not working if Active Directory implementation is enabled at the SMB settings on V 6.7. While checking the /etc/rc.d/rc.samba script, I found out that if [ "$SECURITY" = "ads" ] then no "fruit:..." settings will be done at /etc/samba/smb-names.conf. Without these settings, there is no Time Machine support via SMB. See also here: https://www.mankier.com/8/vfs_fruit If I'm adding the fruit settings manually (and restart the SMB deamon) then I'm able to see the SMB-Share at Time Machine for adding the share. But I also remember, that there are some issues on this implementation of fruit/samba. If im not wrong, maybe this is the reason why it is not working as expected...

It seems that the "Time Machine support via SMB" is not working if Active Directory is enabled (joined to an Active Directory domain controller) at the SMB settings. Correct?

I have done everything exactly as described but no success. One Mac has done the TimeMachine Backup 5 times without issues. At the 6th time, TimeMachine said, a new backup is needed and failed. From that time, I have seen many errors/failures at the unRAIDs syslog (see below). Also from that time, no Mac is able to do a TimeMachine backup anymore and skip the backups to unRAID. At the same time, all Time Machine backups to the old Synology system still works without any issues. After rebooting unRAID the afpd errors disappears and Time Machine is able to doing backups again, but only until the afpd error comes back and the loop starts from the beginning. It seams the the AFP implementation isn't stable enough!? Any other ideas?