The dates and times for these files are listed in Coordinated Universal Time (UTC). The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. This hotfix does not replace any other previously released hotfixes. Restart requirementYou have to restart the computer after you apply this hotfix.
How to obtain the latest service pack for Windows Server 2008 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: The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix. If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix. This hotfix might receive additional testing. Apply this hotfix only to systems that are experiencing this specific problem. However, this hotfix is intended to correct only the problem that is described in this article. Hotfix information A supported hotfix is available from Microsoft. Note This hotfix will not resolve the problem for the existing users if you use a terminal server that is running an operating system other than Windows Server 2008 or Windows Server 2008 R2.
If you install this hotfix on both the domain controller and on the terminal server, this will resolve the problem for all users. If you install this hotfix only on the domain controller, this will resolve the problem only for newly-added users. This hotfix can be installed on a Windows Server 2008-based domain controller, on a Windows Server 2008-based terminal server, Windows Server 2008 R2-based domain controller, or on a Windows Server 2008 R2-based terminal server. A hotfix is available to resolve this problem.