You use Microsoft Office Outlook 2007 on a computer that is running Windows Vista. When you try to connect to a computer that is running Microsoft Exchange Server 2003, you receive the following error message:

Task reported error 0×8004011D. The server is not available. Contact your administrator if this condition persists.

Task ‘username@example.com - Sending’ reported error (0×80040115) : ‘The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action.’

Consider the following scenario. You have a domain on which user accounts reside and another domain on which computer accounts reside. You have established a trust relationship between these domains. However, when you try to log on to a Windows Vista-based client computer across the trust, the logon process fails. Additionally, you receive an error message that contains a white “X� inside a red circle. The text of this error message resembles the following:

There is a time and/or date difference between the client and server.

Note: This issue occurs even though there is no significant time difference between the client computer and the server. This issue occurs only on Windows Vista-based client computers.

You transfer a file between a Windows Vista-based client computer and a file server that is running a previous Windows operating system. Then, the Windows Vista-based client stops responding. This problem occurs if the following conditions are true:

• Windows Vista and the file server use the Server Message Block (SMB) 1.0 protocol to transfer the file.
• The network connection between the Windows Vista-based client computer and the file server is lost when you transfer the file. For example, the network cable is unplugged when you transfer the file.

Note: When you transfer a file between a Windows Vista-based client computer and a file server that is running a previous Windows operating system, Windows Vista uses the SMB 1.0 protocol to transfer files.

When you use a Windows Vista-based computer to try to access files on a Windows Vista-based file server, you may receive an error message that resembles the following:

DriveLetter:\ is not accessible.
Insufficient system resources exist to complete the API.

• Admin Pack replacement to be available for Vista after SP1 RTM
  You’ll be able to manage Server 2008 from a Vista client next spring when SP1 is out for Vista.
  (tags: Server Administer )

You’ll be able to manage Server 2008 from a Vista client next spring when SP1 is out for Vista. Keep reading →

Consider the following scenario. A shared printer is hosted on a Microsoft Windows Server 2003-based computer. On a Windows Vista-based client computer, you use the “Point and Print” feature to connect to this printer. In this scenario, the printer does not work correctly.

In Microsoft Windows Server 2003 or in Windows Vista, you cannot set the maximum number of nested windows.

A program can create up to 50 nested windows. If an application tries to create more than 50 nested windows in a window hierarchy, the nested windows that are created after the first 50 may not work.

You cannot configure the maximum number of concurrent SMB requests that are sent to a Windows Vista-based file server.

When a Windows Vista-based computer is used as a file server, users access files by using long-term Server Message Block (SMB) requests. By default, only 10 SMB requests can be sent to the server at the same time. All other SMB requests are not answered. Therefore, the user of a client computer may receive an error message when the user tries to access files by using long-term SMB requests.

Note: Unlike typical SMB requests, a long-term SMB request remains open until it is answered by the server. A typical long-term SMB request is the NotifyChange SMB request (NT_TRANSACT_NOTIFY_CHANGE).

You install the Microsoft Windows Server 2003 Administration Tools Pack on a Windows Vista-based computer. Then, from the Windows Vista-based computer, you use the Dynamic Host Configuration Protocol (DHCP) snap-in to remotely administer a DHCP server that is running Windows Server 2003. However, in this case, you cannot find the DHCP scopes on the DHCP server.