Skip to main content
Question

Self Service Not Coming Down While Using Casper Imaging

  • November 4, 2016
  • 6 replies
  • 31 views
N
Forum|alt.badge.img+5

Good evening everyone,

I have an issue that doesn't seem consistent while we image computers for our laptop carts. We have two configuration profiles, one where we reinstall the OS and one where we just place our software on top of the existing system.

At times, when we image Self Service gets downloaded no problem and we go on our merry way. However, more times than I'd like to count Self Service doesn't automatically download. As a bandaid we just install it with a QuickAdd package. I want to make my job easier and figure out why this is going on.

While doing some testing on a laptop today I grabbed the jamf log and an error was reported stating it couldn't enroll the computer. When I checked our JSS it reported the inventory stats on the computer, but it wasn't checking in.

Just a little background on this setup;
I had this computer placed in a PreStage Imaging profile, but it wasn't enabled. (not sure if that makes a difference)
Also, this laptop is not enrolled in DEP.
We are running JSS 9.96 on a Windows 2008 server

I'm including the log so hopefully someone can help me out.

Thanks in advanced.
Nicholas

###################################################

Formatted Macintosh HD on 11/3/16 at 2:13 PM

###################################################

2016-11-3 14:16:57 Formatted Macintosh HD

Thu Nov 03 11:18:33 LS7030 jamf[3978]: Creating user 3rdgrade...

Thu Nov 03 11:18:40 LS7030 jamf[4090]: Error Domain=com.jamf.jamfsecurity.error

Code=-25300 "The specified item could not be found in the keychain." UserInfo=

{NSLocalizedDescription=The specified item could not be found in the keychain.}

Thu Nov 03 11:18:40 LS7030 jamf[4117]: Creating user 4thgrade...

Thu Nov 03 11:18:40 LS7030 jamf[4090]: Error Domain=com.jamf.jamfsecurity.error

Code=-25300 "The specified item could not be found in the keychain." UserInfo=

{NSLocalizedDescription=The specified item could not be found in the keychain.}

Thu Nov 03 11:18:41 LS7030 jamf[4090]:

There was an error.

Error enrolling computer: Invalid Message - The message could not be parsed.

Thu Nov 03 11:18:45 LS7030 jamf[4191]: Creating user horizons...

Thu Nov 03 11:18:49 LS7030 jamf[4262]: Installing Office Installer.pkg...

Thu Nov 03 11:20:18 LS7030 jamf[4262]: Successfully installed Office Installer.pkg.

Thu Nov 03 11:20:19 LS7030 jamf[4424]: Installing Office 2011 14.6.9 Update.pkg...

Thu Nov 03 11:22:13 LS7030 jamf[4424]: Successfully installed Office 2011 14.6.9

Update.pkg.

Thu Nov 03 11:22:14 LS7030 jamf[7479]: Installing

HewlettPackardPrinterDrivers3.1.pkg...

Thu Nov 03 11:24:19 LS7030 jamf[7479]: Successfully installed

HewlettPackardPrinterDrivers3.1.pkg.

Thu Nov 03 14:24:42 LS7030 jamf[12936]: Deleting user adobeinstall...

Thu Nov 03 14:24:43 LS7030 jamf[12936]: Deleting home directory for adobeinstall...

Thu Nov 03 14:24:44 LS7030 jamf[12968]: Immediate Restart

Thu Nov 03 14:24:44 LS7030 jamf[12968]: Sending restart to System Events

Thu Nov 03 14:24:44 LS7030 jamf[12968]: Sending Restart command

Thu Nov 03 14:24:44 LS7030 jamf[12968]: Attempting normal restart

    6 replies

    A
    Forum|alt.badge.img+13
    • andrew_nicholas
    • Honored Contributor
    • November 4, 2016

    Sounds like the machines in question don't fully enroll/something breaks. I've seen similar things before and just adding a Recon generated QuickAdd package at the end of the configurations as a catch all takes care of it. Not a fix but an easy enough work around.

    N
    Forum|alt.badge.img+5
    • niacobelli
    • Author
    • Contributor
    • November 4, 2016

    So you add a QuickAdd package at the end of the imaging process @andrew.nicholas ?

    N
    Forum|alt.badge.img+5
    • niacobelli
    • Author
    • Contributor
    • November 4, 2016

    Okay, added a QuickAdd package at the end of the imaging process. Still nothing. I also removed all of the packages except for the OS to rule out a package causing an error. Same result.

    Has anyone seen this issue?

    mpermann
    Forum|alt.badge.img+22
    • mpermann
    • Valued Contributor
    • November 4, 2016

    @niacobelli is the system your re-imaging already in your JSS? If it is, have you noticed if there are any pending MDM commands before you start the imaging process? I'm wondering if there is something already in the computer record in your JSS that is preventing the MDM stuff from making it's way down to the system. I often times remove the computer record before re-imaging it to make sure I don't run into any weird behavior. But I understand in some instances that would not be a good idea.

    S
    Forum|alt.badge.img+12
    • SeanA
    • Contributor
    • November 5, 2016

    The basic stuff about installing Self Service on a computer automatically:

    1) Package Self Service and distribute in a policy
    2) JSS > Settings > Computer Management > Self Service > Install Automatically

    Though the issue does not seem to be a Self Service issue as much as an enrollment issue. My suggestion: on a computer that fails to deliver Self Service, open the Terminal application on that computer and type the following command (which will enroll/re-enroll the Mac into the JSS):

    sudo jamf enroll -prompt -verbose

    The Terminal will prompt you for a JSS Username and JSS Password (a person who has the ability to enroll computers) and then SSH Username and Password (your JSS Management Account). Watch the information and see if the troubleshooting step, especially with the verbose flag, provides more information and insight into the problem.

    N
    Forum|alt.badge.img+5
    • niacobelli
    • Author
    • Contributor
    • November 6, 2016

    @SeanA , thank you for the tips. I'm going to check that and see what it pulls up.

    @mpermann , I didn't check the pending MDM commands before deleting the inventory log in the JSS. But after deleting it and reimaging the computer it seems to pull down Self Service no problem and it's checking in as it should.

    Terms & ConditionsCookie settingsAccessibility statement