This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Issues with Mac User Profile Corruption

After making a lot of headway last week with Safeguard for Mac, I've hit a new roadblock and it's the second time I've experienced this. 

Sequence of events:  logged in as a network / mobile user.

Notification of OS Updates.  Apply and reboot.

Preboot Filevault menu comes up.  Select network user.

Progress bar gets to 50% and hangs.

The first time this happened, I only had one user as an owner and could not get past the 50% mark so I had to erase the hard drive and start over.

This time I had two other local users and one other network user in the pre-boot.

I logged in as a local admin in preboot - which successfully loaded the OS  - and then logged out and logged back in as the network user in question.  I was able to finally log in, although the process was similar to a new user login - asking me for icloud stuff, which I skipped.  This was odd.

Unfortunately, I was unable to properly log out with hanging.  Finally, I deleted the user while logged in as another user.  Now I am logging back in as the user in question, but it is crawling and hanging.

Multiple questions:  Are network logins more prone to corruption than local logins?  Or, is this something that only happens with SafeGuard for Mac?

Thanks for any suggestions you have.

Adam in DC

:56758


This thread was automatically locked due to age.
  • Hi Adam,

    we are aware of this issue (see SafeGuard Enterprise 7.0 Release Notes extract below) and have also reported to Apple.

    This should have been addressed in the recent 10.10.3 release (https://support.apple.com/en-us/HT204490 - "Addresses an issue that could cause Macs bound to an Active Directory server to become unresponsive at startup")

    If you're not running 10.10.3 and want to prevent the issue from occurring, you have to unselect "Use UNC path from Active Directory to derive network home location" option via the 'Directory Utility' on the OS X client.

    "Limitations on Mac OS X 10.10

    A computer may hang when FileVault 2 is enabled: It has been observed that some machines did not successfully boot if mobile accounts are used and following conditions are met:

    • A network home directory is configured in Active Directory
    • The option "Use UNC path from Active Directory to derive network home location" is enabled on the OS X client
    • The network connection is not reliable or not available at all when the computer starts

    To fix this issue, the System Management Controller and also the PRAM have to be reset (see http://support.apple.com/kb/ht3964 and http://support.apple.com/kb/PH18761) possibly multiple (up to 10) times."

    Regards,

    ChrisD

    :56791
  • Thanks for pointing this out.  As you can tell about my multiple posts on SafeGuard for Mac, to effectively deploy the product, you need to know the mac - which is hard for a Windows guy.  This process has forced me to reinstall Yosemite about 6 times - a good thing.  While the fix on this problem is to effectively disable every aspect of a Mobile account on the Mac, this turns out not to be a terrible thing because while the file-sync feature on the Mac is neat in theory, it's terrible in real life.

    The key thing is that Mobile Accounts are necessary on a Network Login on a MacBook.  So, you get the mobile account in name only, with no file sync or recognition of the Active Directory home drive...but that barely matters.  It will matter when Apple comes up with a better method, and hopefully, Safeguard will be able to deal with that technology, whever it may be.

    :56815

    Adam in DC

  • Dear customer,

    SafeGuard Enterprise is able to work with several configuration options. But with this case we should be careful to point in the right direction. You can use SafeGuard with OS X 10.9.x without having similar issues and the available Active Directory configurations are the same if you compare this with OS X 10.10.x. So far we know this issue can be found in several forum entry without involving SafeGuard products. There are some improvments done with OS X 10.10.3+ and we hope that this issues will be resolved in your environment with the latest Apple patch level as well.   

    Best regards
    Rainer

    :57273