| Author | Messages | |
sslists
Posts:51
 | | 12/13/2008 8:46 PM |
| I'm curious what people use for timesync besides the built-in w32time settings. If you use the built-in w32time, do you adjust any default settings on member servers A) like clearing NTP settings. By default the box has time.windows.com,0x9. I've always used the w32time with no issues, but it's always good to check.
Does anyone do additional logging for the w32time service?
TIA,
Steve Schofield
| | | |
| amulnick
Posts:163
| | 12/13/2008 9:53 PM |
| Additional logging? What would you look for? Why don't you have a date for
Friday night instead? 
I believe the default is actually 0x1.
Personally, the built-in time sync is convenient and works well. But my
company instead uses a third-party tool. That was done prior to my getting
there. The feeling was that the third-party tool offered additional
accuracy not attainable with the built-in version. That said, some settings
were adjusted on the clients to have them use the NTP servers. DNS and time
server settings were also adjusted. Oddly, no other client settings were
adjusted. 
Al
On Sat, Dec 13, 2008 at 8:39 PM, Steve Schofield <steve@iislogs.com> wrote:
> I'm curious what people use for timesync besides the built-in w32time
> settings. If you use the built-in w32time, do you adjust any default
> settings on member servers A) like clearing NTP settings. By default the
> box has time.windows.com,0x9. I've always used the w32time with no
> issues, but it's always good to check.
>
> Does anyone do additional logging for the w32time service?
>
> TIA,
> Steve Schofield
>
| | | |
| sslists
Posts:51
| | 12/13/2008 10:05 PM |
| I had a date, seriously. We went to best buy and bought a 1 TB external hard drive $139 bucks (My Christmas gift) and then went to IHOP. See what happens when you have kids and get married. 1 TB for $139, I recall buying a 250 MB for $369 years ago.
The additional logging is something I was looking for to help keep track and prove it was syncing every 8 hours. The logging would help prove the case where I'm at now, they use a 3rd party tool that has pretty straight forward logging. Me personally, the timesync just works and I don't really worry about it. Having objective proof logging would take any subjective opinions out of everything. There is a registry entry you can set to have w32time set.
Steve
----- Original Message -----
From: Al Mulnick
To: ActiveDir@mail.activedir.org
Sent: Saturday, December 13, 2008 9:48 PM
Subject: Re: [ActiveDir] Timesync
Additional logging? What would you look for? Why don't you have a date for Friday night instead?
I believe the default is actually 0x1.
Personally, the built-in time sync is convenient and works well. But my company instead uses a third-party tool. That was done prior to my getting there. The feeling was that the third-party tool offered additional accuracy not attainable with the built-in version. That said, some settings were adjusted on the clients to have them use the NTP servers. DNS and time server settings were also adjusted. Oddly, no other client settings were adjusted.
Al
On Sat, Dec 13, 2008 at 8:39 PM, Steve Schofield <steve@iislogs.com> wrote:
I'm curious what people use for timesync besides the built-in w32time settings. If you use the built-in w32time, do you adjust any default settings on member servers A) like clearing NTP settings. By default the box has time.windows.com,0x9. I've always used the w32time with no issues, but it's always good to check.
Does anyone do additional logging for the w32time service?
TIA,
Steve Schofield
------------------------------------------------------------------------------
No virus found in this incoming message.
Checked by AVG - http://www.avg.com
Version: 8.0.176 / Virus Database: 270.9.17/1847 - Release Date: 12/13/2008 4:56 PM
| | | |
| amulnick
Posts:163
| | 12/13/2008 10:09 PM |
| I felt a disturbance...
Logging can help. By default, w32time (the client) will log if it cannot
sync time. You won't get logging otherwise, by default. So you need to set
the logging on the clients. Do you really want to do that? Is that
realistic?
On Sat, Dec 13, 2008 at 10:01 PM, Steve Schofield <steve@iislogs.com> wrote:
> btw - why are you answering?! I figured I wouldn't get a response
> until Monday.
>
>
> Thank you,
>
> Steve Schofield
> Windows Server MVP - IIS
> http://weblogs.asp.net/steveschofield
>
> http://www.IISLogs.com <http://www.iislogs.com/>
> Log archival solution
> Install, Configure, Forget
>
> ----- Original Message -----
> *From:* Al Mulnick <amulnick@gmail.com>
> *To:* ActiveDir@mail.activedir.org
> *Sent:* Saturday, December 13, 2008 9:48 PM
> *Subject:* Re: [ActiveDir] Timesync
>
> Additional logging? What would you look for? Why don't you have a date
> for Friday night instead?
>
> I believe the default is actually 0x1.
>
> Personally, the built-in time sync is convenient and works well. But my
> company instead uses a third-party tool. That was done prior to my getting
> there. The feeling was that the third-party tool offered additional
> accuracy not attainable with the built-in version. That said, some settings
> were adjusted on the clients to have them use the NTP servers. DNS and time
> server settings were also adjusted. Oddly, no other client settings were
> adjusted.
>
>
> Al
>
> On Sat, Dec 13, 2008 at 8:39 PM, Steve Schofield <steve@iislogs.com>wrote:
>
>> I'm curious what people use for timesync besides the built-in w32time
>> settings. If you use the built-in w32time, do you adjust any default
>> settings on member servers A) like clearing NTP settings. By default the
>> box has time.windows.com,0x9. I've always used the w32time with no
>> issues, but it's always good to check.
>>
>> Does anyone do additional logging for the w32time service?
>>
>> TIA,
>> Steve Schofield
>>
>
> ------------------------------
>
>
> No virus found in this incoming message.
> Checked by AVG - http://www.avg.com
> Version: 8.0.176 / Virus Database: 270.9.17/1847 - Release Date: 12/13/2008
> 4:56 PM
>
>
| | | |
| sslists
Posts:51
| | 12/13/2008 10:15 PM |
| For the short-term to help dispell any issues people think that might happen. Longer term, it's one of the things you just have faith it'll work. The thing I'm trying to overcome with the built-in time is the same when it didn't work in NT4 / w2k days. Yes, I know that was a long time ago. And I agree, the time service didn't work too well in those days, I remember we replaced the time service with the resource kit one.
You know how change happens in a bigger company, slower and opinions are hard to alter. Objective proof always helps.
Steve
----- Original Message -----
From: Al Mulnick
To: ActiveDir@mail.activedir.org
Sent: Saturday, December 13, 2008 10:04 PM
Subject: Re: [ActiveDir] Timesync
I felt a disturbance...
Logging can help. By default, w32time (the client) will log if it cannot sync time. You won't get logging otherwise, by default. So you need to set the logging on the clients. Do you really want to do that? Is that realistic?
On Sat, Dec 13, 2008 at 10:01 PM, Steve Schofield <steve@iislogs.com> wrote:
btw - why are you answering?! I figured I wouldn't get a response until Monday.
Thank you,
Steve Schofield
Windows Server MVP - IIS
http://weblogs.asp.net/steveschofield
http://www.IISLogs.com
Log archival solution
Install, Configure, Forget
----- Original Message -----
From: Al Mulnick
To: ActiveDir@mail.activedir.org
Sent: Saturday, December 13, 2008 9:48 PM
Subject: Re: [ActiveDir] Timesync
Additional logging? What would you look for? Why don't you have a date for Friday night instead?
I believe the default is actually 0x1.
Personally, the built-in time sync is convenient and works well. But my company instead uses a third-party tool. That was done prior to my getting there. The feeling was that the third-party tool offered additional accuracy not attainable with the built-in version. That said, some settings were adjusted on the clients to have them use the NTP servers. DNS and time server settings were also adjusted. Oddly, no other client settings were adjusted.
Al
On Sat, Dec 13, 2008 at 8:39 PM, Steve Schofield <steve@iislogs.com> wrote:
I'm curious what people use for timesync besides the built-in w32time settings. If you use the built-in w32time, do you adjust any default settings on member servers A) like clearing NTP settings. By default the box has time.windows.com,0x9. I've always used the w32time with no issues, but it's always good to check.
Does anyone do additional logging for the w32time service?
TIA,
Steve Schofield
--------------------------------------------------------------------------
No virus found in this incoming message.
Checked by AVG - http://www.avg.com
Version: 8.0.176 / Virus Database: 270.9.17/1847 - Release Date: 12/13/2008 4:56 PM
------------------------------------------------------------------------------
No virus found in this incoming message.
Checked by AVG - http://www.avg.com
Version: 8.0.176 / Virus Database: 270.9.17/1847 - Release Date: 12/13/2008 4:56 PM
| | | |
| Ambroise.Filini
Posts:24
| | 12/15/2008 8:24 AM |
| Do you guys use GPO settings for time sync, i have just enabled NTP server
on a GPO for Domain Controllers but i am reading in articles that it is
better to leave it unconfigured.
2008/12/14 Steve Schofield <steve@iislogs.com>
> For the short-term to help dispell any issues people think that might
> happen. Longer term, it's one of the things you just have faith it'll
> work. The thing I'm trying to overcome with the built-in time is the same
> when it didn't work in NT4 / w2k days. Yes, I know that was a long time
> ago. And I agree, the time service didn't work too well in those days, I
> remember we replaced the time service with the resource kit one.
>
> You know how change happens in a bigger company, slower and opinions are
> hard to alter. Objective proof always helps.
>
> Steve
>
> ----- Original Message -----
> *From:* Al Mulnick <amulnick@gmail.com>
> *To:* ActiveDir@mail.activedir.org
> *Sent:* Saturday, December 13, 2008 10:04 PM
> *Subject:* Re: [ActiveDir] Timesync
>
> I felt a disturbance...
>
> Logging can help. By default, w32time (the client) will log if it cannot
> sync time. You won't get logging otherwise, by default. So you need to set
> the logging on the clients. Do you really want to do that? Is that
> realistic?
>
> On Sat, Dec 13, 2008 at 10:01 PM, Steve Schofield <steve@iislogs.com>wrote:
>
>> btw - why are you answering?! I figured I wouldn't get a response
>> until Monday.
>>
>>
>> Thank you,
>>
>> Steve Schofield
>> Windows Server MVP - IIS
>> http://weblogs.asp.net/steveschofield
>>
>> http://www.IISLogs.com <http://www.iislogs.com/>
>> Log archival solution
>> Install, Configure, Forget
>>
>> ----- Original Message -----
>> *From:* Al Mulnick <amulnick@gmail.com>
>> *To:* ActiveDir@mail.activedir.org
>> *Sent:* Saturday, December 13, 2008 9:48 PM
>> *Subject:* Re: [ActiveDir] Timesync
>>
>> Additional logging? What would you look for? Why don't you have a
>> date for Friday night instead?
>>
>> I believe the default is actually 0x1.
>>
>> Personally, the built-in time sync is convenient and works well. But my
>> company instead uses a third-party tool. That was done prior to my getting
>> there. The feeling was that the third-party tool offered additional
>> accuracy not attainable with the built-in version. That said, some settings
>> were adjusted on the clients to have them use the NTP servers. DNS and time
>> server settings were also adjusted. Oddly, no other client settings were
>> adjusted.
>>
>>
>> Al
>>
>> On Sat, Dec 13, 2008 at 8:39 PM, Steve Schofield <steve@iislogs.com>wrote:
>>
>>> I'm curious what people use for timesync besides the built-in w32time
>>> settings. If you use the built-in w32time, do you adjust any default
>>> settings on member servers A) like clearing NTP settings. By default the
>>> box has time.windows.com,0x9. I've always used the w32time with no
>>> issues, but it's always good to check.
>>>
>>> Does anyone do additional logging for the w32time service?
>>>
>>> TIA,
>>> Steve Schofield
>>>
>>
>> ------------------------------
>>
>>
>> No virus found in this incoming message.
>> Checked by AVG - http://www.avg.com
>> Version: 8.0.176 / Virus Database: 270.9.17/1847 - Release Date:
>> 12/13/2008 4:56 PM
>>
>>
> ------------------------------
>
>
> No virus found in this incoming message.
> Checked by AVG - http://www.avg.com
> Version: 8.0.176 / Virus Database: 270.9.17/1847 - Release Date: 12/13/2008
> 4:56 PM
>
>
| | | |
| amulnick
Posts:163
| | 12/15/2008 8:57 AM |
| You just about have to use GPO. You could use reg settings or logon script,
but that would be silly. By default, windows uses NT5DS for timesync. To
use NTP, you have to reconfigure the clients at least to tell it the servers
and the protocol to use. The rest can be default if you like.
On Mon, Dec 15, 2008 at 8:20 AM, Active Dir <activedirlist@gmail.com> wrote:
> Do you guys use GPO settings for time sync, i have just enabled NTP server
> on a GPO for Domain Controllers but i am reading in articles that it is
> better to leave it unconfigured.
>
> 2008/12/14 Steve Schofield <steve@iislogs.com>
>
> For the short-term to help dispell any issues people think that might
>> happen. Longer term, it's one of the things you just have faith it'll
>> work. The thing I'm trying to overcome with the built-in time is the same
>> when it didn't work in NT4 / w2k days. Yes, I know that was a long time
>> ago. And I agree, the time service didn't work too well in those days, I
>> remember we replaced the time service with the resource kit one.
>>
>> You know how change happens in a bigger company, slower and opinions are
>> hard to alter. Objective proof always helps.
>>
>> Steve
>>
>> ----- Original Message -----
>> *From:* Al Mulnick <amulnick@gmail.com>
>> *To:* ActiveDir@mail.activedir.org
>> *Sent:* Saturday, December 13, 2008 10:04 PM
>> *Subject:* Re: [ActiveDir] Timesync
>>
>> I felt a disturbance...
>>
>> Logging can help. By default, w32time (the client) will log if it cannot
>> sync time. You won't get logging otherwise, by default. So you need to set
>> the logging on the clients. Do you really want to do that? Is that
>> realistic?
>>
>> On Sat, Dec 13, 2008 at 10:01 PM, Steve Schofield <steve@iislogs.com>wrote:
>>
>>> btw - why are you answering?! I figured I wouldn't get a response
>>> until Monday.
>>>
>>>
>>> Thank you,
>>>
>>> Steve Schofield
>>> Windows Server MVP - IIS
>>> http://weblogs.asp.net/steveschofield
>>>
>>> http://www.IISLogs.com <http://www.iislogs.com/>
>>> Log archival solution
>>> Install, Configure, Forget
>>>
>>> ----- Original Message -----
>>> *From:* Al Mulnick <amulnick@gmail.com>
>>> *To:* ActiveDir@mail.activedir.org
>>> *Sent:* Saturday, December 13, 2008 9:48 PM
>>> *Subject:* Re: [ActiveDir] Timesync
>>>
>>> Additional logging? What would you look for? Why don't you have a
>>> date for Friday night instead?
>>>
>>> I believe the default is actually 0x1.
>>>
>>> Personally, the built-in time sync is convenient and works well. But my
>>> company instead uses a third-party tool. That was done prior to my getting
>>> there. The feeling was that the third-party tool offered additional
>>> accuracy not attainable with the built-in version. That said, some settings
>>> were adjusted on the clients to have them use the NTP servers. DNS and time
>>> server settings were also adjusted. Oddly, no other client settings were
>>> adjusted.
>>>
>>>
>>> Al
>>>
>>> On Sat, Dec 13, 2008 at 8:39 PM, Steve Schofield <steve@iislogs.com>wrote:
>>>
>>>> I'm curious what people use for timesync besides the built-in w32time
>>>> settings. If you use the built-in w32time, do you adjust any default
>>>> settings on member servers A) like clearing NTP settings. By default the
>>>> box has time.windows.com,0x9. I've always used the w32time with no
>>>> issues, but it's always good to check.
>>>>
>>>> Does anyone do additional logging for the w32time service?
>>>>
>>>> TIA,
>>>> Steve Schofield
>>>>
>>>
>>> ------------------------------
>>>
>>>
>>> No virus found in this incoming message.
>>> Checked by AVG - http://www.avg.com
>>> Version: 8.0.176 / Virus Database: 270.9.17/1847 - Release Date:
>>> 12/13/2008 4:56 PM
>>>
>>>
>> ------------------------------
>>
>>
>> No virus found in this incoming message.
>> Checked by AVG - http://www.avg.com
>> Version: 8.0.176 / Virus Database: 270.9.17/1847 - Release Date:
>> 12/13/2008 4:56 PM
>>
>>
>
| | | |
|
|