Been spending a few good hours trying to get the super enterprise friendly operating system Apple Mac OS X 10.9.1 (In Denmark we really use irony a lot!). There a some good blog post on how to configure MAC support that I advice you all to follow and if you are working with latest version Maverick 10.9.1 I strongly advise you to read this blog post from Yvette –http://blogs.technet.com/b/configmgrteam/archive/2013/12/16/mac-os-x-10-9-support-for-sc-2012-config-manager-clients.aspx

Here is what I did, the error I saw and how I fixed it.

  1. Configuring Apple MAC support according to Technet
  2. Enrolled the client on OS X version 10.9.1 (which is not yet officially supported by Microsoft). The enrollment process went ok, but the client never successfully communicated with the Management Point and I saw a lot of errors in the local CCM Client log file on the MAC (found in .\Library\Application Support\Microsoft\CCM\Logs).
  3. Failed to read diskutil output for 0x7fe943de8d90.anonymous.launchd. Task terminationStatus – 1.        01-01-1601 00:00:00    0 (0x0000)
    Failed to read diskutil output for 0x7fe943de8af0.anonymous.launchd. Task terminationStatus – 1.        01-01-1601 00:00:00    0 (0x0000)
    Failed to read diskutil output for 0x7fe943e2f970.anonymous.System. Task terminationStatus – 1.        01-01-1601 00:00:00    0 (0x0000)
    Failed to read diskutil output for com.apple.CMValidateMovieDataReferenceService. Task terminationStatus – 1.        01-01-1601 00:00:00    0 (0x0000)
    Failed to read diskutil output for com.apple.qtkitserver. Task terminationStatus – 1.        01-01-1601 00:00:00    0 (0x0000)
    Failed to read diskutil output for com.apple.coremedia.videodecoder. Task terminationStatus – 1.        01-01-1601 00:00:00    0 (0x0000)

  4. Followed the guide from Yvette and disabled all USB invnetory from Client settings. Unfortunately I still got the errors and the client wouldn’t communicate with the Management Point.
  5. Snuck into my youngest daughters room, and took here MAC (running OS X 10.8.X – don’t blame it on here, she’s still not old enough to know what a real operating system is). I enrolled it into ConfigMgr and it worked perfectly the first time.
  6. After version 10.8 started communicating with the Management Point my OS X 10.9.1 also started communicating.