Microsoft KB Archive/908011

From BetaArchive Wiki

Article ID: 908011

Article Last Modified on 10/11/2007



APPLIES TO

  • Microsoft Windows Server 2003, Standard Edition (32-bit x86)
  • Microsoft Windows Server 2003, Enterprise Edition
  • Microsoft Windows Server 2003, Web Edition
  • Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)
  • Microsoft Windows Server 2003, Standard x64 Edition
  • Microsoft Windows Server 2003, Enterprise x64 Edition
  • Microsoft Windows Server 2003, Datacenter x64 Edition
  • Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems
  • Microsoft Windows Server 2003, Datacenter Edition for Itanium-Based Systems




SYMPTOMS

On a Microsoft Windows Server 2003-based computer, you cannot use a Group Policy setting to set the same mandatory profile for all Terminal Services users.

RESOLUTION

Service pack information

To resolve this problem, obtain the latest service pack for Windows Server 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

889100 How to obtain the latest service pack for Windows Server 2003


Hotfix information

Prerequisites

No prerequisites are required.

Restart requirement

You must restart the computer 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 tool in Control Panel.

Windows Server 2003, 32-bit versions
File name File version File size Date Time Platform SP requirement Service branch
System.adm Not Applicable 1,514,106 07-Oct-2005 22:24 Not Applicable None RTMQFE
Winlogon.exe 5.2.3790.421 497,664 08-Oct-2005 00:49 x86 None RTMQFE
Licdll.dll 5.2.3790.2544 449,536 08-Oct-2005 05:39 x86 SP1 SP1QFE
System.adm Not Applicable 1,765,488 07-Oct-2005 22:25 Not Applicable SP1 SP1QFE
Winlogon.exe 5.2.3790.2544 509,440 08-Oct-2005 01:40 x86 SP1 SP1QFE
Windows Server 2003, x64-based versions
File name File version File size Date Time Platform SP requirement Service branch
Licdll.dll 5.2.3790.2544 736,256 07-Oct-2005 18:16 x64 SP1 SP1QFE
System.adm Not Applicable 1,765,488 07-Oct-2005 18:16 Not Applicable SP1 SP1QFE
Winlogon.exe 5.2.3790.2544 923,136 07-Oct-2005 18:16 x64 SP1 SP1QFE
Windows Server 2003, Itanium-based versions
File name File version File size Date Time Platform SP requirement Service branch
System.adm Not Applicable 1,514,106 07-Oct-2005 18:15 Not Applicable None RTMQFE
Winlogon.exe 5.2.3790.421 641,024 07-Oct-2005 18:15 IA-64 None RTMQFE
System.adm Not Applicable 1,765,488 07-Oct-2005 18:15 Not Applicable SP1 SP1QFE
Winlogon.exe 5.2.3790.2544 681,472 07-Oct-2005 18:15 IA-64 SP1 SP1QFE


STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Windows Server 2003 Service Pack 2.

MORE INFORMATION

This hotfix implements a new Do not append the user name to the profile path policy setting. This policy setting has the following path:

Computer Configuration\Administrative Templates\Windows Components\Terminal Services\Set


This policy setting specifies whether Terminal Services uses a specified network path for roaming user profiles.

You can use this policy setting to specify a shared location where the profiles are stored. You can also let users use the same profile on all the terminal servers in an organizational unit. By default, Terminal Services stores all user profiles locally on the server that has Terminal Services enabled.

To use this policy setting, type the path of the shared location. When you specify the path, use the following form:

\\Computername\Sharename


Do not specify a placeholder for the user alias. Terminal Services automatically appends the user alias when the user logs on. If the shared location does not exist, Terminal Services displays an error message on the server and stores the user profiles locally.

If the status of this policy setting is set to Enabled, Terminal Services uses the specified path as the root directory for all the user profiles. The profiles themselves are located in subdirectories that are named as the alias of each user. If the status is set to Disabled or Not Configured, user profiles are stored locally on the server unless the server administrator specifies otherwise.

Note The roaming profiles that are specified with this policy setting apply only to Terminal Services connections. A user may also have a Windows roaming profile. In a Terminal Services session, the Terminal Services roaming profile always takes precedence.

If the Do not append the user name to the profile path check box is selected, Terminal Services does not automatically append the user name when the user logs on. We recommend that you set this option only if you want to specify a mandatory profile for all the Terminal Services users.

The Do not append the user name to the profile path policy setting is based on the following registry entry:

Registry subkey:

HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services



Registry entry name: WFDontAppendUserNameToProfile
Registry entry type: REG_DWORD
Values: 0 (disabled) or 1 (enabled)
Default value: 0

For more information about the terminology that is used in this article, 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


Keywords: kbbug kbfix kbqfe kbpubtypekc kbhotfixserver kbwinserv2003sp2fix KB908011