Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

The "Guaranteed service type" Group Policy setting returns to the default value after you restart a client computer that is running Windows XP or Windows Server 2003


View products that this article applies to.

Symptoms

Consider the following scenario. You are in an Active Directory domain environment. You enable the Guaranteed service type Group Policy setting. You specify an alternative Layer-3 Differentiated Services Code Point (DSCP) value for packets that have the Guaranteed service type setting. When you log on to the domain from a client computer that is running Windows XP or Windows Server 2003, you see that the Group Policy setting is applied correctly. However, after you restart the client computer, the Quality of Service (QoS) DSCP settings in Group Policy are missing. In this scenario, the default value for the Guaranteed service type setting is used by the operating system after the restart.

This problem also occurs on a client computer that is running Windows Vista or Windows Server 2008. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
973779 The "Guaranteed service type" Group Policy setting returns to the default value after you restart a client computer that is running Windows Vista or Windows Server 2008

↑ Back to the top


Cause

This problem occurs because the Pacer.sys driver tries to read the following registry setting before the SOFTWARE hive is loaded:

HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\windows\Psched\DiffservByteMappingConforming

↑ Back to the top


Resolution

Hotfix information for Windows XP

A supported hotfix is 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.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if 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. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, you must have Windows XP Service Pack 3 installed on the computer. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
322389 How to obtain the latest Windows XP service pack

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 item in Control Panel.
Windows XP with Service Pack 3, x86-based versions
File nameFile versionFile sizeDateTimePlatform
Psched.sys5.1.2600.584870,27218-Jul-200911:23x86

Hotfix information for Windows Server 2003

A supported hotfix is 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 the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if 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. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, you must have Windows Server 2003 Service Pack 1 (SP1) or Windows Server 2003 Service Pack 2 (SP2) installed. 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

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 item in Control Panel.
Windows Server 2003 with Service Pack 1, x86-based versions
File nameFile versionFile sizeDateTimePlatform
Psched.sys5.2.3790.338063,48818-Jul-200910:32x86
Windows Server 2003 with Service Pack 2, x86-based versions
File nameFile versionFile sizeDateTimePlatform
Psched.sys5.2.3790.455563,48818-Jul-200911:55x86
Windows Server 2003 with Service Pack 1, Itanium-based versions
File nameFile versionFile sizeDateTimePlatform
Psched.sys5.2.3790.3380222,72018-Jul-200901:31IA-64
Windows Server 2003 with Service Pack 2, Itanium-based versions
File nameFile versionFile sizeDateTimePlatform
Psched.sys5.2.3790.4555222,72018-Jul-200906:41IA-64
Windows Server 2003 with Service Pack 1, x64-based versions
File nameFile versionFile sizeDateTimePlatform
Psched.sys5.2.3790.3380108,03218-Jul-200901:31x64
Windows Server 2003 with Service Pack 2, x64-based versions
File nameFile versionFile sizeDateTimePlatform
Psched.sys5.2.3790.4555108,03218-Jul-200906:41x64
Windows XP x64-based versions with Service Pack 1
File nameFile versionFile sizeDateTimePlatform
Psched.sys5.2.3790.3380108,03218-Jul-200901:31x64
Windows XP x64-based versions with Service Pack 2
File nameFile versionFile sizeDateTimePlatform
Psched.sys5.2.3790.4555108,03218-Jul-200906:41x64

↑ Back to the top


Workaround

To work around this problem, manually update the Guaranteed service type Group Policy setting. To do this, run the following command at the command prompt:

gpupdate /target:computer /force

↑ Back to the top


Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top


More information

You can find the Group Policy setting that is mentioned in the "Symptoms" section in the following location:

Computer Configuration\Administrative Templates\Network\QoS Packet Scheduler\DSCP value of conforming packets\Guaranteed service type

To identify this problem, take a network monitor trace of the ServiceType_Guaranteed-flagged and QoS-tagged traffic flows. Examine the packets, and then verify that the system is using the custom DSCP value as it is set in the Group Policy setting.

For more information about the Guaranteed service type, visit the following Microsoft Web site:For more information about the QoS tools and settings, visit the following Microsoft Web site:For more information about the QoS service types, visit the following Microsoft Web site:

↑ Back to the top


Keywords: kbautohotfix, kbexpertiseinter, kbfix, kbbug, kbsurveynew, kbqfe, KB972878

↑ Back to the top

Article Info
Article ID : 972878
Revision : 2
Created on : 10/7/2011
Published on : 10/7/2011
Exists online : False
Views : 270