Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1396
  • Last Modified:

User Profiles on Terminal Server Continue to added with an incremented number at the end. eg user.000 & user.001

I have several users that continue to get a new profile created every time the log in to TS.  the profiles just incremented by one digit.  eg user.000 then user.001

Users have access to the directory where the profiles are, hence the ability to have new profiles created.

We do not use roaming profiles.

Also the registry has been reset back to the default.

I have deleted the duplicate profiles for users and they keep coming back.  Can't keep up the maintenance of deleting profiles and users are tired of losing their settings for things link Word and IE.

This seems to have stemmed from having to repair 2K3 after a drive  reactivation was not successful.

How can I correct this problem once a for all?
0
TX_SCUBA
Asked:
TX_SCUBA
  • 3
1 Solution
 
michaelgoldsmithCommented:
You can set a group policy to delete cached copies of roaming profiles...  Which will delete the directory entirely on the client machines at logoff.
0
 
TX_SCUBAAuthor Commented:
We are not using roaming profiles.

This issue is around the correct profiles apparently not being accessed during start up. so the system creates another one.

There is no issue with the client machine this is taking place on the Terminal Server
0
 
StuFox100Commented:
Try installing the User Profile Hive Cleanup Service:
http://www.microsoft.com/downloads/details.aspx?FamilyId=1B286E6D-8912-4E18-B570-42470E2F3582&displaylang=en
This normally happens when the profiles don't unload correctly.
Cheers
Stu
0
 
TX_SCUBAAuthor Commented:
StuFox100

Should have mentioned I have that installed and running.  I does clean up the lingering app thread.
0
 
TX_SCUBAAuthor Commented:
I has to modify every use's profile in the registry of the Terminal Server.  Somehow the key was set to not allow access to the user profile files.  Found solution on google after looking up the user.000 & user.001 variables.
0

Featured Post

Free learning courses: Active Directory Deep Dive

Get a firm grasp on your IT environment when you learn Active Directory best practices with Veeam! Watch all, or choose any amount, of this three-part webinar series to improve your skills. From the basics to virtualization and backup, we got you covered.

  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now