With Windows Server 2008 we gained the option to install Server Core, for situations when a graphical user interface was not needed. Well with Windows Server 2016 we have Nano Server, which has just enough functionality and hence is even small than Server Core and much, much smaller than a server with a desktop.
More information on Nano Server is available via the TechNet Blog Nano Server. There is also a good article on Introducing the Nano Server Image Builder – Nano Server.
For a quick overview of Containers in Windows Server 2016 see Containers in Windows Server 2016 and note it uses Docker.
Work was done in Windows Server 2016 to improve time accuracy, see Accurate Time with Windows Server 2016 - YouTube for details.
There is a useful utility called "w32tm", which can be uses as follows:w32tm /resync - update local time with NTP server or domainw32tm /query /status - display the status of the time servicew32tm /query /source - subset of /status displaying just the sourcew32tm /tz - display timezone information
In Active Directory you might find lastLogonTimestamp, this is not always reliably updated, however, when it is, you will see numbers like 132782684735316069, which is clearly not the usual seconds since 00:00:00 on 1st January 1970 that UNIX uses as well as Java and other systems/languages. However if you execute the following:w32tm /ntte 132782684735316069
You will get 09/10/2021 16:54:33. According to the help of w32tm the /htte option will "Convert a NT system time, in (10^-7)s intervals from 0h 1-Jan 1601, into a readable format.". Another way to do the conversion is to visit Windows Filetime to UNIX Timestamp, 1 more - CyberChef, enter the number and click "Bake".