Windows 2008 Remote Desktop User Profile Stored on RDS Server

I have a Windows 2008 R2 Standard Remote Desktop Services server that's part of a Windows SBS 2008 Domain. I'm trying to setup user profiles so that when a user logs into the RDS server, their profile is stored in a central location on the network (\\computername\sharename\useraccount). This is working fine, but it appears that any documents or settings changed by the user are also being stored on the RDS server. I would like the RDS server to strictly be an application server that does not store any data, including user profiles. I've been playing around with the settings in Active Directory to ensure profiles are pointed to the share location, but nothing I do seems to prevent user files from also being stored on the RDS application server. What am I missing?
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.


You can use  roaming profiles and have them point to a central location like what you are doing now and set a policy for your  RDS servers that deletes cached roaming profiles when the user logs off.

Even if you have a centralized store for roaming profile a profile still has to be created on each computer that the user logs onto.  Your profile contains registry settings which are contained in a ntuser.dat file.  
brownmetalsAuthor Commented:
My fear is that these local profiles that are created on the server are going to become bloated and take up more disk space than I'd like. If I understand your 1st post correctly, the GPO you're speaking of will remove the profile from the RDS server as each user logs off. Is that correct? If so, where might I find this policy. I haven't been able to stumble upon it as of yet.

Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.


First, I would put your RDS Servers (Terminal Servers) in a OU named RDS and created a gpo called  "removed roaming profiles when logging off" or something like that so you know the gpo is doing.  Then I would enabled the setting in the gpo to delete cached copies of roaming profiles.

to enable the setting the following the instructions below:

Locate the Group Policy object (GPO) to which you want to apply this setting.
Expand Computer Configuration, expand Administrative Templates, expand System, and then expand User Profiles.
Double-click Delete cached copies of roaming profiles, click Enabled, and then click OK.

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
brownmetalsAuthor Commented:
Thanks for that great info. This does in fact delete the user's LOCAL profile on the RDS Server, but it throws this warning in the Even Viewer.

Event ID 1517

Windows saved user DOMAIN\User registry while an application or service was still using the registry during log off. The memory used by the user's registry has not been freed. The registry will be unloaded when it is no longer in use.

This is often caused by services running a a user account, try configuring the services to run either the LocalService or NetworkService account.

I found this article that provides further explanation:

I also found this article which suggested using the User Profile cleaner to help alleviate the issue:
However, this utility can not be run on a 64-bit machine (I'm using a 64-bit RDS Server).

The first article suggests nothing needs to be done. The 2nd article offers a solution that would work for a 32-bit machine. My concern is that there could be memory leaks if these profiles aren't unloaded properly. Any further thoughts?



check this out:

they have a beta release

From my experience with Terminal Servers I have seen memory  leak issues with user profiles.  I come from an network that is the largest private enterprise network in the world with over 700,000 pc workstations and thousands of servers including terminal servers I have never seen memory leaks associated with roaming profiles.

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 Server 2008

From novice to tech pro — start learning today.