@spraguga][/url : Your post is much appreciated, and saved my organization lots of time. Thanks!
I used your knowledge as a starting point, and did a little more testing. I was looking for a way to avoid stripping out the homedir redirection, as many Mac users in my organization use that functionality. I stumbled onto a workaround that worked for me. I was able to confirm that the workaround is successful on all the Macs in my organization that presented the issue.
TL;DR
1) Login normally until you see the progress bar
2) DONT TOUCH ANYTHING until you see the spinning pinwheel of death (~60 to 120 seconds)
3) Hit enter (if it does not immediately work, wait \~90 seconds and hit enter again)
4) Profit.
Here is a write up of this, included for clarity. I honestly laughed out loud when I figured this out.
Issue: On Macintosh computers running OSX 10.10 (Yosemite), there is an issue with logging into an Active Directory account, when “off the wire” (i.e. not on the network with access to the location that the OriginalHomedir Attribute points to.) with FileVault enabled
Symptoms: Upon login attempt from cold boot, progress bar will quickly reach \~25%, and stop, followed shortly by the cursor turning into the Apple “pinwheel” and spinning. The spinning appears to continue forever.
Suspected cause: When logging in from cold boot, with FileVault enabled, 2 things happen: 1) Filevault disk lock is “unlocked”, and 2) login to the selected account is attempted. In cases where the home directory is an unaccessible SMB share on an Active Directory account, the disk will be “unlocked” and login is successful, but OSX will throw an error dialog stating that the SMB share can not be connected. Unfortunately, at this time, it spawns that error dialog behind the login screen, where the user can not see it, nor move focus back to it if initial focus is lost.
NOTE: If one were to “Login” from cold boot with a local account that does not have an SMB Share mounted as the home directory account, log out of the local account, and then login as the network account, the dialog is spawned in the correct GUI ‘layer’, and the user is able to see it and move focus on and off of it. In this scenario, it displays the same behavior of the spinning pinwheel until the “Close” button is pressed.
Workaround: When logging in from cold boot, enter password and hit the login button or press enter, as you would normally. Once you see the progress bar, it is imperative that you not click anywhere. The cursor will be drawn on the screen at some point; if it is not on screen after 10 seconds, move the cursor around till you can see it. In between 60 and 120 seconds, the cursor will start to pinwheel. Press enter. Login should finish almost immediately and drop you onto the desktop. If it does not immediately work, wait \~90 seconds and hit enter again.
TL;DR
1) Login normally until you see the progress bar
2) DONT TOUCH ANYTHING until you see the spinning pinwheel of death (~60 to 120 seconds)
3) Hit enter (if it does not immediately work, wait \~90 seconds and hit enter again)
4) Profit.