Hardcode the primary email as it will stay static.Ĭentralized deployments where every endpoint will be logged into a primary Backblaze account that is managed by IT. Custom scripting can be involved with the bash script below to actively pass these values in at runtime.Ĭentralized Deployment 'IT Managed Account' If you don't have a JAMF Pro setup you will need to fill in a relevant email for each deployment.

Within the context of this guide, this requires a JAMF Pro environment to be set up.In this scenario, the end-user will have access to their own data through the Backblaze portal. The email parameter that is passed by the script will need to be unique to each user related to the endpoint at runtime.ĭecentralized deployments involve an account for each endpoint that is then part of your business group which manages payment and admin activity (if enabled). Let's go over the two main types of deployments we see.ĭecentralized Deployment 'User-Managed Account' Using our shell script to silently deploy with JAMF.Using our shell script to silently deploy w/o JAMF.Using the installer through the command line.In this article, we will go over the following scenarios

In this article, we will go over the various types of silent deployment and the steps we will need to do in preparation. The key difference however is in order to deploy the client silently there are a few unique steps needed to make this process work as smooth as possible. This is no different for our Computer Backup Installer for macOS.

For Apple's line of macOS operating systems, this generally involves a mountable dmg with an installer package contained within. All of them have some similarities in that they assume an installer of some kind. Pushing out an application to hundreds or thousands of users is a task faced by many IT professionals, there is no shortage of tools (like JAMF) attempting to simplify this.

Jamf autorun data