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.

  • Windows NT operating system

  • Windows 2000 operating system

  • Windows XP operating system

  • Windows Server 2003 operating system

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

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

<1> Section 1.7: The Windows NT 4.0 operating system version of this protocol always runs in nondirectory mode.

<2> Section 2.2.3.6: The Windows implementation of locator does not store endpoint information.

<3> Section 2.2.4.3.2: This value is unused by the receiver of this message.

<4> Section 2.2.5.1.1: Locator ignores the domain name if any is specified in the entry name.

<5> Section 3.1.3.1: The Windows NT 4.0 locator always runs in this mode.

<6> Section 3.1.3.1: By default, nameServiceFlags is not set in Active Directory.

<7> Section 3.1.3.2: On a non-domain-joined computer, the nonmaster locator discovers the master locator by issuing a master locator discovery query. In addition, locators also cache the sender of a broadcast lookup request as a master locator (see section 3.4.1.5.1). On a non-domain-joined computer, if none of the locators in its cache is accessible as determined by calling the I_nsi_ping_locator method on the target locator once, a nonmaster locator changes its role to be a master locator.

<8> Section 3.1.4.1: The master locator ignores this value if the entry_name is null or an empty string.

<9> Section 3.1.4.1: The locator assumes the default value of 100 if 0 is specified.

<10> Section 3.1.4.4: Windows XP, Windows Server 2003, Windows Vista operating system, Windows Server 2008 operating system and Windows Server 2008 R2 operating system always return NSI_S_OK.

<11> Section 3.2.2.3: The server locator establishes and caches a connection to Active Directory at startup.

<12> Section 3.3.1.2: This timer is initialized to 3 seconds and has a granularity of 1 msec. Each time a response is received, the current time-out period is halved and used as the new time-out period.

<13> Section 3.3.1.4: The client locator only forwards the request to the master locator if the request cannot be satisfied locally first by looking at the unexpired name service entries in the cache. The client locator only forwards the request to the master locator if the request cannot be satisfied locally first by looking at the unexpired name service entries in the cache.

<14> Section 3.3.1.4.1: Windows initializes this value to be the same as the value specified by the caller. If the caller has not specified a value, a default value of 100 is used.

<15> Section 3.3.1.4.1: Windows initializes this value to be the same as the value specified by the caller. If the caller has not specified a value, a default value of 7,200 is used.

<16> Section 3.3.1.4.2: Client locator invokes this method to retrieve all the object UUIDs associated with the name service entry.

<17> Section 3.3.2.3: The client locator initializes a connection to Active Directory when it starts.

<18> Section 3.3.2.4.1: The client locator eliminates cycles in this lookup by keeping track of the nodes visited by the search algorithm. The client locator performs the lookup of the referred entries only as needed.

<19> Section 3.4.1.1: The Master locator only broadcasts a lookup request once it has returned the results from the Discovered Entries cache (taking into account the cache expiration age specified by the caller) and if the last broadcast lookup request for the entry was made before the cache expiration time.

<20> Section 3.4.1.1: The Master locator updates the Discovered Entries cache with the information from Broadcast Lookup responses and uses the Discovered Entries cache to return results for subsequent enumerations by the client locators.

<21> Section 3.4.1.2: This timer is initialized to 3 seconds and has a granularity of 1 msec. Each time a response is received, the current time-out period is halved and used as the new time-out period.

<22> Section 3.4.1.3: The Windows implementation initializes the LocToLoc interface only after one of the name service function is invoked locally on the machine. An example of the name service functions is RpcNsBindingExport.

<23> Section 3.4.1.5.1: The master locator ignores this value if the entry_name is null or an empty string.

<24> Section 3.4.1.5.1: The master locator uses a default value of 7,200 seconds if a value of 0 is specified and no calls have been made to update the cache expiration value on the master locator.

<25> Section 3.4.1.5.2: This parameter wraps around in 136 years.

<26> Section 6: The Microsoft implementation of the OCSP admin interface has a CLSID whose value is { 0x6d5ad135, 0x1730, 0x4f19, { 0xa4, 0xeb, 0x3f, 0x78, 0xe7, 0xc9, 0x76, 0xbb}}.