10.10.3 Released

Alright, I got a 10.10.3 Recovery partition.

JSS 9.65, Casper Imaging 9.65.
10.10.3 Base OS created with AutoDMG 1.53
10.10.3 NetBoot (using the above Base OS) created with AutoCasperNBI 1.17.

Anyone seeing issues deploying the 10.10.3 combo via Self Service? I am seeing it hang up on "cleaning up" and not rebooting, though it looks like the install is done in the install.log. Same package works like a charm locally in the GUI. I have the policy set to install the 10.10.2 combo and reboot immediately.

@dgreen Sort of similar issue seen with applying the 10.10.3 update as the final stage of our imaging process. Netboot with Casper Imaging 9.65 puts down 10.10.2 autoDMG made OS and reboots with lots of after reboot pkg and scripts. The final script is to run Apple Software updates. It appears to do much of the 10.10.3 update but hanging and not doing the expected final reboot. I can see Photo.app is in place, but can't open console or activity monitor. For now, I've removed the software update script from the end of the configuration.

I suspect I can include the script again once I update our configuration to include the 10.10.3 autoDMG.

For what its worth my 10.10.3 base which I made in AutoDMG works fine when I image with 9.65 Casper Imaging. I tried to lay down the 10.10.3 Combo on top of the 10.10.2 base and it ends up sitting forever on the "Installing additional software" phase of the imaging. I tried to image the 10.10.3 base using 9.7 imaging and it hangs in the same manner. Ah well. We knew that this one was going to take some testing... So it is... so it is...

Created a Netboot image using AutoCasperNBI and an OS X 10.10.3 DMG using AutoDMG. Everything worked fine and the recovery partition showed up fine.

Currently using Casper 9.65.

Thought it would be wise to move the Netboot discussion.

10.10.3 Recovery HD Missing using AutoDMG

Regards,
TJ

Ok, so I can confirm that either installing the combo update via Self Service or running Software Update via Self Service coupled with the "Reboot Immediately" item WILL NOT reboot the machine, and results in a barely functional machine until a manual reboot. No bundled apps will launch, and any you try to launch will prevent a manual reboot until you force quit them. This is JSS 9.62.

Running Software Update from the command line (softwareupdate -ai) seems to work fine, as does running them from the App Store.

Any thoughts as to what could be causing this? We really need to be able to point people to Self Service for updates as we have done in the past. Our branded Self Service app is front and center in terms of the Mac Teams visibility, and not being able to use it for the 10.10.3 update breaks our successful run of offering both specific OS updates and being able to kick off Software Update.

Suggest opening a ticket with support. I've seen some hangups on a logout policy with just running softwareupdate -i -a (pointed, via configuration profile, to an internal server with updates enabled). I suspect the FirmwareUpdate.pkg may have something to do with this...

--Robert

I cried when I read the apple release notes...

Yeah... I am testing a few more things and then i'll file a ticket with support. We really like to control what users are allowed to do what via Self Service, and if we can't on this... well...

why not just add a reboot via the policy?

Oh I have, both the built in reboot options in the policy, and /sbin/reboot command. Neither execute a reboot. I see in the logs that the policy completes and blesses the system, but it hangs there and never reboots.

I am going to walk back my saying "softwareupdate -ai" works properly as well. While this method does grab the updates and installs them, once its finished and gives you the "You have installed one or more updates which requires that you restart your computer...", if you don't reboot and try to launch any of Apples included apps or utilities, they never launch and must be force quit before you can manually reboot. This is the same result as installing the combo update via Self Service or using a policy based Software Update kickoff.

I had one out of 43 users that updated run into the bouncy-dock-no-load weirdness after the combo update. Had him boot into Recovery, do a disk fix and permissions check/fix and he was back in business afterwards.

Yeah, thats what I am seeing with any method but the App Store method. A manual reboot brings the machine up as expected on 10.10.3.

I am having issues creating a monolithic image with 10.10.3. I built an image on a MacBook Pro and uploaded it to the JSS. I netboot the target machine, run my workflow, and then reboot the machine. It keeps coming up with the Circle/Slash saying the OS is no good. We are running JSS 9.65 and Casper Imaging 9.65.

@joemamasmac Step into the new with AutoDMG. I've had good luck imaging Macs old and new with 10.10.3 images created by AutoDMG.

@joemamasmac sounds more like a broken image. +1 for AutoDMG in this case, but if you wanted to troubleshoot, try deploying your image to the Mac in target disk mode using disk utility. If it still fails, its not related to Casper.

I see Apple places a Photos.app icon in the Dock for all local accounts in 10.10.3. Not surprised, but always frustrating.