Have a strange issue when testing deployment of a custom 10.10.3 update pkg to 10.9.5 machines via Casper Imaging. The Casper Imaging Configuration worked perfectly with a 10.10.1 custom pkg, but now that I have replaced it with a 10.10.3 pkg when deploying via Casper Imaging, upon reboot, the screen has a dreaded prohibitory symbol on it. I've recreated the 10.10.3 pkg, thinking I did something wrong but every time, I replace the 10.10.3 with the older 10.10.1, it works fine. All custom pkgs create in combination of Rich Trouton's First Boot Install Generator and createOSXinstallPkg
Question
10.10.3 update pkg breaks current OS install
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
