6 Appendix A: Product Behavior

The information in this specification is applicable to the following Microsoft products or supplemental software. References to product versions include updates to those products.

  • Windows XP operating system

  • Windows Server 2003 operating system

Exceptions, if any, are noted in this section. If an update version, service pack or Knowledge Base (KB) number appears with a product name, the behavior changed in that update. The new behavior also applies to subsequent updates unless otherwise specified. If a product edition appears with the product version, behavior is different in that product edition.

Unless otherwise specified, any statement of optional behavior in this specification that is prescribed using the terms "SHOULD" or "SHOULD NOT" implies product behavior in accordance with the SHOULD or SHOULD NOT prescription. Unless otherwise specified, the term "MAY" implies that the product does not follow the prescription.

<1> Section 2.2.3: Windows has a variety of prohibited characters and names; for more information, see [MSDN-FILE].

<2> Section 2.2.4: On Windows XP and Windows Server 2003, these configuration elements may also be set via group policy on the machine running the CER client, which will cause those values to override the defaults described here.

<3> Section 2.2.4: On Windows XP and Windows Server 2003, these configuration elements may also be set via group policy on the machine running the CER client, which will cause those values to override the defaults described here.

<4> Section 2.2.4: On Windows XP and Windows Server 2003, these configuration elements may also be set via group policy on the machine running the CER client, which will cause those values to override the defaults described here.

<5> Section 2.2.4: On Windows XP and Windows Server 2003, these configuration elements can also be set via group policy on the machine running the CER client, which will cause those values to override the defaults described here.

<6> Section 2.2.5: It is possible to configure a CER tool in such a way that the URLLaunch value is left empty.

<7> Section 3.1.1: On Windows XP and Windows Server 2003, the following registry key specifies the UNC path of the CER file share:

 [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\PCHealth\
 ErrorReporting\DW] "DWFileTreeRoot"

<8> Section 3.1.7: On Windows XP and Windows Server 2003, these configuration elements can also be set via group policy on the machine running the CER client, which will cause those values to override the defaults described in section 2.2.4.

<9> Section 3.1.7: On Windows XP and Windows Server 2003, if a MemoryDump is requested and the CER client cannot generate one, the CER client will skip to step 8 of this section.

<10> Section 3.1.7: Windows uses a new file for each piece of information collected (for example, .reg for a registry key or .mdmp for a minidump).

<11> Section 3.1.7: Windows uses .CAB files for this compression; for more information, see [MSDN-CAB].