Entering Jamf Pro Settings at Initial Start Up

info

[CHECK THIS: THIS IS A DUPLICATE TOPIC WITH ONE IN SITE MANAGEMENT CHAPTER. THEY SHOULD EITHER BE COMBINED OR THIS ONE SHOULD BE STRIPPED DOWN AND POINT TO THE OTHER ONE. THIS SHOULD BE JUST THE TOPIC THAT YOU NEED WHEN USING THE CONFIGURATION WIZARD.]

With App Portal, you can deliver a universal enterprise app store that includes both Windows and OS X desktop applications. You can connect App Portal to a Jamf Pro Suite server and create catalog items for OS X desktop applications. This gives you deployment automation and control.

To connect App Portal / App Broker to a Jamf Pro server, you can, optionally, enter settings on the Jamf Pro tab of the Deployment Configuration screen which opens at initial start up after you have uploaded your license file.

info

In order for App Portal to be successfully integrated with Jamf Pro, your Jamf Pro account needs to have a specific set of minimum permissions. For more information, see Required Jamf Pro Account Permissions.

info

[CHECK THIS: This is awesome! It very clearly enumerates the minimum permissions required for App Portal to integrate with Casper and how to configure them. Thank you! Thank you! Thank you! We should really have this for all the deployment systems and other integrations we natively support - e.g. ServiceNow, BMC Remedy, Orchestrator, WFM. If the "how to" is too much or not possible (since UI's will change periodically and may be too much to keep up with), we at least need the minimum permissions documented (simply stating Full Administrator isn't really acceptable to customers unless that's literally the only option to achieve the desired functionality). I know Brian Cooper submitted support cases/JIRA tickets for this kind of documentation a couple years ago. Glad to see we at least have a start with Casper!

note

You can also specify Jamf Pro deployment settings at any time on the Jamf Pro tab of the Site Management > Settings > Deployment view. App Portal and Jamf Pro communicate using Jamf Pro's JSS API. By default, Jamf Pro uses port 8443 for inbound SSL traffic to the JSS. You will need to include the port number in the Jamf Pro URL when configuring your settings. If you have modified the inbound SSL port within your JSS configuration, specify your custom port number in the Jamf Pro URL.

To enter Jamf Pro connection settings upon initial start up of App Portal / App Broker, perform the following steps:

To enter Jamf Pro connection settings:

Perform the steps in Uploading Your App Portal / App Broker License File and click Next . The Deployment Configuration screen opens.
Open the Jamf Pro tab. The Jamf Pro Server Details are listed.
In the Jamf Pro URL field, enter the URL to your Jamf Pro server.
Enter the User Name and Password to your Jamf Pro server.
In the App Portal policy folder field, enter the folder/category in Jamf Pro under which the policies created by App Portal / App Broker will reside.
In the Policy template name field, enter the name of the policy in Jamf Pro which can be used as a template.
In the Computer group template name field, enter the name of the static group in Jamf Pro which can be used as a template.
Click Test to test connection settings.
- Jamf Pro users (which are based upon an email address) and are synced to App Portal / App Broker at the same time that the System Center Configuration Manager / Altiris users and are synced. App Portal / App Broker users are matched with System Center Configuration Manager / Altiris users by having the same email address.
Proceed with setting additional deployment technology settings on the other tabs of the Deployment Configuration screen, if desired.
Click Next to continue.
Proceed with the steps in Specifying Integration Connection Settings.