Anti-Mhz
asked on
Qos Packet Scheduler - Disable or not Disable
I'm debating whether disable or not to disable Q0s packet scheduler on the Windows XP Machines in a small business network (windows 2003 sbs as DC). From what I read the only time Qos comes into play is when dealing with applications that are specifically Qos aware. We are running a pretty standard set of programs on each workstation and I'm wondering whether any of them could in fact utilize Qos feature.
This is what a typical setup looks like
MS Office 2007
IE 8
Mozilla Firefox 3.6
Pidgin (latest)
Adobe Acrobat Standard (6.0 and 8.0 flavors throughout the network)
Symantec Endpoint Protection
Follow-up question:
We also have 3 servers in the netowkr (2 2003 standard boxes and 1 2003 sbs dc)
Wold I benefit from disabling Qos packedt scheduler on those? Or is this a no no?
This is what a typical setup looks like
MS Office 2007
IE 8
Mozilla Firefox 3.6
Pidgin (latest)
Adobe Acrobat Standard (6.0 and 8.0 flavors throughout the network)
Symantec Endpoint Protection
Follow-up question:
We also have 3 servers in the netowkr (2 2003 standard boxes and 1 2003 sbs dc)
Wold I benefit from disabling Qos packedt scheduler on those? Or is this a no no?
Clarification about the use of QoS in end computers that are running Windows XP
As in Windows 2000, programs can take advantage of QoS through the QoS APIs in Windows XP. One hundred percent of the network bandwidth is available to be shared by all programs unless a program specifically requests priority bandwidth. This "reserved" bandwidth is still available to other programs unless the requesting program is sending data. By default, programs can reserve up to an aggregate bandwidth of 20 percent of the underlying link speed on each interface on an end computer. If the program that reserved the bandwidth is not sending sufficient data to use it, the unused part of the reserved bandwidth is available for other data flows on the same host.
For more information about the QoS Packet Scheduler, see Windows XP Help. Additional information about Windows 2000 QoS is available in the Windows 2000 technical library
As in Windows 2000, programs can take advantage of QoS through the QoS APIs in Windows XP. One hundred percent of the network bandwidth is available to be shared by all programs unless a program specifically requests priority bandwidth. This "reserved" bandwidth is still available to other programs unless the requesting program is sending data. By default, programs can reserve up to an aggregate bandwidth of 20 percent of the underlying link speed on each interface on an end computer. If the program that reserved the bandwidth is not sending sufficient data to use it, the unused part of the reserved bandwidth is available for other data flows on the same host.
For more information about the QoS Packet Scheduler, see Windows XP Help. Additional information about Windows 2000 QoS is available in the Windows 2000 technical library
Correction of some incorrect claims about Windows XP QoS support
There have been claims in various published technical articles and newsgroup postings that Windows XP always reserves 20 percent of the available bandwidth for QoS. These claims are incorrect. The information in the "Clarification about QoS in end computers that are Running Windows XP" section correctly describes the behavior of Windows XP systems
There have been claims in various published technical articles and newsgroup postings that Windows XP always reserves 20 percent of the available bandwidth for QoS. These claims are incorrect. The information in the "Clarification about QoS in end computers that are Running Windows XP" section correctly describes the behavior of Windows XP systems
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER