[MacTUG] Yosemite and AD bound Macs not booting when away from corporate network.

[Herbert Balagtas]

I've only encountered this issue with one prof with an iMac who upgraded to Yosemite. What we did was to login into a local account, disabled FV, restarted and enabled it again.

After that I've able to login using AD accounts without locking up.

Best regards,

Herbert Balagtas
Unix Systems/Web Development Specialist
Arts Computing Office, PAS 2026
Hbalagtas at uwaterloo.ca<mailto:Hbalagtas at uwaterloo.ca>
519-888-4567 x 32597

How was my service today? Please fill out the survey and let us know!<https://uwaterloo.ca/arts-computing/feedback-form>
https://uwaterloo.ca/arts-computing/feedback-form

From: mactug-bounces at lists.uwaterloo.ca [mailto:mactug-bounces at lists.uwaterloo.ca] On Behalf Of James McConachie
Sent: Wednesday, November 12, 2014 10:28 AM
To: mactug at lists.uwaterloo.ca
Subject: [MacTUG] Yosemite and AD bound Macs not booting when away from corporate network.

*
An interesting thread I've been following from the PSU MACENTERPRISE Lists. We (MFCF) have not tested so no first hand knowledge to impart. Consume with the appropriate reticence.

/James
MFCF


We are seeing this issue involving FV2 and the mobile accounts unlocking
the disk off network resulting in the stuck progress bar.

John Altonen



On Tue, Nov 11, 2014 at 8:53 PM, Eric Boughton
wrote:

> Hi,
>
> We have been seeing an issue with Yosemite 10.0, Filvevault and upgrade
> installs. It sounds like the issue you are describing. The user will login
> to a Mobile AD account on the system and then get stuck with the loading
> bar at half for hours. The sort term fix has been and archive install and
> then disabling filevault. I reached out to apple and submitted a but as
> well but I dont have any fix yet.
> I'll take a look at see if there is some logs about the watchdog for AD.
>
> I'm recommending users wait till 10.1 right now.
>
> ~Eric
> ________________________________________
> From: Mac OS X enterprise deployment project
> on behalf of Jussi Uosukainen
> Sent: Tuesday, November 11, 2014 4:03 PM
> Subject: AD bound Yosemite machines not booting (outside of the company
> network)
>
> Hi,
>
> we just came across this at a client site: laptops bound to the ad
> will not boot outside the network, but get stuck (for hours) during
> the boot process. The logs reveal little, the only stuff in system.log
> when a machine is stuck in the boot process are multiple warnings
> about watchdog, but that seems unrelated.
>
> watchdogd[]: [watchdog_daemon] @( wd_watchdog_open) - IOIteratorNext
> failed (kr=0)
>  watchdogd[]: [watchdog_daemon] @( wd_daemon_init) - could not
> initialize the hardware watchdog
>  watchdogd[]: [watchdog_daemon] @( main) - cannot initialize the
> watchdog service
>
> Instead, there are several other people complaining about this on the
> apple forums:
>
> https://discussions.apple.com/thread/6650075
> https://discussions.apple.com/thread/6606429
>
> The machine can be made to boot with a pram-reset or similar
> shenanigans, but it needs to be done every time. Filevault2 is
> enabled.
>
> I am not too familiar with the inner workings of the AD plugin, but
> this seems like an issue that more people on this list would have come
> across. Or are your users conservative enough to wait until 10.10.1?
>
> Any troubleshooting ideas? I plan to test the "force local home
> directory on startup disk" -option and if it has any bearing, but
> otherwise  I am a bit short on ideas. Any help greatly appreciated!
>
> --
> Jussi Uosukainen
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.uwaterloo.ca/pipermail/mactug/attachments/20141112/c994022b/attachment.html>