Mac os x automount afp share

Any time you modify the map files you need to inform the automount service in order for them to become active:. The only option that you are likely to ever want to change is the timeout period. This is time that the automount service will wait before unmounting a filesystem that has not been accessed. It should be noted that filesystems that are automounted in this way will not show up automatically in the sidebar of the OS X Finder application.

Nor will they automatically appear as disk icons on the desktop. If that is important you may want to simply add the share as a login item and have it mounted whenever you login. For filesystems that are accessed by scripts or applications I prefer having them automatically mounted and unmounted in the background on demand.

Use Your Loaf. Why automount may be useful I have a number of remote filesystems that are stored on Network Attached Storage NAS devices connected to my local network wireless router. Create a local mount point To get started you need to create a local directory that will be managed by the automount service. You will need to use sudo to create the directory: This assumes that anonymous access to the filesystem is allowed otherwise you need to include a username and password e.

Automatically Connect to a Network Drive on Mac OS X Start Up & Login

Add each new filesystem map on a separate line. Activate the changes Any time you modify the map files you need to inform the automount service in order for them to become active: Unsubscribe at any time. See Privacy Policy. Not to mention, if the volume is already mounted, the volume they want to go to will be grayed out since it is already mounted. This happens on our end, not sure about everyone else.

Sure, it's on the desktop and they can get to it that way, but it's creating an extra step for some not so tech savy users. I second what cizdziem is saying, while it is not respecting the absolute path. When mounting the volume, it will bring you to the root level of the share; forcing users to scroll through hundreds of shares they don't have permissions to to find theirs. Even though the path displayed to users should mount their specific share.

No password is needed just like what was said in the above post. Does anybody know if Authenticated Network Mounts are affected by this? Whats frustrating about this is that this could have easily been a non-issue with some MDM framework from Apple, something like a trusted network locations payload that can allow shares to operate in their previous state, but instead the changes have been made without any consideration to the education and enterprise environments.

Even if this is an 'intended solution' we are still unable to add network locations directly to a network share as it only maps to the root of the server, if this is intentional and not a bug then I cant see any reason why this has been done. In our specific case we use AppleScript to tell the Finder to "open location" and then specify the server mount path.

After applying the update the users are prompted to connect and enter their password if not in the keychain or prompted to connect with the password pre-filled, if it is in the keychain, however in both cases the next window is 'Select the volume' regardless of specified share path. The behaviour is similar to that described in this article: Interestingly pasting the full mount path, with username and password as created by our script, e.


  • share outlook calendar with mac ical.
  • macos - OSX automount AFP network volume? - Ask Different;
  • ftp programm mac os x freeware?
  • Using the Mac OS X automounter;
  • mac os external hard drive wont mount.

This is a real nuisance for us. I would really appreciate it if we could get a definitive answer if this very specific behaviour is a bug or a 'feature'. Like they were thinking of the Connect or Cancel box that pops up the first time you connect to a new share. Everything prior to the latest updates and the shares mount just fine.

TL;DR / Solution:

The typical scripts I had failed to connect to the shares, even with user authentication, unless the user manually did Connect to Server through Finder. Ended up making a simple script into an app to open the shares for now Since that communication, I've had further correspondence with him that makes me confident he understands the scope of the issue. Additionally he stated that the engineering team said the "specific security consideration this change was made for impacted NTLM only.

The current fix applies before any credentials are even checked NTLM or kerberos. He's also "arguing that training end users to ignore password prompts is problematic" due to the fact that users don't actually have to provide a password when prompted to Connect, despite the presence of an empty password field.

Automatically Connect to a Network Drive on Mac OS X Start Up & Login

As jordan. We use NoMad to facilitate mounting the user's network share. We also want to echo the issue all the way from When mounting the share, normally the share will auto mount and opened to the user; now, there is another prompt and all the shares are visible to the user prohibit signs obviously. The user then will have to figure out the absolute path. This creates a less-than-ideal situation for our lesser-savvy users.

We have submitted a ticket with JAMF about this and from the response, the problem is not unique.

2) Setting Up Automatic Connections to the Network Drive on Login

My co-worker erik. Took some time before we realised this effected I have rewritten our mount procedures using a signed AppleScript.

77 comments

One being able to re mount the server in the background transparent without disturbing the user using the -g do not bring app to front key. The second being able to place these "servermount. The mounting of the servers is done with a script triggered by two launchagents - one for network change and one for login of the user. Thanks very much for posting your workaround. Would you mind sharing the contents of your servermount.

Keep Network Drives Mounted on Mac OS X using Autofs

This in my opinion presents a security risk by exposing the names of potentially sensitive shares to users without access permissions. I've found a mounting method that bypasses the issue. Use the AppleScript "mount volume" command:. Below is the AppleScript I package as a signed run only app the script is found somewhere in the internetz. I see the same thing as you do with all shares on the server you want to connect to being shown using the old method with open "afp: However, we are testing nomad as an option for shares and it seems to not be affected by this security patch.

If we move to use Nomad instead, then we have to figure out how to remove the dead link that is auto-created in the dock. If i replace it with a simple mount volume "afp: I've also had issues with smb shares in the Dock not working on I have logged a bug report with Apple which is currently with engineering.

The macOS From the "Resolved Issues" section of the I've asked my AppleCare support rep if there are plans to apply this resolution to I can confirm that everything is working as usual with the