Usually writing a file owned by the user who created it and not giving any other permissions. If MacOS can set permissions it will, and it will usually do it poorly.
#EXTREMEZ IP FULL#
End users get modify permissions to groups Shares, never Full Control.
#EXTREMEZ IP MAC#
Two things to do to help with Mac file sharing issues.
#EXTREMEZ IP PRO#
Do you have any tooling for managing Macs? JAMF Pro for example. I’ve used it in the past, it works but it’s not really needed. I've been in Support team for 7 years in various positions: Expert Engineer, Trainer, Service Providers Support but till this moment had no idea that we have some other separate Support team, though guys working with ExtremeZ-IP (Acronis Files Connect) are sitting on the same floor with me :))) In regards to other products - same as above - I would use any opportunity for the Company and for Support team to learn and would like to ask to share support case numbers if you do please. I would really love to learn more about your out-of-the-box experience other than Apple bug described in the KB article you're referring to.Īcronis support via ExtremeZ-IP is decent as it goes through another company but damn their support for other products suck. Users reported to be in the same file 8 times over, sometimes they have 18 files open, then 3, then 15 the next second when they're not doing anything - it's crazy.
#EXTREMEZ IP MAC OS#
It's bugged on Mac OS 10.9-10.12 as found here: - this causes lots of file locking and oddities for us.
#EXTREMEZ IP HOW TO#
Seems to follow Acronis' trend of not working effectively out of the box - or have any useful documentation on how to implement it. Then we applied an explicit ACE on "test" granting full control the group "Users".įor more information see also ExtremeZ-IP: Troubleshooting Windows Server Access from Mac Clients.Hi /u/sysadminarino! Thanks for your feedback! You can see on the screenshot below that the child folder "test" did not inherit the read only ACE from the parent folder "Share" pictured in the screenshot above. This will support the safe save operation documented in the Apple KB article at TemporaryItems at the root of all shares would need an explicit ACE granting pretty much full control to everyone. Then on the child folders, apply an explicit ACE granting permissions to each particular group. That way the staff group ACE will not inherit down but the SYSTEM ACE will. If you need restricted permissions at the root of a share, the best advice we have been able to give is to apply an explicit ACE with limited permissions, such as read only, for a staff group to a parent folder, typically the directory that is being shared and change the "Apply to" setting to "This folder only" so the clients can mount the share. CREATOR OWNER, Full Control, Applies to subfolders and files onlyĪ note regarding CREATOR OWNER: since it applies to subfolders and files only, Full Control will display as "Special" on 2008 and above.įor typical workfiows, the Mac users will need all the granular NTFS permissions except Full control, Change permissions, and Take ownership.SYSTEM, Full Control, Applies to this folder, subfolders, and files.Administrators, Full Control, Applies to this folder, subfolders, and files.The default rights we expect to see inheriting from the drive letter are:
0 kommentar(er)
