+8So, in 10.12.2, we have found on multiple models that using Migration Assistant to migrate applications results in the binding to our AD break, and in some cases it can not be re-bound due to an authentication error, requires an erase and re-image.
Is anybody else seeing this? More importantly, has anybody figured out a way to solve this issue (short of not transferring applications)?
+20Did any of those migrated accounts happen to have iCloud set up at the time?
There is a long thread on JamfNation about AD binding issues in Sierra, which appear to be resolved in 10.12.3 (still in beta).
+8So, I've actually had two issues: One is the account, which may be what you're referencing, and I've just told my users that I can move their data manually but can't bring over preferences, etc.
The other is simply migrating applications, which is what I'm currently experiencing. Migrate apps, binding is shot.
+13We have seen this issue but attributed it to JAMF enrollment. If the receiving Mac was on JAMF before migration, we had issues. If we removed JAMF then migration worked.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.