On a client computer that is running Windows Vista or Windows Server 2008, you apply some Quality of Services (QoS) Group Policy settings under the following subsection:
Local Computer Policy\Computer Configuration\Administrative Templates\Network\QoS Packet Scheduler
When you log on to the client computer, you see the Group Policy settings are applied correctly. However, after you restart the client computer, the Group Policy settings are no longer applied.
For example, you enable the Group Policy setting "Guaranteed service type." You specify a custom Layer-3 Differentiated Services Code Point (DSCP) value for packets with the "Guaranteed service type." After you restart the client computer, the custom Quality of Service (QoS) DSCP settings in the Group Policy are not retained. In this scenario, the default value for "Guaranteed service type" is used by the operating system after the computer is restarted.
This problem occurs whether you apply the Group Policy settings by using the local policy, or by using Group Policy objects in an Active Directory domain.
This problem also occurs on a client computer that is running Windows XP or Windows Server 2003.
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
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
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 on computers that are running Windows Vista, you must have Windows Vista SP1 or Windows Vista SP2 installed.
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
How to obtain the latest Windows Vista service pack
No prerequisites are required for computers that are running Windows Server 2008.
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 Vista and Windows Server 2008 file information notes
The MANIFEST files (.manifest) and MUM files (.mum) installed for each environment are
listed separately
. MUM and MANIFEST files, and the associated security catalog (.cat) files, are critical to maintaining the state of the updated component. The security catalog files (attributes not listed) are signed with a Microsoft digital signature.
For all supported x86-based versions of Windows Server 2008 and Windows Vista
Collapse this tableExpand this table
File name
File version
File size
Date
Time
Platform
Pacer.sys
6.0.6001.22475
74,240
18-Jul-2009
10:01
x86
Pacercnt.h
Not Applicable
3,010
01-Apr-2009
19:01
Not Applicable
Pacerprf.dll
6.0.6001.22475
15,360
18-Jul-2009
11:55
x86
Pacerprf.ini
Not Applicable
13,750
01-Apr-2009
19:01
Not Applicable
Traffic.dll
6.0.6001.22475
33,280
18-Jul-2009
11:56
x86
Wshqos.dll
6.0.6001.22475
13,824
18-Jul-2009
11:56
x86
Pacer.sys
6.0.6002.22180
74,240
18-Jul-2009
09:44
x86
Pacercnt.h
Not Applicable
3,010
03-Apr-2009
21:04
Not Applicable
Pacerprf.dll
6.0.6002.22180
15,360
18-Jul-2009
09:44
x86
Pacerprf.ini
Not Applicable
13,750
03-Apr-2009
21:04
Not Applicable
Traffic.dll
6.0.6002.22180
33,280
18-Jul-2009
11:47
x86
Wshqos.dll
6.0.6002.22180
13,824
18-Jul-2009
09:44
x86
For all supported x64-based versions of Windows Server 2008 and Windows Vista
Collapse this tableExpand this table
File name
File version
File size
Date
Time
Platform
Pacer.sys
6.0.6001.22475
95,744
18-Jul-2009
10:31
x64
Pacercnt.h
Not Applicable
3,010
01-Apr-2009
16:12
Not Applicable
Pacerprf.dll
6.0.6001.22475
17,920
18-Jul-2009
12:24
x64
Pacerprf.ini
Not Applicable
13,750
01-Apr-2009
16:12
Not Applicable
Traffic.dll
6.0.6001.22475
39,424
18-Jul-2009
12:25
x64
Wshqos.dll
6.0.6001.22475
16,896
18-Jul-2009
12:25
x64
Pacer.sys
6.0.6002.22180
95,744
18-Jul-2009
10:03
x64
Pacercnt.h
Not Applicable
3,010
03-Apr-2009
20:49
Not Applicable
Pacerprf.dll
6.0.6002.22180
17,920
18-Jul-2009
11:46
x64
Pacerprf.ini
Not Applicable
13,750
03-Apr-2009
20:49
Not Applicable
Traffic.dll
6.0.6002.22180
39,424
18-Jul-2009
11:46
x64
Wshqos.dll
6.0.6002.22180
16,896
18-Jul-2009
11:47
x64
Pacerprf.dll
6.0.6001.22475
15,360
18-Jul-2009
11:55
x86
Traffic.dll
6.0.6001.22475
33,280
18-Jul-2009
11:56
x86
Wshqos.dll
6.0.6001.22475
13,824
18-Jul-2009
11:56
x86
Pacerprf.dll
6.0.6002.22180
15,360
18-Jul-2009
09:44
x86
Traffic.dll
6.0.6002.22180
33,280
18-Jul-2009
11:47
x86
Wshqos.dll
6.0.6002.22180
13,824
18-Jul-2009
09:44
x86
For all supported IA-64-based versions of Windows Server 2008
The Group Policy setting mentioned in the Symptoms section is as follows:
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 ServiceType_Guaranteed-flagged and QoS-tagged traffic flows. Examine the packets and 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 Web site:
Back to the top
