It does not mention anything about GPOs or indicate that GPOs should not be recommended to configure time settings for a domain. The article itself quotes this in the very beginning and though it refers to another link regarding configuration, those links cascade into others.
For information about how to configure Windows Time service, see the list of topics in the section No where in my research, thus far, did I find that using GPO to configure time settings is not recommended. If the GPO settings are only used in the same way that using w32tm, direct registry editing, Microsoft FixIt's, or other methods, of setting the time configurations are used, I don't see an issue. I know this is a slightly old posting but I am looking into an odd issue with one of our DCs VM with no time configured from VM and cannot let a possible ambiguous response lay as if it is a complete answer.
Office Office Exchange Server. Not an IT pro? Resources for IT Professionals. Sign in. United States English. Ask a question. Most of our user's do not connect regularly to the VPN, so many of their time is not staying in sync since they are not contacting the domain controller regularly.
I wanted to consider changing the group policy so they point to directly to the nist. Currently, they all point to the domain controller. It has been a long time since I have revisited Windows Group Policy settings, and I was hoping the Spiceworks community could give me some guidance on setting up the Default Domain policy to point to a list of the nist. Attached is our current GP and the registry key configured on the DC. Thank you for the reply.
What is mentioned in the article is what we are currently doing. Set sync with external NTP server for example " 0. Attachments: Up to 10 attachments including images can be used with a maximum of 3. Hi DSPatrick Thanks for your reply. I have thought about external NTP server for all hosts computers and servers due to all PC are laptop and many times are outside company.
Domain members should use NT5DS domain time always when connected to domain. Trying to use external NTP for all members is not really workable. Hi, Thanks for your reply. So domain controller will be NTP server for domain and all windows domain client "take" right time from DC. After that I would found a way to set time zone, so I am sure that all computer has got the same time zone. At the moment user can change it and sometimes during Windows 10 setup I don't get the right one.
I have seen that it is possible only using regedit as value of GPO. Someone know other way to do it?
0コメント