We recently had to upgrade to 10.3.1 as our 10.0.0 environment was spiking the server CPU to a consistent 100% per core utilization causing tomcat to become unresponsive after about 15 minutes of uptime before we had to reset tomcat again. After a lot of back and forth with JAMF we were unable to address the issue with 10.0.0 so as a last resort we installed 10.3.1. This addressed our performance issue and from the console side of things JAMF has been pretty snappy.
However, on the build workflow side of things, it has been nothing but trouble. Prior to 10.3.1 we were on 10.0.0 and our workflow was as follows:
JAMF 10.0.0
- DEP enroll or User-Initiated JAMF Enrollment (Quickadd.pkg)
- Launch Self Service and run the build policies for a particular group (AD Bind, HostName, Apps, etc. etc.)
- Deploy Mac to end user
JAMF 10.3.1
- DEP enroll or User-Initiated JAMF Enrollment (Install MDM profile)
- Wait anywhere from 10 to 60 minutes for the JAMF Binaries to fully install. (Current average is about 30 minutes for us)
- Launch Self Service and run the build policy for a particular group (AD Bind, HostName, Filevault, Install Apps, etc. etc.)
- Deploy Mac to end user
On JAMF 10.3.1 the build policy results seem to be inconsistent. Sometimes the SMB distro point fails to mount, sometimes our hostname script doesn't complete properly. I am troubleshooting these as unrelated to the JAMF upgrade, but it is odd we didn't see these under 10.0.0
I know the switch from the quick add to the MDM profile method is due to the changes Apple made in 10.13 for user approved kernel extensions, but there has to be some way to speed up the installation of the JAMF binaries.
What are other people using for the DEP and User-Initiated enrollment build workflows? Is there something simple I am missing here?