Has anyone else noticed odd behavior with your Mavericks 10.9.x netboot image on newer Macs? Prior to Mavericks, my netboot images worked like a charm, while they took longer to boot since they're going over the network, they'd otherwise act more or less like a local installation.

However, I've been noticing that my Mavericks netboot images (I've made 10.9, 10.9.1, 10.9.2 and just today 10.9.3) are a little funny in that once the desktop comes up, just about every action has a HUGE delay before the action happens. This usually means a beach ball, but not always.

Also, sometimes the dock icons are "invisible". The space where they should be is occupied and when you hover the pointer you get the name of the icon, and clicking the space opens the app (after a long delay, I think it took a minute or more to open the image utility). Also, if you can manage to get a Finder window to open, icons are sporadically "invisible" here as well.

In addition, there's this weird system error box that sometimes shows up. It says "Unapproved caller. SecurityAgent may only be invoked by Apple software." I assume that's some sort of low level OSX security feature and something is trying to call a function that is not allowed by non-Apple software.


Answer Summary:
With 3.6, a tether is required to resolve this issue with 10.9 netboot environments.
2 Comments   [ - ] Hide Comments


  • I believe maveicks has more forks than previous versions of osx. Are you building on one site of hardware and deploying to other types of models?
  • I thought of that. My most recent build uses the 10.9.3 Mavericks installer from the App store. I figured that would contain all drivers for all supported Macs.
Please log in to comment

Community Chosen Answer



With 3.6, a tether is required to resolve this issue with 10.9 netboot environments.

Please see


and reference this knowledgebase article when submitting a ticket.

Lead T3 Enterprise Solutions Consultant, K2000

Answered 06/12/2014 by: cserrins
Red Belt

  • thanks for the update, opening a ticket now
Please log in to comment
Answer this question or Comment on this question for clarity



I've seen all of these exact issues. I wound up submitting a support ticket, and the K2000 engineering team tethered into my box, did some voodoo, and fixed the issues. 

I recommend you do the same...I never followed up to ask the root cause of the issue(s), so if you find out, please let me know!

Answered 05/16/2014 by: dgretch
Third Degree Blue Belt

  • I submitted a ticket right after you commented, but have not heard from KACE yet.
    • this has been pretty consistent with my experiences with their support of late
      • I don't know what went wrong, but my ticket sent from the K2000 box didn't go through, so I resubmitted on the support.kace.com site yesterday and today they tethered in and fixed it.
Please log in to comment

Same here.  I just spoke with K2000 support and this is a known issue, there internal bug track number for this is K2-4459.  You will need to create a support ticket to get it resolved with tier 3 engineer, and they will need to tether in to resolve.

Answered 05/22/2014 by: kpm8
Senior Purple Belt

Please log in to comment