Assume that you monitor the system performance of a remote computer from a computer that is running Windows Vista or Windows Server 2008. However, if you try to capture the performance data by using the comma-separated values (CSV) format, some performance data in the log is missing.

Notes:

• This issue occurs when you monitor the V2 performance counters.
• This issue does not occur if you save the performance data by using a binary file format.
• When this issue occurs, the content of the performance data log resembles the following:
  “[Date] [Time]” “2″ “1″ “1″
  “[Date] [Time]” “2″ “1″ “1″
  “[Date] [Time]” ” ” ” ” ” ”
  “[Date] [Time]” “2″ “1″ “1″
  “[Date] [Time]” ” ” ” ” ” ”
  “[Date] [Time]” “2″ “1″ “1″
  “[Date] [Time]” ” ” ” ” ” ”
  “[Date] [Time]” “2″ “1″ “1″
  “[Date] [Time]” ” ” ” ” ” ”
  “[Date] [Time]” “2″ “1″ “1″

Consider the following scenario:

• You have a computer that is running Windows Vista Service Pack 2 (SP2) or Windows Server 2008 SP2. The computer is a member of a domain.
• You configure users to apply multiple Group Policy objects (GPOs) when they log on to the domain from the computer. For example, domain level policies, organization unit level policies or local computer policies.
• These GPOs contain the following Group Policy, each with a different setting:
  

  User Configuration\Administrative Templates\System\User Profiles\Limit profile size

In this scenario, the Profile Quota Manager tool (Proquota.exe) may receive incorrect profile quota settings. This behavior causes data loss if the incorrect quota size that is actually applied is too small.

Consider the following scenario:

• You request a certificate from a computer that is running Windows Server 2008 or Windows Vista.
• You build multiple certificate chains for the certificate.
• One certificate chain has a revoked certificate.
  Note: The other certificate chains are good.
• You try to verify the certificate.

In this scenario, certificate validation fails and you receive the following error message:

0×80092013, CRYPT_E_REVOCATION_OFFLINE, The revocation function was unable to check revocation because the revocation server was offline

On a client computer that is running Windows Vista or Windows Server 2008, you try to generate a Resultant Set of Policy (RSoP) report by using the gpresult /h GPReport.html command. The central store for Group Policy stores Windows Server 2008 R2-based ADMX files. In this situation, you receive the following error message:

Encountered an error while parsing. Expected one of the following possible element(s), text, decimalTextBox, textBox, checkBox, comboBox, dropdownList, listBox, but found multiTextBox instead. File\\Path\File_Name line Line, column Column Encountered an unknown error while parsing (error = 0x87400001): -2025848831 (0x87400001) File \\Path\File_Name line Line, column Column

Assume that you try to use the Logman command prompt utility (Logman.exe) to create and manage event tracing sessions and performance logs on a computer that is running one of the following operating systems:

• Windows Vista
• Windows Server 2008
• Windows 7
• Windows Server 2008 R2

However, an access violation occurs when Logman.exe starts.

Consider the following scenario:

• You run a Windows Filtering Platform (WFP)-based network filtering application on a computer that is running Windows Vista or Windows Server 2008.
• A WPF callout driver is used to pend packet processing by calling the FwpsPendOperation0() API.
• This call returns a completion context.

In this scenario, the Remote Address field in the completion context is zeroed out. Additionally, the computer may crash, depending on how the callout driver handles the Remote Address field.

Note: This issue may occur if a reauthentication request is triggered by calling the FwpsCompleteOperation0() API.

Consider the following scenario:

• Multiple network adapters are installed on a computer.
• One network adapter is configured to use an Automatic Private Internet Protocol Addressing (APIPA) IP address.
• Another network adapter is configured to use a non-APIPA IP address.
• The interface metric is smaller on the second network adapter than the metric that is configured on the first network adapter.
• An application calls the getaddrinfo function on the computer.

In this scenario, the first-returned IP address is the APIPA IP address.

Notes:

• This issue prevents network applications that use only the first-returned local IP address by calling the getaddrinfo function (such as a Java-based application that calls the GetLocalHost Java API) from connecting to network resources.
• This issue occurs on a computer that is running one of the following operating systems:
  • Windows Vista Service Pack 2 (SP2)
  • Windows Server 2008 Service Pack 2 (SP2)
  • Windows 7
  • Windows 7 Service Pack 1 (SP1)
  • Windows Server 2008 R2
  • Windows Server 2008 R2 Service Pack 1 (SP1)

Assume that an application or a service loads and then unloads the Netshell.dll module frequently on a computer that is running Windows Vista or Windows Server 2008. For example, an application frequently queries the Win32_NetworkAdapter WMI namespace. In this situation, the memory usage of the application or the service keeps increasing. With time, the application or the service stops working if available memory resources are exhausted.

Note: The Netshell.dll module can be loaded directly or indirectly by an application or a service.

When you change the network adapter teaming configuration on a computer that is running Windows Vista or Windows Server 2008, you randomly receive various Stop error messages that resemble the following:

STOP: 0x000000D1 (parameter1, parameter2, parameter3, parameter4)

Note: This Stop error describes a DRIVER_IRQL_NOT_LESS_OR_EQUAL issue.

STOP 0×00000050 (parameter1, 0, parameter3, parameter4)

Note: This Stop error describes a PAGE_FAULT_IN_NONPAGED_AREA issue.

STOP: 0x0000000A (parameter1, parameter2, parameter3, parameter4)

Note: This Stop error describes an IRQL_NOT_LESS_OR_EQUAL issue.

Notes:

• The parameters in these Stop error messages vary, depending on the configuration of the computer.
• Not all “0x000000D1″, “0×00000050″, and “0x0000000A” Stop errors are caused by this issue.
• You may also experience other Stop errors when this issue occurs.

When user is trying to monitor network using SNMP agent (SNMP Service) , it can not collect NIC name correctly.
It is using ifAlias (.1.3.6.1.2.1.31.1.1.1.18) If NIC name contains multi byte Characters, then, it fails to get NIC name using ifAlias