This question comes up in one form or another fairly often especially in the context of Terminal Services.  Terminal Services and other services store certain information in an attribute on the user account called userParameters.  Some of the most common items to be stored here is TS profile and TS home directory path.  Other information specific to the user and Terminal Services is also stored here if you are using the legacy methods of the user account storage to perform the given task.

 

Various reasons may exist where you may want to remove this attribute for troubleshooting or perhaps you want to clean your environment up and get rid of the attribute for some or all user accounts.  This may be especially true if you have retired applications which once used this attribute but no longer do.  Be sure that if you delete the attribute you are fully prepared to repopulate the necessary information if needed.

 

If you are interested only in the Terminal Services profile and Terminal Services profile path, this can now be set on Windows 2000 and Windows 2003 using group policy. 

 

More information on the Windows 2000 policy:

policy which allows you to specify TS home and TS profile path on Windows 2000

 

To delete the users blob you may use a rather simple method I documented in this KB article, the relevant section is below:

  

1.

Create a text file with the following lines of text, where username is the name of the user account with the corrupted information and where domain is your domain name.

dn: CN=username,CN=Users,DC=domain,DC=com
changetype: modify
delete: userParameters

2.

Name the file "Users.txt."

3.

At a command prompt, type the following command to run the file:

Ldifde –I –f users.txt

Running this command will also clear the properties and resolve the issue on an Active Directory domain.

Note Clearing the userParameters attribute in the user account may affect other programs. If program-specific information is stored there, it will have to be repopulated. For example, programs that may be affected are FPNW, RAS, and all Terminal Services-specific user information.

 

 

 

Greg Lirette

 

This posting is provided "AS IS" with no warranties, and confers no rights.