Consider the following scenario:

• A Fibre Channel host bus adapter (HBA) is installed on a computer that is running Windows Server 2008.
• You open the Storage Explorer Microsoft Management Console (MMC) snap-in window to monitor the HBA status and the performance statistics by using a computer that is running Windows Server 2008 or a Windows Vista. This computer has Remote Server Administration Tools (RSAT) installed.

In this scenario, the Storage Explorer MMC snap-in window stops responding at the Gathering SAN information window. If you click the window, it crashes, and the following event is added to the Application log:

Log Name: Application
Source: Application Error
Date: date
Event ID: 1000
Task Category: Application Crashing Events
Level: Error
Computer: computer name
Description:
Faulting application name: mmc.exe, version: version number, time stamp: time stamp
Faulting module name: ntdll.dll, version: version number, time stamp: time stamp
Exception code: 0xc0000374

Consider the following scenario:

• You have a computer that is running Windows Server 2008 or Windows Vista.
• The event history for a scheduled task is larger than approximately 10,000 events.

In this scenario, when you view the history tab, the Task Scheduler Microsoft Management Console (MMC) snap-in stops responding.

Consider the following scenario:

• You use the Group Policy Management MMC snap-in to define and configure some policies in a domain.
• You do either of the following:
  • You export some group policies, and then you import them into the current domain or into a new one.
  • You copy some group policies, and then you paste them into the current domain or into a new one.

In this scenario, the importing or the pasting action reports a “successful” result. However, some random group policies are missing after the importing or pasting action is finsihed.

For example, you define a wired network policy in a domain, and then you export it. You then import the policy into a new domain. After the importing process finishes, the defined wired network policy is missing in the new domain.

Consider the following scenario:

• The Terminal Server Licensing Microsoft Management Console (MMC) snap-in is installed on a computer that is running Windows Server 2003 or the TS Licensing Manager MMC snap-in is installed on a computer that is running Windows Server 2008 or Windows Vista.
• You use the TS Licensing Manager MMC snap-in or the Terminal Server Licensing MMC snap-in to connect to a remote terminal licensing server.
• Only Kerberos authentication is enabled in the network environment, such as smartcard only logon.

In this scenario, you cannot connect to the remote terminal licensing server in the TS Licensing MMC snap-in or the TS Licensing Manager MMC snap-in.

This is because the TS licensing Manager MMC snap-in or TS Licensing MMC snap-in uses NT LAN Manager (NTLM) instead of the Kerberos protocol to pass authentication.

Consider the following scenario. You have a computer that is running Windows Vista or Windows Server 2008. You use the Group Policy Management snap-in of Microsoft Management Console (MMC) to browse Group Policy objects. However, when you select a Group Policy object, the Group Policy Management MMC snap-in responds slowly or even stops responding. In this scenario, you have to wait awhile before the MMC snap-in responds again.

Note: This problem usually occurs in a domain that has lots of organizational units (OUs). For example, you select a Group Policy object in a domain that has more than 100,000 OUs. In this example, it may take the Group Policy Management MMC snap-in about a half hour to resume responsiveness.

Consider the following scenario:

• You create a customized Microsoft Management Console (MMC) snap-in that is based on the Active Directory Users and Computers (Dsa.msc) snap-in.
• In the customized snap-in console, you create an Actions pane. In this Action pane, you create a new task that opens an entry by expanding multiple levels of an object structure hierarchy.
• You open the customized console, and then you click the new task.

In this scenario, you receive one of the following error messages:

Error 1

MMC cannot complete the task because an error occurred

Error 2

The specified action could not be completed

Additionally, the number of error messages that appear equals the number of levels that the new task opens. For example, if an Actions pane is selected to open domain, level1, level2, and level3. In this case, you receive the error message three times consecutively after each error message is closed.

Note: This problem does not occur if, before you open the task, the hierarchical entry is already expanded.

On a computer that is running Windows Server 2008 or Windows Vista, you try to import the .p7b format certificate by using the Certificate Import Wizard in Microsoft Management Console (MMC). However, the certificate does not import correctly. When this issue occurs, you can experience the following symptoms:

• The imported certificate does not have a private key associated with it.
• The certificate request object in the Certificate Request store remains.
• The Certificate Import Wizard completes without displaying any errors.

Consider the following scenario:

• IPv6 is disabled on a Windows Server 2008-based or Windows
  Vista-based computer.

  Note To disable IPv6, follow the steps in Microsoft Knowledge Base article
  929852.

• The Pre-Populate printer search location text policy is enabled on this computer.

In this scenario, when you right-click
<domain>, click <organization
unit>, click <container>, and
then click the Find menu, the “Active Directory Users and
Computers” MMC crashes. Additionally, the following Event is logged in the
Application log after the issue occurs:

Log Name: Application
Source:
Application Error
Event ID: 1000
Task Category: (100)
Level:
Error
Keywords: Classic
Description:
Faulting application
mmc.exe, version <version>, time stamp
<time stamp>, faulting module printui.dll,
version <version>, time stamp
<time stamp>, exception code 0xc0000005, fault
offset <address>, process id
<process ID>, application start time
<start time>.

You install Windows Vista Service Pack 1 (SP1) on a computer that is running the original version of Windows Vista. When you try to run the Group Policy Management Console (GPMC) snap-in, you receive an error message that resembles the following:

MMC could not create the snap-in.

MultiMediaCard: A flash memory memory card standard based on Toshiba’s NAND-based flash memory which about the size of a postage stamp: 24 mm x 32 mm x 1.4 mm.