Skip to content

Allow for on-prem JAMF instances #2

@innowintay

Description

@innowintay

Thanks for this most recent update! I'm actually in the process of rolling out Backblaze using JAMF to my company and had just perfected my adaptations of the older script when I noticed this one had been updated to fix the error reporting.

I saw where you requested that we enter an issue before PRing any major changes. The way you had the JAMF URL scripted prevents anyone using JAMF on-prem from using this script without adaptation. I'm going to PR a change that not only allows users to enter the full FQDN but also ensures it strips the HTTP/HTTPS protocol if they should happen to include it.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions