2019 Macbook Pro Reset Itself

[djpatrickb]

Hi!

I am in IT at a marketing firm. One of our users rebooted his 16" 2019 MacBook Pro and when he logged back in the computer took him through a new setup of the computer. He lost all of his settings (including bookmarks) but all of his files and apps were still there. Has anyone seen this happen before or know why this may have happened?

Thanks for any help.
Patrick

 

[DeltaMac]

If the user decided to change the user account name, or accidentally changed the name of the user/home folder, the next restart would make a default account, still with the same, old name.
That kind of issue (resetting the user account to defaults) has been around since the beginning of OS X.
Apple still has not made it simple to rename a user account (safely)

Check the names of the user folders in /Users folder. You will likely find a folder (with a new name), in addition to a correctly named folder, created by the system when the user restarted the system.

 

[djpatrickb]

If the user decided to change the user account name, or accidentally changed the name of the user/home folder, the next restart would make a default account, still with the same, old name.
That kind of issue (resetting the user account to defaults) has been around since the beginning of OS X.
Apple still has not made it simple to rename a user account (safely)

Check the names of the user folders in /Users folder. You will likely find a folder (with a new name), in addition to a correctly named folder, created by the system when the user restarted the system.

Thank you. I did check the Users folders and only saw one correctly named folder (which is the one he is logged into now). One thing I failed to mention is that his Mac is joined to our company domain. When we set up his laptop we open the directory utility set the log in to create a "mobile" account and then bind it to our domain. When we log in for the first time as the user the Mac will ask if we want to create a mobile account and we say yes. I am thinking that the mobile domain account got corrupted somehow. I also just found out that this is the second time this has happened to this user.