roaming profiles keep coming back on server share

I used to use roaming profiles for users but have switched to using folder redirection to prevent documents from being cached in c:\users on the Windows 7 Professional workstations.  Folder redirection went just fine with GPO and I have Documents, Pictures, Favorites and Desktop being stored in each user's secured home folder.  I went into all user accounts and cleared the profile path which used to point to \\servername\profiles$\%USERNAME%.

Even though I have cleared this out of the user account and deleted the roaming profiles, each morning I still see roaming profiles being created in the share again.  Why is this and what am I missing?  I know the Windows 7 registry tracks where the roaming profile is, but I'd think this would reset the next time the user logs in and this would clear out based on it not being a property of the user account any longer.
LVL 1
Steve BantzIT ManagerAsked:
Who is Participating?
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.

William FulksSystems Analyst & WebmasterCommented:
Go to Control Panel - System and click Advanced system Settings, then under the Advanced tab click the Settings button next to User Profiles and see what the Type is. You can try changing it there, or you may need to create new user profiles for everyone.
0
Steve BantzIT ManagerAuthor Commented:
The problem eventually went away.  It must take a couple of logins for the registry key on the workstation to know there is no roaming profile on the server anymore.  HKLM\SOFTWARE\MICROSOFT\Windows NT\CurrentVersion\ProfileList refects there is no roaming profile any longer.
0
William FulksSystems Analyst & WebmasterCommented:
Group Policy changes can take up to 90 minutes to kick in, so if the users had their computer off when you made the changes, then when they turned them on and logged in it would still be trying to operate under the old policy until it updated, and then that update would reflect the next time they logged in, which may not be until the next day. That may explain why it took a little while.

https://technet.microsoft.com/en-us/library/Cc940895.aspx
0

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
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.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.