"Connect to Server" questions
What is the best way to push out a "Connect to Server" UNC/URI to Mac OS X clients?
I have a new server that my Mac uses will need to access. Is there a way to update all my Macs to have a new SMB based URI in their "Connect to Server" dialog box using ARD or SSH?
Worst case scenario is that I email my Mac uses and tell them how to add a "smb://new_server_name" URI on their Macs, but I hate doing that ,as many users will not understand what I am talking about, or they will type the path wrong, etc. I would rather blast out the new URI remotely for them at night.
I played with the ~/Library/Favorites folder a little bit (including the ".afploc" and ".inetloc" files), but the behavior is a little funky. Can I just send out a .inetloc file to my users?
It looks like the URI info in the "xxx.inetloc" and "xxx.afploc" files in NOT in the data fork, but instead is in the resource fork of the "xxx.loc" file. Is that correct?
I have a new server that my Mac uses will need to access. Is there a way to update all my Macs to have a new SMB based URI in their "Connect to Server" dialog box using ARD or SSH?
Worst case scenario is that I email my Mac uses and tell them how to add a "smb://new_server_name" URI on their Macs, but I hate doing that ,as many users will not understand what I am talking about, or they will type the path wrong, etc. I would rather blast out the new URI remotely for them at night.
I played with the ~/Library/Favorites folder a little bit (including the ".afploc" and ".inetloc" files), but the behavior is a little funky. Can I just send out a .inetloc file to my users?
It looks like the URI info in the "xxx.inetloc" and "xxx.afploc" files in NOT in the data fork, but instead is in the resource fork of the "xxx.loc" file. Is that correct?