Dominic Phelan
asked on
User being logged in with a temporary account
Hi All,
We are using Server 2012,
Currently one of my users is having issues logging onto his account,
When he does log in it comes up as Temporary account and all his data is missing?
How could this be fixed?
We are using Server 2012,
Currently one of my users is having issues logging onto his account,
When he does log in it comes up as Temporary account and all his data is missing?
How could this be fixed?
Sandeep has some good steps there, but his steps will only resolve the issue if the problem is with the local profile.
If the problem is with a roaming profile, those steps may not resolve the issue.
When the user logs on, the system will log the profile issue to the Event Log (I believe it's in the Windows System Event log, but could be in the App Event log). That log entry will give you the reason why the system failed to load the user's profile & is thus logging them in using a temp profile. Usually, a permissions issue is to blame. Or, I have seen a temp file cause a temp profile because the file name is too long.
So, if the user continues to get a temp profile after following the steps outlined by Sandeep, I would check the Event Logs for the reason the user is getting the temp profile.
If the problem is with a roaming profile, those steps may not resolve the issue.
When the user logs on, the system will log the profile issue to the Event Log (I believe it's in the Windows System Event log, but could be in the App Event log). That log entry will give you the reason why the system failed to load the user's profile & is thus logging them in using a temp profile. Usually, a permissions issue is to blame. Or, I have seen a temp file cause a temp profile because the file name is too long.
So, if the user continues to get a temp profile after following the steps outlined by Sandeep, I would check the Event Logs for the reason the user is getting the temp profile.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.
Now rename his profile from registry by browsing through Registry Editor (regedit)
HKLM\SOFTWARE\MICROSOFT\WI
in this find the key which got .bak name to the SID.
On right side you will see the values which can help you to identify the faulty profile. There is no harm to delete .bak (All) from there.
After you delete the .bak key you can log in with your profile and it should work.