Share via

7 Appendix B: Product Behavior

  • Article

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

The terms "earlier" and "later", when used with a product version, refer to either all preceding versions or all subsequent versions, respectively. The term "through" refers to the inclusive range of versions. Applicable Microsoft products are listed chronologically in this section.

  • Windows 2000 operating system

  • Windows 2000 Server 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

  • Windows 10 operating system

  • Windows Server 2016 operating system

  • Windows Server operating system

  • Windows Server 2019 operating system

  • Windows Server 2022 operating system

  • Windows 11 operating system

  • Windows Server 2025 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.1.1.1: The RPC_C_AUTHN_LEVEL_PKT_PRIVACY authentication level is not available in Windows 2000 Server.

<2> Section 2.1.2.1: The No Authentication service registration is specified in Windows 2000 Server.

<3> Section 2.1.2.1: Additional authentication services are not supported in Windows 2000 Server.

<4> Section 2.1.2.1: The RPC_C_AUTHN_LEVEL_PKT_PRIVACY authentication level is not available in Windows 2000 Server.

<5> Section 2.1.2.1: Windows 2000 Server supported clients connect with RPC_C_AUTHN_LEVEL_NONE.

<6> Section 2.1.2.2: The "Simple and Protected GSS-API Negotiation Mechanism" is not available in Windows 2000 Server.

<7> Section 2.1.2.2: The No Authentication service is specified in Windows 2000 Server.

<8> Section 2.1.2.2: The RPC_C_AUTHN_LEVEL_PKT_PRIVACY authentication level is not supported in Windows 2000 Server.

<9> Section 2.2.1.1.1: The ROUTER_IF_TYPE_TUNNEL1 value is only defined in Windows 2000 Server.

<10> Section 2.2.1.1.16: The RDT_PPPoE value is not defined in Windows 2000 Server.

<11> Section 2.2.1.1.16: The RDT_Tunnel_Sstp value is not defined in Windows 2000 Server and Windows Server 2003.

<12> Section 2.2.1.1.16: The RDT_Tunnel_Ikev2 value is not defined in Windows 2000 Server, Windows Server 2003, and Windows Server 2008.

<13> Section 2.2.1.1.16: The RDT_Broadband value is not defined in Windows 2000 Server.

<14> Section 2.2.1.1.22: The BGP_POLICY_DIRECTION enumeration is not available in Windows 2000 Server, Windows Server 2003, Windows Server 2008, and Windows Server 2008 R2.

<15> Section 2.2.1.1.23: The BGP_POLICY_TYPE enumeration is not available in Windows 2000 Server, Windows Server 2003, Windows Server 2008, and Windows Server 2008 R2.

<16> Section 2.2.1.1.24: The BGP_PEERING_OP_MODE enumeration is not available in Windows 2000 Server, Windows Server 2003, Windows Server 2008, and Windows Server 2008 R2.

<17> Section 2.2.1.2.4: IPv6-related information and features are not defined in Windows 2000 Server and Windows Server 2003.

<18> Section 2.2.1.2.4: The IP_PROT_PRIORITY_INFO_EX value is not available in Windows 2000 Server, Windows Server 2003, Windows Server 2008, Windows Server 2008 R2, and Windows Server 2012 operating system.

<19> Section 2.2.1.2.4: The IPINIP_CONFIG_INFO structure (section 2.2.1.2.17) is only defined in Windows 2000 Server.

<20> Section 2.2.1.2.4: The MPR_FILTER_0 structure (section 2.2.1.2.89) is not available on Windows 2000 Server and Windows Server 2003.

<21> Section 2.2.1.2.4: The MS_IP_OSPF value is only available on Windows 2000 Server and Windows Server 2003.

<22> Section 2.2.1.2.4: IPX-related information and features are only defined in Windows 2000 Server.

<23> Section 2.2.1.2.7: The InfoType values 0xFFFF0011, 0xFFFF0012, or 0xFFFF0013 for IPv6 are only defined in Windows Server 2008.

<24> Section 2.2.1.2.8: IPv6-related information and features are not defined in Windows 2000 Server and Windows Server 2003.

<25> Section 2.2.1.2.11: The INTERFACE_ROUTE_INFO structure is only defined in Windows Server 2008.

<26> Section 2.2.1.2.11: The MIB_IPFORWARDROW structure is only defined in Windows Server 2003 and Windows Server 2008.

<27> Section 2.2.1.2.11: The IP_ROUTE_INFO (0xFFFF0005) value is only defined in Windows Server 2008.

<28> Section 2.2.1.2.11: Windows implementations always return 0x00000000 for the dwRtInfoType field when the INTERFACE_ROUTE_INFO structure is queried using the RRouterInterfaceTransportGetInfo (section 3.1.4.19) method.

<29> Section 2.2.1.2.13: The PROTOCOL_METRIC structure is defined only in Windows 2000 Server, Windows Server 2003, Windows Server 2008, Windows Server 2008 R2, and Windows Server 2012.

<30> Section 2.2.1.2.13: Windows does not validate the dwProtocolId member of PROTOCOL_METRIC structure to be one of the values specified in the MIB_IPFORWARD_PROTO enumeration. A set operation (using RRouterInterfaceTransportSetGlobalInfo) with a value specified outside of MIB_IPFORWARD_PROTO will be accepted, and the same will be returned when a get operation (using RRouterInterfaceTransportGetGlobalInfo) is performed.

<31> Section 2.2.1.2.17: The IPINIP_CONFIG_INFO structure is only defined in Windows 2000 Server.

<32> Section 2.2.1.2.29: The dwLastChange member is not currently supported by the Network Driver Interface Specification (NDIS). On Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2, NDIS returns zero for this member. On other versions, an arbitrary value is returned in this member for the interfaces supported by NDIS. For interfaces supported by other interface providers, an appropriate value might be returned.

<33> Section 2.2.1.2.32: The wType field is not defined in Windows 2000 Server.

<34> Section 2.2.1.2.35: The ForwardType field is not defined in Windows 2000 Server and Windows Server 2003.

<35> Section 2.2.1.2.35: The ForwardProto field is not defined in Windows 2000 Server and Windows Server 2003.

<36> Section 2.2.1.2.49: The Forwarding field is not defined in Windows 2000 Server and Windows Server 2003.

<37> Section 2.2.1.2.55: The State field is not defined in Windows 2000 Server and Windows Server 2003.

<38> Section 2.2.1.2.56: The RtoAlgorithm field is not defined in Windows 2000 Server and Windows Server 2003.

<39> Section 2.2.1.2.62: The port limit is determined by the Windows Server license.

<40> Section 2.2.1.2.62: The port limit is determined by the Windows Server license.

<41> Section 2.2.1.2.63: The MPR_SERVER_2 structure is not defined in Windows 2000 Server and Windows Server 2003.

<42> Section 2.2.1.2.63: The port limit is determined by the Windows Server license.

<43> Section 2.2.1.2.63: The port limit is determined by the Windows Server license.

<44> Section 2.2.1.2.63: The dwNumSstpPorts field is not defined in Windows 2000 Server and Windows Server 2003. The port limit is determined by the Windows Server license.

<45> Section 2.2.1.2.63: The dwSstpPortFlags field is not defined in Windows 2000 Server and Windows Server 2003.

<46> Section 2.2.1.2.64: The PPP_NBFCP_INFO structure is only defined in Windows 2000 Server.

<47> Section 2.2.1.2.67: The PPP_IPXCP_INFO structure is only defined in Windows 2000 Server.

<48> Section 2.2.1.2.69: The PPP_ATCP_INFO structure is only defined in Windows 2000 Server.

<49> Section 2.2.1.2.71: The PPP_LCP_PAP, PPP_LCP_SPAP, and PPP_LCP_CHAP values are not defined in Windows 2000 Server.

<50> Section 2.2.1.2.71: The PPP_LCP_CHAP_MD5 and PPP_LCP_CHAP_MS values apply to Windows 2000 Server and Windows Server 2003 only.

<51> Section 2.2.1.2.71: The PPP_LCP_PAP, PPP_LCP_SPAP, and PPP_LCP_CHAP values are not defined in Windows 2000 Server.

<52> Section 2.2.1.2.71: The PPP_LCP_AES_128 and PPP_LCP_AES_256 values are not defined in Windows 2000 Server and Windows Server 2003. The PPP_LCP_AES_192, PPP_LCP_GCM_AES_128, PPP_LCP_GCM_AES_192, and PPP_LCP_GCM_AES_256 values are not available in Windows 2000 Server, Windows Server 2003, Windows Server 2008, Windows Server 2008 R2.

<53> Section 2.2.1.2.72: The PPP_IPXCP_INFO structure is only defined in Windows 2000 Server.

<54> Section 2.2.1.2.72: The PPP_ATCP_INFO structure is only defined in Windows 2000 Server.

<55> Section 2.2.1.2.73: The PPP_INFO_2 structure is not defined in Windows 2000 Server.

<56> Section 2.2.1.2.73: The PPP_IPXCP_INFO structure is only defined in Windows 2000 Server.

<57> Section 2.2.1.2.73: The PPP_ATCP_INFO structure is only defined in Windows 2000 Server.

<58> Section 2.2.1.2.74: The PPP_INFO_3 structure is not defined in Windows 2000 Server and Windows Server 2003.

<59> Section 2.2.1.2.77: The RAS_FLAGS_ARAP_CONNECTION value is only defined in Windows 2000 Server.

<60> Section 2.2.1.2.80: The PPP_INFO_3 structure is not defined in Windows 2000 Server and Windows Server 2003.

<61> Section 2.2.1.2.82: The MPRI_INTERFACE_1 structure is not defined in Windows 2000 Server.

<62> Section 2.2.1.2.83: The MPRI_INTERFACE_2 structure is not defined in Windows 2000 Server.

<63> Section 2.2.1.2.83: Windows also require that the interface be registered in the registry as specified in 2.2.3.2.1; otherwise, the interface will not be available for managing after the Remote Access Service is restarted.

<64> Section 2.2.1.2.83: In applicable Windows Server releases, specifying a new value for wszInterfaceInfo with MPRI_INTERFACE_2 in calls to RRouterInterfaceSetInfo results in a new phonebook entry being created; that new entry will not be available for management.

<65> Section 2.2.1.2.83: The MPRIO_RequireSPAP and MPRIO_RequireMsCHAP values are available in Windows 2000 Server and Windows Server 2003. The MPRIO_RequireMachineCertificates, MPRIO_UsePreSharedKeyForIkev2Initiator, and MPRIO_UsePreSharedKeyForIkev2Responder values are not available in Windows 2000 Server, Windows Server 2003, Windows Server 2008, and Windows Server 2008 R2.

<66> Section 2.2.1.2.83: The MPRNP_Ipx value is only defined in Windows 2000 Server. The MPRNP_Ipv6 value is not defined in Windows 2000 Server and Windows Server 2003.

<67> Section 2.2.1.2.83: The X.25 PAD feature is only supported in Windows 2000 Server, Windows Server 2003, and Windows Server 2003 R2 operating system. In Windows NT operating system and Windows 2000 the szX25PadType string maps to a section name in PAD.INF.

<68> Section 2.2.1.2.83: The X.25 PAD feature is only supported in Windows 2000 Server, Windows Server 2003, and Windows Server 2003 R2.

<69> Section 2.2.1.2.83: The MPRDM_DialAsNeeded feature is only supported in Windows 2000 Server, Windows Server 2003, and Windows Server 2003 R2. On Windows Server 2008 and Windows Server 2008 R2, this value is ignored and treated identically to MPRDM_DialAll.

<70> Section 2.2.1.2.83: The MPRET_Direct value is supported only in Windows 2000 Server.

<71> Section 2.2.1.2.83: Support for dialing IKEv2 is not available in Windows 2000 Server, Windows Server 2003, Windows Server 2008, and Windows Server 2008 R2.

<72> Section 2.2.1.2.84: The MPRI_INTERFACE_3 structure is not defined in Windows 2000 Server and Windows Server 2003.

<73> Section 2.2.1.2.84: Windows also require that the interface be registered in the registry as specified in 2.2.3.2.1; otherwise, the interface will not be available for managing after the Remote Access Service is restarted.

<74> Section 2.2.1.2.84: In applicable Windows Server releases, specifying a new value for wszInterfaceInfo with MPRI_INTERFACE_3 in calls to RRouterInterfaceSetInfo results in a new phonebook entry being created; that new entry will not be available for management.

<75> Section 2.2.1.2.84: The following values: MPRIO_RequirePAP, MPRIO_RequireSPAP, MPRIO_RequireCHAP, and MPRIO_RequireMsCHAP are not defined in Windows 2000 Server. The values MPRIO_RequireMachineCertificates, MPRIO_UsePreSharedKeyForIkev2Initiator, and MPRIO_UsePreSharedKeyForIkev2Responder are not available in Windows 2000 Server, Windows Server 2003, Windows Server 2008, and Windows Server 2008 R2.

<76> Section 2.2.1.2.84: The X.25 PAD feature is only supported in Windows 2000 Server, Windows Server 2003, and Windows Server 2003 R2. In Windows NT and Windows 2000 the szX25PadType string maps to a section name in PAD.INF.

<77> Section 2.2.1.2.84: The X.25 PAD feature is only supported in Windows 2000 Server, Windows Server 2003, and Windows Server 2003 R2.

<78> Section 2.2.1.2.84: The MPRDM_DialAsNeeded feature is only supported in Windows 2000 Server, Windows Server 2003, and Windows Server 2003 R2. On Windows Server 2008 and Windows Server 2008 R2, this value is ignored and treated identically to MPRDM_DialAll.

<79> Section 2.2.1.2.84: In the dwVpnStrategy field support for dialing IKEv2 is not available in Windows 2000 Server, Windows Server 2003, Windows Server 2008, and Windows Server 2008 R2.

<80> Section 2.2.1.2.89: The MPR_FILTER_0 structure is not available on Windows 2000 Server and Windows Server 2003.

<81> Section 2.2.1.2.90: The IPX_GLOBAL_INFO structure is only defined in Windows 2000 Server.

<82> Section 2.2.1.2.91: The IPX_IF_INFO structure is only defined in Windows 2000 Server.

<83> Section 2.2.1.2.92: The IPXWAN_IF_INFO structure is only defined in Windows 2000 Server.

<84> Section 2.2.1.2.93: The IPX_STATIC_ROUTE_INFO structure is only defined in Windows 2000 Server.

<85> Section 2.2.1.2.94: The IPX_STATIC_SERVICE_INFO structure is only defined in Windows 2000 Server.

<86> Section 2.2.1.2.95: The IPX_STATIC_NETBIOS_NAME_INFO structure is only defined in Windows 2000 Server.

<87> Section 2.2.1.2.96: The IPX_ADAPTER_INFO structure is only defined in Windows 2000 Server.

<88> Section 2.2.1.2.97: The IPX_TRAFFIC_FILTER_GLOBAL_INFO structure is only defined in Windows 2000 Server.

<89> Section 2.2.1.2.98: The IPX_TRAFFIC_FILTER_INFO structure is only defined in Windows 2000 Server.

<90> Section 2.2.1.2.99: The IF_TABLE_INDEX structure is only defined in Windows 2000 Server.

<91> Section 2.2.1.2.100: The ROUTING_TABLE_INDEX structure is only defined in Windows 2000 Server.

<92> Section 2.2.1.2.101: The SERVICES_TABLE_INDEX structure is only defined in Windows 2000 Server.

<93> Section 2.2.1.2.102: The SERVICES_TABLE_INDEX structure is only defined in Windows 2000 Server.

<94> Section 2.2.1.2.103: The STATIC_SERVICES_TABLE_INDEX structure is only defined in Windows 2000 Server.

<95> Section 2.2.1.2.104: The IPX_MIB_INDEX union is only defined in Windows 2000 Server.

<96> Section 2.2.1.2.105: The IPX_MIB_GET_INPUT_DATA structure is only defined in Windows 2000 Server.

<97> Section 2.2.1.2.106: The IPXMIB_BASE structure is only defined in Windows 2000 Server.

<98> Section 2.2.1.2.107: The IPX_IF_STATS structure is only defined in Windows 2000 Server.

<99> Section 2.2.1.2.108: The IPX_INTERFACE structure is only defined in Windows 2000 Server.

<100> Section 2.2.1.2.108: The NdisMediumWirelessWan media type is available only in Windows 2000, Windows XP, and Windows Server 2003.

<101> Section 2.2.1.2.109: The IPX_ROUTE structure is only defined in Windows 2000 Server.

<102> Section 2.2.1.2.110: The IPX_MIB_ROW union is only defined in Windows 2000 Server.

<103> Section 2.2.1.2.111: The IPX_MIB_SET_INPUT_DATA structure is only defined in Windows 2000 Server.

<104> Section 2.2.1.2.112: The SAP_SERVICE_FILTER_INFO structure is only defined in Windows 2000 Server.

<105> Section 2.2.1.2.113: The SAP_IF_FILTERS structure is only defined in Windows 2000 Server.

<106> Section 2.2.1.2.114: The SAP_IF_CONFIG structure is only defined in Windows 2000 Server.

<107> Section 2.2.1.2.115: The SAP_MIB_BASE structure is only defined in Windows 2000 Server.

<108> Section 2.2.1.2.116: The SAP_IF_STATS structure is only defined in Windows 2000 Server.

<109> Section 2.2.1.2.117: The SAP_INTERFACE structure is only defined in Windows 2000 Server.

<110> Section 2.2.1.2.118: The SAP_MIB_GET_INPUT_DATA structure is only defined in Windows 2000 Server.

<111> Section 2.2.1.2.119: The SAP_MIB_SET_INPUT_DATA structure is only defined in Windows 2000 Server.

<112> Section 2.2.1.2.120: The IPX_SERVICE structure is only defined in Windows 2000 Server.

<113> Section 2.2.1.2.121: The SAP_IF_INFO structure is only defined in Windows 2000 Server.

<114> Section 2.2.1.2.125: The RIP_MIB_GET_INPUT_DATA structure is only defined in Windows 2000 Server.

<115> Section 2.2.1.2.126: The RIP_MIB_SET_INPUT_DATA structure is only defined in Windows 2000 Server.

<116> Section 2.2.1.2.129: The MPRAPI_OBJECT_HEADER_IDL structure is not available in Windows 2000 Server, Windows Server 2003, and Windows Server 2008.

<117> Section 2.2.1.2.130: The PPP_PROJECTION_INFO_1 structure is not available in Windows 2000 Server, Windows Server 2003, and Windows Server 2008.

<118> Section 2.2.1.2.131: The IKEV2_PROJECTION_INFO_1 structure is not available in Windows 2000 Server, Windows Server 2003, and Windows Server 2008.

<119> Section 2.2.1.2.133: The RAS_FLAGS_ARAP_CONNECTION flag is defined only in Windows 2000 Server. The RAS_FLAGS_DORMANT flag is not available in Windows 2000 Server, Windows Server 2003, and Windows Server 2008.

<120> Section 2.2.1.2.136: The IKEV2_TUNNEL_CONFIG_PARAMS_1 structure is not available in Windows 2000 Server, Windows Server 2003, and Windows Server 2008.

<121> Section 2.2.1.2.137: The IKEV2_CONFIG_PARAMS_1 structure is not available in Windows 2000 Server, Windows Server 2003, and Windows Server 2008.

<122> Section 2.2.1.2.137: The port limit is determined by the Windows Server license.

<123> Section 2.2.1.2.138: The PPTP_CONFIG_PARAMS_1 structure is not available in Windows 2000 Server, Windows Server 2003, and Windows Server 2008.

<124> Section 2.2.1.2.138: The port limit is determined by the Windows Server license.

<125> Section 2.2.1.2.139: The L2TP_CONFIG_PARAMS_1 structure is not available in Windows 2000 Server, Windows Server 2003, and Windows Server 2008.

<126> Section 2.2.1.2.139: The port limit is determined by the Windows Server license.

<127> Section 2.2.1.2.140: The SSTP_CERT_INFO_1 structure is not available in Windows 2000 Server, Windows Server 2003, and Windows Server 2008.

<128> Section 2.2.1.2.141: The SSTP_CONFIG_PARAMS_1 structure is not available in Windows 2000 Server, Windows Server 2003, and Windows Server 2008.

<129> Section 2.2.1.2.141: The port limit is determined by the Windows Server license.

<130> Section 2.2.1.2.142: The MPR_SERVER_EX_1 structure is not available in Windows 2000 Server, Windows Server 2003, and Windows Server 2008.

<131> Section 2.2.1.2.143: The MPR_SERVER_EX_IDL union is not available in Windows 2000 Server, Windows Server 2003, and Windows Server 2008.

<132> Section 2.2.1.2.143: The MPR_SERVER_EX_3 structure is not available in Windows 2000 Server, Windows Server 2003, Windows Server 2008, Windows Server 2008 R2, and Windows Server 2012.

<133> Section 2.2.1.2.144: The MPRAPI_TUNNEL_CONFIG_PARAMS_1 structure is not available in Windows 2000 Server, Windows Server 2003, and Windows Server 2008.

<134> Section 2.2.1.2.145: The MPR_SERVER_SET_CONFIG_EX_1 structure is not available in Windows 2000 Server, Windows Server 2003, and Windows Server 2008.

<135> Section 2.2.1.2.147: The RAS_UPDATE_CONNECTION_1_IDL structure is not available in Windows 2000 Server, Windows Server 2003, and Windows Server 2008.

<136> Section 2.2.1.2.148: The RAS_UPDATE_CONNECTION_IDL union is not available in Windows 2000 Server, Windows Server 2003, and Windows Server 2008.

<137> Section 2.2.1.2.190: The MIB_DA_MSG structure is available in Windows 2000 Server and Windows Server 2003 only.

<138> Section 2.2.1.2.201: The IP_ALG_GLOBAL_INFO structure is not available in Windows 2000 Server.

<139> Section 2.2.1.2.202: The RIP_GLOBAL_INFO structure is not defined in Windows 2000 Server.

<140> Section 2.2.1.2.204: The RIP_IF_FILTERS structure is not defined in Windows 2000 Server.

<141> Section 2.2.1.2.205: The RIP_IF_INFO structure is only defined in Windows 2000 Server.

<142> Section 2.2.1.2.206: The RIP_IF_CONFIG structure is not defined in Windows 2000 Server.

<143> Section 2.2.1.2.207: The SAP_GLOBAL_INFO structure is not defined in Windows 2000 Server.

<144> Section 2.2.1.2.208: The OSPF_ROUTE_FILTER structure is only available in Windows 2000 Server and Windows Server 2003.

<145> Section 2.2.1.2.209: The OSPF_ROUTE_FILTER_INFO structure is only available in Windows 2000 Server and Windows Server 2003.

<146> Section 2.2.1.2.210: The OSPF_PROTO_FILTER_INFO structure is only available in Windows 2000 Server and Windows Server 2003.

<147> Section 2.2.1.2.211: The OSPF_GLOBAL_PARAM structure is only applicable in Windows 2000 Server and Windows Server 2003.

<148> Section 2.2.1.2.212: The OSPF_AREA_PARAM structure is only applicable in Windows 2000 Server and Windows Server 2003.

<149> Section 2.2.1.2.213: The OSPF_AREA_RANGE_PARAM structure is only applicable in Windows 2000 Server and Windows Server 2003.

<150> Section 2.2.1.2.214: The OSPF_VIRT_INTERFACE_PARAM structure is only applicable in Windows 2000 Server and Windows Server 2003.

<151> Section 2.2.1.2.215: The OSPF_INTERFACE_PARAM structure is only applicable in Windows 2000 Server and Windows Server 2003.

<152> Section 2.2.1.2.216: The OSPF_NBMA_NEIGHBOR_PARAM structure is only applicable in Windows 2000 Server and Windows Server 2003.

<153> Section 2.2.1.2.217: The RB_Dummy field is not defined in Windows 2000 Server.

<154> Section 2.2.1.2.218: For the dwVersion field, the server version is 5 for Windows 2000 Server. Otherwise the version is 6 in applicable Windows Server releases.

<155> Section 2.2.1.2.219: For the dwVersion field, the server version is 5 for Windows 2000 Server. Otherwise the version is 6 in applicable Windows Server releases.

<156> Section 2.2.1.2.219: The fRouterOutboundEnabled field is not defined in Windows 2000 Server.

<157> Section 2.2.1.2.219: The wszDeviceName field is not defined in Windows 2000 Server.

<158> Section 2.2.1.2.228: The RI_dwSessionId field is not defined in Windows 2000 Server.

<159> Section 2.2.1.2.228: The RI_dwFlags field is not defined in Windows 2000 Server.

<160> Section 2.2.1.2.228: The RI_CorrelationGuid field is not defined in Windows 2000 Server and Windows Server 2003.

<161> Section 2.2.1.2.230: The values PBDT_Pad and PBDT_X25 are only defined in Windows 2000 Server and Windows Server 2003. The value PBDT_PPPoE is not defined in Windows 2000 Server.

<162> Section 2.2.1.2.233: The PPP_PROJECTION_INFO_2 structure is not available in Windows 2000 Server, Windows Server 2003, Windows Server 2008, and Windows Server 2008 R2.

<163> Section 2.2.1.2.234: The IKEV2_PROJECTION_INFO_2 structure is not available in Windows 2000 Server, Windows Server 2003, Windows Server 2008, and Windows Server 2008 R2.

<164> Section 2.2.1.2.235: The PROJECTION_INFO_IDL_2 structure is not available in Windows 2000 Server, Windows Server 2003, Windows Server 2008, and Windows Server 2008 R2.

<165> Section 2.2.1.2.236: The RAS_CONNECTION_4_IDL structure is not available in Windows 2000 Server, Windows Server 2003, Windows Server 2008, and Windows Server 2008 R2.

<166> Section 2.2.1.2.237: The ROUTER_CUSTOM_IKEv2_POLICY_0 structure is not available in Windows 2000 Server, Windows Server 2003, Windows Server 2008, and Windows Server 2008 R2.

<167> Section 2.2.1.2.238: The IKEV2_TUNNEL_CONFIG_PARAMS_2 structure is not available in Windows 2000 Server, Windows Server 2003, Windows Server 2008, and Windows Server 2008 R2.

<168> Section 2.2.1.2.239: The IKEV2_CONFIG_PARAMS_2 structure is not available in Windows 2000 Server, Windows Server 2003, Windows Server 2008, and Windows Server 2008 R2.

<169> Section 2.2.1.2.240: The MPRAPI_TUNNEL_CONFIG_PARAMS_2 structure is not available in Windows 2000 Server, Windows Server 2003, Windows Server 2008, and Windows Server 2008 R2.

<170> Section 2.2.1.2.241: The MPR_SERVER_SET_CONFIG_EX_2 structure is not available in Windows 2000 Server, Windows Server 2003, Windows Server 2008, and Windows Server 2008 R2.

<171> Section 2.2.1.2.242: The MPR_SERVER_EX_2 structure is not available in Windows 2000 Server, Windows Server 2003, Windows Server 2008, and Windows Server 2008 R2.

<172> Section 2.2.1.2.243: The ROUTER_IKEv2_IF_CUSTOM_CONFIG_0 structure is not available in Windows 2000 Server, Windows Server 2003, Windows Server 2008, andWindows Server 2008 R2.

<173> Section 2.2.1.2.244: The MPR_IF_CUSTOMINFOEX_0 structure is not available in Windows 2000 Server, Windows Server 2003, Windows Server 2008, and Windows Server 2008 R2.

<174> Section 2.2.1.2.245: The MPR_IF_CUSTOMINFOEX_IDL structure is not available in Windows 2000 Server, Windows Server 2003, Windows Server 2008, and Windows Server 2008 R2.

<175> Section 2.2.1.2.246: The CERT_EKU_1 structure is not available in Windows 2000 Server, Windows Server 2003, Windows Server 2008, Windows Server 2008 R2, and Windows Server 2012.

<176> Section 2.2.1.2.247: The IKEV2_TUNNEL_CONFIG_PARAMS_3 structure is not available in Windows 2000 Server, Windows Server 2003, Windows Server 2008, Windows Server 2008 R2, and Windows Server 2012.

<177> Section 2.2.1.2.248: The IKEV2_CONFIG_PARAMS_3 structure is not available in Windows 2000 Server, Windows Server 2003, Windows Server 2008, Windows Server 2008 R2, and Windows Server 2012.

<178> Section 2.2.1.2.249: The MPRAPI_TUNNEL_CONFIG_PARAMS_3 structure is not available in Windows 2000 Server, Windows Server 2003, Windows Server 2008, Windows Server 2008 R2, and Windows Server 2012.

<179> Section 2.2.1.2.250: The MPR_SERVER_SET_CONFIG_EX_3 structure is available in Windows 2000 Server, Windows Server 2003, Windows Server 2008, Windows Server 2008 R2, and Windows Server 2012.

<180> Section 2.2.1.2.251: The MPR_SERVER_EX_3 structure is not available in Windows 2000 Server, Windows Server 2003, Windows Server 2008, Windows Server 2008 R2, and Windows Server 2012.

<181> Section 2.2.1.2.252: The BGP_CONFIG_HEADER structure is not available in Windows 2000 Server, Windows Server 2003, Windows Server 2008, Windows Server 2008 R2, and Windows Server 2012.

<182> Section 2.2.1.2.253: The BGP_TOC_ENTRY structure is not available in Windows 2000 Server, Windows Server 2003, Windows Server 2008, Windows Server 2008 R2, and Windows Server 2012.

<183> Section 2.2.1.2.254: The BGP_IP_ADDRESS structure is not available in Windows 2000 Server, Windows Server 2003, Windows Server 2008, Windows Server 2008 R2, and Windows Server 2012.

<184> Section 2.2.1.2.255: The BGP_IP_PREFIX structure is not available in Windows 2000 Server, Windows Server 2003, Windows Server 2008, Windows Server 2008 R2, and Windows Server 2012.

<185> Section 2.2.1.2.256: The BGP_ASN_RANGE structure is not available in Windows 2000 Server, Windows Server 2003, Windows Server 2008, Windows Server 2008 R2, and Windows Server 2012.

<186> Section 2.2.1.2.257: The BGP_ROUTER_CONFIG structure is not available in Windows 2000 Server, Windows Server 2003, Windows Server 2008, Windows Server 2008 R2, and Windows Server 2012.

<187> Section 2.2.1.2.258: The BGP_POLICY_MATCH structure is not available in Windows 2000 Server, Windows Server 2003, Windows Server 2008, Windows Server 2008 R2, and Windows Server 2012.

<188> Section 2.2.1.2.259: The BGP_POLICY_MODIFY structure is not available in Windows 2000 Server, Windows Server 2003, Windows Server 2008, Windows Server 2008 R2, and Windows Server 2012.

<189> Section 2.2.1.2.260: The BGP_POLICY_ACTION structure is not available in Windows 2000 Server, Windows Server 2003, Windows Server 2008, Windows Server 2008 R2, and Windows Server 2012.

<190> Section 2.2.1.2.261: The BGP_POLICY structure is not available in Windows 2000 Server, Windows Server 2003, Windows Server 2008, Windows Server 2008 R2, and Windows Server 2012.

<191> Section 2.2.1.2.262: The BGP_PEER structure is not available in Windows 2000 Server, Windows Server 2003, Windows Server 2008, Windows Server 2008 R2, and Windows Server 2012.

<192> Section 2.2.1.2.263: The BGP_PEER_TO_POLICIES structure is not available in Windows 2000 Server, Windows Server 2003, Windows Server 2008, Windows Server 2008 R2, and Windows Server 2012.

<193> Section 2.2.1.2.264: The BGP_ADVERTISE structure is not available in Windows 2000 Server, Windows Server 2003, Windows Server 2008, Windows Server 2008 R2, Windows Server 2012.

<194> Section 2.2.1.2.265: The BGP_ROUTER_V6 structure is not available in Windows 2000 Server, Windows Server 2003, Windows Server 2008, Windows Server 2008 R2, and Windows Server 2012.

<195> Section 2.2.1.2.266: The PRIORITY_INFO_EX structure is not available in Windows 2000 Server, Windows Server 2003, Windows Server 2008, Windows Server 2008 R2, and Windows Server 2012.

<196> Section 2.2.1.2.267: The PROTOCOL_METRIC_EX structure is not available in Windows 2000 Server, Windows Server 2003, Windows Server 2008, Windows Server 2008 R2, and Windows Server 2012.

<197> Section 2.2.1.2.268: The ROUTER_IKEv2_IF_CUSTOM_CONFIG_1 structure is not available in Windows 2000 Server, Windows Server 2003, Windows Server 2008, Windows Server 2008 R2, and Windows Server 2012.

<198> Section 2.2.1.2.269: The MPR_IF_CUSTOMINFOEX_1 structure is not available in Windows 2000 Server, Windows Server 2003, Windows Server 2008, Windows Server 2008 R2, and Windows Server 2012.

<199> Section 2.2.1.2.270: The L2TP_TUNNEL_CONFIG_PARAMS_1 structure is not available in Windows 2000 Server, Windows Server 2003, Windows Server 2008, Windows Server 2008 R2, and Windows Server 2012.

<200> Section 2.2.1.2.271: The L2TP_CONFIG_PARAMS_2 structure is not available in Windows 2000 Server, Windows Server 2003, Windows Server 2008, Windows Server 2008 R2, and Windows Server 2012.

<201> Section 2.2.2: The client-side Remote Access Service (RAS) is not in this server-side RRASM protocol. The client RAS creates a different default phonebook file called rasphone.pbk. If the caller does not specify a phonebook file, the default phonebook file is used. For more information, see legacy information in [MSDOCS-RASpbk].

<202> Section 2.2.2: The phonebook file used by Windows servers is router.pbk present under the directory System32 under the Windows folder. For example, C:\Windows\System32\ras\router.pbk is the file used on RRAS server where Windows folder is C:\Windows.

<203> Section 2.2.2.1: On Windows 2000 Server and Windows Server 2003, the number of characters in a RRAS entry section name cannot exceed 256 bytes. Otherwise on applicable Windows Server releases the numbers of characters in a RRAS entry section name cannot exceed 1536 bytes.

<204> Section 2.2.2.2.3: The Type key is not optional on Windows 2000 Server, Windows Server 2003, and Windows Server 2008. Otherwise on applicable Windows Server releases the Type key is optional.

<205> Section 2.2.2.2.3:  Broadband connection value 5 is not available on Windows 2000 Server.

<206> Section 2.2.2.2.11: The RAS client-side RASENTRY structure, dwVpnStrategy field uses a different set of VpnStrategy values. The following client values are not supported by the RRASM server protocol. For more information, see legacy information in [MSDOCS-RASENTRY].

Value

Name

Meaning

5

VS_SstpOnly

Windows Vista operating system with Service Pack 1 (SP1) and later: RAS attempts only SSTP.

6

VS_SstpFirst

Windows Vista SP1 and later: RAS attempts SSTP first followed by IKEv2, PPTP, and then L2TP.

12

VS_PptpSstp

Windows 7 and later: RAS attempts PPTP followed only by SSTP.

13

VS_L2tpSstp

Windows 7 and later: RAS attempts L2TP followed only by SSTP.

14

VS_Ikev2Sstp

Windows 7 and later: RAS attempts IKEv2 followed only by SSTP.

15

VS_ProtocolList

Windows 10 and later: Use a Protocol List to determine the protocols to connect to.

<207> Section 2.2.2.2.11: In Windows 2000 Server, Windows Server 2003, and Windows Server 2008, RRAS attempts L2TP first. If L2TP fails, PPTP is tried. If PPTP fails, demand-dial connection fails.

In Windows Server 2008 R2, RRAS attempts PPTP first. If PPTP fails, L2TP is tried. If L2TP fails, demand-dial connection fails.

Otherwise on applicable Windows Server releases RRAS attempts PPTP first. If PPTP fails, L2TP is tried. If L2TP fails, IKEv2 is tried. If IKEv2 fails, demand-dial connection fails.

<208> Section 2.2.2.2.11: The IKEv2 is not available in Windows 2000 Server, Windows Server 2003, Windows Server 2008, and Windows Server 2008 R2.

<209> Section 2.2.2.2.12: The NetBEUI network protocol is available only on Windows 2000 Server.

<210> Section 2.2.2.2.12: The IPX network protocol is available only on Windows 2000 Server.

<211> Section 2.2.2.2.12: The IPv6 network protocol is not available on Windows 2000 Server and Windows Server 2003.

<212> Section 2.2.2.2.20: On Windows 2000 and Windows Server 2003, RRAS adjusts the number of subentries configured for the connection as bandwidth is needed. RRAS uses DialPercent, DialSeconds, HangupPercent, and HangupSeconds to determine when to dial or disconnect a subentry. Otherwise on applicable Windows Server releases RRAS ignores this key and assumes the value to be 1.

<213> Section 2.2.2.2.21: The DialPercent key is only used on Windows 2000 Server and Windows Server 2003. Otherwise the key is ignored on applicable Windows Server releases.

<214> Section 2.2.2.2.22: The DialSeconds key is only used on Windows 2000 Server and Windows Server 2003. Otherwise the key is ignored on applicable Windows Server releases.

<215> Section 2.2.2.2.23: The HangupPercent key is only used on Windows 2000 Server and Windows Server 2003. Otherwise the key is ignored on applicable Windows Server releases.

<216> Section 2.2.2.2.24: The HangupSeconds key is only used on Windows 2000 Server and Windows Server 2003. Otherwise the key is ignored on applicable Windows Server releases.

<217> Section 2.2.2.2.35: The DisableIKENameEkuCheck key is ignored on Windows 2000 Server and Windows Server 2003.

<218> Section 2.2.2.2.38: In Windows 2000 Server and Windows Server 2003 the option to enable NetBT on the RRAS entry is based on the values for the keys ShareMsFilePrint and BindMsNetClient. When both key values are set to zero (0) that indicates disable NetBT. Otherwise a value of one (1) for either or both keys indicates enable NetBT.

On Windows Server 2008 and Windows Server 2008 R2, RRAS relies on the keys ShareMsFilePrint, BindMsNetClient, and IpNBTFlags to configure NetBT on the RRAS entry.

<219> Section 2.2.2.2.46: The PreferredHwFlow key is ignored on Windows 2000 Server.

<220> Section 2.2.2.2.47: The PreferredProtocol key is ignored on Windows 2000 Server.

<221> Section 2.2.2.2.48: The PreferredCompression key is ignored in Windows 2000 Server.

<222> Section 2.2.2.2.49: The PreferredSpeaker key is ignored in Windows 2000 Server.

<223> Section 2.2.2.2.58: The SPAP (bit 5) and MSCHAPv1 (bit 7) are present only on Windows 2000 Server and Windows Server 2003.

<224> Section 2.2.2.2.58: The Windows 95 operating system compatible MSCHAP (bit 11) is present only on Windows 2000 Server and Windows Server 2003.

<225> Section 2.2.2.2.58: The machine certificate authentication method for IKEv2 is not available in Windows 2000 Server, Windows Server 2003, Windows Server 2008, and Windows Server 2008 R2.

<226> Section 2.2.2.2.58: The preshared key authentication method for IKEv2 is not available in Windows 2000 Server, Windows Server 2003, Windows Server 2008, and Windows Server 2008 R2.

<227> Section 2.2.2.2.73: The IpNBTFlags key is not available on Windows 2000 Server and Windows Server 2003. The meaning for the combination of values for keys IpNBTFlags, BindMsNetClient, and ShareMsFilePrint is given in the following table.

Value

Meaning

0

Disable NetBT.

1

Disable NetBT if the value for the keys ShareMsFilePrint and BindMsNetClient is set to "0".

1

Enable NetBT if the value for either of the keys ShareMsFilePrint and BindMsNetClient is "1".

<228> Section 2.2.2.2.74: The TcpWindowSize key is ignored on applicable Windows Server releases except on Windows 2000 Server and Windows Server 2003.

<229> Section 2.2.2.2.79: The Ipv6Assign key is ignored on Windows 2000 Server, Windows Server 2003, and Windows Server 2008.

<230> Section 2.2.2.2.80: The Ipv6PrefixLength key is ignored on Windows 2000 Server, Windows Server 2003, and Windows Server 2008.

<231> Section 2.2.2.2.84: The Ipv6DnsAddress key is ignored on Windows 2000 Server and Windows Server 2003.

<232> Section 2.2.2.2.85: The Ipv6Dns2Address key is ignored on Windows 2000 Server and Windows Server 2003.

<233> Section 2.2.2.2.86: The Ipv6Prefix key is ignored on Windows 2000 Server, Windows Server 2003, and Windows Server 2008.

<234> Section 2.2.2.2.87: The Ipv6InterfaceId key is ignored on Windows 2000 Server, Windows Server 2003, and Windows Server 2008.

<235> Section 2.2.2.2.97: If the PBVersion key is present and is set to "1", and the Type key is present, then this key is optional on applicable Windows Server releases except on Windows 2000 Server, Windows Server 2003, and Windows Server 2008.

<236> Section 2.2.2.2.100: In Windows 2000 Server the value of DEVICE key is same as that of MEDIA key for all the device types other than Modem, Isdn, X25, Pad, and Switch. The X25 and Pad device types are supported in Windows 2000 Server and Windows Server 2003. The PPPoE device type is not supported in Windows 2000 Server.

 

<237> Section 2.2.2.2.101: The Terminal key is not available in Windows 2000 Server.

<238> Section 2.2.2.2.104: The X25 and Pad device types are present on Windows 2000 Server and Windows Server 2003. Otherwise this key is ignored in applicable Windows Server releases.

<239> Section 2.2.2.2.105: The X25 and Pad device types are present on Windows 2000 Server and Windows Server 2003. Otherwise this key is ignored in applicable Windows Server releases.

<240> Section 2.2.2.2.106: The X25 and Pad device types are present on Windows 2000 Server and Windows Server 2003. Otherwise this key is ignored in applicable Windows Server releases.

<241> Section 2.2.2.2.107: The X25 and Pad device types are present on Windows 2000 Server and Windows Server 2003.  Otherwise this key is ignored in applicable Windows Server releases.

<242> Section 2.2.3: Windows clients use these registry keys to manage RRAS configuration when the RRASM server is offline.

<243> Section 2.2.3.1: The IPX value is available only in Windows 2000 Server.

<244> Section 2.2.3.1.3: The GlobalInterfaceInfo value is defined only for the IPX transport available only in Windows 2000.

<245> Section 2.2.3.4.18.3: The RADIUS accounting server-specific setting registry key is defined only on Windows 2000 Server and Windows Server 2003.

<246> Section 2.2.3.4.19.4: The RADIUS authentication server-specific setting registry keys are only defined on Windows 2000 Server and Windows Server 2003.

<247> Section 2.2.5.1.1: The IPv6-related information and features are not defined in Windows 2000 Server and Windows Server 2003.

<248> Section 3.1.1: The PID_IPX value is available only in Windows 2000. The PID_IPV6 value is not available in Windows 2000 Server and Windows Server 2003.

<249> Section 3.1.4.1: The MPR_SERVER_1 structure is not defined in Windows 2000 Server.

<250> Section 3.1.4.1: The MPR_SERVER_2 structure is not defined in Windows 2000 Server and Windows Server 2003.

<251> Section 3.1.4.1: The MPR_SERVER_1 structure is not defined in Windows 2000 Server.

<252> Section 3.1.4.1: The MPR_SERVER_2 structure is not defined in Windows 2000 Server and Windows Server 2003.

<253> Section 3.1.4.2: The RASI_CONNECTION_3 structure is not defined in Windows 2000 Server and Windows Server 2003.

<254> Section 3.1.4.10: The RRouterInterfaceTransportSetGlobalInfo method is not available on Windows 2000, Windows XP, Windows Vista, or Windows 7.

<255> Section 3.1.4.10: The PID_IPX value is available only in Windows 2000 Server. The PID_IPV6 value is not available in Windows 2000 Server and Windows Server 2003.

<256> Section 3.1.4.11: The RRouterInterfaceTransportGetGlobalInfo method is not available on Windows 2000, Windows XP, Windows Vista, or Windows 7.

<257> Section 3.1.4.11: The PID_IPX value is available only in Windows 2000 Server. The PID_IPV6 value is not available in Windows 2000 Server and Windows Server 2003.

<258> Section 3.1.4.11: The MS_IP_OSPF value is only available in Windows 2000 Server and Windows Server 2003.

<259> Section 3.1.4.11: The MS_IP_ALG value is not available in Windows 2000 Server.

<260> Section 3.1.4.12: The RRouterInterfaceGetHandle method is not available on Windows 2000, Windows XP, Windows Vista, or Windows 7.

<261> Section 3.1.4.13: The RRouterInterfaceCreate method is not supported in Windows 2000, Windows XP, Windows Vista, and Windows 7.

<262> Section 3.1.4.13: If dwIfType is set to ROUTER_IF_TYPE_TUNNEL1, no error is returned in Windows 2000 Server.

<263> Section 3.1.4.14: The RRouterInterfaceGetInfo method is not available on Windows 2000, Windows XP, Windows Vista, or Windows 7.

<264> Section 3.1.4.15: The RRouterInterfaceSetInfo method is not available on Windows 2000, Windows XP, Windows Vista, or Windows 7.

<265> Section 3.1.4.15: The MPRI_INTERFACE_3 structure is not available in Windows 2000 Server and Windows Server 2003.

<266> Section 3.1.4.16: The RRouterInterfaceDelete method is not available on Windows 2000, Windows XP, Windows Vista, or Windows 7.

<267> Section 3.1.4.17: The RRouterInterfaceTransportRemove method is not available on Windows 2000, Windows XP, Windows Vista, or Windows 7.

<268> Section 3.1.4.17: The PID_IPX value is available only in Windows 2000 Server. The PID_IPV6 value is not available in Windows 2000 Server and Windows Server 2003.

<269> Section 3.1.4.18: The RRouterInterfaceTransportAdd method is not available on Windows 2000, Windows XP, Windows Vista, or Windows 7.

<270> Section 3.1.4.18: The PID_IPX value is available only in Windows 2000 Server. The PID_IPV6 value is not available in Windows 2000 Server and Windows Server 2003.

<271> Section 3.1.4.18:  IPv6-related information and features are not defined in Windows 2000 Server and Windows Server 2003.

<272> Section 3.1.4.18: The MS_IP_OSPF value is available only in Windows 2000 Server and Windows Server 2003.

<273> Section 3.1.4.19: The RRouterInterfaceTransportGetInfo method is not available on Windows 2000, Windows XP, Windows Vista, or Windows 7.

<274> Section 3.1.4.19: The PID_IPX value is available only in Windows 2000 Server. The PID_IPV6 value is not available in Windows 2000 Server and Windows Server 2003.

<275> Section 3.1.4.19: The IPV6_ROUTE_INFO and FILTER_DESCRIPTOR_V6 (section 2.2.1.2.7) cannot be retrieved in Windows 2000 Server, Windows Server 2003, and in Windows Server 2008.

<276> Section 3.1.4.20: The RRouterInterfaceTransportSetInfo method is not available on Windows 2000, Windows XP, Windows Vista, or Windows 7.

<277> Section 3.1.4.20: The PID_IPX value is available on Windows 2000 Server only. The PID_IPV6 value is not available on Windows 2000 Server and Windows Server 2003.

<278> Section 3.1.4.20: IPv6-related information and features are not defined in Windows 2000 Server and Windows Server 2003.

<279> Section 3.1.4.20: The MS_IP_OSPF value is available only in Windows 2000 Server and Windows Server 2003.

<280> Section 3.1.4.21: The RRouterInterfaceEnum method is not available on Windows 2000, Windows XP, Windows Vista, or Windows 7.

<281> Section 3.1.4.22: The RRouterInterfaceConnect method is not available on Windows 2000, Windows XP, Windows Vista, or Windows 7.

<282> Section 3.1.4.24: The RRouterInterfaceUpdateRoutes method is not available on Windows 2000, Windows XP, Windows Vista, or Windows 7.

<283> Section 3.1.4.24: The PID_IPX value is available only in Windows 2000 Server.

<284> Section 3.1.4.25: The RRouterInterfaceQueryUpdateResult method is not available on Windows 2000, Windows XP, Windows Vista, or Windows 7.

<285> Section 3.1.4.25: The PID_IPX value is available only in Windows 2000 Server.

<286> Section 3.1.4.26: The RRouterInterfaceUpdatePhonebookInfo method is not available on Windows 2000, Windows XP, Windows Vista, or Windows 7.

<287> Section 3.1.4.27: The RMIBEntryCreate method is not available on Windows 2000, Windows XP, Windows Vista, or Windows 7.

<288> Section 3.1.4.28: The RMIBEntryDelete method is not available on Windows 2000, Windows XP, Windows Vista, or Windows 7.

<289> Section 3.1.4.28: Not supported in Windows Server 2008 and Windows Server 2008 R2 operating system.

<290> Section 3.1.4.29: The RMIBEntrySet method is not available on Windows 2000, Windows XP, Windows Vista, or Windows 7.

<291> Section 3.1.4.30: The RMIBEntryGet method is not available on Windows 2000, Windows XP, Windows Vista, or Windows 7.

<292> Section 3.1.4.30: The PID_IPX value is available only in Windows 2000 Server. The PID_IPV6 value is not available in Windows 2000 Server and Windows Server 2003.

<293> Section 3.1.4.30: The MS_IP_OSPF value is available only in Windows 2000 Server and Windows Server 2003.

<294> Section 3.1.4.31: The RMIBEntryGetFirst method is not available on Windows 2000, Windows XP, Windows Vista, or Windows 7.

<295> Section 3.1.4.31: The PID_IPX value is available only in Windows 2000 Server. The PID_IPV6 value is not available in Windows 2000 Server and Windows Server 2003.

<296> Section 3.1.4.31: The MS_IP_OSPF value is available only in Windows 2000 Server and Windows Server 2003.

<297> Section 3.1.4.32: The RMIBEntryGetNext method is not available on Windows 2000, Windows XP, Windows Vista, or Windows 7.

<298> Section 3.1.4.32: Windows returns ERROR_SUCCESS when the global configuration for IPBOOTP is requested. Since only one global configuration is available for IPBOOTP, RMIBEntryGetNext method is treated the same as RMIBEntryGetFirst method and the global configuration always returns the value ERROR_SUCCESS.

<299> Section 3.1.4.33: The RMIBGetTrapInfo method is not available on Windows 2000, Windows XP, Windows Vista, or Windows 7.

<300> Section 3.1.4.33: The PID_IPX value is available only in Windows 2000 Server. The PID_IPV6 value is not available in Windows 2000 Server and Windows Server 2003.

<301> Section 3.1.4.34: The RMIBSetTrapInfo method is not available on Windows 2000, Windows XP, Windows Vista, or Windows 7. This method is not invoked by Windows remotely.

<302> Section 3.1.4.35: The RRasAdminConnectionNotification method is not available on Windows 2000, Windows XP, Windows Vista, or Windows 7. This method is not invoked by Windows remotely.

<303> Section 3.1.4.36: The RRasAdminSendUserMessage method is not available on Windows 2000, Windows XP, Windows Vista, or Windows 7.

<304> Section 3.1.4.36: The hDimServer handle is only defined in Windows Server 2003.

<305> Section 3.1.4.37: The RRouterDeviceEnum method is not available on Windows 2000, Windows XP, Windows Vista, or Windows 7.

<306> Section 3.1.4.38: The RRouterInterfaceTransportCreate method is not available on Windows 2000, Windows XP, Windows Vista, or Windows 7.

<307> Section 3.1.4.38: The PID_IPX value is available only in Windows 2000 Server. The PID_IPV6 value is not available in Windows 2000 Server and Windows Server 2003.

<308> Section 3.1.4.38: In Windows, iprtrmgr.dll MUST be present in the %systemroot%\system32 folder.

<309> Section 3.1.4.39: The RRouterInterfaceDeviceGetInfo method is not available on Windows 2000, Windows XP, Windows Vista, or Windows 7.

<310> Section 3.1.4.40: The RRouterInterfaceDeviceSetInfo method is not available on Windows 2000, Windows XP, Windows Vista, or Windows 7.

<311> Section 3.1.4.40: Windows does not validate the type of devices being added for a connection. Thus, if the devices specified are valid serial, ISDN, PPPoE, or VPN devices (as provided by the RRouterDeviceEnum method), the addition of the VPN/PPPoE devices still succeeds and the method returns ERROR_SUCCESS, though the functionality itself is not supported.

<312> Section 3.1.4.41: The RRouterInterfaceSetCredentialsEx method is not available on Windows 2000, Windows XP, Windows Vista, or Windows 7.

<313> Section 3.1.4.42: The RRouterInterfaceGetCredentialsEx method is not available on Windows 2000, Windows XP, Windows Vista, or Windows 7.

<314> Section 3.1.4.43: The RRasAdminConnectionRemoveQuarantine method is not available on Windows 2000, Windows XP, Windows Vista, or Windows 7.

<315> Section 3.1.4.43: The hDimServer handle is only defined in Windows Server 2003.

<316> Section 3.1.4.44: The RMprAdminServerSetInfo method is not available on Windows 2000, Windows XP, Windows Vista, or Windows 7.

<317> Section 3.1.4.44: For each VPN Tunnel Type, Windows maintains the port configuration by using the registry keys MaxWanEndpoints and WanEndpoints as specified in section 2.2.3.3.1.7 and section 2.2.3.3.1.8, respectively. The WanEndpoints key corresponds to the number of ports being configured through the MPR_SERVER_1 and MPR_SERVER_2 structures. When WanEndpoints is configured to be more than MaxWanEndpoints, a reboot is required for the configuration change to be applied by the RRAS implementation. In such a case, Windows will return the error code ERROR_SUCCESS_REBOOT_REQUIRED.

<318> Section 3.1.4.44: Windows will return the error value ERROR_SUCCESS_REBOOT_REQUIRED when the configuration change requires a reboot of the machine for the settings to be applied. One such implementation requirement is when the number of ports configured is more than the maximum number of ports that the tunneling protocols are configured to support initially.

<319> Section 3.1.4.45: The RMprAdminServerGetInfoEx method was introduced in Windows Server 2008 R2 and Windows 7.

<320> Section 3.1.4.46: The RRasAdminConnectionEnumEx method was introduced in Windows Server 2008 R2 and Windows 7.

<321> Section 3.1.4.47: The RRasAdminConnectionGetInfoEx method is not available on Windows 2000, Windows 2000 Server, Windows XP, Windows Server 2003, or Windows Vista.

<322> Section 3.1.4.48: The RMprAdminServerSetInfoEx method is not available on Windows 2000, Windows XP, Windows Vista, or Windows 7.

<323> Section 3.1.4.48: Windows returns the error value ERROR_SUCCESS_REBOOT_REQUIRED (0x00000BC2) when the configuration change requires a reboot of the machine for the settings to be applied. One such instance is when the number of ports configured is more than the maximum number of ports that the tunneling protocols are configured to support initially.

<324> Section 3.1.4.48: Windows returns the error value ERROR_SUCCESS_RESTART_REQUIRED (0x00000BC3) when a configuration change is being done for SSTP or IKEv2, such as when the value for the setConfigForProtocols member of MPR_SERVER_SET_CONFIG_EX_1 in pServerConfig is specified as MPRAPI_SET_CONFIG_PROTOCOL_FOR_SSTP (0x00000004) or MPRAPI_SET_CONFIG_PROTOCOL_FOR_IKEV2 (0x00000008).

<325> Section 3.1.4.49: The RRasAdminUpdateConnection method is not available on Windows 2000, Windows XP, Windows Vista, or Windows 7.

<326> Section 3.1.4.50: The RRouterInterfaceSetCredentialsLocal method is not available on Windows 2000, Windows XP, Windows Vista, or Windows 7.

<327> Section 3.1.4.51: The RRouterInterfaceGetCredentialsLocal method is not available in Windows 2000 Server, Windows Server 2003, and Windows Server 2008.

<328> Section 3.1.4.52: The RRouterInterfaceGetCustomInfoEx method is not available in Windows 2000 Server, Windows Server 2003, Windows Server 2008, and Windows Server 2008 R2.

<329> Section 3.1.4.53: The RRouterInterfaceSetCustomInfoEx method is not available in Windows 2000 Server, Windows Server 2003, Windows Server 2008, and Windows Server 2008 R2.

<330> Section 3.2.4.15: The error code ERROR_IKEV2_PSK_INTERFACE_ALREADY_EXISTS is not available in Windows 2000 Server, Windows Server 2003, Windows Server 2008, and Windows Server 2008 R2.

<331> Section 3.2.4.15: Windows calls RRouterInterfaceGetInfo method (section 3.2.4.14) in order to construct and fill the structures with which RRouterInterfaceSetInfo will be called. After the structure is retrieved the RRouterInterfaceGetInfo method is used to apply the necessary configuration modifications to the structure before RRouterInterfaceSetInfo method is called.

<332> Section 3.3.4: Windows 2000 Server does not throw an exception to indicate the client does not have access.

<333> Section 3.3.4: Windows 2000 Server returns the status value of E_ACCESSDENIED (0x80070005).

<334> Section 3.3.4.1: Windows 2000 Server does not throw an RPC exception. Instead it returns an error value of E_ACCESSDENIED (0x80070005).

<335> Section 3.3.4.2: Windows 2000 Server does not throw an RPC exception. Instead it returns an error value of E_ACCESSDENIED (0x80070005).

<336> Section 3.3.4.2: Windows 2000 Server does not perform access permission validation.

<337> Section 3.3.4.3: Windows 2000 Server does not throw an RPC exception. Instead, it returns an error value of E_ACCESSDENIED (0x80070005).

<338> Section 3.3.4.4: Windows 2000 Server does not throw an RPC exception. Instead, it returns an error value of E_ACCESSDENIED (0x80070005).

<339> Section 3.3.4.4: Windows 2000 Server does not validate access permission.

<340> Section 3.3.4.5: Windows 2000 Server does not throw an RPC exception. Instead, it returns an error value of E_ACCESSDENIED (0x80070005).

<341> Section 3.3.4.5: The maximum for ReqTypes enumeration is 122 for Windows 2000 Server, 129 for Windows Server 2003, 137 for Windows Server 2008, and 141 for Windows Server 2008 R2.

<342> Section 3.3.4.5: The version is 5 for Windows 2000 Server, 6 for Windows Server 2003, Windows Server 2008, and Windows Server 2008 R2.

<343> Section 3.3.4.5: Validation is not available in Windows 2000 Server.

<344> Section 3.3.4.6: The NP_Nbf value is valid only in Windows 2000 Server.

<345> Section 3.3.4.6: The NP_Ipx value is valid only in Windows 2000 Server.

<346> Section 3.3.4.6: The NP_Ipv6 vlaue is not valid in Windows 2000 Server and Windows Server 2003.

<347> Section 3.3.4.6: Windows 2000 Server does not throw an RPC exception. Instead, it returns an error value of E_ACCESSDENIED (0x80070005).

<348> Section 3.3.4.7: Windows 2000 Server does not throw an RPC exception. Instead, it returns an error value of E_ACCESSDENIED (0x80070005).

<349> Section 3.3.4.7: Windows 2000 Server does not validate access permission.

<350> Section 3.3.4.7: The RRAS server version is 5 for Windows 2000 Server, and 6 for Windows Server 2003, Windows Server 2008, and Windows Server 2008 R2.

<351> Section 3.4.4: Windows 2000 Server will return a status of E_ACCESS_DENIED if the client is not an administrator of the RRASM server.

<352> Section 3.5.4.4.1: The GetIcfEnabled method is defined only in Windows 2000 Server, Windows Server 2003, and Windows Server 2003 R2.

<353> Section 3.5.4.7: SSTP methods in the IRemoteSSTPCertCheck interface are not available in Windows 2000 Server, Windows Server 2003, and Windows Server 2008.

<354> Section 4.2: The Information level 3 is not defined in Windows 2000 Server and Windows Server 2003.