• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1660
  • Last Modified:

When setting MaxPosPhaseCorrection using a GPO the settings are not changing on the client.

Hey Experts,

I am attempting to create a GPO under  \Computer Configuration\Administrative Templates\System\Windows Time Service\Global Configuration Settings.

That will create the following settings for me

Value name / Default value in GPEditor / Default for a DC

LargePhaseOffset / 1,280,000 / 50,000,000
SpikeWatchPeriod / 90 / 900
MaxPollInterval / 5 / 10
MinPollInterval / 10 / 6
UpdateInterval / 30,000 / 100
PhaseCorrectRate / 1 / 7

Value name / Default value in GPEditor / New recomended value for a DC

MaxPosPhaseCorrection / 54000 / 172800

MaxNegPhaseCorrection / 54000 / 172800


I am ok with creating the GPO. I assign it to a custom OU and moved my test servers into the OU. the problem is that the settings don't appear to be changing on the server that I have moved into the OU.

This is in a test environment with no other GPO's applied. I have ran gpresults to make sure it is receiving the timesync GPO that I have created. But when i look in the registry under HKLM\System\CurrentControlSet\Services\W32Time\Config

the settings are still the default 0xFFFFFFFF (4,294,967,295)

Am i looking in the right location to determine if the GPO has been successfully applied or not?

ssiimmppllee
0
ssiimmppllee
Asked:
ssiimmppllee
1 Solution
 
ssiimmpplleeAuthor Commented:
I was able to find the proper location for this. Because this is a GPO editing the registry the actual key is located in HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\W32Time\Config

0

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Tackle projects and never again get stuck behind a technical roadblock.
Join Now