Thought I would share that I have been successful at deploying UrBackup to remote mac users with Jamf. It was fairly straight forward. I’m using mac client version 2.4.11 and server version 2.4.13.
I created a new group on the server with the settings I desired. (wildcards are not acceptable when defining a backup directory)
I uploaded the client .pkg in Jamf Admin.
I built a .mobileconfig to allow UrBackup Full Disk Access using PPPC and uploaded it as a profile into Jamf and pushed.
I wrote a super simple script in Jamf with the following:
#!/bin/bash
# modifies settings for urbackup to point to the server and aquire settings from the server
# we'll need 2 parameters: the name of the client that was generated on the server and the internet auth key
# $4 = clientname
# $5 = internet_authkey
/Applications/UrBackup\ Client.app/Contents/MacOS/bin/urbackupclientctl set-settings -k internet_mode_enabled -v true
/Applications/UrBackup\ Client.app/Contents/MacOS/bin/urbackupclientctl set-settings -k internet_server -v <url>
/Applications/UrBackup\ Client.app/Contents/MacOS/bin/urbackupclientctl set-settings -k internet_server_port -v 55415
/Applications/UrBackup\ Client.app/Contents/MacOS/bin/urbackupclientctl set-settings -k computername -v "${4}"
/Applications/UrBackup\ Client.app/Contents/MacOS/bin/urbackupclientctl set-settings -k internet_authkey -v "$5"
I modified the parameter labels of var4 and var5 to ‘Client Name’ and ‘Internet Authkey’ in the script options to make it easier to remember.
I built out a policy to include the .pkg installer and the script, Vars 4 and 5 need to be defined.
My deployment process is to Add a New Client on the server. I then add that client to the group I created for mac laptops. Failure to do so causes the laptop to try to find a C:\ drive and causes headaches. I copy over the name and authkey into the Jamf policy into Vars 4 and 5. I then scope the policy to 1 laptop at a time.
I can push to more than 1 laptop at a time by just cloning the policy, making the changes necessary and pushing to the next on the list. It’s a little annoying on the initial deployment, but only really needs to be done once.
The only real ‘issue’ and it’s not an issue just an annoyance is that there’s a popup for UrBackup Client wanting a password input so it can be used as a login item. If you cancel, it will add it anyway so the input can safely be ignored.
I built out a second policy with a simple script:
#!/bin/bash
/Applications/UrBackup\ Client.app/Contents/MacOS/bin/urbackupclientctl start -i
I can push this if I want to manually start a client to backup.
So far so good on the handful of remote users I’ve been testing with. We’re planning to expand the storage pool for the Server in the next couple weeks and deploy to about 100 remote mac users.