You cannot use the IPv6 protocol to connect to the remote VDS on a Windows Vista Service Pack 1-based computer from a Windows Server 2008-based computer

Symptoms
Consider the following scenario:You try to connect to the remote Virtual Disk Service (VDS)on a Windows VistaService Pack 1 (SP1)-based computerfrom a Windows Server 2008-based computer.Both computers are located on a domain that is managed by a Windows Server 2003 R2-based domain controller.You use an Internet Protocol version 6 (IPv6) address to connect.You use the Windows Server 2008 Disk Management UI to connect to VDS.You enable a single exception in the firewall settings of both the Windows Vista SP1-based computer and the Windows Server 2008-based computer. The exception is as follows:
Remote Volume Management Exception In this scenario, the connection fails. Additionally, you receive the following error message in the Disk Management console:

Disk Management could not start Virtual Disk service (VDS) on 2001:4898:1000:412E:D7D1:DF52:9F83. This can happen if the remote computer does not support VDS, or if a connection cannot be established because it was blocked by Windows Firewall.
For additional information about diagnosing and correcting this problem, see Troubleshooting Disk Management in Disk Management Help.Note You can connect to the remote VDS by using a NetBIOS name, a DNS name, or an IPv4 address.
Resolution
This issue is specific to a domain that is managed by a Windows Server 2003 R2-based domain controller. If you have a Windows Vista SP1 computer and a Windows Server 2008 computer in a domain that is managed by aWindows Server 2008-based domain controller, you do not receive the error message that is mentioned in the “Symptoms” section.

When you try to install a Web Services for Devices (WSD) printer on a Windows Server 2008-based computer, the operation fails

Symptoms
When you try to install a Web Services for Devices (WSD) printeron a Windows Server 2008-based computer, the operation fails. You do not receive an error message.
Resolution
This problem occurs if the Print Services role has not been added onthe computer.By default, the Print Services role is not added in Windows Server 2008. Additionally, the WSD print proxy is not installed.When you add the Print Services role, the WSD print proxy is also installed.

The computer stops responding when you access some shared files from a computer that is running Windows Server 2008 or Windows Vista

Symptoms
When you access some shared files from a computer that is running Windows Server 2008 or Windows Vista, the computer stops responding under a heavy stress situation. Additionally, the computer does not recover until you force the computer to restart.
Resolution
This issue occurs because of a deadlock between the memory manager and the Redirected Drive Buffering SubSystem (Rdbss.sys) driver.

SQL Server Connection Fails When RC4 Encryption Is Disabled

Symptoms
You may disable various Schannel encryption algorithms such as RC4 to enforce FIPS 140-1 compliant encryption on a computer that is running Microsoft Windows. If you have a server that is running SQL Server on this computer, and if you enable protocol encryption, you cannot connect to the server that is running SQL Server from a client computer. When you try to connect, you receive the following error message on the client computer:

Communication link failure.
Resolution
A supported fix is now available from Microsoft, but it is only intended to correct the problem described in this article. Only apply it to systems that are experiencing this specific problem. This fix may receive additional testing to further ensure product quality. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next SQL Server 2000 and Microsoft Data Access Components (MDAC) service pack that contains this hotfix.
To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:
http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS(http://support.microsoft.com/default.aspx?scid=fh;en-us;cntactms)Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
The English version of this fix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel. MDAC 2.7 and SQL Server 2000 Service Pack 2 (SP2)

DateTimeVersionSizeFile name————————————————————–03-Jul-200216:022000.81.9001.961,440Dbnetlib.dll02-Jul-200217:542000.80.653.082,492Ssnetlib.dll
MDAC 2.7 SP1 and SQL Server 2000 Service Pack 3 (SP3)

DateTimeVersionSizeFile name————————————————————–21-Feb-200316:022000.81.903161,440Dbnetlib.dll

PRB: Error message: Cannot generate SSPI context

Symptoms
When you try to connect to a computer running SQL Server 7.0, you may receive an error message if all the following conditions are true:Your computer is running Windows 2000.You are using Windows Authentication with domain user credentialsThere is no active network connection from the computer running SQL Server to the domain. You may receive the following error message:

Cannot generate SSPI context
Resolution
This problem occurs because the computer runningSQL Server cannot connect to a domain controller to authenticate your user credentials.

Offline files that are ghost items on a computer that is running Windows Vista or Windows Server 2008 cannot be synchronized with the corresponding files on a file server

Symptoms
On a computer that is running Windows Vista orWindows Server 2008, you have some offline files that are ghost items. In this situation, you cannot synchronize the offline files on this computer with the corresponding files on a file server. Additionally, you cannot access or delete these offline files.
Note Ghosting is a new feature for offline files in Windows Vista and in Windows Server 2008. Sometimes, a synchronization process may stop responding because ofnetwork issues that occur when the contents of a file ordirectory are only partly cached. In this case, client-side caching (CSC) creates ghost items on the client computer. Ghost items cannot be deleted. Additionally, the ghosting feature cannot be disabled.
Resolution
Hotfix information A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
If the hotfix is available for download, there is a “Hotfix download available” section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=support(http://support.microsoft.com/contactus/?ws=support)Note The “Hotfix download available” form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.PrerequisitesTo apply this hotfix, the computer must be running one of the following: Windows Vista Windows Vista SP1Windows Server 2008Restart requirementYou mustrestart the computer after you apply this hotfix.Hotfix replacement information This hotfix does not replace any other previously released hotfixes. Registry information To use this hotfix, you do not have to make any changes to the registry.File information The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.Windows Vista and Windows Server 2008 file information notesThe files that apply to a specific product, milestone (RTM, SPn) can be identified by examining the file version numbers as shown in the following table:
Collapse this tableExpand this table
VersionProductMilestoneService branch 6.0.6000.20xxx Windows RTM LDR 6.0.6001.22xxx Windows Vista SP1 and Windows Server 2008 SP1 SP1 LDR Service Pack 1 is integrated into Windows Server 2008. Therefore, RTM milestone files apply only to Windows Vista. RTM milestone files have a 6.0.0000.xxxxxx version number. The MANIFEST files (.manifest) and MUM files (.mum) that are installed for each environment are listed separately. MUM and MANIFEST files, and the associated security catalog (.cat) files, are critical to maintaining the state of the updated component. The security catalog files (attributes not listed) are signed with a Microsoft digital signature. For all supported x86-based versions of Windows Server 2008 and of Windows Vista
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformCscobj.dll6.0.6000.20793131,58415-Mar-200803:30x86Offlinefileswmiprovider.mofNot Applicable42,87713-Dec-200720:11Not ApplicableOfflinefileswmiprovider_uninstall.mofNot Applicable42,87713-Dec-200720:11Not ApplicableCscsvc.dll6.0.6000.20793489,47215-Mar-200803:30x86Microsoft-windows-offlinefiles.mofNot Applicable1,93113-Dec-200720:11Not ApplicableCscsvc.dll6.0.6001.22137487,42415-Mar-200803:32x86Microsoft-windows-offlinefiles.mofNot Applicable1,93118-Dec-200721:26Not ApplicableFor all supported x64-based versions of Windows Server 2008 and of Windows Vista
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformCscobj.dll6.0.6000.20793216,57615-Mar-200803:46x64Offlinefileswmiprovider.mofNot Applicable42,87714-Dec-200721:49Not ApplicableOfflinefileswmiprovider_uninstall.mofNot Applicable42,87714-Dec-200721:49Not ApplicableCscsvc.dll6.0.6000.20793603,13615-Mar-200803:46x64Microsoft-windows-offlinefiles.mofNot Applicable1,93114-Dec-200721:48Not ApplicableCscsvc.dll6.0.6001.22137603,64815-Mar-200803:58x64Microsoft-windows-offlinefiles.mofNot Applicable1,93118-Dec-200721:26Not ApplicableCscobj.dll6.0.6000.20793131,58415-Mar-200803:30x86Offlinefileswmiprovider.mofNot Applicable42,87713-Dec-200720:11Not ApplicableOfflinefileswmiprovider_uninstall.mofNot Applicable42,87713-Dec-200720:11Not ApplicableFor all supported Itanium-based versions of Windows Server 2008
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformCscsvc.dll6.0.6001.221371,226,75215-Mar-200803:44IA-64Microsoft-windows-offlinefiles.mofNot Applicable1,93118-Dec-200721:26Not Applicable