MCX Login Items: Mounting Server Volumes

I noticed that when you set up a policy for a user,group or computer to mount a remote volue at login, you will get a Finder error if the volume can't be mounted for some reason (i.e.; the server is down, the volume is not available etc. This can be handy for troubleshooting.
Is there a way to surpress the error, so my mobile users dont get an error when the remote volumes are unavailable?
Example: A lot of my Mac users will have laptops, and thus sometimes they will be away from our LAN. I want they to still be bound to OD and have cached MCX settings when they are on the road. However, I dont want the users to get "Volume could not be found" errors.
Message was edited by: Daniel Stranathan

I think you should be able to use AppleScript to mount the volume, put that code inside a "try" construct, and leave the "on error" blank. Like this:
try
tell "Finder"
mount volume "afp://[user]:[passwd]@[server hostname or IP]:/[sharepoint]"
end tell
on error
-- do nothing
end try
I haven't tried this, but thought it might work.

Similar Messages

  • Mounting Server Volumes Via Startup Items

    I'm going crazy here trying to figure out what's going on with my wireless AirPort network!!!
    While trying to set up the first G4 iBook (10.4.2) from an Apple wireless cart I've discovered that I can't get a server volume to automatically mount at startup. I'm connecting to an AirPort Extreme base station. The iBook has no problem detecting and connecting to the base station and allowing an Internet connection and you can manually connect to a file server. But if I add a server volume to the Startup Items I can't get it to mount the volume at startup.
    Here's some stuff I've done to try to isolate the problem but nothing seems to point to a solution:
    - If I connect via Ethernet, it works everytime - so the issue is definately AirPort related.
    - Since I have 3 other independent AirPort networks (Extreme & Dual Ethernet) I tried connecting to them - no help.
    - After startup is finished I can connect manually (Go/Connect to Server).
    - Here's a real stumper... If I log out (not a reboot) & log back in - the volumes mount!!!
    - Up until now I had my personal eMac (10.3.9) connecting and mounting the same volumes via one of my previously mentioned AirPort networks with no problems. In trying to solve this problem I cleared out my Startup Items, Keychains, etc. - now I can't get it to work either.
    - I tried setting a new user in case it was some fouled up user setting - no help.
    - I've cleared out and set up Keychains & Startup Items numerous times - no help.
    - I disabled security - no help.
    So in my opinion I've ruled out the following by process of elimination:
    - System hardware - problem exists with eMac & iBook
    - OS - problem exists with 10.3.9 & 10.4.2
    - Base station - problem exists across differing base stations (Extreme & Dual Ethernet) & differing networks
    - Users - problem exists with new user
    - Security - problem exists with security disabled
    Here's the one thing that seems evident....
    The connection to any Airport network takes a momentary delay during startup - enough to cause to Startup Items (server volumes) not to mount. Since I can connect to the server manually shows that the AirPort connection is good. Logging out & then back in uses an AirPort connection that is already established and then will mount the Startup Items (server volumes).
    I've seen some Internet posts that suggest using scripts to somehow delay certain Startup Items from executing until an AirPort connection is established - I would rather avoid that mess. There's got to be a better solution! This seems to me like a very basic function that shouldn't take scripts or other such voodoo!
    I'm all out of ideas.....
    Dave

    Hi Dave,
    I recently had the same problem. I think a recent update messed up the way I was using applescript to mount drives. I would get messages while the script ran that would indicate things timing out while looking for drives. After reading through a lot of forums I found that this script worked for me:
    tell application "Finder"
         mount volume "afp://user:[email protected]/VolumeName"
    end tell
    This is for mounting a Mac server volume. I think you use smb:// for a win server.
    Let me know if this works for you.
    Herb

  • First Volume Alias in Login Items Aways Fails

    I am using OS X 10.4.5.
    I have a number of Volumes in my list of Login Items. The first one always fails to mount, but the others mount without any problems. It doesn't matter which Volume I put first in the list - it always fails.
    The Volumes are share points set up on the server, OS X Server 10.4.5.
    Any suggestions?

    When I look at the path of the CLOSET in Login Items, it reads /Volumes/CLOSET, so I can't even figure out how Mac knows how to find it and connect to it.
    Another strange detail is that when you try to open one of the applications that has a database in the CLOSET, the CLOSET connects immediately. I haven't tried to create a text file or something in the CLOSET and try to connect to it, but I will try that.

  • ZFS tries to mount SAN volume before ISCSI is running

    I am running Solaris 10 x86 U7. It is actually a VMWare guest (ESX4) on a Sun X4170 server- although I do not believe that that is relevant. I have a Sun 2510 iSCSI SAN appliance. I have an iSCSI volume with a ZFS Pool that is mounted on the server. All was fine until yesterday when I installed the following patches:
    142934-02 SunOS 5.10_x86: failsafe patch
    142910-17 SunOS 5.10_x86: kernel patch
    144489-02 SunOS 5.10_x86: kernel patch
    142912-01 (as a dependency requirement for one of the others.)
    I had installed the patches in run level 1 , then switched to run level S to allow the patch install to finish.
    Now, when I restart the zfs volume on the san is marked as off line. the /var/adm/messages shows the following
    Nov 7 00:26:30 hostnameiscsi: [ID 114404 kern.notice] NOTICE: iscsi discovery failure - SendTargets (ip.ad.dr.ess)
    I can mount the SAN ZFS pool with
    #zpool clear ZFSPOOL1
    #zfs mount -a
    For iscsi device discovery, I am using send targets (not static or iSNS.) I am not using CHAP authentication.
    It seems to be me this may merely be a timing in services and not fundamentally an iscsi issue. Can I tell the OS to wait for a minute after starting iscsi service before continuing with zfs mount and autofs shares? Can I tell the OS to delay mounting non OS zfs pools?
    Thanks

    Here is what I tried. Installed Batchmod and Xupport on each of internal system disk, backup internal system disk and external system disk. Batchmod could not find the folders automount or Network.
    Booting from external disk, I made hidden files visible using Xupport, then deleted automount > Servers, automount > Static on internal disk and backup disk. The folder Network had no files or folder named "Server". Booting from internal disk, the desktop tried to mount server volumes. Examining the internal disk automount folder showed aliases for "Servers" and "static". Get Info said they pointed to originals "Servers" and "static" in folder /automount but these items do not appear in the Finder.
    Sometimes icons, not aliases, for "Network", "Servers", and "static" appear on all three desktops on login. Trying to eject these icons by dragging to Trash or highlighting and clicking File > Eject has no effect. Examining Users > Username > Desktop does not show these items. Sometimes ".DS_Store" appears on desktop and in folder Users > Username > Desktop.
    Next I deleted user accounts so that all system disks are single user. Booted up on External disk and deleted automount > Servers, automount > Static on internal disk and internal backup disk or their aliases, whichever appeared in Finder. Booting up on internal disk results in... desktop trying to mount server volumes.
    Will try an archive and install on internal disk.

  • Missing server volume

    We have a G5 set up as our server, runninf Snow Leopard Server which has shared volumes on, which we can all access.  I didn't set this up to start with, so bear with me...!
    I think the hard drive is partitioned, as there are three volumes shown on the desktop (or should be). One is called "server" which is the regular hard drive - contains apps, library, etc. This isn't shared. One is called "xxx server" which contains all our working files - this is shared. The other is called "FTP server" and this contains folders that we can share with others outside the company, to exchange larger files.
    Normally, all of these volumes show on the server desktop. When I go into server admin, I can usually also see all of the volumes listed under the "volume" tab and then I can see the individual share points within those volumes under the 'share points' tab. 
    Yesterday, I had a problem with a DVD which caused the whole server to crash.  I restarted and everything looked normal APART from the "xxx server" was missing from the desktop.  When I look in server admin, it's not listed under the volumes tab. The share points are listed, but they're saying that the volume can't be found.  When we try to access from another mac on the network (via apple-k, as usual) it finds the share points on 'FTP server' but not the ones on 'xxx server' - they're just not listed.
    Does anyone know what might have happened to my volume?  We really need to get it back, as it's got all our working files on it!!   I do have a BounceBack backup that is from the evening before, so worst case scenario I could restore that (could I? Even if the volume is missing? Where do I restore it to??) But because BounceBack is incremental there would be a lot of tidying up to do to get the files back to the state they were in before this happened!
    Any help would be much appreciated!! 

    Here is what I tried. Installed Batchmod and Xupport on each of internal system disk, backup internal system disk and external system disk. Batchmod could not find the folders automount or Network.
    Booting from external disk, I made hidden files visible using Xupport, then deleted automount > Servers, automount > Static on internal disk and backup disk. The folder Network had no files or folder named "Server". Booting from internal disk, the desktop tried to mount server volumes. Examining the internal disk automount folder showed aliases for "Servers" and "static". Get Info said they pointed to originals "Servers" and "static" in folder /automount but these items do not appear in the Finder.
    Sometimes icons, not aliases, for "Network", "Servers", and "static" appear on all three desktops on login. Trying to eject these icons by dragging to Trash or highlighting and clicking File > Eject has no effect. Examining Users > Username > Desktop does not show these items. Sometimes ".DS_Store" appears on desktop and in folder Users > Username > Desktop.
    Next I deleted user accounts so that all system disks are single user. Booted up on External disk and deleted automount > Servers, automount > Static on internal disk and internal backup disk or their aliases, whichever appeared in Finder. Booting up on internal disk results in... desktop trying to mount server volumes.
    Will try an archive and install on internal disk.

  • Delay Login Items?

    Hi,
    I have a computer (Com1) that's connected to another computer (Com2) via Firewire, in order for Com1 to connect to the internet. There's a folder (CLOSET) on a server that all the computers connect to on login. All the other computers in the school connect just fine to the folder, as I dragged the folder to the login items after I had connected to the server. The normal computers simply mount the volume CLOSET at startup, without having to connect to the server. However, the computer connected to the internet/network via Firewire starts up with the message that it can't connect to the server. I want to delay the login items to ensure that Com1 connects to the network before trying to mount the CLOSET.
    I have tried using a third-party app (DelayedLauncher) to mount the CLOSET after 15 seconds, but it can't seem to find the volume, considering the CLOSET lives on the server that Com1 is not yet connected to.
    Mac's Login Items finds the CLOSET just fine, so I'd like to find a way to simply delay or re-run Mac's native Login Items feature.
    If this is not possible, is there a way to write a script to do the mounting the way the Mac remembers how to do it? The problem is that to connect manually, you must first connect to the server. Then you must select Guest. Then you must hit "Connect." Then select the volume CLOSET to mount. I can't figure out how to navigate through all the necessary selections in AppleScript.
    Thanks for any help provided.

    When I look at the path of the CLOSET in Login Items, it reads /Volumes/CLOSET, so I can't even figure out how Mac knows how to find it and connect to it.
    Another strange detail is that when you try to open one of the applications that has a database in the CLOSET, the CLOSET connects immediately. I haven't tried to create a text file or something in the CLOSET and try to connect to it, but I will try that.

  • Prefs code show server volumes in sidebar by default?

    I support a K-12 installation of around 4000 Macs, roughly 1000 of which are now running Leopard. I'm creating a new image for these systems, and cleaning up glitches, including this one:
    In Tiger, mounted server volume names appeared in the sidebar below the hard drive icon in any Finder window. When you click on the volume name, the contents of that volume are immediately available as any regular disk would be. When you click the eject icon beside the volume name, only that volume is ejected.
    In Leopard, the server name appears in the sidebar instead of the volume name. The server name is not particularly meaningful, since it's the volume name which our users recognize. When you click on the server name, a list of available volumes appears after a longish pause. This also creates confusion ("what are those other names?" "can I save there?" "why do these appear?"). When you click the eject icon beside the server name, all mounted volumes are ejected. Many of our education applications don't handle well this new way of accessing server volumes -- some crash, some hang when you click on the server name instead of a volume name. This is a serious reduction in ease of use for our end-users! Now they have to deal with the confusion of clicking on an unfamiliar item like the server's name, then figure out which share they want to use, and finally save their document ("why can't I save to the server like I can save to my USB key?").
    I haven't yet found a way to reproduce Tiger Finder's shared-volume-in-the-sidebar behaviour as a default, beyond manually dragging each server volume to the sidebar (not an ideal solution, since volume names change, and servers change). Is there some XML key I can add to the Finder prefs to revert to the old way of displaying server volumes in the sidebar?

    Hi,
    I have the same problem (and there are threads archived starting 2007 dealing with the same issue) This is not a SERVER problem. Its simply that the 10.5 finders sidebar does not show mounted volumes or mountpoints anymore. Instead of that you see whole servers, which makes navigation slow.
    Any way to get TIGERS behaviour back?

  • ITunes Library incorrectly linked to Mounted Server

    Hi there,
    I've got a huge problem. I, foolishly, tried to share my iTunes library between my iMac and MacBook yesterday doing the following:
    1. In System Preferences I added both my iTunes Music folder, which is located on an external hard drive and holds all my media files and my iTunes Library files, which are located locally on my iMac (Home - Music - iTunes)
    2. On the MacBook, I opened iTunes and then under the preferences, selected the iTunes Music folder which now showed up within the finder when I selected the Shared - iMac option.
    3. I then optioned click iTunes on the MacBook Pro and selected the iTunes Library as shared above (again, it showed up in Finder under the Shared option, where I clicked on the iMac symbol and was then able to pick the library folder).
    On the MacBook Pro, when I now open iTunes it properly shows my iTunes library as it used to be on the iMac and when I add songs it adds them wirelessly to the external hard drive and updates the library, playlist, play count etc.
    So far so good. That is what I wanted. Well at least until I went back to my iMac opening iTunes there and now while all the songs are still listed (including the new ones I added from the MacBook), all the songs in iTunes on the iMac have the exclamation mark next to them.
    Double clicking a song brings up to boxes then. The first box says: "Connection failed. The server "iMac" is available on your computer. Access the volumes and files locally." When i hit okay, i then get a second box coming up saying "The Song "XYZ" could not be used because the original file could not be found. Would you like to locate it?". If I hit Locate, I can go through to the external hard drive selecting the song and it plays, but my iTunes library is fairly extensive so it's not feasible to do that with all the songs.
    What I think happened is that somehow the iTunes library files have been updated so to link to the iMac as a mounted 'server volume' when on the home network and while this works fine on the MacBook, the iMac still seems to link to the 'network' twin of its files rather than using the 'normal' library stored on its hard drive.
    Is there any way I can revert back to the original set up - i.e. have my iTUnes library on my iMac, not sharing it etc. I've tried to remove the shared folders under the system preferences etc but nothing works so I'm a bit stuck as the last thing I want to do is to remove all the songs from iTunes and re-add them as I would like to keep the order they were added as well as the play count, dates and all that.
    Thank you soo much for any help anyone can offer.

    You'd be better off starting a thread of your own, this is quite an old post. Also there are a number of issues in the original post so it's unclear from yours which one you are experiencing. If you are unsure of how to add a new topic, click on the Help & Terms of Use link in the box to your right or click here: Discussions Help & Terms of Use"

  • Why don't network volume mounts (login items) configured in Profile Manager show up

    Using Lion server and Lion clients.  Bound both the server and client to Active Directory and successfully got Profile Manager up and running.  All I really need from Profile Manager is the ability to mount network volumes so when the user logs in it mounts their home directory.  Please note we do not specify any home directory paths in AD.  I can login with my AD accounts on the Lion client and get other Profile Manager settings to work, however when I try and mount a network volume via login items nothing happens.  I am using SMB for this.  If I try to manually connect to the same path via Go -> Connect To Server it works fine.  For a simple test I even created a folder on one of my Windows servers D drive and shared it and within profile manager configured it as SMB://server/share and still nothing.  I tried setting it in the Dock section as well which I read in another post somewhere but all I get is a question mark.  I have tried all variations of server name, FQDN, ip address, etc.  I know it's not permissions since it works when I try it manually so am really at a loss here.  Is there any way to log what happens at login to see if it's even trying to mount the volume?  I do know the client is getting the profile since i can see it in system preferences but it never works.  Any ideas would be greatly appreciated, thank you!

    @bkma did you find any solution? i run into the same problem.

  • All Network Volumes set as Login Items open in Finder on EVERY startup

    ...after updating to 10.5.8
    I have a Mac running on an otherwise all PC network. Before updating to 10.5.8 I had 5 network volumes set to "connect" on startup automatically (System Prefs / Accounts / Login Items). This worked perfectly and connected to these volumes silently without me having to ever worry about it. I didn't even have to check the "Hide" boxes.
    After updating to 10.5.8 however, it became completely annoying. Now it still connects to these volumes, but opens up every single one in Finder upon every startup. That's 5 windows I have to close every time I startup my computer. It may not sound like the worst thing in the world, but mind you I have to log out and back in every day for work. Even checking the "Hide" checkboxes don't do anything.
    Anybody experiencing the same problem? Anybody know a workaround or fix? My company has a rather large and complex network so staying connected to certain folders that I use is a must. Thanks.
    Screenshots:
    Login Items - http://img.photobucket.com/albums/v326/Magick0ne/Other/Login_Items.jpg
    Every Startup - http://img.photobucket.com/albums/v326/Magick0ne/Other/Finder_Windows.jpg
    Message was edited by: Pifman

    Pifman wrote:
    Thanks to both of you. I guess the search I ran wasn't good enough as I didn't find the discussion that you posted.
    One of the possible workarounds posted there was to use a third-party program that I found difficult to understand and use. Instead I took V.K.'s advice and made an AppleScript and then made that script launch at login. Works like a charm.
    Only difference is that my AppleScript isn't located in the Utilities folder (10.5.8), instead I got to it by going to Applications / AppleScript / Script Editor.
    sorry, my mistake on the location.
    Then I made a script and saved it as an application. I then put that application in my Login Items (System Prefs / Accounts / Login Items).
    If you're having trouble finding the mount volume (or server) address, here's how you can find it: If you are currently connected to the volume(s) that you want to use, left-click it and hit Cmd+I (or right-click, Get Info). Use the address next to "Server:" - That's it!
    Hopefully Apple will fix this bug soon so people don't have to make AppleScripts just to make the OS work correctly.
    I wouldn't bet on it for leopard. leopard development has stopped now after snow leopard has been released. historically, Apple only releases security patches for old OS versions once a new one comes out. Interestingly, this bug is present in snow leopard too! or maybe they don't consider it a bug and this is how it should work. one can make a case for this, I guess.

  • Login Items Remote Volume, always open window on Boot

    I've set up connecting to a drive on a network, and then dragged the volume into the Accounts/login items. So that everytime it reboots it connects to theses volumes, however each time it does it also opens a window for each of them. I have ticked the hide box next to them, but neither makes any difference.
    Thanks
    Matt

    Yes, that is one way to do it. I usually make a shell script and package it as an application using Platypus.
    To do so you would use a text editor (I prefer pico) to create a script file with the .command extension and make it executable. The syntax is as follows:
    mkdir /Volumes/yourvolume
    mkdir /Volumes/anothervolume
    mount_afp afp://username:password@server/yourvolume /Volumes/yourvolume
    mount_afp afp://username:password@server/anothervolume /Volumes/anothervolume
    Of course you can leave out username:password@ and you can use mount_smb as well as other protocols.
    http://www.sveinbjorn.org/platypus

  • Login Items connect to server in 10.5.6

    When you select a server volume in System Preferences / Accounts / Login items / to open a directory on a network server every time you log in, in system 10.5.5 and earlier the directory will be automatically opened on your desktop after startup.
    Not any more in system 10.5.6. The connection is made but the map will not be automatically openened any more (even when "hide" is not selected).

    Sounds like a tip that you should post to the server forums. Unless I missed something, there doesn't appear to be a question in your post.

  • Workgroup Manager - AFP Login Items no longer mount

    A wierd problem.
    I have the same URL in my Login Items for all of my groups in Workgroup Manager. It is to mount a folder share. After logging in as any network user, the share will not mount, and I do not even receive an error saying that it couldn't be mounted. Also, while still logged in as a network user, even as an admin network user, and I click "Go...Connect to Server" I can connect to the server, but the share doesn't even show up, though all the other shares do. Also, when I log in locally as an administrator, or from any other computer not going through OD, I can browse to the server and hit the share.
    In my attempts to trouble shoot, I have changed the URL for the share in Login Items to mount the share with SMB, and it does work.
    Seems as though the problem is taht the share is being blocked to all network users when logged in through OD.
    What do you suggest?

    In Server Admin, under file sharing. Select your sharepoint.
    Click the "Share Point" button below the file browser.
    Check to make sure that all the settings are correct.
    ie, if it's not a home folder location don't have auto mount checked. Also in the protocol options, check to make sure that you have the right protocols selected. AFP and SMB are probably all you need.
    -Graham

  • Shortcut to new server volume mounts old server

    I have recently transferred all files from a Windows NT Server and a Windows 2000 Server to an OSX Tiger Server. I duplicated the files to the new server using Retrospect but have left copies on the old server in case anything was missed.
    On my four OSX Panther G4s, I have mounted the new server and created shortcuts (aliases) to the new volumes. Three of them work fine. On the fourth G4, however, the aliases to the new server mount the volumes on the old server! I have deleted all the aliases and recreated them to no avail. I have deleted the aliases to the old server entirely and all is well until it becomes necessary to mount the old server. Even if the old server is mounted manually, the next time the aliases to the new server are used, they will mount the old server.
    All four G4s access the servers via AFP because we still have OS9 workstations which need to access the same files.
    Any suggestions?
    PowerMac G4   Mac OS X (10.4.4)   Server

    Hi There!!!!
    In Exchange 2010, clients do not connect directly to the mailbox role, they go through the
    CAS role, so it sounds like you need to set the RPCClientAccessServer to point to the new Exchange 2010 server.
    Do this via PowerShell : 
    GET-MAILBOXDATA | SET-MAILBOXDATABASE -RPCCLIENTACCESSSERVER <FQDN OF NEW CAS SERVER>
    But as you have 160 mailboxes to migrate , which would be quite time consuming and needs lots
    of efforts, so rather than opting manual way for migration  I would refer you to do this using any professional Migration Software like Stellar Mailbox Extractor for Exchange Server, which can perform the Migration of 160 mailboxes in quick time. 

  • Hide Volume als Login Item doesn't work

    Hi folks!
    When I login into my account on my mac all network volumes appear despite the hide-configuration in login items. Are there any ways to resolve that issue?
    Thanks...
    Timi

    see this link for a workaround
    http://discussions.apple.com/thread.jspa?messageID=10511740&#10511740

Maybe you are looking for