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 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 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.1: Not available in Windows 2000 Server.

<2> Section 2.1.2.1: In Windows 2000 Server no authentication service registration is specified.

<3> Section 2.1.2.1: Not supported in Windows 2000 Server.

<4> Section 2.1.2.1: Not available in Windows 2000 Server.

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

<6> Section 2.1.2.2: Not available in Windows 2000 Server

<7> Section 2.1.2.2: In Windows 2000 Server no authentication service is specified.

<8> Section 2.1.2.2: Not supported in Windows 2000 Server.

<9> Section 2.2.1.1.1: Only defined in Windows Server 2000 and not defined for Windows Server 2008 and Windows Server 2003.

<10> Section 2.2.1.1.16: Not defined in Windows 2000 Server

<11> Section 2.2.1.1.16: Not defined in Windows 2000 Server and Windows Server 2003

<12> Section 2.2.1.1.16: Not defined in Windows 2000 Server, Windows Server 2003, and Windows Server 2008.

<13> Section 2.2.1.1.16: Not defined in Windows 2000 Server

<14> Section 2.2.1.1.22: BGP_POLICY_DIRECTION is available in Windows Server 2012 R2 only.

<15> Section 2.2.1.1.23: BGP_POLICY_TYPE is available in Windows Server 2012 R2 only.

<16> Section 2.2.1.1.24: BGP_PEERING_OP_MODE is available in Windows Server 2012 R2 only.

<17> Section 2.2.1.2.4: IPv6-related information and features are only defined in Windows Server 2008.

<18> Section 2.2.1.2.4: IP_PROT_PRIORITY_INFO_EX is available only in Windows Server 2012 R2.

<19> Section 2.2.1.2.4: Only defined in Windows 2000 Server.

<20> Section 2.2.1.2.4: IPv6-related information and features are only defined in Windows Server 2008.

<21> Section 2.2.1.2.4: IPv6-related information and features are only defined in Windows Server 2008.

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

<23> Section 2.2.1.2.4: IPv6-related information and features are only defined in Windows Server 2008.

<24> Section 2.2.1.2.4: IPv6-related information and features are only defined in Windows Server 2008.

<25> Section 2.2.1.2.4: Available on Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2.

<26> Section 2.2.1.2.4: Available on Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2.

<27> Section 2.2.1.2.4: Windows 2000 Server and Windows Server 2003 only.

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

<29> Section 2.2.1.2.7: Only defined in Windows Server 2008.

<30> Section 2.2.1.2.8: IPv6-related information and features are only defined in Windows Server 2008.

<31> Section 2.2.1.2.11: Only defined in Windows Server 2008.

<32> Section 2.2.1.2.11: Only defined in Windows Server 2003 and Windows Server 2008.

<33> Section 2.2.1.2.11: Only defined in Windows Server 2008.

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

<35> Section 2.2.1.2.13: The PROTOCOL_METRIC is defined only in the following versions of Windows:

  • Windows 2000 Server

  • Windows Server 2003

  • Windows Server 2008

  • Windows Server 2008 R2

  • Windows Server 2012

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

<37> Section 2.2.1.2.17: Windows 2000 Server only.

<38> 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.

<39> Section 2.2.1.2.32: wType is not defined in Windows 2000 Server.

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

<41> Section 2.2.1.2.35: ForwardProto is not defined in Windows 2000 Server and windows_server_2003.

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

<43> Section 2.2.1.2.56: State is not defined in Windows 2000 Server and Windows Server 2003.

<44> Section 2.2.1.2.57: RtoAlgorithm is not defined in Windows 2000 Server and Windows Server 2003.

<45> Section 2.2.1.2.63: The port limit is determined by the Windows server license.

<46> Section 2.2.1.2.63: The port limit is determined by the Windows server license.

<47> Section 2.2.1.2.64: Not defined in Windows 2000 Server and Windows Server 2003.

<48> Section 2.2.1.2.64: The port limit is determined by the Windows server license.

<49> Section 2.2.1.2.64: The port limit is determined by the Windows server license.

<50> Section 2.2.1.2.64: Not defined in Windows 2000 Server and Windows Server 2003.

<51> Section 2.2.1.2.64: The port limit is determined by the Windows server license.

<52> Section 2.2.1.2.64: Not defined in Windows 2000 Server and Windows Server 2003.

<53> Section 2.2.1.2.65: Only defined in Windows 2000 Server.

<54> Section 2.2.1.2.68: Only defined in Windows 2000 Server.

<55> Section 2.2.1.2.69: IPv6-related information and features are only defined in Windows Server 2008.

<56> Section 2.2.1.2.70: Only defined in Windows 2000 Server.

<57> Section 2.2.1.2.72: Not defined in Windows 2000 Server.

<58> Section 2.2.1.2.72: Not defined in Windows 2000 Server.

<59> Section 2.2.1.2.72: Not defined in Windows 2000 Server.

<60> Section 2.2.1.2.72: Applies to Windows 2000 Server and Windows Server 2003 only.

<61> Section 2.2.1.2.72: Applies to Windows 2000 Server and Windows Server 2003 only.

<62> Section 2.2.1.2.72: Not defined in Windows 2000 Server.

<63> Section 2.2.1.2.72: Not defined in Windows 2000 Server.

<64> Section 2.2.1.2.72: Not defined in Windows 2000 Server.

<65> Section 2.2.1.2.72: Not defined in Windows 2000 Server and Windows Server 2003.

<66> Section 2.2.1.2.72: Not defined in Windows 2000 Server and Windows Server 2003.

<67> Section 2.2.1.2.72: Only available in Windows Server 2012 R2.

<68> Section 2.2.1.2.72: Only available in Windows Server 2012 R2.

<69> Section 2.2.1.2.72: Only available in Windows Server 2012 R2.

<70> Section 2.2.1.2.72: Only available in Windows Server 2012 R2.

<71> Section 2.2.1.2.73: Only defined in Windows 2000 Server.

<72> Section 2.2.1.2.73: Only defined in Windows 2000 Server.

<73> Section 2.2.1.2.74: Not defined in Windows 2000 Server.

<74> Section 2.2.1.2.74: Only defined in Windows 2000 Server.

<75> Section 2.2.1.2.74: Only defined in Windows 2000 Server.

<76> Section 2.2.1.2.75: Not defined in Windows 2000 Server and Windows Server 2003.

<77> Section 2.2.1.2.75: IPv6-related information and features are only defined in Windows Server 2008.

<78> Section 2.2.1.2.78: Only defined in Windows 2000 Server.

<79> Section 2.2.1.2.81: Not defined in Windows 2000 Server and Windows Server 2003.

<80> Section 2.2.1.2.81: Not defined in Windows 2000 Server and Windows Server 2003.

<81> Section 2.2.1.2.83: Not defined in Windows 2000 Server.

<82> Section 2.2.1.2.84: Not defined in Windows 2000 Server.

<83> Section 2.2.1.2.84: Windows implementations 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.

<84> Section 2.2.1.2.84: In Windows Serverimplementations, 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.

<85> Section 2.2.1.2.84: Only defined in Windows 2000 Server and Windows Server 2003.

<86> Section 2.2.1.2.84: Only defined in Windows 2000 Server and Windows Server 2003.

<87> Section 2.2.1.2.84: This is available in Windows Server 2012 and Windows Server 2012 R2.

<88> Section 2.2.1.2.84: This is available in Windows Server 2012 and Windows Server 2012 R2.

<89> Section 2.2.1.2.84: This is available in Windows Server 2012 and Windows Server 2012 R2.

<90> Section 2.2.1.2.84: Defined in Windows 2000 Server only.

<91> Section 2.2.1.2.84: Not defined in Windows 2000 Server and Windows Server 2003.

<92> Section 2.2.1.2.84: This feature is only supported in Windows 2000 Server, Windows Server 2003, and Windows Server 2003 R2.

<93> Section 2.2.1.2.84: In Windows 2000 and Windows NT the szX25PadType string maps to a section name in PAD.INF.

<94> Section 2.2.1.2.84: This feature is only supported in Windows 2000 Server, Windows Server 2003, and Windows Server 2003 R2.

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

<96> Section 2.2.1.2.84: Supported only in Windows 2000 Server.

<97> Section 2.2.1.2.84: Support for dialing IKEv2 is available in Windows Server 2012 and Windows Server 2012 R2.

<98> Section 2.2.1.2.84: Support for dialing IKEv2 is available in Windows Server 2012 and Windows Server 2012 R2.

<99> Section 2.2.1.2.84: Support for dialing IKEv2 is available in Windows Server 2012 and Windows Server 2012 R2.

<100> Section 2.2.1.2.84: This is available Windows Server 2012 and Windows Server 2012 R2.

<101> Section 2.2.1.2.84: This is available in Windows Server 2012 and Windows Server 2012 R2.

<102> Section 2.2.1.2.85: Not defined in Windows 2000 Server and Windows Server 2003.

<103> Section 2.2.1.2.85: Windows implementations 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.

<104> Section 2.2.1.2.85: In Windows Serverimplementations, 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.

<105> Section 2.2.1.2.85: Not defined in Windows 2000 Server.

<106> Section 2.2.1.2.85: Not defined in Windows 2000 Server.

<107> Section 2.2.1.2.85: Not defined in Windows 2000 Server.

<108> Section 2.2.1.2.85: Not defined in Windows 2000 Server.

<109> Section 2.2.1.2.85: This is available in Windows Server 2012 and Windows Server 2012 R2.

<110> Section 2.2.1.2.85: This is available in Windows Server 2012 and Windows Server 2012 R2.

<111> Section 2.2.1.2.85: This is available in Windows Server 2012 and Windows Server 2012 R2.

<112> Section 2.2.1.2.85: This feature is only supported in Windows 2000 Server, Windows Server 2003, and Windows Server 2003 R2.

<113> Section 2.2.1.2.85: In Windows 2000 and Windows NT, the szX25PadType string maps to a section name in PAD.INF.

<114> Section 2.2.1.2.85: This feature is only supported in Windows 2000 Server, Windows Server 2003, and Windows Server 2003 R2.

<115> Section 2.2.1.2.85: This 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.

<116> Section 2.2.1.2.85: Support for dialing IKEv2 is available in Windows Server 2012 and Windows Server 2012 R2.

<117> Section 2.2.1.2.85: Support for dialing IKEv2 is available in Windows Server 2012 and Windows Server 2012 R2.

<118> Section 2.2.1.2.85: Support for dialing IKEv2 is available in Windows Server 2012 and Windows Server 2012 R2.

<119> Section 2.2.1.2.85: This is available in Windows Server 2012 and Windows Server 2012 R2.

<120> Section 2.2.1.2.85: This is available in Windows Server 2012 and Windows Server 2012 R2.

<121> Section 2.2.1.2.91: Only defined in Windows 2000 Server.

<122> Section 2.2.1.2.92: Only defined in Windows 2000 Server.

<123> Section 2.2.1.2.93: Only defined in Windows 2000 Server.

<124> Section 2.2.1.2.94: Only defined in Windows 2000 Server.

<125> Section 2.2.1.2.95: Only defined in Windows 2000 Server.

<126> Section 2.2.1.2.96: Only defined in Windows 2000 Server.

<127> Section 2.2.1.2.97: Only defined in Windows 2000 Server.

<128> Section 2.2.1.2.98: Only defined in Windows 2000 Server.

<129> Section 2.2.1.2.99: Windows 2000 Server only.

<130> Section 2.2.1.2.100: Only defined in Windows 2000 Server.

<131> Section 2.2.1.2.101: Only defined in Windows 2000 Server.

<132> Section 2.2.1.2.102: Only defined in Windows 2000 Server.

<133> Section 2.2.1.2.103: Only defined in Windows 2000 Server.

<134> Section 2.2.1.2.104: Only defined in Windows 2000 Server.

<135> Section 2.2.1.2.105: Only defined in Windows 2000 Server.

<136> Section 2.2.1.2.106: Only defined in Windows 2000 Server.

<137> Section 2.2.1.2.107: Only defined in Windows 2000 Server.

<138> Section 2.2.1.2.108: Only defined in Windows 2000 Server.

<139> Section 2.2.1.2.109: Only defined in Windows 2000 Server.

<140> Section 2.2.1.2.109: This media type is available only in Windows 2000, Windows XP, and Windows Server 2003.

<141> Section 2.2.1.2.110: Only defined in Windows 2000 Server.

<142> Section 2.2.1.2.111: Only defined in Windows 2000 Server.

<143> Section 2.2.1.2.112: Only defined in Windows 2000 Server.

<144> Section 2.2.1.2.113: Only defined in Windows 2000 Server.

<145> Section 2.2.1.2.114: Only defined in Windows 2000 Server.

<146> Section 2.2.1.2.115: Only defined in Windows 2000 Server.

<147> Section 2.2.1.2.116: Only defined in Windows 2000 Server.

<148> Section 2.2.1.2.117: Only defined in Windows 2000 Server.

<149> Section 2.2.1.2.118: Only defined in Windows 2000 Server.

<150> Section 2.2.1.2.119: Only defined in Windows 2000 Server.

<151> Section 2.2.1.2.120: Only defined in Windows 2000 Server.

<152> Section 2.2.1.2.121: Only defined in Windows 2000 Server.

<153> Section 2.2.1.2.122: Only defined in Windows 2000 Server.

<154> Section 2.2.1.2.126: Only defined in Windows 2000 Server.

<155> Section 2.2.1.2.127: Only defined in Windows 2000 Server.

<156> Section 2.2.1.2.130: The MPRAPI_OBJECT_HEADER_IDL structure is available in Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2.

<157> Section 2.2.1.2.130: This is available in Windows Server 2012 and Windows Server 2012 R2.

<158> Section 2.2.1.2.130: MPR_SERVER_SET_CONFIG_EX is available only in Windows Server 2012 R2.

<159> Section 2.2.1.2.130: This is available in Windows Server 2012 and Windows Server 2012 R2.

<160> Section 2.2.1.2.130: MPR_SERVER_EX_3 is available only in Windows Server 2012 R2.

<161> Section 2.2.1.2.130: This is available in Windows Server 2012 and Windows Server 2012 R2.

<162> Section 2.2.1.2.130: MPR_IF_CUSTOMINFOEX_1 is available only in Windows Server 2012 R2.

<163> Section 2.2.1.2.130: This is available in Windows Server 2012and Windows Server 2012 R2.

<164> Section 2.2.1.2.131: The PPP_PROJECTION_INFO_1 is available in Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2.

<165> Section 2.2.1.2.132: IKEV2_PROJECTION_INFO_1 is available in Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2.

<166> Section 2.2.1.2.134: RAS_FLAGS_ARAP_CONNECTION is only defined in Windows 2000 Server.

<167> Section 2.2.1.2.134: RAS_FLAGS_DORMANT is available in Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2.

<168> Section 2.2.1.2.137: IKEV2_TUNNEL_CONFIG_PARAMS_1 is available in Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2.

<169> Section 2.2.1.2.138: This is available in Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2.

<170> Section 2.2.1.2.138: The port limit is determined by the Windows server license.

<171> Section 2.2.1.2.139: PPTP_CONFIG_PARAMS_1 is available in Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2.

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

<173> Section 2.2.1.2.140: L2TP_CONFIG_PARAMS_1 is available in Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2.

<174> Section 2.2.1.2.140: The port limit is determined by the Windows Server license.

<175> Section 2.2.1.2.141: SSTP_CERT_INFO_1 is available in Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2.

<176> Section 2.2.1.2.142: SSTP_CONFIG_PARAMS_1 is available in Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2.

<177> Section 2.2.1.2.142: The port limit is determined by the Windows server license.

<178> Section 2.2.1.2.143: MPR_SERVER_EX_1 is available in Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2.

<179> Section 2.2.1.2.144: MPR_SERVER_EX_IDL is available in Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2.

<180> Section 2.2.1.2.144: MPR_SERVER_EX_3 is available only in Windows Server 2012 R2.

<181> Section 2.2.1.2.145: This is available beginning with Windows Server 2008 R2.

<182> Section 2.2.1.2.146: This is available beginning with Windows Server 2008 R2.

<183> Section 2.2.1.2.148: This is available beginning with Windows Server 2008 R2.

<184> Section 2.2.1.2.149: This is available beginning with Windows Server 2008 R2.

<185> Section 2.2.1.2.190: Windows 2000 Server and Windows Server 2003 only.

<186> Section 2.2.1.2.201: IP_ALG_GLOBAL_INFO is not available in Windows 2000 Server.

<187> Section 2.2.1.2.202: RIP_GLOBAL_INFO is not defined in Windows 2000 Server.

<188> Section 2.2.1.2.204: RIP_GLOBAL_INFO is not defined in Windows 2000 Server.

<189> Section 2.2.1.2.205: Only defined in Windows 2000 Server.

<190> Section 2.2.1.2.206: RIP_IF_CONFIG is not defined in Windows 2000 Server.

<191> Section 2.2.1.2.207: SAP_GLOBAL_INFO is not defined inWindows 2000 Server.

<192> Section 2.2.1.2.208: Windows 2000 Server and Windows Server 2003 only.

<193> Section 2.2.1.2.209: Windows 2000 Server and Windows Server 2003 only.

<194> Section 2.2.1.2.210: Windows 2000 Server and Windows Server 2003 only.

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

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

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

<198> Section 2.2.1.2.214: OSPF_VIRT_INTERFACE_PARAM is application in Windows 2000 Server and Windows Server 2003 only.

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

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

<201> Section 2.2.1.2.217: Not defined in Windows 2000 Server.

<202> Section 2.2.1.2.218: 5 for Windows 2000 Server, 6 for Windows Server 2003, Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2.

<203> Section 2.2.1.2.219: 5 for Windows 2000 Server, 6 for Windows Server 2003, Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2.

<204> Section 2.2.1.2.219: fRouterOutboundEnabled is not defined in Windows 2000 Server.

<205> Section 2.2.1.2.219: wszDeviceName is not defined in Windows 2000 Server.

<206> Section 2.2.1.2.228: RI_dwSessionId is not defined in Windows 2000 Server.

<207> Section 2.2.1.2.228: RI_dwFlags is not defined in Windows 2000 Server.

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

<209> Section 2.2.1.2.230: Defined in Windows 2000 Server and Windows Server 2003.

<210> Section 2.2.1.2.230: Defined in Windows 2000 Server and Windows Server 2003.

<211> Section 2.2.1.2.230: Not defined in Windows 2000 Server.

<212> Section 2.2.1.2.233: This is available in Windows Server 2012 and Windows Server 2012 R2.

<213> Section 2.2.1.2.234: IKEV2_PROJECTION_INFO_2 is available in Windows Server 2012 and Windows Server 2012 R2.

<214> Section 2.2.1.2.235: PROJECTION_INFO_IDL_2 is available in Windows Server 2012 and Windows Server 2012 R2.

<215> Section 2.2.1.2.236: RAS_CONNECTION_4_IDL is available in Windows Server 2012 and Windows Server 2012 R2.

<216> Section 2.2.1.2.237: ROUTER_CUSTOM_IKEv2_POLICY_0 is available in Windows Server 2012 and Windows Server 2012 R2.

<217> Section 2.2.1.2.238: IKEV2_TUNNEL_CONFIG_PARAMS_2 is available in Windows Server 2012 and Windows Server 2012 R2.

<218> Section 2.2.1.2.239: IKEV2_CONFIG_PARAMS_2 is available in Windows Server 2012 and Windows Server 2012 R2.

<219> Section 2.2.1.2.240: MPRAPI_TUNNEL_CONFIG_PARAMS_2 is available in Windows Server 2012 and Windows Server 2012 R2.

<220> Section 2.2.1.2.241: MPR_SERVER_SET_CONFIG_EX_2 is available in Windows Server 2012 and Windows Server 2012 R2.

<221> Section 2.2.1.2.242: MPR_SERVER_EX_2 is available in Windows Server 2012 and Windows Server 2012 R2.

<222> Section 2.2.1.2.243: ROUTER_IKEv2_IF_CUSTOM_CONFIG_0 is available in Windows Server 2012 and Windows Server 2012 R2.

<223> Section 2.2.1.2.244: MPR_IF_CUSTOMINFOEX_0 is available in Windows Server 2012 and Windows Server 2012 R2.

<224> Section 2.2.1.2.245: MPR_IF_CUSTOMINFOEX_IDL is available in Windows Server 2012 and Windows Server 2012 R2.

<225> Section 2.2.1.2.246: CERT_EKU_1 is available in Windows Server 2012 R2 only.

<226> Section 2.2.1.2.247: The IKEV2_TUNNEL_CONFIG_PARAMS_3 is available in Windows Server 2012 R2 only.

<227> Section 2.2.1.2.248: IKEV2_CONFIG_PARAMS_3 is available in Windows Server 2012 R2 only.

<228> Section 2.2.1.2.249: MPRAPI_TUNNEL_CONFIG_PARAMS_3 is available in Windows Server 2012 R2 only.

<229> Section 2.2.1.2.250: MPR_SERVER_SET_CONFIG_EX_3 is available in Windows Server 2012 R2 only.

<230> Section 2.2.1.2.251: MPR_SERVER_EX_3 is available only in Windows Server 2012 R2.

<231> Section 2.2.1.2.252: BGP_CONFIG_HEADER is available only in Windows Server 2012 R2.

<232> Section 2.2.1.2.253: BGP_TOC_ENTRY is available only in Windows Server 2012 R2.

<233> Section 2.2.1.2.254: BGP_IP_ADDRESS is available only in Windows Server 2012 R2.

<234> Section 2.2.1.2.255: BGP_IP_PREFIX is available only in Windows Server 2012 R2.

<235> Section 2.2.1.2.256: BGP_ASN_RANGE is available only in Windows Server 2012 R2.

<236> Section 2.2.1.2.257: BGP_ROUTER_CONFIG is available only in Windows Server 2012 R2.

<237> Section 2.2.1.2.258: BGP_POLICY_MATCH is available only in Windows Server 2012 R2.

<238> Section 2.2.1.2.259: BGP_POLICY_MODIFY is available only in Windows Server 2012 R2.

<239> Section 2.2.1.2.260: BGP_POLICY_ACTION is available only in Windows Server 2012 R2.

<240> Section 2.2.1.2.261: BGP_POLICY is available only in Windows Server 2012 R2.

<241> Section 2.2.1.2.262: BGP_PEER is available only in Windows Server 2012 R2.

<242> Section 2.2.1.2.263: BGP_PEER_TO_POLICIES is available only in Windows Server 2012 R2.

<243> Section 2.2.1.2.264: BGP_ADVERTISE is available only in Windows Server 2012 R2.

<244> Section 2.2.1.2.265: BGP_ROUTER_V6 is available only in Windows Server 2012 R2.

<245> Section 2.2.1.2.266: PRIORITY_INFO_EX is available only in Windows Server 2012 R2.

<246> Section 2.2.1.2.267: PROTOCOL_METRIC_EX is available only in Windows Server 2012 R2.

<247> Section 2.2.1.2.268: ROUTER_IKEv2_IF_CUSTOM_CONFIG_1 is available only on Windows Server 2012 R2.

<248> Section 2.2.1.2.269: MPR_IF_CUSTOMINFOEX_1 is available only on Windows Server 2012 R2.

<249> Section 2.2.1.2.270: L2TP_TUNNEL_CONFIG_PARAMS_1 is available only on Windows Server 2012 R2.

<250> Section 2.2.1.2.271: Is available only on Windows Server 2012 R2.

<251> Section 2.2.2: The phonebook file used by Windows 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.

<252> Section 2.2.2.1: On Windows 2000 Server and Windows Server 2003, the number of characters in RRAS entry section name cannot exceeds 256 bytes.

On Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2, the numbers of characters in the RRAS entry section name cannot exceed 1536 bytes.

<253> Section 2.2.2.2.3: On Windows Server 2008 R2, Windows Server 2012,and Windows Server 2012 R2, the Type key is optional. On Windows 2000 Server, Windows Server 2003, and Windows Server 2008, the Type key must be present.

<254> Section 2.2.2.2.3: This option is not available on Windows 2000 Server.

<255> Section 2.2.2.2.11: On 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.

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

On Windows Server 2012 and Windows Server 2012 R2, RRAS attempts PPTP first. If PPTP fails, L2TP is tried. If L2TP fails, IKEv2 is tried. If IKEv2 fails, demand-dial connection fails.

<256> Section 2.2.2.2.11: This is available in Windows Server 2012 and Windows Server 2012 R2.

<257> Section 2.2.2.2.12: Available only on Windows 2000 Server.

<258> Section 2.2.2.2.12: Available only on Windows 2000 Server.

<259> Section 2.2.2.2.12: Available on Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2.

<260> 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.

On Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2, RRAS ignores this key and assumes the value to be 1.

<261> Section 2.2.2.2.21: This key is ignored on Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2.

<262> Section 2.2.2.2.22: This key is ignored on Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2.

<263> Section 2.2.2.2.23: This key is ignored on Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2.

<264> Section 2.2.2.2.24: This key is ignored on Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2.

<265> Section 2.2.2.2.35: This key is ignored on Windows 2000 Server and Windows Server 2003.

<266> Section 2.2.2.2.38: On 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. The following table specifies the behavior on Windows 2000 Server and Windows Server 2003:

ShareMsFilePrint

BindMsNetClient

Meaning

0

0

Disable NetBT.

0

1

Enable NetBT.

1

0

Enable NetBT.

1

1

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.

<267> Section 2.2.2.2.46: This key is ignored on Windows 2000 Server.

<268> Section 2.2.2.2.47: This key is ignored on Windows 2000 Server.

<269> Section 2.2.2.2.48: This key is ignored in Windows 2000 Server.

<270> Section 2.2.2.2.49: This key is ignored in Windows 2000 Server.

<271> Section 2.2.2.2.58: SPAP is not present on Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2.

<272> Section 2.2.2.2.58: MSCHAPv1 is not present on Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2.

<273> Section 2.2.2.2.58: MSCHAP Windows 95 compatible is present only on Windows 2000 Server and Windows Server 2003.

<274> Section 2.2.2.2.58: This is available beginning with Windows Server 2012.

<275> Section 2.2.2.2.58: This is available beginning with Windows Server 2012.

<276> Section 2.2.2.2.73: IpNBTFlags key is present only on Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2. 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".

<277> Section 2.2.2.2.74: This key is ignored on Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2.

<278> Section 2.2.2.2.79: This key is ignored on Windows 2000 Server, Windows Server 2003, and Windows Server 2008.

<279> Section 2.2.2.2.80: This key is ignored on Windows 2000 Server, Windows Server 2003, and Windows Server 2008.

<280> Section 2.2.2.2.84: This key is ignored on Windows 2000 Server and Windows Server 2003.

<281> Section 2.2.2.2.85: This key is ignored on Windows 2000 Server and Windows Server 2003.

<282> Section 2.2.2.2.86: This key is ignored on Windows 2000 Server, Windows Server 2003, and Windows Server 2008.

<283> Section 2.2.2.2.87: This key is ignored on Windows 2000 Server, Windows Server 2003, and Windows Server 2008.

<284> Section 2.2.2.2.97: On Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2, if the key PBVersion is present and is set to "1", and the Type key is present, then this key is optional.

<285> Section 2.2.2.2.100:

  1. X25 and Pad device types are supported in Windows 2000 Server and Windows Server 2003.

  2. PPPoE device type is not supported in Windows 2000 Server.

  3. In Windows 2000 Server the value of DEVICE key is same as that of MEDIA key for all the device types other than isdn, x25, Pad, modem, and switch.

<286> Section 2.2.2.2.101: This key is not available in Windows 2000 Server.

<287> Section 2.2.2.2.104: X25 and Pad device types are ignored in Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2.

<288> Section 2.2.2.2.105: X25 and Pad device types are ignored in Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2.

<289> Section 2.2.2.2.106: X25 and Pad device types are ignored in Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2.

<290> Section 2.2.2.2.107: X25 and Pad device types are ignored in Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2..

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

<292> Section 2.2.3.1: Available in Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2.

<293> Section 2.2.3.1: Available only in Windows 2000 Server.

<294> Section 2.2.3.1.3: Windows defines GlobalInterfaceInfo only for the IPX transport, which is available only in Windows 2000.

<295> Section 2.2.3.4.18.3: Windows defines this registry key only on Windows 2000 Server and Windows Server 2003.

<296> Section 2.2.3.4.19.4: Windows defines this registry key only on Windows 2000 Server and Windows Server 2003.

<297> Section 3.1.1: Windows 2000 only.

<298> Section 3.1.1: Available in Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2.

<299> Section 3.1.4.1: Not defined in Windows 2000 Server.

<300> Section 3.1.4.1: Not defined in Windows 2000 Server and Windows Server 2003.

<301> Section 3.1.4.1: Not defined in Windows 2000 Server.

<302> Section 3.1.4.1: Not defined in Windows 2000 Server and Windows Server 2003.

<303> Section 3.1.4.2: This is available in Windows Server 2012 and Windows Server 2012 R2.

<304> Section 3.1.4.2: Not defined in Windows 2000 Server and Windows Server 2003.

<305> Section 3.1.4.2: This is available in Windows Server 2012 and Windows Server 2012 R2.

<306> Section 3.1.4.3: Defined in Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2.

<307> Section 3.1.4.3: Defined in Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2.

<308> Section 3.1.4.10: Not available on Windows 2000, Windows XP, Windows Vista, or Windows 7.

<309> Section 3.1.4.10: Available in Windows 2000 Server only.

<310> Section 3.1.4.10: Not available in Windows 2000 Server and Windows Server 2003.

<311> Section 3.1.4.11: Not available on Windows 2000, Windows XP, Windows Vista, or Windows 7.

<312> Section 3.1.4.11: Windows 2000 Server only.

<313> Section 3.1.4.11: Not available in Windows 2000 Server or Windows Server 2003.

<314> Section 3.1.4.11: Windows 2000 Server and Windows Server 2003 only.

<315> Section 3.1.4.11: Not available in Windows 2000 Server.

<316> Section 3.1.4.12: Not available on Windows 2000, Windows XP, Windows Vista, or Windows 7.

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

<318> Section 3.1.4.13: No error is returned in Windows 2000 Server if dwIfType is set to ROUTER_IF_TYPE_TUNNEL1.

<319> Section 3.1.4.14: Not available on Windows 2000, Windows XP, Windows Vista, or Windows 7.

<320> Section 3.1.4.15: Not available on Windows 2000, Windows XP, Windows Vista, or Windows 7.

<321> Section 3.1.4.15: Not available in Windows 2000 Server and Windows Server 2003.

<322> Section 3.1.4.16: Not available on Windows 2000, Windows XP, Windows Vista, or Windows 7.

<323> Section 3.1.4.17: Not available on Windows 2000, Windows XP, Windows Vista, or Windows 7.

<324> Section 3.1.4.17: Not available in Windows 2000 Server and Windows Server 2003.

<325> Section 3.1.4.17: Available in Windows 2000 Server only.

<326> Section 3.1.4.17: Windows 2000 Server only.

<327> Section 3.1.4.17: Not available in Windows 2000 Server and Windows Server 2003.

<328> Section 3.1.4.18: Not available on Windows 2000, Windows XP, Windows Vista, or Windows 7.

<329> Section 3.1.4.18: Windows 2000 Server only.

<330> Section 3.1.4.18: Not available in Windows 2000 Server and Windows Server 2003.

<331> Section 3.1.4.18: IPv6-related information and features are only defined inWindows Server 2008, Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2.

<332> Section 3.1.4.18: IPv6-related information and features are defined in Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2.

<333> Section 3.1.4.18: See the IP_IN_FILTER_INFO_V6 product behavior note for Windows versions that support IPv6.

<334> Section 3.1.4.18: See the IP_IN_FILTER_INFO_V6 product behavior note for Windows versions that support IPv6.

<335> Section 3.1.4.18: See the IP_IN_FILTER_INFO_V6 product behavior note for Windows versions that support IPv6.

<336> Section 3.1.4.18: Windows 2000 Server and Windows Server 2003 only.

<337> Section 3.1.4.19: Not available on Windows 2000, Windows XP, Windows Vista, or Windows 7.

<338> Section 3.1.4.19: Windows 2000 Server only.

<339> Section 3.1.4.19: Not available before Windows Server 2008.

<340> Section 3.1.4.19: IPV6_ROUTE_INFO and FILTER_DESCRIPTOR_V6 (section 2.2.1.2.7) can only be retrieved beginning with Windows Server 2008 R2.

<341> Section 3.1.4.20: Not available on Windows 2000, Windows XP, Windows Vista, or Windows 7.

<342> Section 3.1.4.20: Windows 2000 Server only.

<343> Section 3.1.4.20: Not available in Windows 2000 Server and Windows Server 2003.

<344> Section 3.1.4.20: IPv6-related information and features are only defined in Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2.

<345> Section 3.1.4.20: IPv6-related information and features are only defined in Windows Server 2008.

<346> Section 3.1.4.20: IPv6-related information and features are only defined in Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2.

<347> Section 3.1.4.20: IPv6-related information and features are only defined in Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2.

<348> Section 3.1.4.20: IPv6-related information and features are only defined in Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2.

<349> Section 3.1.4.20: Windows 2000 Server and Windows Server 2003 only.

<350> Section 3.1.4.21: Not available on Windows 2000, Windows XP, Windows Vista, or Windows 7.

<351> Section 3.1.4.22: Not available on Windows 2000, Windows XP, Windows Vista, or Windows 7.

<352> Section 3.1.4.24: Not available on Windows 2000, Windows XP, Windows Vista, or Windows 7.

<353> Section 3.1.4.24: Windows 2000 Server only.

<354> Section 3.1.4.25: Not available on Windows 2000, Windows XP, Windows Vista, or Windows 7.

<355> Section 3.1.4.25: Windows 2000 Server only.

<356> Section 3.1.4.26: Not available on Windows 2000, Windows XP, Windows Vista, or Windows 7.

<357> Section 3.1.4.27: Not available on Windows 2000, Windows XP, Windows Vista, or Windows 7.

<358> Section 3.1.4.28: Not available on Windows 2000, Windows XP, Windows Vista, or Windows 7.

<359> Section 3.1.4.28: Not supported in Windows Server 2008 and Windows Server 2008 R2.

<360> Section 3.1.4.29: Not available on Windows 2000, Windows XP, Windows Vista, or Windows 7.

<361> Section 3.1.4.30: Not available on Windows 2000, Windows XP, Windows Vista, or Windows 7.

<362> Section 3.1.4.30: Windows 2000 Server only.

<363> Section 3.1.4.30: The method does not support PID_IPV6 in Windows Server 2008 and earlier.

<364> Section 3.1.4.30: Windows 2000 Server and Windows Server 2003 only.

<365> Section 3.1.4.31: Not available on Windows 2000, Windows XP, Windows Vista, or Windows 7.

<366> Section 3.1.4.31: Windows 2000 Server only.

<367> Section 3.1.4.31: Not available before Windows Server 2008.

<368> Section 3.1.4.31: Windows 2000 Server and Windows Server 2003 only.

<369> Section 3.1.4.32: Not available on Windows 2000, Windows XP, Windows Vista, or Windows 7.

<370> 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 is treated same as RMIBEntryGetFirst and the global configuration is always returned with return value ERROR_SUCCESS.

<371> Section 3.1.4.33: Not available on Windows 2000, Windows XP, Windows Vista, or Windows 7.

<372> Section 3.1.4.33: Windows 2000 Server only.

<373> Section 3.1.4.33: PID_IPV6 is not available on Windows 2000 Server and Windows Server 2003.

<374> Section 3.1.4.34: Not available on Windows 2000, Windows XP, Windows Vista, or Windows 7.

<375> Section 3.1.4.34: This method is not invoked by Windows remotely.

<376> Section 3.1.4.35: Not available on Windows 2000, Windows XP, Windows Vista, or Windows 7.

<377> Section 3.1.4.35: This method is not invoked by Windows remotely.

<378> Section 3.1.4.36: Not available on Windows 2000, Windows XP, Windows Vista, or Windows 7.

<379> Section 3.1.4.36: Only defined in Windows Server 2003.

<380> Section 3.1.4.37: Not available on Windows 2000, Windows XP, Windows Vista, or Windows 7.

<381> Section 3.1.4.38: Not available on Windows 2000, Windows XP, Windows Vista, or Windows 7.

<382> Section 3.1.4.38: Windows 2000 Server only.

<383> Section 3.1.4.38: Not available in Windows 2000 Server and Windows Server 2003.

<384> Section 3.1.4.38: IP_PROT_PRIORITY_INFO_EX is available only in Windows Server 2012 R2.

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

<386> Section 3.1.4.39: Not available on Windows 2000, Windows XP, Windows Vista, or Windows 7.

<387> Section 3.1.4.40: Not available on Windows 2000, Windows XP, Windows Vista, or Windows 7.

<388> 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.

<389> Section 3.1.4.41: Not available on Windows 2000, Windows XP, Windows Vista, or Windows 7.

<390> Section 3.1.4.42: Not available on Windows 2000, Windows XP, Windows Vista, or Windows 7.

<391> Section 3.1.4.43: Not available on Windows 2000, Windows XP, Windows Vista, or Windows 7.

<392> Section 3.1.4.43: Only defined in Windows Server 2003.

<393> Section 3.1.4.44: Not available on Windows 2000, Windows XP, Windows Vista, or Windows 7.

<394> 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 sections 2.2.3.3.1.7 and 2.2.3.3.1.8, respectively. WanEndpoints corresponds to the number of ports being configured through the MPR_SERVER_1 and MPR_SERVER_2 structures. When WanEndpoints configured is more than MaxWanEndpoints, a reboot is required for the configuration change to be applied by the RRAS implementation. In such a case, Windows returns the error code ERROR_SUCCESS_REBOOT_REQUIRED.

<395> Section 3.1.4.44: Windows returns the error value ERROR_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.

<396> Section 3.1.4.45: This method is introduced in Windows Server 2008 R2 and Windows 7.

<397> Section 3.1.4.46: This method is introduced in Windows Server 2008 R2 and Windows 7.

<398> Section 3.1.4.47: This method is not available on Windows 2000, Windows 2000 Server, Windows XP, Windows Server 2003, or Windows Vista.

<399> Section 3.1.4.48: This method is not available on Windows 2000, Windows XP, Windows Vista, or Windows 7.

<400> Section 3.1.4.48: Windows returns the error value ERROR_REBOOT_REQUIRED 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.

<401> Section 3.1.4.48: Windows returns the error value ERROR_SUCCESS_RESTART_REQUIRED 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).

<402> Section 3.1.4.49: This method is not available on Windows 2000, Windows XP, Windows Vista, or Windows 7.

<403> Section 3.1.4.50: This method is not available on Windows 2000, Windows XP, Windows Vista, or Windows 7.

<404> Section 3.1.4.51: RRouterInterfaceGetCredentialsLocal is available in Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2.

<405> Section 3.1.4.52: RRouterInterfaceGetCustomInfoEx is available in Windows Server 2012 and Windows Server 2012 R2.

<406> Section 3.1.4.53: RRouterInterfaceSetCustomInfoEx is available in Windows Server 2012 and Windows Server 2012 R2.

<407> Section 3.2.4.15: The error code ERROR_IKEV2_PSK_INTERFACE_ALREADY_EXISTS is introduced in Windows Server 2012.

<408> Section 3.2.4.15: Windows implementation calls RRouterInterfaceGetInfo (section 3.2.4.14) in order to construct and fill the structures with which RRouterInterfaceSetInfo will be called. After the structure is retrieved using RRouterInterfaceGetInfo, the necessary configuration modifications are applied to the structure before RRouterInterfaceSetInfo is called.

<409> Section 3.2.4.26: The error code ERROR_IKEV2_PSK_INTERFACE_ALREADY_EXISTS is available in Windows Server 2012 and Windows Server 2012 R2.

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

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

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

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

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

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

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

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

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

<419> Section 3.3.4.5: Maximum ReqTypes enumeration is 141 for Windows Server 2008 R2, 137 for Windows Server 2008, 129 for Windows Server 2003, 122 for Windows 2000 Server.

<420> 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

<421> Section 3.3.4.5: Not available in Windows 2000 Server.

<422> Section 3.3.4.6: NP_Nbf is valid only in Windows 2000 Server.

<423> Section 3.3.4.6: NP_Ipx is valid only in Windows 2000 Server.

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

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

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

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

<428> Section 3.3.4.7: 5 for Windows 2000 Server, 6 for Windows Server 2003, Windows Server 2008, Windows Server 2008 R2.

<429> 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.

<430> Section 4.1: Only defined in Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2.

<431> Section 4.1: Only defined in Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2.

<432> Section 4.1: MPR_SERVER_2 is defined in Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2.

<433> Section 4.2: Only defined in Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2.

<434> Section 4.2: Only defined in Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2.

<435> Section 5.1.1: RPC_C_AUTHN_LEVEL_PKT_PRIVACY is not supported in Windows 2000 Server.

 
Show:
© 2014 Microsoft