![]() The groups sys, wheel and operator only contain user "System Administrator". "Staff" group is only used for local accounts, network accounts are member of group "Workgroup" by default. ![]() Regarding mentioned groups: with this checkbox "Administer this server" enabled, the user is added to the group "Administrators" (admin). From now on, "testuser2" is able to use the share, but "testuser1" still doesn't (with error message that no shares exist, as before). Then I gave "testuser2" the rights to admin the server (enabled checkbox in account profile). > both users can't connect to the serverĭrwxr-xr-x+ 2 myserver admin - 68 23 Nov 01:20 TestĠ: user:testuser2 allow list,search,readattr,readextattr,readsecurity,file_inherit,directory_inheritġ: user:testuser1 allow list,search,readattr,readextattr,readsecurity,file_inherit,directory_inherit created folder "Test", set permission rights to "read only" for both 3. added users "testuser1" and "testuser2" as Network Accounts 2. I'm really confused about the logic behind and would like to ask you for advise. I suspect that membership of admins group doesn't make the difference directly, but this group is probably also member of another system group which enables the connectivity in general. ![]() But then user is member of the group "Administrators" (admins) and I don't know what this means for server security. The access rights are also correctly shared. □ĭuring my tests, I found the following strange behaviour: if the "admin" flag is set in the account profile (see above picture checkbox named "Diesen Server administrieren" in german), user is able to see all shares and also connect properly. I did also the same on another iMac without macOS Server installed and it worked perfectly. It also makes no difference using SMB or/and AFP. I already spent hours with a lot of different settings and tries, even with Open Directory enabled and using Network Accounts instead of local ones, but it didn't help. However, it doesn't work (server is refusing/rejecting). ![]() set up a file share with user credentials (read, read/write doesn't matter for this issue)įrom my perspective, user "testuser" should now able to connect to the server and access this share, right? I indend to mainly use it as my file server and did the following: Obviously, don't click on any suspicious links in the reviews, and have a nice day/night.MacOS Server 5.4 was freshly set up on iMac with High Sierra 10.13. I notice a handful of people that come here spamming viruses and porn ads, and I feel like I'm partially responsible for reviews like that. It is version 12.6.06, and 12.6.03 was used to circumvent an error preventing me from creating the file. I changed it to 12.6.03 so when you boot up this ISO, and quicklook at the app inside you may see that it says 12.6.03. macOS Server 5.4 Beta Question The release notes for the macOS Server 5.4 beta state, 'Caching Server, Time Machine Server, and File Sharing advanced options are now built directly into macOS.' However, there is no mention of how to manage these features in macOS High Sierra. I had to modify ist () to change the app version in order for it to work. dmg file also installs the application to your Applications folder.į2 - The app used to make the ISO was downloaded prior to Sierra being invalidated from the App Store, and also prior to being added to the support article in PKG form.į3 - When using the app to build the ISO, it failed. (Keep in mind that opening and running the. app/Contents/SharedSupport (This generates the app, and I will explain how the app is used) Move InstallESD.dmg to Payload/Install macOS. pkg file was unziped using pkgutil -expand-fullĢ.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |