Export (0) Print
Expand All

7 Appendix B: Product Behavior

The information in this specification is applicable to the following Microsoft products or supplemental software. References to product versions include released service packs:

  • Windows NT 4.0 operating system

  • Windows 2000 operating system

  • Windows XP operating system

  • Windows Server 2003 operating system

  • Windows Vista operating system

  • Windows Server 2008 operating system

  • Windows 7 operating system

  • Windows Server 2008 R2 operating system

  • Windows 8 operating system

  • Windows Server 2012 operating system

  • Windows 8.1 operating system

  • Windows Server 2012 R2 operating system

Exceptions, if any, are noted below. If a service pack or Quick Fix Engineering (QFE) number appears with the product version, behavior changed in that service pack or QFE. The new behavior also applies to subsequent service packs of the product 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.1.1: Windows NT 4.0: The Remote Administrative Interface: WINS protocol does not define query-level access; the only access level available is control-level access. Clients that invoke RPC have control-level access.

<2> Section 2.2.2.7: In Windows 2000, Windows Server 2003, Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2, if the value of the WINSPriorityClass member is other than NORMAL_PRIORITY_CLASS or HIGH_PRIORITY_CLASS, the system assumes the latter.

<3> Section 3.1.4.1: Windows NT 4.0: The Remote Administrative Interface: WINS Protocol uses implicit binding, in which the RPC run-time library maintains the handle internally. No RPC methods except R_WinsTombStoneDbRecs, R_WinsTerm, and R_WinsGetBrowserNames take ServerHdl as a parameter.

<4> Section 3.1.4.1: Windows NT 4.0: The RPC method caller is required to have control-level access regardless of the action used.

<5> Section 3.1.4.1: In Windows 2000, Windows Server 2003, Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2, a maximum of 25 IP address mappings are allowed for a multihomed or special group Name Record.

<6> Section 3.1.4.2: Windows NT 4.0: The R_WinStatus caller is required to have control-level access regardless of the command used.

<7> Section 3.1.4.6: Windows NT 4.0: The RPC method caller is required to have control-level access regardless of the command used.

<8> Section 3.1.4.10: The execution of R_WinsPullRange by a client with sufficient access permissions can cause the WINS service on the target WINS server to restart.

<9> Section 3.1.4.14: Windows NT 4.0: The R_WinsGetNameAndAdd caller is required to have control-level access regardless of the command used.

<10> Section 3.1.4.14: Windows NT 4.0: The R_WinsGetNameAndAdd caller does not need access permissions to call this method.

<11> Section 3.1.4.19: Windows NT 4.0: The RPC method caller is required to have control-level access regardless of the command used.

<12> Section 3.2.4.2: Windows NT 4.0: This RPC method is not supported.

 
Show:
© 2014 Microsoft