One of the biggest complaints we get from field techs is that the QuickAdd.pkg installer takes too $^&%@ long to complete. Is there a reason we can't decouple the install of the jamf binary from the actual enrollment process? This way Installer.app can finish and the tech can move on? Right now Installer.app waits for the postflight script to exit, which may take a considerable amount of time...it would be better for our techs if the QuickAdd.app installer was quick and painless. :)
Answer
Decouple jamf install from the enrollment process [QuickAdd.pkg]
+36Best answer by mscottblake
You could modify the package to run enrollment with the noRecon flag: ```
sudo jamf enroll -noRecon
```
That should speed it up considerably.
+24You could modify the package to run enrollment with the noRecon flag: ```
sudo jamf enroll -noRecon
```
That should speed it up considerably.
+36I suppose it would be an option to edit the QuickAdd.pkg's postflight script to use -noRecon option, and then the next Last Report cycle would submit inventory data? Still, would be nice to have the option when creating the QuickAdd.pkg...
$ jamf help enroll
Usage:jamf enroll [-prompt | -invitation] [-noRecon] [-noManage]
-promptPrompts for JSS and SSH credentials.
-invitationUses an invitation ID for credentials instead of a user name and password.
-noReconStops enroll from acquiring inventory.
-noManageStops enroll from enforcing the management framework....hmm, I hope the -noRecon option isn't persistent. ;)
Don
+24It is not persistent, I can guarantee it. I use the noRecon flag often when I'm doing it manually.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.