Posted on 07-09-2012 11:40 AM
Hi, I am creating a new netboot image from the 2012 macbook pro build, its working for any MBP that shipped with 10.7 but with older MBPs it crashes when trying to launch with the error "Casper Imaging could not find the target disk: Macintosh HD" and then "Error parsing XML for Autorun"
I am using Casper 8.31 but I also tested 8.52 with the same results.
During my testing I dropped my dmg image to a mid 2010 MBP and tried to launch Casper Imaging, it launched into an image confg automatically and looked like it was trying to run the packages, I killed it and started the app again and got the “could not find the target disk” message anytime after that.
Any Ideas or advice would be nice. Thanks.
Solved! Go to Solution.
Posted on 07-17-2012 08:11 AM
Please disregard my orignal problem, found out this problem was specific to this computer and I was able to correct the issue. The 10.7.4 mid 2012 netboot image is working fine on the older hardware and I am testing the image itself now.
Posted on 07-11-2012 11:27 AM
We are working on a Mid 2012 MacBook Pro image, so wondered if anyone is having this problem, where NetBoot image from this new model isn't allowing older models to NetBoot? We can keep our current images, with the Lion 10.7.4 as default, but was hoping not to have to ask the deployment techs to hold OPTION on reboot to select specific images. :)
Posted on 07-11-2012 11:46 AM
I believe it's one netboot for 2012 macbook pro, one for 2012 airs, and one for everything else, until 10.7.5 is released.
Posted on 07-12-2012 12:20 PM
My image built using 2012 MBP works on all my MBP Hardware (have not worked on Airs yet). I am only having problems launching Casper Imaging on any MBP that is pre 10.7.0 hardware.
Posted on 07-12-2012 02:22 PM
@CasperSally Yep, sounds right. I'm wondering though why a Mid 2012 MacBook Pro that shipped with 10.7.3 (11D2097) won't boot from our 10.7.4 (11E53) NBI. :(
Don
Posted on 07-17-2012 08:11 AM
Please disregard my orignal problem, found out this problem was specific to this computer and I was able to correct the issue. The 10.7.4 mid 2012 netboot image is working fine on the older hardware and I am testing the image itself now.