Article ID: 821929
Article Last Modified on 1/3/2008
APPLIES TO
- Microsoft Windows Server 2003, Standard Edition (32-bit x86)
- Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
- Microsoft Windows Server 2003, Enterprise x64 Edition
SYMPTOMS
When you configure the Set path for TS Roaming Profiles Group Policy setting, this setting does not work as expected. Specifically, if two users with the same user name in different domains log on to a Microsoft Windows Server 2003-based terminal server, they cannot access their Terminal Server roaming profiles.
When this problem occurs, the following entry appears in the Application log:
Event Type: Error
Event Source: Winlogon
Event Category: None
Event ID: 1219
Date: 5/27/2004
Time: 9:35:22 AM
Description: Logon rejected for user_name. Unable to obtain Terminal Server User Configuration. Error: The RPC server is unavailable.
CAUSE
This problem occurs when both of the following conditions are true:
- Users with the same user name are hosted in different domains.
- One of those users has logged on to the terminal server and has created a roaming profile.
For example, in a scenario where the following users exist
username1@example.com
username1@domain.example.com
if username1@example.com logs on to the terminal server, a roaming profile that is named "username1" is created. When username1@domain.example.com logs on, username1@domain.example.com cannot access the existing username1 profile. After you apply this hotfix, each user receives a unique profile name with a format of username.domain.
RESOLUTION
Hotfix information
A supported hotfix is now available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next service pack that contains this hotfix.
To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:
Note If additional issues occur or any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. To create a separate service request, visit the following Microsoft Web site:
Prerequisites
No prerequisites are required.
Restart requirement
You must restart the computer to apply the changes after you apply this hotfix. However, you do not have to restart the computer immediately after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace any other hotfixes.
File information
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
Windows Server 2003, 32-bit versions
Date Time Version Size File name ----------------------------------------------------------- 14-Jul-2003 21:58 5.2.3790.68 538,624 Winlogon.exe
Windows Server 2003 64-bit Itanium-based versions
Date Time Version Size File name ----------------------------------------------------------- 11-Jul-2003 19:39 5.2.3790.68 635,904 Winlogon.exe IA-64
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
MORE INFORMATION
After you apply this hotfix, Windows determines the location of the user's home directory by using the following logic when a user logs on:
- Try to locate the ...\
UserName.Domainpath. If it exists and the user has full control permissions configured in the folder, this path is used for the home directory. - If ...\
UserName.Domainis not accessible or does not exist, try to access ...\UserName. - If ...\
UserNameexists and the user has Full Control permissions to it, this path is used for the home directory. - If ...\
UserNameis not accessible, create ....\UserName.Domainwith full control permission. This path is used for the home directory.
For more information about the terms that are used to describe software updates, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
Additional query words: append
Keywords: kbhotfixserver kbenv kbbug kbfix kbqfe kbwinserv2003presp1fix KB821929
