Stay tuned for the confirmation of the solution proposed. Later this day, I am gonna try with the other MacOS app and more in-depth testing. This was tested only through FreeFileSync (for now) both sides: from L to R and viceversa, either with new files as well as simply modifying the file name. 2, is described a potential solution to the matter: change the Share permission for Everyone from Full Control to Modify.Īfter reading that, I then modified the permission as stated and BOOOM: I got perfectly clean NTFS security permissions, without that weird Account unknown. Thanks to both for your quick replies, but in particular to who gave me the starting (useful) hint.ĭespite I cannot understand the connection with NFS, because the shared folder is not an NFS shared but a standard SMB one, I have started to look around on the net and found this topic on the Edugeek forum: files and folders synchronised from MBP to WS2016 report my_domain\my_ad_account as owner, so they are recognised as created by that specific AD account.MBP has joined my AD domain and I login to MBP with my AD account.Instead of doing this manually you can import an ffsbatch file via Menu File Open or simply via drag and drop. The website cites Arch Linux, CentOS, Debian, Fedora, Manjaro, Mint, openSUSE and Ubuntu. On Linux many well-known distributions are supported. macOS 11.0 'Big Sur' down to Mac OS X 10.10 'Yosemite'. As of June 2021 the then current version 11.11 of FreeFileSync supported the following operating systems and versions: Windows 10 down to Windows 7. The security rules applied to the \\server_ip\homes$\username\Documents is the following:ĭo you have any clue why this unknown account is being created and how to avoid it? Start RealTimeSync.exe located in FreeFileSync's installation directory and enter the folders you want to monitor. FreeFileSync is available for 32bit and 64bit operating systems. This happens any time I perform a synchronization from the MBP to the file server, for any file/folder synced and for both applications, so I guess it is not a matter of the application used. They do what they are intended for, but during the test phase I have noted that the synced files/folders (from MBP to WS2016) show in the Security tab an " Account unknown", with the security rule DENY applied to "This folder" only, as in the following screenshot. files/folders previously synced (see a.) could be edited, so when backed home, they should be synced back to the file server.įor managing those above tasks, I tried some applications for MacOS systems: Chronosync and FreeFileSync. System One System Two OS: macOS (plus VMs: Windows XP, 7, 10 Home/Pro, 11 Home/Pro, Linux Distros). MBP could have new files/folder which have to be synced to the file server when backed home Ĭ. some files/folders have to be synced on the MBP prior leaving home ī. For an intelligent storage management on the MBP, I don't have a replica of the entire file server obviously, so when I am on the road I have the following needs:Ī. Database > Internet Software > FreeFileSync Uninstall FreeFileSync Guides How to Remove FreeFileSync for Mac Hard to uninstall FreeFileSync from Mac Dont know where the file is or where to start the removal This post is all about the how-to guides to help you remove this program from Mac. I have a MacBook Pro (MBP) which I wanna get in sync with the file/folders stored centrally on my home file server (running Windows Server 2016).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |