+ Post New Thread
Results 1 to 7 of 7
Windows Thread, Ive tried, followed guides but failed!! To simply set the clock!!!! in Technical; We have always used a .bat script to set the clock from one of the Domain Controllers. Reading about this ...
  1. #1

    Join Date
    Aug 2007
    Posts
    812
    Thank Post
    98
    Thanked 64 Times in 46 Posts
    Rep Power
    26

    Ive tried, followed guides but failed!! To simply set the clock!!!!

    We have always used a .bat script to set the clock from one of the Domain Controllers.
    Reading about this is apparently not recommended and was used in W2000
    time.bat - "Set time \\dc1 /set /yes"
    Can anyone please talk me through the correct way to set the clock with Group Policy.?

    Thanks in advance !!

    Latest failed effort:
    System/Windows Time Service/Time Providers
    Policy Setting
    Configure Windows NTP Client Enabled
    NtpServer DC1.wolverley.local
    Type NTP
    CrossSiteSyncFlags 2
    ResolvePeerBackoffMinutes 15
    ResolvePeerBackoffMaxTimes 7
    SpecialPollInterval 3600
    EventLogFlags 0

  2. #2


    Join Date
    Mar 2009
    Location
    Leeds
    Posts
    6,581
    Thank Post
    228
    Thanked 854 Times in 733 Posts
    Rep Power
    295
    the workstations should all pick up time from the pdc without any intervention

  3. #3
    box_l's Avatar
    Join Date
    May 2007
    Location
    Herefordshire
    Posts
    427
    Thank Post
    68
    Thanked 90 Times in 75 Posts
    Rep Power
    61
    Not using Group policy, but

    One of the schools I picked up recently had the server referencing itself and the clients working from micrsofts' time server.

    To fix this I did the following.

    On the FSMO role holder

    Code:
    w32tm /configure /manualpeerlist:your.ntp.time.server.here,0x1 /syncfromflags:MANUAL
    net stop w32time
    net start w32time
    w32tm /resync
    where your.ntp.time.server.here is the one provided by LEA/county or a trusted one from the web, pool.ntp.org etc

    On the clients

    Code:
    W32tm /config /syncfromflags:domhier /update
    net stop w32time
    net start w32time
    W32tm /resync /rediscover
    Check clients with
    Code:
    w32tm /monitor
    BoX

  4. Thanks to box_l from:

    burgemaster (29th March 2011)

  5. #4

    Join Date
    Dec 2008
    Location
    Essex
    Posts
    2,137
    Thank Post
    1
    Thanked 326 Times in 316 Posts
    Rep Power
    77

  6. #5
    chrisbrown's Avatar
    Join Date
    Aug 2010
    Location
    Melbourne, Australia
    Posts
    103
    Thank Post
    2
    Thanked 16 Times in 14 Posts
    Rep Power
    16
    time.bat should read "net time" and it will still work.

  7. #6
    chrisbrown's Avatar
    Join Date
    Aug 2010
    Location
    Melbourne, Australia
    Posts
    103
    Thank Post
    2
    Thanked 16 Times in 14 Posts
    Rep Power
    16
    Is it just me or was a post deleted from here?

  8. #7

    Join Date
    Aug 2007
    Posts
    812
    Thank Post
    98
    Thanked 64 Times in 46 Posts
    Rep Power
    26
    Right...
    I now have all desktops syncing perfectly to our PDC... I have also manually set the servers to correct their time.
    Thanks for all the help!!

SHARE:
+ Post New Thread

Similar Threads

  1. The server method 'set object' failed - exchange 2010 on server 2008 R2
    By artfulmatt in forum Windows Server 2008 R2
    Replies: 0
    Last Post: 27th April 2010, 01:32 PM
  2. just what ive been waiting for...
    By RabbieBurns in forum AV and Multimedia Related
    Replies: 12
    Last Post: 11th August 2009, 05:26 PM
  3. Using WDS simply
    By SimpleSi in forum Windows
    Replies: 2
    Last Post: 26th February 2009, 10:25 AM

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •