Profiles are often reset for RDP users on RDS server

I have a domain with a Microsoft Small Business Server 2011 Premium plus two additional servers.
The os on the servers is Server 2008R2 X64.
On one server I have installed the Remote Desktop Services role and added 25 remote users.

For some strange reason, these users often complains, that when they log into their profile on the RDS server, their profile is back to default. This means, that they have to setup Outlook with profile, printers, desktop and other things.

Can anyone give me a clue in the right direction?
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.

MikeIT ManagerCommented:
It sounds like they are logging into temporary profiles due to an issue with roaming profiles loading.  I would check event viewer to confirm this.

This KB article may help you if this is the case
Joshua GrantomSenior Systems AdministratorCommented:
This would be happening if their user profile folder under C:\Users is being deleted. I would check for any scripts that are setup for automated tasks.

I would also make sure that its actually reverting to default. It could be that they are being logged in to a TEMP profile and if that is the case, that would delete their profile on logout.

Another possibility is that roaming profiles are being used and the path does not exist or is not writable. This would also cause a TEMP profile.
Spike99On-Site IT TechnicianCommented:
I would check the event logs. If the users are getting temp profiles due to some sort of issue, the logs will give you the reason why they're having a problem.  

Problems loading a roaming profile will often cause that to happen.  If a file can't be copied from the roaming profile to the local profile folder for whatever reason (file name too long, file can't be found, insufficient rights to the folder are examples)

With server 2008, if you "clear" a user's local profile by just deleting the user's folder from C:\Users, it will cause issues. This is because just deleting that folder leaves behind the registry entries associated with that profile.  Server 2003 was cool with that: it would just re-create the folder if the folder referenced in the registry couldn't be found. But, in 2008, the server will look for the folder & if it doesn't find it, it will not create a new one.  It will generate an error & load the user with a temp profile.

You will need to look in the registry to see a list of the profile hives for each user. Each user will be listed by their SID.  To find a particular user's SID, run this command at a command prompt, substitute the actual user name & domain name:

wmic useraccount where (name='USERNAME' and domain='MY_DOMAIN') get name,sid

Open in new window

Then, look in this key in the registry
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList

Each user with a profile on the server, should have a SID listed there.  If a person has a temp profile, they will actually have 2 entries there when they are logged on: SID and SID.bak.  When they log off the SID will go away & only the backup of the profile hive ending in .BAK will remain.

What does the event log say is causing these issues?   Depending on what you find, you might need to just clear the remnants of the user's profile from the server to resolve the issues.

To clear out the profile manually for a person with a temp profile problem, do the following:
1.  have them log off (the temp profile in C:\users and their temp profile key in the ProfileList should go away when they log off)
2.  check the ProfileList key for their SID
3.  Only the backup profile hive ending in .BAK should be there, delete it
4.  If you have configured a roaming profile folder for them, rename the current profile folder to USERNAME.OLD
5.  Create a new roaming folder for them using the same name as the old one
6.  Give the user FULL rights to the folder
7.  Have them log back on to the terminal server
8.  Once their local profile has been re-generated, have them log off to verify the local profile is copied up to roaming profile folder as expected
9.  Copy over any files or folders they might need from their old profile to their new one (like NK2 files if you're using Outlook 2003 or their MS signatures folder)
10.  Then, they are ok to log back on

By default, Admins are not granted any rights to roaming profile folders if they are auto-created when the user logs on. So, if you have trouble renaming the folder, you will have to take ownership of the folder to rename it.

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

From novice to tech pro — start learning today.