Consider the following scenario:

• In an Active Directory Domain Services (AD DS) environment, you apply the Allow user name hint Group Policy setting to the Windows Vista-based or Windows Server 2008-based client computers. This Group Policy setting displays the domain name when a user enters the user name.
• A user uses a Smart Card certificate for authentication during logon.
• The Smart Card certificate has a subject name that is presented in the fully distinguished name (also known as DN) format. Additionally, the domain component of the subject name does not match the domain in the network.

In this scenario, when the user tries to join the domain from a Windows Vista-based or Windows Server 2008-based client computer by using the Smart Card certificate, the user cannot join the domain. This problem occurs even though the name of the domain that the user tries to join is presented by the hint. In this case, the user receives the following error message:

The following error occurred attempting to join the domain Domain_Name:
The specified username is invalid.

Consider the following scenario:

• You have a computer that is running Windows Vista Service Pack 1 or Windows Server 2008.
• The computer has an integrated graphics adapter and a discrete graphics adapter.
• When you start the computer, you are using the discrete graphics adapter for the display output.
• You switch the display output from the discrete graphics adapter to the integrated graphics adapter.
• A power event occurs. For example, when your AC power cord is disconnected, the power supply system fails over to a DC power source.

In this scenario, you may receive the following Stop error:

Stop: 0×00000018 (parameter1, parameter2, parameter3, parameter4)
REFERENCE_BY_POINTER

Note: This problem occurs only on computers that have certain hardware installed.

When you right-click a shared network folder or a shared network file on a Windows Vista-based computer or on a Windows Server 2008-based computer, and then you click Always Available Offline to pin the network resource, you cannot access the shared file or folder. This problem occurs if only part of the network resource is cached. Additionally, you receive an error message that resembles the following:

Access is denied.

If you synchronize the file or the folder, the synchronization operation is successful. However, you still cannot access the file or the folder.

When you try to install updates by using the Windows Update Web site or the Microsoft Update Web site, you may receive the following error message:

0×80070422

When you try to install updates by using the Windows Update or Microsoft Update Web site, you may receive the following error message:

0×8024002D

When you try to install updates from the Windows Update site or from Microsoft Update Web site, you may receive the following error code:

0×80246007

When you installed the Autodesk Data Management Server (ADMS) on the Microsoft Vista™ operating system, an error occurred during the pre-checks on the TestASPNetStatic.txt file.

Applies to:

• AutoCAD® 2008
• AutoCAD® Architecture 2008
• AutoCAD® Civil 3D® 2008
• AutoCAD® Land Desktop 2008
• AutoCAD® Map 3D 2008
• AutoCAD® MEP 2008
• Autodesk® Inventor™ Professional 2008
• Autodesk® Inventor™ Suite 2008
• Autodesk® Productstream™ 2009
• Autodesk® Productstream™ 2008
• Autodesk® Productstream™ Replicator 2008
• Autodesk® Vault 2009
• Autodesk® Vault 2008
• Autodesk® VIZ 2008

For more information on this issue, including potential causes, workarounds, and resolutions, see: AutoDesk Knowledge Base Article TS1077186.

A computer that is running Windows Server 2003, Windows Vista, or Windows Server 2008 may restart unexpectedly. Additionally, you may receive the following Stop error message:

Stop 0×00000050 (parameter1, 00000000, parameter3, 00000000)
PAGE_FAULT_IN_NONPAGED_AREA

Notes

• The parameters in this Stop error message vary, depending on the configuration of the computer.
• Not all “0×00000050″ Stop error messages are caused by this problem.

This problem may occur if the computer uses some OpenType fonts that are provided by printer drivers.

Consider the following scenario:

• You have data that is stored in one of the new Microsoft SQL Server 2008 collations.
• You have an application on a computer that is running one of the following operating systems:
  • Windows XP
  • Windows Server 2003
  • Windows Vista
  • Windows Server 2008

In this scenario, you may experience one of the following symptoms:

Symptom 1

You receive an error message when the following conditions are true:

• The application uses the Open Database Connectivity (ODBC) driver or the SQL OLE DB provider to request a result set.
• The result set contains a column that uses one of the new collations.
• The column is defined as the SQLTEXT type, the SQLBIGCHAR type, or the SQLBIGVARCHAR type.

If the application uses the ODBC driver, you receive the following error message:

Msg 40242

Unable to resolve column level collations system

If the application uses the SQL OLE DB provider, you receive the following error message:

Msg 40234

Unicode conversion failed. Code page of server not on client

Symptom 2

The connection to the new SQL Server 2008 collations is closed, and an error message is logged in the SQL Server Error log file when the following conditions are true:

• The application uses the Open Database Connectivity (ODBC) driver or the SQL OLE DB provider to request a result set.
• The result set contains data of the SQL_VARIANT data type.
• The data is stored in one of the new collations, and the SQL_VARIANT data contains the SQLTEXT type, the SQLBIGCHAR type, or the SQLBIGVARCHAR type.

If the application uses the ODBC driver, you receive the following error message:

Msg 40242

Unable to resolve column level collations system

If the application uses the SQL OLE DB provider, you receive the following error message:

Msg 40234

Unicode conversion failed. Code page of server not on client

Symptom 3

The client application requests an output parameter. If the output parameter uses one of the new collations, the parameter is defined as the SQLBIGCHAR type, the SQLBIGVARCHAR type, or the SQLTEXT type, and an error is returned to the client application.

If the application uses the ODBC driver, you receive the following error message:

Msg 40242

Unable to resolve column level collations system

If the application uses the SQL OLE DB provider, you receive the following error message:

Msg 40234

Unicode conversion failed. Code page of server not on client

Symptom 4

The connection to the new SQL Server 2008 collations is closed, and an error message is logged in the SQL Server Error log file when the following conditions are true:

• The application requests an output parameter.
• The data type of the output parameter is SQL_VARIANT.
• The output parameter uses one of the new collations, and the SQL_VARIANT data contains the SQLCHAR type or the SQLVARCHAR type.

If the application uses the ODBC driver, you receive the following error message:

Msg 40242

Unable to resolve column level collations system

If the application uses the SQL OLE DB provider, you receive the following error message:

Msg 40234

Unicode conversion failed. Code page of server not on client

Symptom 5

The client application connects to a database, and the default collation that the database uses is one of the new collations. In this case, an error is returned to the client application.

If the application uses the ODBC driver, you receive the following error message:

Msg 40205

Unicode conversion failed

If the application uses the SQL OLE DB provider, you receive the following error message:

Msg 40234

Unicode conversion failed. Code page of server not on client

Symptom 6

When you run the USE statement to switch to a database that uses one of the new collations, you receive the error messages that are listed for “Symptom 5.”

You are running a Windows Server 2008-based or a Windows Vista-based computer that uses the non-uniform memory access (NUMA) architecture. When you try to start a Hyper-V virtual machine, the operation may fail because of a memory allocation issue. Additionally, you may receive the following error message:

An error occurred while attempting to change the state of virtual machine VMNAME.
‘VMNAME’ failed to initialize.
Unable to allocate 1024* MB of RAM: Insufficient system resources exist to complete the requested service. (0×800705AA)
*number will vary based on the amount of RAM assigned to the VM

This issue occurs even when there is sufficient memory available.