Image

Managed Service Designer

What is this?

The purpose of this tool is to assist with Discovery and Scoping for a managed instances based on specific criteria. Aiding MSPs to get a designed output for their Customers with help from the Jamf Sales team. 

What happens when I complete this form?

After this form is complete, our Sales team will begin the purchase process using the details provided. This will then be passed to our Services team to produce a managed instance that can begin enrolling devices and be integrated into Jamf Insights. 

Managed Service Designer - version 1

Details

 

This should be the technical contact for your records. Jamf will only hold this information within this form.

 

Jamf Service Provider Plan - Manage

Automated Device Enrolment is the most reliable way to ensure your managed instance is secure. We recommend all devices are either new or erased before enrolment to your managed service and are enrolled within Apple School/Apple Business Manager.
For further information, please review: https://support.datajar.co.uk/hc/en-us/articles/360019113513

If you would like to know more about Apple School/Apple Business Manager, please review:

Apple School Manager User Guide
Apple Business Manager User Guide

Automated Device Enrolment is the most reliable way to ensure your managed instance is secure. We recommend all devices are either new or erased before enrolment to your managed service and are enrolled within Apple School/Apple Business Manager.

For migrating an existing instance, it is recommended that at least one of these is true for your devices
The devices are within Apple School/Business Manager.
The devices are already enrolled within an existing MDM that is being migrated to a managed instance.

For further information, please review: https://support.datajar.co.uk/hc/en-us/articles/360019113513

If you would like to know more about Apple School/Apple Business Manager, please review:

Apple School Manager User Guide
Apple Business Manager User Guide

For further information on our requirements, please see: https://support.datajar.co.uk/hc/en-us/articles/360019113513
For further information on our requirements, please see: https://support.datajar.co.uk/hc/en-us/articles/360019113513
Support:
jamfcloud.com
This identifier can be your organisation name, it cannot contain spaces any special characters, for example './*!-@£$%^&*()' and must be lowercase. This will be used as your vanity URL for your web application and software packages, this cannot be changed.
jamfcloud.com
This identifier can be your organisation name, it cannot contain spaces any special characters, for example './*!-@£$%^&*()' and must be lowercase. This will be used as your vanity URL for your web application and software packages, this cannot be changed.

macOS client configuration

This reflects the number of macOS devices you wish to manage. Minimum order quantities apply.
Deferring updates from being offered on device in order to ensure versions work well in your environment with your software.
For more details on how we manage software updates on macOS within a managed instance, please see this KB article: https://support.datajar.co.uk/hc/en-us/articles/4407461389969
Base macOS application(s):
We can include any of the titles from the above list for your initial setup. These have been chosen as the most common apps requested. Additional Custom Applications can be added from the Auto Update catalogue and from the Mac App Store.
Jamf Service Provider Plan has some defaults set that cannot be changed during the initial build, however some items can be requested now to be changed post build.

macOS custom configurations

Custom configurations will be completed after the initial setup of your instance. These options will be used to define your instance further once you've been able to enrol with the initial roles & restrictions.
Branding will be completed post-build. We will request the correct formats via a ticket.

Graphics must be in JPEG or PNG format ensuring a resolution 5120 × 2880 (144ppi).

For more details on available resolutions, please see the Apple website here: https://www.apple.com/uk/mac/compare/

We will send out further details following the initial setup for additional application scoping and custom packaging requirements.

macOS custom configuration (1:1)

When a 1:1 device configuration is built, we recommend that all devices are encrypted, with a passcode and biometric authentication. All 1:1 device configurations require an integration with a directory service.

If you have not specified a directory service, then you will not be able to proceed. If you need to adjust this, please go back to the Identity Services section and add a directory service there.

For further information on device types, please review the following: https://support.datajar.co.uk/hc/en-us/articles/4411352018193

One "Standard" role will be set up from the initial configuration. If you require additional roles with the same client configuration, simply specify the roles with a comma (e.g. Marketing, Sales, Admin, Engineering)
This is how long the machine takes to lock once the screen goes off or the screensaver begins.

macOS custom configuration (shared)

When a shared non-personalised device configuration is built, we will ensure that all devices are not encrypted, with no passcode or biometric authentication. This device configuration does not require an integration with a directory service, although this is recommended for multi-user environments.

For further information on device types, please review the following: https://support.datajar.co.uk/hc/en-us/articles/4411352018193

One "Standard" role will be set up from the initial configuration. If you require additional roles with the same client configuration, simply specify the roles with a comma (e.g. Marketing, Sales, Admin, Engineering)
This is how long the machine takes to lock once the screen goes off or the screensaver begins.
If you'd like a customer power schedule, ie Shared Macs power on at XX:XX and power off at XX:XX

iOS/iPadOS client configuration
This reflects the number of iOS/iPadOS devices you wish to manage. Minimum order quantities apply.
Deferring updates from being offered on device in order to ensure versions work well in your environment with your software.
For more details on how we manage software updates on iOS/iPadOS within a managed instance, please see this KB article: https://support.datajar.co.uk/hc/en-us/articles/4758806482589
Base iOS/iPadOS application(s):
We can include any of the titles from the above list for your initial setup. These have been chosen as the most common apps requested. Additional Applications can be added from the App Store.
Jamf Service Provider Plan has some defaults set that cannot be changed during the initial build, however some items can be requested now to be changed post build.

iOS/iPadOS custom configuration

Custom configurations will be completed after the initial setup of your instance. These options will be used to define your instance further once you've been able to enrol with the initial roles & restrictions.
Branding will be completed post-build. We will request the correct formats via a ticket.

Graphics must be in JPEG or PNG format with a file size of less than 2MB.

Resolutions must match your deployed devices, for more details please see the Apple website here: https://www.apple.com/uk/ipad/compare/ https://www.apple.com/uk/iphone/compare/ 

We will send out further details following the initial setup for additional application scoping requirements.

iOS/iPadOS custom configuration (1:1)

When a 1:1 device configuration is built, we recommend that all devices are encrypted, with a passcode and biometric authentication. All 1:1 device configurations require an integration with a directory service.

If you have not specified a directory service, then you will not be able to proceed. If you need to adjust this, please go back to the Identity Services section and add a directory service there.

For further information on device types, please review the following: https://support.datajar.co.uk/hc/en-us/articles/4411352018193

Apple Mail supported only.
Smallest number of passcode characters allowed.
Smallest number of non-alphanumeric characters allowed.
Number of minutes before the device automatically locks.
Period of inactivity before the passcode is required to unlock the device.
Number of passcode entry attempts allowed before all data on device will be erased.

iOS/iPadOS custom configuration (shared)

Details below will not be completed during the initial setup of your instance. These options will be used to define your instance further once you've been able to enrol with the initial roles & restrictions.
If you do not specify these items, they will stay as the default set from your initial build

When a shared non-personalised device configuration is built, we will ensure that all devices are not encrypted, with no passcode or biometric authentication. This device configuration does not require an integration with a directory service.

Devices setup for multi-user use with a Managed Apple account will be enabled with a passcode.

For further information on device types, please review the following: https://support.datajar.co.uk/hc/en-us/articles/4411352018193

One "Standard" role will be set up from the initial configuration. If you require multiple roles with the same client configuration, simply specify the roles with a comma (e.g. Marketing, Sales, Admin, Engineering)
Period of inactivity before the passcode is required to unlock the device.

Setup Cloud identity

We can integrate seamlessly into multiple directory/identity services. Please note, these services are required for some deployment models.

Please note, some integrations will be done post-engagement
Jamf Connect is required to enable Shared macOS devices.

Infrastructure and networking

In order to ensure your devices can communicate with cloud services, we need to know a few more details about your environment. These details will enable us to understand your environment better.

Content filters with an agent will be set up following the initial build of your managed instance.
We may need to manually package your Content Filter agent. We will ask for the agent during your set up to complete this step.
An Apple Content Cache is recommended if your organisation plans to use Shared iPad (with Managed Apple IDs).
Or your organisation has more than 100 Apple devices in one physical location.

A content cache role will be set up as standard, more details can be found here: https://support.datajar.co.uk/hc/en-us/articles/7101725095197