IMPORTANT ANNOUNCEMENT FOR OUR READERS!
AskPFEPlat is in the process of a transformation to the new Core Infrastructure and Security TechCommunity, and will be moving by the end of March 2019 to our new home at https://aka.ms/CISTechComm (hosted at https://techcommunity.microsoft.com). Please bear with us while we are still under construction!
We will continue bringing you the same great content, from the same great contributors, on our new platform. Until then, you can access our new content on either https://aka.ms/askpfeplat as you do today, or at our new site https://aka.ms/CISTechComm. Please feel free to update your bookmarks accordingly!
Why are we doing this? Simple really; we are looking to expand our team internally in order to provide you even more great content, as well as take on a more proactive role in the future with our readers (more to come on that later)! Since our team encompasses many more roles than Premier Field Engineers these days, we felt it was also time we reflected that initial expansion.
If you have never visited the TechCommunity site, it can be found at https://techcommunity.microsoft.com. On the TechCommunity site, you will find numerous technical communities across many topics, which include discussion areas, along with blog content.
NOTE: In addition to the AskPFEPlat-to-Core Infrastructure and Security transformation, Premier Field Engineers from all technology areas will be working together to expand the TechCommunity site even further, joining together in the technology agnostic Premier Field Engineering TechCommunity (along with Core Infrastructure and Security), which can be found at https://aka.ms/PFETechComm!
As always, thank you for continuing to read the Core Infrastructure and Security (AskPFEPlat) blog, and we look forward to providing you more great content well into the future!
Stay a while and….oh wait wrong place. Welcome! My name is Tim Medina, Senior PFE with Microsoft and today we are going to look at what’s new with Windows Time for Server 2019 (part 1 of a 3 part series). As with everything, time has marched on and we are looking forward with the way we provide to time services to your environments. We did release some information on what’s to come here.
So, building on the introduction of highly accurate time, we have implemented this to use the same configuration and gotten some of that space down to the 1s, 50s, and 1ms accuracy. This has a high impact on time sensitive businesses and requirements. It should also be noted that it may extend to normal operations and keeping control of ticket lifetimes to the millisecond can further control of organizations identities.
As with previous releases, the configuration can be controlled via the registry, time commands, and Group Policy. The extensions have been made for the configuration of highly accurate time in the registry as well. Also note there are some requirements and restrictions.
We have also worked inside the service controls to reduce the possible impact of using the SpecialPollInterval to work in conjunction with high accuracy requirements. This should move the flag controls as well to a more uniform usage.
All and all we are continuing the work we started in Server 2016 and moving things forward from there. Next blog we will be doing a dive into the configuration paths outlined above. Then to wrap things up we will look into the deeper functions and flows inside the service. So as the bell tolls, we will see you next time.
For some extra information, you can also take a look at the product group’s post on this topic over at https://blogs.technet.microsoft.com/networking/2018/07/18/top10-ws2019-hatime/!