I do have a problem with user profiles on a win7 and a vista desktop. in both cases the userprofiles only want to load temporarely. instead setting up a local profile from the roaming profile. this happened after deleting the user profiles from the machine. in followed the advisories on the subject, kb947215, but it did not solve this problem.

Actually: there is no SID.bak file in the registry which should be removed from the registry.

It must be a local machine problem, when I log the users in on a system they haven't seen yet or where the users are already known (without deleting of course) downloading the roaming profile is not a problem.

14 Replies

Why not rename the users profile on the server. This will allow the workstation to load up a new profile. Then move the files from the renamed one back into the new one once the new profile is working correctly.

Ensure the associated directories in c:\users are, in fact, gone. Some versions of Flash Player do odd things to the permissions on .OCX files located in the user directories that prevent the folders from being removed because they're not empty.

Run CHKDSK on the affected systems. File system corruption can cause a host of oddness.

i have been seeing this a lot lately. I think there may be a new virus causing this, but don't quote me on it. I have had to do a complete backup of local user data, delete the user profile, delete the user profile registry keys, have the user log in, then restore their data. It's a real headache, but it is more efficient than trying to get an answer out of Microsoft.

i have been seeing this a lot lately. I think there may be a new virus causing this, but don't quote me on it. I have had to do a complete backup of local user data, delete the user profile, delete the user profile registry keys, have the user log in, then restore their data. It's a real headache, but it is more efficient than trying to get an answer out of Microsoft.

No it's not a virus, you have no grounds to base that on.

me again wrote:

Why not rename the users profile on the server. This will allow the workstation to load up a new profile. Then move the files from the renamed one back into the new one once the new profile is working correctly.

This is the solution I've used when coming across the same issue as the OP.

I have seen this exact issue on our Windows 7 machines. Look at the link David8749 posted. The User Profile does not delete cleanly from the registry so when Windows boots the registry is pointing to a profile location that does not exist, and then creates a temp one.

I feel your pain... in the past I have had to go through the registry and clear out the user name in question. Typically, if the roaming profile does not unload in time it will leave fragments behind in the C:\users directory and or the registry and cause the users local profile to become corrupted on the computer. Use caution if you decide to hack the registry. I would make a backup of it just in case prior to going in and removing anything, just in case. When you are in the registry, search for the user name in question and remove when applicable.

In case anyone isn't aware of this, in widows 7, and probably vista, the correct way to delete a profile is to go to system properties > profiles and then select and delete. I haven't had that proven since.

After trying all this and that assuming this is a local problem I ended up frustrated. I followed all good advise, including the technet files on the subject. Nothing did the trick.

So I went over to the profile server to find out if something changed on the profile foldert. And yes, there was.

I looked to the security settings at the users profile folder. What happened: the destined user had no user and/or owner rights anymore on the folder. This happened after a local profile deletion on a machine, it shouldn't, but it did. the only thing I had to do was bringing in user rights again. Hereafter downloading the user profile was easy.

I must say I have never seen such behaviour on windows domain profiles. Normally when you locally delete a user profile nothing changes or should change on the profile folder at the server.

All this, of course, is a work around. The real problem is deleting user rights on a network folder when deleting a user profile from a local machine. Till this moment I don't know how and why this happened. I've never seen this before in 10 years of network engineering. I'd like to hear your experiences on the subject.

0

This discussion has been inactive for over a year.

You may get a better answer to your question by starting a new discussion.