Hi, this is a cut down version of the script we use sometimes:
#!/bin/bash
username="$3"
if [ -z "$username" ]; then # Checks if the variable is empty (user running script from Self Service)
username="$USER"
fi
echo "User: $username"
protocol="$4" # This is the protocol to connect with (afp | smb)
echo "Protocol: $4"
serverName="$5" # This is the address of the server, e.g. my.fileserver.com
echo "Server: $5"
shareName="$6" # This is the name of the share to mount
echo "Sharename: $6"
# Mount the drive
mount_script=`/usr/bin/osascript > /dev/null << EOT
tell application "Finder"
activate
mount volume "$protocol://${serverName}/${shareName}"
end tell
EOT`
exit 0You add the script and set the parameter labels as:
Once thats in place you can re-use the script in a policy, setting the relevant options:
Hope this helps.
Hello everyone, despite the not so encouraging comments and suggested alternative routes, I am testing config profiles to manage network volumes with a "login items" payload.
I can limit the profile (applied at user level) to a specific Active Directory usergroup and its network volumes.
This all seems to work fine, except when the computer if off network (e.g.: laptop)
When there's no network available, being the profile still there, an error message appears in the Finder, as the server is obviously not reachable
Would you think there's a workaround for this?
Many thanks for your help!
Ciao
Carlo
