JAMF connect via pre-stage enrollment

[mkhadgi]

What is the best practice to deploy Jamf connect via pre-stage?

I tried to push it via prestage, it installed Jamf connect app but not any of the agents or bundle. There is no login window for Jamf connect. When I run the same package via policy, it fixes the issue.

[Tribruin]

Take a look at this guide:
https://community.jamf.com/t5/jamf-connect/jamf-connect-meta-package-for-zero-touch-deployment/m-p/2...

I use a very similar process. It works well. I just upload the meta package to Jamf and assign it to my prestage. The Jamf Connect Login screen is then presented to the user after setup. 

[nixsky]

It's not necessary to package Jamf Connect, so long as you deploy the Jamf Connect configuration profile, it'll pull down the latest version of Jamf Connect. 

I've found that I need to manually add the launchAgent to my pre-stage however. But that'll be preference, you don't technically need it 

[AJPinto]

I have 3 packages for Jamf Connect, and push all 3 in the prestage along with the configuration profiles. Works fine for me.

The 3 packages are:

• Jamf Connect itself
• Jamf Connect's image assts
• Jamf Connect's launch daemon

[PhillyPhoto]

Be sure to check out https://ideas.jamf.com/ideas/JPRO-I-605 and upvote if you think adding Mac Apps to PreStage enrollments would be beneficial for this exact scenario so you can always have the current version of Jamf Connect installed at enrollment!