A list of the Simple Network Time Protocol (SNTP) time servers that are available on the Internet

Symptoms
This article describes the Simple Network Time Protocol (SNTP) time servers that are available on the Internet.
Resolution
There are two levels, or tiers, of Network Time Protocol (NTP) time servers that are available on the Internet. The NTP is defined in Request for Comments (RFC) 1305.
The first-level time servers are primarily intended to act as source time servers for second-level time servers. The first-level time servers may also be capable of providing mission-critical time services. Some first-level time servers may have a restricted access policy.
Second-level time servers are intended for general SNTP time service needs. Second-level time servers usually enable public access. It is recommended that you use second-level time servers for normal SNTP time server configuration because they are usually located on a closer network that can produce faster updates.
It is recommended that you research any time server selection to ensure that it can meet your specific time server requirements.
Time server listNote You may receive an error message that resembles the following:

There is a problem with this website’s security certificate.
The security certificate presented by this website was not issued by a trusted certificate authority.
Security certificate problems may indicate an attempt to fool you or intercept any data you send to the server.
We recommend that you close this webpage and do not continue to this website. If you receive this error message when you click any of the following links,continue to the Web site.For the list of stratum one time servers, visit the following Web site:
https://support.ntp.org/bin/view/Servers/StratumOneTimeServers(https://support.ntp.org/bin/view/Servers/StratumOneTimeServers)For the list of stratum two time servers, visit the following Web site:
https://support.ntp.org/bin/view/Servers/StratumTwoTimeServers(https://support.ntp.org/bin/view/Servers/StratumTwoTimeServers)For the list of NIST Internet Time Servers, visit the following Web site:
http://tf.nist.gov/tf-cgi/servers.cgi(http://tf.nist.gov/tf-cgi/servers.cgi)For the list of NTP Pool Servers, visit one of the following Web sites:
https://support.ntp.org/bin/view/Servers/NTPPoolServers(https://support.ntp.org/bin/view/Servers/NTPPoolServers)
http://www.pool.ntp.org(http://www.pool.ntp.org)Microsoft does not maintain the list of time servers or recommend one time server over the other one. These links are for your reference and research to select the time server(s) appropriate for your configuration.Microsoft does recommend that workgroup computers sync from the Microsoft NTP server (time.windows.com). If another time source is desired, we recommend that you use one of the Stratum 2 Time Servers. To find the Stratum 2 Time Servers that are available, visit the following Web site:
https://support.ntp.org/bin/view/Servers/StratumTwoTimeServers(https://support.ntp.org/bin/view/Servers/StratumTwoTimeServers)Note Please read the “Rules Of Engagement” before using the Stratum Two Time Servers list. To read the “Rules of Engagement,” visit the following Web site:
https://support.ntp.org/bin/view/Servers/RulesOfEngagement(https://support.ntp.org/bin/view/Servers/RulesOfEngagement) Domain joined member computers and application servers should be configured to synchronize time by using the domain hierarchy as described in the Domain Hierarchy-Based Synchronization topic at the following Microsoft TechNet Web site:
http://technet.microsoft.com/en-us/library/cc773013(WS.10).aspx(http://technet.microsoft.com/en-us/library/cc773013(WS.10).aspx)To synchronize non-domain-joined (workgroup) workstations or servers, visit the following Microsoft TechNet Web site:
http://technet.microsoft.com/en-us/library/cc757721(WS.10).aspx(http://technet.microsoft.com/en-us/library/cc757721(WS.10).aspx)

You receive an error message when you use SQL Server 2008 Reporting Services: “HTTP 401.1 – Unauthorized: Logon Failed”

Symptoms
Consider the following scenario that occurs when you use Microsoft SQL Server 2008 Reporting Services:You try to access Report Manager or Report Server by using a URL that resembles one of the following URLs:
http://name/reports
https://name/reportsNote The name placeholder is not the name of the computer on which Report Server and Report Manager are deployed.However, the DNS Client service, the computer’s hosts header files, or the computer’s Lmhosts files that are located in the C:\WINDOWS\system32\drivers\etc folder are configured to send requests to name back to the report server computer.You try to access Report Server directly by using one of the following URLs. When you do this, you experience no problems. Additionally, you can browse the Report Server namespace and view all reports by using the following URLs:
http://name/reportserver
https://name/reportserverThe ReportServerUrl element is specified in the Rsreportserver.config file and is set to resemble one of the following URLs:
http://name/reportserver
https://name/reportserverYou try toaccess Report Manager by using one of the following URLs:
http://name/reports
https://name/reportsIn this scenario, you receive what resembles the Report Manager user interface. However, where you expect to see a list of reports, you receive the following error message:

HTTP 401.1 – Unauthorized: Logon FailedNote If you use SharePoint Integrated mode, you receive the error message on the SharePoint Webpages. The symptoms in this scenario are most likely to occur when one of the following conditions is true: Reporting Services is deployed in a scale-out deployment.Reporting Services is accessed by using a user-friendly name that does not match the computer name.
Resolution
This problem occurs because Windows includes a loopback check security feature that helps prevent reflection attacks on your computer. Therefore, authentication fails if the FQDN or the custom host header that you use does not match the local computer name.

You cannot install the Terminal Services CAL pack on Windows Server 2003-based or Windows 2000 Server-based computers

Symptoms
When you try to install the Terminal Services client access license(CAL) pack on a Windows Server 2003-basedor a Microsoft Windows 2000 Server-based server, you may receive the following error message:

Licensing Wizard was unable to install the client license key pack. Please verify your entry and try this operation again. Message Number 0x13A7.Note The message number may also be 0x13A4 or 0xFA1.
The following event ID error message may be logged in the application event log:
Event ID: 41
Source: TermServLicensing
Description: Can’t initialize policy module because of error ‘Missing Policy module registry entry for product Microsoft Corporation, company 004′
Resolution
This problem may occur for one or more of the following reasons:Cause 1: You are trying to install a Windows Server 2008 CAL pack on a Windows Server 2003-based license server.Cause 2: You are trying to install a Windows Server 2003 CAL pack on a Windows 2000-based license server.Cause 3: The Terminal Services Licensing component is corrupted or missing.Cause 4: The Terminal Services registry key has incorrect settings.

When you use a file handle for FileStream access in a SQL Server 2008 transaction, the transaction may randomly fail to commit in Windows Vista or in Windows Server 2008

Symptoms
On a computer that is running Windows Vista or Windows Server 2008, when you use the OpenSqlFilestream API or the .NET SqlFilestream class to obtain a file handle for FileStream access in a transaction in Microsoft SQL Server 2008, the transaction may randomly fail to commit. When this problem occurs, one of the following errors is logged in the SQL Server Errorlog file:3910 (Transaction context in use by another session)3981 (The transaction operation cannot be performed because there are pending requests working on this transaction)3922 (Cannot enlist in the transaction because the transaction does not exist)This problem occurs when the client computer is running an earlier Windows operating system. For example, the client computer is running Windows XP, Windows XP Professional x64 Edition, or Windows Server 2003.
The cause of this problem is not related to the FILESTREAM feature in SQL Server 2008. However, you typically encounter this problem when you use the FILESTREAM feature in SQL Server 2008.
Resolution
This problem occurs because of an error in the Server service. The Server service incorrectly delays the request of closing file handles. Therefore, the transactions cannot commit.

Two warning messages are logged for the Resultant Set of Policy (RSoP) data when you run the “gpupdate /force” command on a computer that is running Windows Server 2008 Server Core

Symptoms
Consider the following scenario:You add a computer that is running Windows Server 2008 Server Core to a Windows Server 2008 domain.You enable one or more Group Policy preferences in a Group Policy object (GPO). You deploy this GPO to the computer.At an elevated command prompt on the computer, you run the gpupdate /force command.In this scenario, the Group Policy preferences are applied successfully. However, the following warning message is logged in the Application log:
Log Name: Application
Source: Group Policy Folders
Date: Date
Event ID: 4099
Task Category: (2)
Level: Warning
Keywords: Classic
User: SYSTEM
Computer: Computer Name
Description:
The client-side extension could not log RSoP data because it failed with error code ”0x8004401e This is not a valid MOF file”.Additionally, the following warning message is logged in the System log:
Log Name: System
Source: Microsoft-Windows-GroupPolicy
Date: Date
Event ID: 1091
Task Category: None
Level: Warning
Keywords:
User: SYSTEM
Computer: Computer Name
Description:
Windows could not record the Resultant Set of Policy (RSoP) information for the Group Policy extension Group Policy Folders. Group Policy settings successfully applied to the computer or user; however, management tools may not report accurately.These two event logs indicate that the following files are missing on the computer:%SYSTEMROOT%\system32\wbem\polprocl.mof%SYSTEMROOT%\system32\wbem\en-US\polprocl.mflNote This problem occurs inWindows Server 2008 Service Pack 2 (SP2) Server Core and Windows Server 2008 Server Core.
Resolution
This problem occurs because the Windows Server 2008 Server Core Setup program does not copy the two missing files to the computer during the installation process.

Some font files that are marked as system-protected cannot be updated in Windows Vista or in Windows Server 2008

Symptoms
You have a computer that is running Windows Vista or Windows Server 2008. When you install an application on this computer, some font files that are marked as system- protected cannot be updated.
Additionally, when you try to manually delete or update the font files, the operation fails.
Resolution
This issue is fixed in an update for Windows Vista and for Windows Server 2008. This update is intended to remove the protection of some font files that are not required for the Windows user interface.
Update informationHow to obtain this updateThis update is available from the Microsoft Update Web site:
http://update.microsoft.com(http://update.microsoft.com)The following files are available for download from the MicrosoftDownload Center:

Collapse this tableExpand this table
Operating systemUpdateAll supported x86-based versions of Windows Vista
Collapse this imageExpand this image
Download the update package now.(http://www.microsoft.com/downloads/details.aspx?FamilyId=cd779de9-97e4-40ff-8990-be4c24c61287)All supported x86-based versions of Windows Server 2008
Collapse this imageExpand this image
Download the update package now.(http://www.microsoft.com/downloads/details.aspx?FamilyId=b3b7d700-910f-4879-9e96-0d8050f5f9c6)All supported x64-based versions of Windows Vista
Collapse this imageExpand this image
Download the update package now.(http://www.microsoft.com/downloads/details.aspx?FamilyId=c16e703f-5a4a-4e8a-8998-87eda1efc302)All supported x64-based versions of Windows Server 2008
Collapse this imageExpand this image
Download the update package now.(http://www.microsoft.com/downloads/details.aspx?FamilyId=5ca78c7b-bfba-4101-ae46-951ca60c7aa4)All supported IA-64-based versions of Windows Server 2008
Collapse this imageExpand this image
Download the update package now.(http://www.microsoft.com/downloads/details.aspx?FamilyId=a55db39a-69ce-4b2b-8db9-e5c71c1c1bfa)For more information about how to download Microsoft support files, click the following article number to view the article in the Microsoft Knowledge Base:
119591?(http://support.microsoft.com/kb/119591/) How to obtain Microsoft support files from online servicesMicrosoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.PrerequisitesTo apply this update, your computer must be running one of the following operating systems:Windows Vista Service Pack 1Windows Vista Service Pack 2Windows Server 2008Windows Server 2008 Service Pack 2For more information about how to obtain a Windows Vista service pack, click the following article number to view the article in the Microsoft Knowledge Base:
935791?(http://support.microsoft.com/kb/935791/) How to obtain the latest Windows Vista service packFor more information about how to obtain a Windows Server 2008 service pack, click the following article number to view the article in the Microsoft Knowledge Base:
968849?(http://support.microsoft.com/kb/968849/) How to obtain the latest service pack for Windows Server 2008Restart requirementYou must restart the computer after you apply this update.Update replacement informationThis update does not replace a previously released update.File informationThe global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.Windows Vista and Windows Server 2008 file information notesGDR service branches contain only those fixes that are widely released to address widespread, extremely important issues. LDR service branches contain hotfixes in addition to widely released fixes.For all supported versions of Windows Server 2008 and of Windows Vista
Collapse this tableExpand this table
File nameVersionFile sizeAhronbd.ttf5.0050,332Andlso.ttf5.00117,960Angsa.ttf5.00109,808Angsab.ttf5.00106,220Angsai.ttf5.00103,444Angsaz.ttf5.00105,636Angsau.ttf5.00109,784Angsaub.ttf5.00106,236Angsaui.ttf5.00103,408Angsauz.ttf5.00105,592Arabtype.ttf5.01621,580Arial.ttf5.06766,656Arialbd.ttf5.06744,556Arialbi.ttf5.06551,824Ariali.ttf5.06546,536Ariblk.ttf5.00119,492Browa.ttf5.0089,656Browab.ttf5.0075,424Browai.ttf5.00100,224Browaz.ttf5.0089,380Browau.ttf5.0089,616Browaub.ttf5.0075,416Browaui.ttf5.00100,216Browauz.ttf5.0089,376Calibri.ttf5.62352,736Calibrib.ttf5.62351,544Calibrii.ttf5.62362,524Calibriz.ttf5.62365,864Cambria.ttc5.961,090,432Cambriab.ttf5.96328,500Cambriai.ttf5.96336,764Cambriaz.ttf5.96325,976Candara.ttf5.61161,632Candarab.ttf5.61164,892Candarai.ttf5.61167,752Candaraz.ttf5.61165,916Comic.ttf5.00132,832Comicbd.ttf5.00117,456Consola.ttf5.2298,504Consolab.ttf5.22100,420Consolai.ttf5.22104,128Consolaz.ttf5.22110,252Constan.ttf5.90313,860Constanb.ttf5.90317,704Constani.ttf5.90305,980Constanz.ttf5.90313,024Corbel.ttf5.61205,008Corbelb.ttf5.61210,780Corbeli.ttf5.61209,844Corbelz.ttf5.61217,300Cordia.ttf5.00108,572Cordiab.ttf5.0095,892Cordiai.ttf5.00100,104Cordiaz.ttf5.0094,816Cordiau.ttf5.00108,544Cordiaub.ttf5.0095,888Cordiaui.ttf5.00100,100Cordiauz.ttf5.0094,812Cour.ttf5.11690,208Courbd.ttf5.11697,096Courbi.ttf5.11503,460Couri.ttf5.11593,740David.ttf5.0256,600Davidbd.ttf5.0255,652Framd.ttf5.01139,332Framdit.ttf5.01152,104Frank.ttf5.0263,840Georgia.ttf5.00157,080Georgiab.ttf5.00145,940Georgiai.ttf5.00162,380Georgiaz.ttf5.00164,332Gisha.ttf5.0072,932Gishabd.ttf5.0074,056Impact.ttf5.00135,848Kaiu.ttf5.005,178,844L_10646.ttf5.00325,400Leelawad.ttf5.0097,752Leelawdb.ttf5.0097,420Lvnm.ttf5.0056,964Lvnmbd.ttf5.0054,940Moolbor.ttf5.00342,840Mriam.ttf5.0252,128Mriamc.ttf5.0257,064Msuighur.ttf5.00203,360Nrkis.ttf5.0256,944Pala.ttf5.00472,664Palab.ttf5.00420,052Palabi.ttf5.00336,476Palai.ttf5.00413,824Rod.ttf5.0261,560Simfang.ttf5.0110,576,012Simhei.ttf5.019,751,960Simkai.ttf5.0111,785,184Simpbdo.ttf5.0091,968Simpfxo.ttf5.0090,904Simpo.ttf5.0090,692Symbol.ttf5.0070,128Times.ttf5.01828,152Timesbd.ttf5.01835,868Timesbi.ttf5.01610,820Timesi.ttf5.01651,500Tradbdo.ttf5.00127,456Trado.ttf5.00126,124Trebuc.ttf5.00136,172Trebucbd.ttf5.00126,376Trebucbi.ttf5.00133,716Trebucit.ttf5.00141,836Upcdb.ttf5.0065,156Upcdbi.ttf5.0068,784Upcdi.ttf5.0169,956Upcdl.ttf5.0169,448Upceb.ttf5.0174,076Upcebi.ttf5.0176,736Upcei.ttf5.0175,360Upcel.ttf5.0172,360Upcfb.ttf5.0164,056Upcfbi.ttf5.0167,216Upcfi.ttf5.0167,424Upcfl.ttf5.0164,900Upcib.ttf5.0171,080Upcibi.ttf5.0173,612Upcii.ttf5.0173,632Upcil.ttf5.0171,068Upcjb.ttf5.0174,428Upcjbi.ttf5.0177,692Upcji.ttf5.0176,456Upcjl.ttf5.0173,568Upckb.ttf5.0164,648Upckbi.ttf5.0168,872Upcki.ttf5.0168,140Upckl.ttf5.0164,316Upclb.ttf5.0154,260Upclbi.ttf5.0157,100Upcli.ttf5.0156,752Upcll.ttf5.0154,264Verdana.ttf5.02185,704Verdanab.ttf5.02152,872Verdanai.ttf5.02174,088Verdanaz.ttf5.00172,600Webdings.ttf5.00121,664Wingding.ttf5.0083,740