It is easy to set the time and date in Windows Server Core 2012 R2, despite the lack of a graphical user interface. In this Ask the Admin, we’ll cover two different methods to set date and time.
Maintaining the correct time and date in Windows 2012 Core server can be critical for certain operations such as Kerberos authentication in Active Directory (AD) domains. On domain member servers (with either the full GUI or Server Core) the time is automatically synchronized with the domain. Assuming the primary time server in your domain is set correctly, all domain members should maintain the correct time and date in Windows Server 2012 Core.
Time is synchronized in an Active Directory forest in a top-down hierarchical manner, starting with the domain controller that holds the Primary Domain Controller (PDC) role in the forest root domain. This domain controller is often set to synchronize with an external Internet-based time server. If the PDC in the forest root domain goes offline or malfunctions, time synchronization issues in your AD forest could result in log-on failures.
On a standalone server you might need to set the date and time manually. While no configuration is necessary for automatic time synchronization in a domain, it is possible to maintain the default time synchronization settings using Group Policy. What follows are directions for setting the date and time in Windows Server Core 2012 R2, but we also have separate instructions for setting the date and time in Windows Server Core 2008 as well.
Microsoft includes a simple text-based configuration tool that system administrators can use to set up Windows Server 2012 Core without having to remember PowerShell commands. So if you forget a particular command you can always launch sconfig.cmd.
Alternately, it’s easy to set the time and date using PowerShell.
Remember that you must use numbers to specify the date, so you can’t type July 4th 2014. It is possible to specify the time like 6:53pm instead of using the 24-hour clock.
You can also just run the set-date cmdlet and press ENTER. You will then be prompted to enter the date and time in the same format as in the command shown above, but without the quotation marks.
Yes, Windows Server 2012 Core can be converted to GUI mode using PowerShell commands. Use the Install-WindowsFeature Server-Gui-Mgmt-Infra, Server-Gui-Shell command, followed by a system restart to implement the full GUI interface.
Windows Server 2012 Core can be managed remotely using Windows Remote Server Administration Tools (RSAT), PowerShell remoting, or Server Manager. Enable remote management first using the Configure-SMRemoting.exe -enable command.
Windows Server 2012 Core requires a minimum of 512MB RAM, 32GB disk space, and a 1.4GHz 64-bit processor. However, for optimal performance, 2GB RAM and 80GB disk space are recommended.
In Windows Server 2012 Core, use command-line tools like ipconfig, ping, tracert, and netsh for network troubleshooting. PowerShell cmdlets such as Test-NetConnection and Get-NetIPConfiguration are also available for advanced diagnostics.
Yes, Windows Server 2012 Core updates can be managed through PowerShell using the Get-WindowsUpdate and Install-WindowsUpdate cmdlets, or through the command line using wusa.exe for standalone updates.