?
Solved

Group Policy Registry Setting Change

Posted on 2013-12-26
3
Medium Priority
?
641 Views
Last Modified: 2013-12-30
How do I use group policy to change the following registry on all end user virtual machines so that their windows time is correct?

HKLM>System>CurrentControlSet>Services>W32Time>Parameters
NtpServer (192.20.1.132)
0
Comment
Question by:Robert Mohr
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
3 Comments
 
LVL 53

Accepted Solution

by:
Will Szymkowski earned 2000 total points
ID: 39740856
Why you are wanting to set this reg value? Servers/workstations get there time from the Domain Controllers and the Domain Controllers get their time from the PDC holder. You should not need to configure this option in the registry. If you are using VMware and the clients and getting the time source from the Hosts you can simply either configure the host to get the Time from the PDC or you can disable the clients from getting time source from the Host server that they are on and they will contact the DC directly to get the time.

However, that being said you can use Group Policy Perferences to accomplish this. Refer to the below link which outlines this clearly.
http://social.technet.microsoft.com/Forums/windowsserver/en-US/80fad09a-420c-487f-8dfa-8a59c9ea8664/gpo-to-change-a-registry-value?forum=winserverGP

Will.
0
 

Author Comment

by:Robert Mohr
ID: 39742539
I decided I wanted to delete the registry value and then add the correct registry to point the Virtual Machine to sync with the hosts.

I am not able to get the registry to delete however.
Here are the steps. Not sure what I am doing wrong.
See attached screen shot of the Group Policy Management console and what I added.
GPO.jpg
0
 

Author Closing Comment

by:Robert Mohr
ID: 39746819
Very helpful. Come to find out my VMs were pulling their time from the WYSE Device Thing Clients and it couldn't access the correct config file location. Although your solution changed the IP address via group policy it ultimately wasn't my issue. It wasn't until I changed the config file and pointed the thin clients to the correct file server did the time pass thru.
0

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Always backup Domain, SYSVOL etc.using processes according to Microsoft Best Practices. This is meant as a disaster recovery process for small environments that did not implement backup processes and did not run a secondary domain controller that ne…
Auditing domain password hashes is a commonly overlooked but critical requirement to ensuring secure passwords practices are followed. Methods exist to extract hashes directly for a live domain however this article describes a process to extract u…
This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…
Are you ready to implement Active Directory best practices without reading 300+ pages? You're in luck. In this webinar hosted by Skyport Systems, you gain insight into Microsoft's latest comprehensive guide, with tips on the best and easiest way…
Suggested Courses
Course of the Month15 days, 7 hours left to enroll

743 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question