AutoCasperNBI - open beta

I'll confirm a 10.10.1 AutoCasper NBI and Casper Imaging 9.6.3 will block-copy both 10.10.1 and 10.10.2 base OSes.
10.10.2 AutoCasper NBI and Casper Imaging 9.6.3 will file-by-file copy a 10.10.2 base OS.

The issue seems like it's in Casper Imaging. Has anyone opened a case with JAMF? @amanda.wulff are you guys aware of this possibility?

@RobertHammen][/url

We do actually have a defect open for this behavior (D-008472) that came out of a few cases.

What it’s looking like so far, and please bear in mind that this is new to us as well so we’re still doing testing on the behavior which means the information I have at the time of this posting may change, is that if the OS that is running Casper Imaging is 10.10.2 we’ll see the behavior described both in this thread and over in this thread.

If the OS that is running Casper Imaging is 10.10.1 or something lower, it works as we’d expect, as it looks like you’ve already seen in your environment.

Currently, I’m testing out what @maccentric][/url has seen in their environment and, once it finishes (or fails), will be looking at my system.log file to see if anything leaps out as different between the OS Imaging is running on being 10.10.2 or something that is not 10.10.2.

If you’d like to dig into it further, or would like to get a case opened up for confirmation that the behavior you're seeing in your environment is D-008472 and not something else, and so we can get your case attached to D-008472 once the behavior is confirmed, please get in touch with your Technical Account Manager either by giving Support a call, by sending an e-mail to support@jamfsoftware.com (it routes directly to their case queue), or by using the My Support section of JAMF Nation.

Thanks!
Amanda Wulff
JAMF Software Support

Edited because I misspelled my own name. Good thing it's Friday and a short drive home. :)

@bmarks, thanks for confirming.

Everyone else, this says it's fixed in 9.64.

https://jamfnation.jamfsoftware.com/discussion.html?id=13184#responseChild77918

Is there any kind of ETA or workaround for the time being? Just image off a host running 10.10.1 or lower for now?

@CorpTech, imaging off of a 10.10.1 host for now.

@bentoms this seems like it would be perfect for us, but when we try to use the NBI we built with AutoCasperNBI, it doesnt actually boot to any of our hardware, whereas NBIs we made with SIU have worked without problem.

I verified that the kernelcache is reasonably sized (13MB) and in both i386/ and i386/x86_64/

We're netbooting from an OSX server and using a 10.9.5 base image.

Not sure what else could be causing this.

For what it's worth, my problem was related to using AutoCasperNBI on a machine running 10.10 to create a 10.9 NBI. Creating a 10.10 NBI worked without problem.

The error I was seeing was "error loading kernelcache (0xe)"

AutoDMG requires you to be booted from the OS to make the base OS DMG, so I tend to use AutoCasperNBI as a 2nd step and build it on the same OS that the NetBoot image is...

Yeah I had already had a few base OS images lying around that I had made with AutoDMG, so I was using those to test.

In the future it will be extremely unlikely that I would have an OS mismatch during this process.

@lynnp, thanks for logging the issue on GitHub.. I've an update version in the works & I'll see if I can work a fix into that.

@RHammen, @justinrummel & @lynnp.. FWIW.. The OS running AutoCasperNBI shouldn't matter. I had 10.10 beta creating 10.7.5-10.10 NBI's fine. So there must be a new change.

AutoCasperNBI generates the needed files for the NBI it creates, so no same OS dependency.

@lynnp Please try this pre-release version of AutoCasperNBI

Hopefully the fix in there works for you.

More pre-release information:

Do you know where the Untitled volume on the desktop is located used for the RAM disk?

Possibly this can be hidden with a launchdaemon and chflags hidden command?

@bentoms - I saw in some of your docs that you had pkgs installed to setup the dock. Can you point me in the direction of how to create those? Is it just capturing the dock plist in Composer? I would love to add some stuff to the dock (Disk Utility, etc.). Thank you!

@jubei I did this by enabling the root user on my local Mac. Set up the Dock the way I wanted, set Safari homepage prefs to my JSS, set Debug menu in Disk Utility.

Used Composer to package those 3 plists from /private/var/root/Library/Preferences and built a PKG file, which I copied to the root of the drive.

Logged out, logged back in as my standard user and disabled the root account. Then, added that .pkg file to my AutoCasperNBI workflow.

@jubei what @RHammen said.

He's on fire today.

Heh. Someday Ben will remember that my main account here is @RobertHammen ;-)

Thanks you @RobertHammen !

Created a launch daemon with chflags hidden command to hide the RAM disk, packaged it up and added it to Auto CasperNBI. Now the RAM disk is hidden every time :)

Does AutoCasperNBI support 10.10.3? Because I've created the disk image with Disk Utility and tried with Composer and it says "Cannot read OS Version"

Yes it does (newest version FYI). I am running a 10.10.3 NBI, with casper Imaging 9.7 that was created using AutoCasperNBI 1.1.7

The newest that downloads from https://macmule.com/autocaspernbi/ by clicking the big Download Now button for me is 1.1.4.....Where's 1.1.7?

Ignore me, i see 1.1.7 and 1.1.8 are pre-releases.

You caught me there for a moment! I realized that 1.1.7 was an open beta along with 1.1.8. Glad you found them!

Hi all,

I'll probably release 1.2 this weekend, it has all of the fixes from the pre-releases & one outstanding issue that I can't recreate myself.

launchdaemon to hide the ram disk

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
    <key>Label</key>
    <string>com.hide.ramdisk.Launchd</string>
    <key>ProgramArguments</key>
    <array>
        <string>chflags</string>
        <string>hidden</string>
        <string>/private/var/netboot</string>
    </array>
    <key>RunAtLoad</key>
    <true/>
</dict>
</plist>