Domain user gets temp profile on all machines she logs in to

[cprelude]

Hi all,

 

We have a user on our domain (Windows 8.1 client PCs), who, whenever she logs on always gets a temporary profile assigned. I have so far tried all the routines involving deleting her profile from registry (dealing with the .bak profile if present etc). I have tried Deleting ntuser.dat, ntuser.ini and and ntuser.dat.log from her network profile. I have checked her profile path in AD Users and Computers, for any rogue characters. Both based on advice from other forums. Nothing has worked so far.

 

Does anyone have any suggestions that might help us out of this?

 

Best wishes,

 

Paul

[round2it]

permissions on the share where you store profiles?

[chazzy2501]

The event viewer is your friend here, what ever it is I can't imagine it's not there. On the local PC.

[Sonic007]

We used to have this issue.

Are roaming profiles turned on? These cause more problems than sollutions Ive found.

 

As well as clearing the profile from registry, make sure the user is completly out of the system and then remove the profile from the server.

 

Also delete her c:\users folder too. Reboot.

 

Try logging in again after that.

[MatthewL]

There isn't a profile specified within AD is there?

[dapaulio]

Where is your profile stored?

Look at Permissions on the share as well as the Nt security permission

Or

Is the user in question part of the group that has permission to read/write the profile?

[dapaulio]

There isn't a profile specified within AD is there?

 

Has the user got a home directory specified in ad and share and permissions set correctly

[cprelude]

Thanks to everyone who has posted so far, and sorry for delay in replying. I have checked the following: The user does have a profile path specified in AD, but, there again, so do all the other users, and they don't have this problem. I have checked the permissions on both the profile folder, and the user folder, and, all I can tell you is that these are exactly the same as for every other user on the system. I.e., no obvious discrepancies that would cause her login to be rejected each time. I did check the event viewer on one of the clients and, despite what I just said about permissions, there is the following error message in Event Viewer: Windows could not load your profile because a server copy of the profile folder already exists that does not have the correct security. Either the current user or the Administrators group must be the owner of the folder". This message appeared to be very helpful. Except, as I say, when I went to look closely at the security settings for this user's profile, they are identical in every way to the security settings for other users who don't have this problem. Just wanted to update you all with the things I've tried, and very many thanks again to all who have so kindly posted. But I'm still looking for something that will get us out of this?

[tdecker]

Hi cprelude,

We have experienced this issue occasionally. The best fix I have found is to reimage the computer.

Tony

[dapaulio]

Hi cprelude,

We have experienced this issue occasionally. The best fix I have found is to reimage the computer.

Tony

 

My understanding is it follows the user to what ever pc she logs onto.

Other users are ok on the computers that the subject user is not.

 

How old is this user on the network?

Has she never been able to logon successfully?

[tdecker]

Make sure there is nothing in Profile Path on her account, otherwise, I would try deleting her AD account and make her a new one. Sorry if that's already been suggested.

[Katy]

Have you tried deleting the profile folder on the server? (don't just empty their folder, delete it completely - or if you want to be able to rescue items out of it then just rename it, I usually rename to _username). Then make sure they're not logged on and delete the local cached profile off the machine. The next time they log on they'll get a fresh profile, then when they log off it should save back to the server with whatever permissions it deems "correct".

[cprelude]

Hi All,

Well, thanks again for all the helpful contributions, and sorry for the delay in updating. In the end, this got solved in quite a low-tech way. We found every PC the particular user had ever used in the school and blitzed her local profiles on all of them, meanwhile making sure she was not logged in anywhere else. Then one by one we tested her login on each machine we had just worked on. Hey presto, we got her clean profile back on all the machines. I'm not at all saying this is the definitive method, and other suggestions here may also have worked. However, the user is now back up and running again. Thanks again, everyone.

Paul

[kevin_lane]

You could also use delprof and delete any profiles older than x amount of days or by size aswell