Temporary Profile logged in...
-
I've saw this in a couple environments. I just saw this at my current company, where I logged into the domain controller with a domain admin account and I get notified it's a temporary profile. My username is not cached anywhere locally, but there are temp profiles in the list. Like temp/temp000/temp001. Any ideas?
I've usually figured that the file server couldn't be contacted, or the folder redirection GPO couldn't be processed, so it failed the job and simply logged the user in with a temp profile, but that doesn't seem to be the case here as we have lots of bandwidth (we own the 10GB fiber between sites), DFS to multiple servers with plenty of resources and a fairly low load.
-
Seems like some info is missing here.. do you have roaming profiles or what?
-
I should also mention that I have not logged into that DC with my username before. So there is nothing to delete locally in regards to my username (some recommend deleting the local profile and remove the registry entry). Though, that doesn't fix the root of the issue anyway, when people recommend it. It just gets written off as a corrupted profile.
-
There can be several reasons for this happening. Mostly, it is a corrupt user profile. You can navigate to the registry key and locate the user that has the .bak and rename it by removing the .bak
HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList
EDIT: LOL. Guess it isn't that...
-
@Jason said in Temporary Profile logged in...:
Seems like some info is missing here.. do you have roaming profiles or what?
No roaming profiles. We have folder redirection enabled as a GPO, and people use only the machine they're given so they don't move around.
Any other info needed? I couldn't think of anything off the top of my head...
-
Maybe this could be of use. Although, I don't know what Windows does if it tries to login and can't and then can't create a temp profile.
http://serverfault.com/questions/309692/disable-temporary-user-profile-on-workstations-in-a-windows-2008-envFrom the answer:
Use the group policy setting "Do not log users on with temporary profiles", to be found in Computer Configuration -> Policies -> Administrative Templates-> System -> User Profiles.So I did a search and found that it will just log the user out if it can't load the profile.
-
@wrx7m said in Temporary Profile logged in...:
So I did a search and found that it will just log the user out if it can't load the profile.
Care to post that link? I'd give it a read...
-
Nvm... it says it right in the GPO setting...
-
I've looked through so many YouTube videos and forum posts over many months on this... All comes down to removing the registry entry. Can't believe that nobody has posted anything other than that. Considering that this happens on different, much faster networks, logging into the DC, and logging into it for the very first time so a profile couldn't even be loaded to be corrupted.
Anyone?
-
@BBigford said in Temporary Profile logged in...:
@Jason said in Temporary Profile logged in...:
Seems like some info is missing here.. do you have roaming profiles or what?
No roaming profiles. We have folder redirection enabled as a GPO, and people use only the machine they're given so they don't move around.
Any other info needed? I couldn't think of anything off the top of my head...
I have dealt with this several times for a client with Folder Redirect.
Log in as the Local Administrator and do the Regedit.
https://support.microsoft.com/en-us/kb/947242
Generally, I delete ALL SIDs with the exception of the 18 19 and 20.
-
@gjacobse said in Temporary Profile logged in...:
@BBigford said in Temporary Profile logged in...:
@Jason said in Temporary Profile logged in...:
Seems like some info is missing here.. do you have roaming profiles or what?
No roaming profiles. We have folder redirection enabled as a GPO, and people use only the machine they're given so they don't move around.
Any other info needed? I couldn't think of anything off the top of my head...
I have dealt with this several times for a client with Folder Redirect.
Log in as the Local Administrator and do the Regedit.
https://support.microsoft.com/en-us/kb/947242
Generally, I delete ALL SIDs with the exception of the 18 19 and 20.
Ummm, you can't log in as a local admin on a DC... BUT the method is still the same using a Domain Admin account.
-
@BBigford run DCDIAG to check for errors
-
@nadnerB said in Temporary Profile logged in...:
@gjacobse said in Temporary Profile logged in...:
@BBigford said in Temporary Profile logged in...:
@Jason said in Temporary Profile logged in...:
Seems like some info is missing here.. do you have roaming profiles or what?
No roaming profiles. We have folder redirection enabled as a GPO, and people use only the machine they're given so they don't move around.
Any other info needed? I couldn't think of anything off the top of my head...
I have dealt with this several times for a client with Folder Redirect.
Log in as the Local Administrator and do the Regedit.
https://support.microsoft.com/en-us/kb/947242
Generally, I delete ALL SIDs with the exception of the 18 19 and 20.
Ummm, you can't log in as a local admin on a DC... BUT the method is still the same using a Domain Admin account.
Okay I may have missed that point that this was for the DC and not a desktop/laptop and you were dealing with users.
-
@BBigford said in Temporary Profile logged in...:
I've looked through so many YouTube videos and forum posts over many months on this... All comes down to removing the registry entry. Can't believe that nobody has posted anything other than that. Considering that this happens on different, much faster networks, logging into the DC, and logging into it for the very first time so a profile couldn't even be loaded to be corrupted.
Anyone?
I've this problem may times, only way to solve ii It's changing the windows register
I did not found any other way to do it.
-
I've run dcdiag, everything comes back showing healthy.
I don't want to go the route of the registry fix because I've saw this in multiple domains now, and it doesn't fix the root of the cause, it is just a work around and writing off the situation as "it's just a corrupt profile". Well I don't see how it can be corrupt when it's never been on that server before...
Seems like too common of a problem, and has been happening for years for there not to be more coverage on the matter than just deleting it from ProfileList.
