Temporary User Profile Windows 7


I have a user here who keeps getting the Windows 7 temporary profile when she logs on.  We are a Windows domain with roaming profiles.  She is a roamer and the profile is copied to her home folder and is pulled down from there via her AD account.  I have tried deleting the SID.bak file from the registry and the local profile, to no avail.  I copied the profile from her home folder over to her local profile.  That did not work either.  I have not given her a new AD account yet.  Any ideas?

Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

network isn't ready when system logs on run gpedit on the machine administrative templates / system / logon enable always wait for network at startup and logon and see if that corrects issue, if not make sure user is owner and has full access to the folder that has roaming profile
cheesebugahAuthor Commented:

Can't seem to locate the policy location you speak of locally?
cheesebugahAuthor Commented:
Okay, I deleted all of the local profiles for her again.  I then logged her off of the computer.  I then renamed her profile folder on her home folder.  I then logged into AD and removed the path to her roaming profile.  I then logged her onto the machine.  I copied everything from the renamed profile folder over to her newly created local profile.  I then went back into AD and put the path to her roaming profile back.  I then had her log off and then log back on and it seems to have done the trick.  I did get a warning that not all of the profile was copied, but she seems to be able to run everything as she did before.  

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

on the workstation run GPEDIT.MSC with admin account go to  administrative templates / system / logon enable always wait for network at startup and logon

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
cheesebugahAuthor Commented:

Thank you for your recommendation.  I will look into this policy.  Is this policy something you have set before on workstations in a domain environment with roaming profiles and/or logon scripts and/or group policies?
cheesebugahAuthor Commented:
This setting seems to have helped along with going through the steps I outlined.  We have not seen this issue since.

It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows 7

From novice to tech pro — start learning today.