Link to home
Start Free TrialLog in
Avatar of cheesebugah
cheesebugahFlag for United States of America

asked on

Temporary User Profile Windows 7

Hello,

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?

Thanks,
Cheese
Avatar of tmoore1962
tmoore1962

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
Avatar of cheesebugah

ASKER

tmoore1962,

Can't seem to locate the policy location you speak of locally?
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.  

Thanks
ASKER CERTIFIED SOLUTION
Avatar of tmoore1962
tmoore1962

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
tmoore1962,

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?
This setting seems to have helped along with going through the steps I outlined.  We have not seen this issue since.

Thanks