Casper Imaging 9.32? I would not use a version of Casper Imaging prior to 9.65 to try to lay down a 10.10.2 or later base OS. Can't believe it's working for you, knowing the version detection code in Casper Imaging was horribly broken before the (pulled) 9.64 release.

Is anyone still seeing this behavior with 9.72?

9.72 (JSS/Casper Imaging app) is working fine for me. Lays down an AutoDMG-created 10.10.3 and Recovery HD, no secondary installers/packages needed.

Having some issues with imaging new OOB machines with CoreStorage enabled out-of-the-box, can diskutil core storage revert /dev/diskx and then it works fine, but really wish Casper Imaging would handle this automagically (like it apparently did for some in 9.65).

Just tried my first NetBoot imaging with JSS 9.72/Casper Imaging 9.72/AutoDMG'd 10.10.3/AutoCasperNBI 1.2 and it put down the Recovery HD. Huzzah.

Just a note here. I had the same issue with no Recover Partition using AutoDMG. I was also using create user package. This was done to add a local admin on my image. The package was then added to Additional Software (lower input box on AutoDMG). I found that doing this while creating the image was causing the issue.

Fix was to create the image only with the OSX App. Do not add any additional software. Once the DMG was created you can drop that back into AutoDMG and add the Additional Software. Hope this helps someone.

I usually keep my base OS image clean/virgin and add the CreateUserPkg (and many other packages and scripts) to my imaging workflow, for maximum flexibility.

Fantastic news, @emilykausalik !
I will be attempting to go from Casper Imaging 9.65/JSS 9.72/AutoDMG'd 10.10.3/AutoCasperNBI 1.2 to Casper Imaging 9.72 tomorrow.

Fingers crossed along with @mhasman !

FWIW...Apple Developer login required:

Recovery HD missing (<REDACTED>)

Don