Skip to main content
Question

User initated enrollment fails after upgrade to 9.4

  • August 22, 2014
  • 6 replies
  • 29 views
S
Forum|alt.badge.img+12
  • Simmo
  • Contributor
  • 222 replies

Upgrade was from 9.32

Pretty major issue for us, we use user initiated enrollment for all OS X devices, I decided to hold off on 9.4 for a week to see any bugs and everything seemed fine, I haven't seen this issue reported so I'm not entirely sure where the issue is coming from.

After logging in, downloading the Quickadd.pkg and running the installer, the install gets to running package scripts and then comes up with "The installation failed."

Anyone else seeing this? We are in the middle of enrolling our fleet so it's pretty important for me to get this working again.

external image link

The machine appears in the JSS but the vast majority of information has not been captured.

Edit:
I have found that it does install Self Service and the JAMF binary, so I am able to do a recon on the machine to bring the rest of the information down. It also does not create the management account I have found.

    6 replies

    A
    Forum|alt.badge.img+8
    • Adminham
    • Contributor
    • 31 replies
    • August 22, 2014

    Are you using Thunderbolt/USB to Ethernet adaptors? https://jamfnation.jamfsoftware.com/discussion.html?id=10875
    I'm seeing similar issues with Thunderbolt adaptors (running JSS 9.31) whereby a partial record gets created in the JSS, but there is no management ability, the enrollment never fully completes. This happens on any Mac I use the Ethernet adaptor on. When I use built-in Ethernet or Wi-Fi to enrol, no problems.

    S
    Forum|alt.badge.img+12
    • Simmo
    • Author
    • Contributor
    • 222 replies
    • August 22, 2014

    @Adminham No this is over Wi-Fi

    A
    Forum|alt.badge.img+8
    • Adminham
    • Contributor
    • 31 replies
    • August 22, 2014

    Interesting. If you haven't already, try running the QuickAdd package via the Terminal:
    installer -verbose -pkg /PathToQuickAdd.pkg -tgt /
    May throw up a few clues

    S
    Forum|alt.badge.img+12
    • Simmo
    • Author
    • Contributor
    • 222 replies
    • August 22, 2014

    @Adminham Unfortunately this does not reveal anything new

    external image link

    E
    Forum|alt.badge.img+1
    • eclemens
    • New Contributor
    • 5 replies
    • August 25, 2014

    I saw this problem occur randomly during re-imaging of computers this summer. Unable to pin down the cause, but in some cases if we deleted the JSS certificate from the keychain and ran QuickAdd a second time it usually succeeded.

    A
    Forum|alt.badge.img+1
    • applegrrl
    • Employee
    • 3 replies
    • May 6, 2015

    I had this occur in JSS version 9.72 running on an Ubuntu 14 / MySQL 5.7x / JDK 7 VM. You may want to try right click and open the Quickadd package contents and open post flight in a text editor. This was helpful to me as it provided output such as this on my problematic Quickadd package:

    !/bin/bash

    Enforce Permissions

    /bin/chmod 551 /usr/sbin/jamf

    Create conf file for JSS

    /usr/sbin/jamf createConf -k -url https://jss.name.in.here:8443/

    Starting SSH

    /usr/sbin/jamf startSSH

    Enrolling device with invitation

    /usr/sbin/jamf enroll -invitation 52843249082276333236724744186976336883 -endUsername "User" -realname "My Name" -email "My.name@yep.com" -position "Desktop Sys Administrator" -department "Information Technology" -phone "0867, 5309" -ldapServerID 3 -userID "User"

    enrolled=$?

    if [ $enrolled -ne 0 ]
    then
    echo "Enrollment Failed. This PKG may be used already."
    fi

    exit $enrolled

    This was odd as it was a never used web enrollment QA package. (The enrollment user was also not allowed to re-enroll using this package as set in the JSS.) After seeing this, I opted to not have the JSS assign a user to the Quickadd web enrollment .pkg and found that the Quickadd then worked. In looking in my JSS LDAP settings I then changed the attribute mapping for User ID to uSNCreated from what it was set to and this seemed to allow the enrollment AND adding a LDAP user when enrolling via User Initiated web enrollment.


    Terms & ConditionsCookie settingsAccessibility statement