We generally talk about what's not in Server Core - now we're going to try a different approach and tell you what's included and whether something is installed by default. The following roles, role services, and features are in the Server Core installation option of Windows Server. Use this information to help figure out if the Server Core option works for your environment. Because this is a large list, consider searching for the specific role or feature you're interested in - if that search doesn't return what you're looking for, it's not included in Server Core.
The Windows Time service (W32Time) synchronizes the date and time for all computers managed by Active Directory Domain Services (AD DS). This article covers the different tools and settings used to manage the Windows Time service.
Also, on older computers that run Windows XP or earlier, the Net time /querysntp command displays the name of a Network Time Protocol (NTP) server with which a computer is configured to synchronize, but that NTP server is used only when the computer's time client is configured as NTP or AllSync. This command has since been deprecated.
The Windows Time service follows the Network Time Protocol (NTP) specification, which requires the use of UDP port 123 for all time synchronization. Whenever the computer synchronizes its clock or provides time to another computer, it happens over UDP port 123. This port is reserved by the Windows Time service as the destination port.
You can use the w32tm command to configure Windows Time service settings and diagnose computer time problems. W32tm is the preferred command-line tool for configuring, monitoring, and troubleshooting the Windows Time service. Membership in the local Administrators group is required to run this tool locally and membership in the Domain Admins group is required to run this tool remotely.
/update: Notifies the Windows Time service that the configuration has changed, causing the changes to take effect./manualpeerlist:: Sets the manual peer list to , which is a space-delimited list of DNS or IP addresses. When specifying multiple peers, this option must be enclosed in quotes./syncfromflags:: Sets what sources the NTP client should synchronize from. should be a comma-separated list of these keywords (not case sensitive):
Since Windows Server 2016, there has been improvement to the time synchronization algorithms to align with RFC specifications. Therefore, if you want to set the local time client to point to multiple peers, we recommended that you prepare three or more different time servers.
If you have only two time servers, you should specify the NtpServer UseAsFallbackOnly flag (0x2) to deprioritize one of them. For example, if you want to prioritize ntpserver.contoso.com over clock.adatum.com, run the following command:
The Windows Time service stores several configuration properties as registry entries. You can use Group Policy Objects (GPOs) in Local Group Policy Editor to configure most of this information. For example, you can use GPOs to configure a computer to be an NTPServer or NTPClient, configure the time synchronization mechanism, or configure a computer to be a reliable time source. Group Policy settings for the Windows Time service can be applied to domain controllers starting with Windows Server 2003 and future iterations.
df19127ead