|
Corey et al.,
In my initial testing, 10.10.2 exhibits the same behavior after a force shutdown. No joy. In my limited testing, I’ve found the workaround still is effective, but it has only been effective some of the time, on occasion requiring multiple cycles of force-shutdown
and re-execution of the workaround. I’ve only been testing on a single machine, so I do not know if this behavior is common or not.
Corey, the release notes did not include any clear reference to this problem, which is likely why it is not fixed. As our “Apple Insider,” is there any clarity around where this problem sits with engineering that you can provide, or additional gentle pressure
that you can exert? As it stands, moving clients to Yosemite results in a potential increase in support staff workload that we can’t afford to expose ourselves to. With the next OS update cycle just starting, I am not optimistic we will see relief soon. I’ve
spoken with level-2 enterprise support and received the “we’re aware of the impact” and “we can’t predict when it will be fixed” and a lot of “engineering doesn’t share that information with us” comments, all of which I understand, but none of which help me
communicate with my management a resolution roadmap.
Regards,
Andy
Andy, Zach, Don and everybody else…thanks for the excellent write-ups and detail on the issue. While I’m glad that the workaround was successful as an interim solution, I’m also curious if 10.10.2 fixed the issue. When you complete any testing and have some
results, let us know.
Thanks,
Corey
Corey Carson, Field Engineering Manager
Apple Education
Apple Inc.
(303) 746-1634
On Jan 22, 2015, at 10:33 AM, Andy Gerhard < email@hidden> wrote:
I have found Chris’s suggestion works in my environment. The “fix,” however, makes for a very long boot delay. So I’ve deployed a file of a different name to all my Yosemite machines that will allow the support personnel to quickly resolve failed
boots without imposing the penalty of slow boots across the install base.
I created a script /etc/rc.server_bootfix that contains:
#!/bin/sh
/usr/sbin/BootCacheControl jettison
mv /etc/rc.server /etc/rc.server.bootfix
My instructions to my support team are:
Boot single-user (command-s)
mount –uw /
mv /etc/rc.server_bootfix /etc/rc.server
Exit
The machine boots (slowly). Subsequent boots do not run the script, so boot performance is not affected. Users that are in the habit of forcing shutdown can have the last line of the script removed and suffer long boots until 10.10.2 is released.
As for saving files as PDF’s to get around version mismatches in iWork, we long ago concluded that this was not a viable solution for students, particularly in the lower grades. That decision has caused us to scramble with each iOS release, but
that’s why we use Casper Suite to manage our OS X devices.
With 10.10.2 in developer preview, and the observation that AD/force-shutdown does not result in a boot-hang in 10.10.2, I am hopeful the release is just around the corner.
Regards,
Andy
Thank you Don! I am so grateful that you have found this article. I am embarrassed I didn't find it. Thank you for all your help and support Rockies Edu!
Zach
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Rockies-edu mailing list ( email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
|