Guest Scott Posted August 21, 2007 Posted August 21, 2007 The server clock seems to run freely. Can someone advise how to maintain the server accurate and the workstations linked to the server. Thanks, Scott
Guest Coraleigh Miller Posted August 21, 2007 Posted August 21, 2007 Re: Clock accuracy Hi Scott, On your PDC Emmulator, from a command prompt type: NET TIME /SetSNTP:<ServerName> The server name should be the name of an external time server such as bigben.cac.washington.edu or one of these http://support.microsoft.com/kb/262680 Your other servers and workstations should already have this registry key, is its added when joining a domain... HKLM\System\CurrentControlSet\Services\W32Time\Parameters Key 'Type' is NT5DS ....but you may want to check to confirm as this key insures that these machines sync with your PDC Emmulator. Restarting the w32time service should then activate a sync on your machines. This doc explains some available NET TIME switches. http://technet2.microsoft.com/windowsserver/en/library/396e2cab-b011-459a-ac5c-326a562d42461033.mspx?mfr=true Coraleigh Miller "Scott" <NoSpan-Scott.Xe@GMail.com> wrote in message news:%23U7njY54HHA.1204@TK2MSFTNGP03.phx.gbl... > The server clock seems to run freely. Can someone advise how to maintain > the server accurate and the workstations linked to the server. > > Thanks, > > Scott >
Guest Scott Posted August 21, 2007 Posted August 21, 2007 Re: Clock accuracy Coraleigh, Thanks for your advice. I have further queries for you. Do I need to run NET TIME regularily to maintain the clock accuracy? If so, I may need to have run it schedulelly. I tried to run it on server. Before I did it, I changed the time behind one hour. The command ran successfully but the time was not changed immediately. How long would it take to correct the time? Your further advice is appreciated. Scott "Coraleigh Miller" <CoraleighMiller@yahoo.com> wrote in message news:uaZdPr54HHA.4184@TK2MSFTNGP06.phx.gbl... > Hi Scott, > > On your PDC Emmulator, from a command prompt type: > NET TIME /SetSNTP:<ServerName> > The server name should be the name of an external time server such as > bigben.cac.washington.edu or one of these > http://support.microsoft.com/kb/262680 > > Your other servers and workstations should already have this registry key, > is its added when joining a domain... > HKLM\System\CurrentControlSet\Services\W32Time\Parameters > Key 'Type' is NT5DS > > ...but you may want to check to confirm as this key insures that these > machines sync with your PDC Emmulator. > > Restarting the w32time service should then activate a sync on your > machines. > > This doc explains some available NET TIME switches. > http://technet2.microsoft.com/windowsserver/en/library/396e2cab-b011-459a-ac5c-326a562d42461033.mspx?mfr=true > > > Coraleigh Miller > > > "Scott" <NoSpan-Scott.Xe@GMail.com> wrote in message > news:%23U7njY54HHA.1204@TK2MSFTNGP03.phx.gbl... >> The server clock seems to run freely. Can someone advise how to maintain >> the server accurate and the workstations linked to the server. >> >> Thanks, >> >> Scott >> > >
Guest KA Kueh Posted August 21, 2007 Posted August 21, 2007 Re: Clock accuracy Hi Scott, No, once you have done the sync with the external clock the AD will periodically sync with the external clock.' "Scott" <NoSpan-Scott.Xe@GMail.com> wrote in message news:uBjQDL74HHA.2312@TK2MSFTNGP06.phx.gbl... > Coraleigh, > > Thanks for your advice. I have further queries for you. > > Do I need to run NET TIME regularily to maintain the clock accuracy? If > so, I may need to have run it schedulelly. > > I tried to run it on server. Before I did it, I changed the time behind > one hour. The command ran successfully but the time was not changed > immediately. How long would it take to correct the time? > > Your further advice is appreciated. > > Scott > > "Coraleigh Miller" <CoraleighMiller@yahoo.com> wrote in message > news:uaZdPr54HHA.4184@TK2MSFTNGP06.phx.gbl... >> Hi Scott, >> >> On your PDC Emmulator, from a command prompt type: >> NET TIME /SetSNTP:<ServerName> >> The server name should be the name of an external time server such as >> bigben.cac.washington.edu or one of these >> http://support.microsoft.com/kb/262680 >> >> Your other servers and workstations should already have this registry >> key, is its added when joining a domain... >> HKLM\System\CurrentControlSet\Services\W32Time\Parameters >> Key 'Type' is NT5DS >> >> ...but you may want to check to confirm as this key insures that these >> machines sync with your PDC Emmulator. >> >> Restarting the w32time service should then activate a sync on your >> machines. >> >> This doc explains some available NET TIME switches. >> http://technet2.microsoft.com/windowsserver/en/library/396e2cab-b011-459a-ac5c-326a562d42461033.mspx?mfr=true >> >> >> Coraleigh Miller >> >> >> "Scott" <NoSpan-Scott.Xe@GMail.com> wrote in message >> news:%23U7njY54HHA.1204@TK2MSFTNGP03.phx.gbl... >>> The server clock seems to run freely. Can someone advise how to >>> maintain the server accurate and the workstations linked to the server. >>> >>> Thanks, >>> >>> Scott >>> >> >> > >
Guest Coraleigh Miller Posted August 21, 2007 Posted August 21, 2007 Re: Clock accuracy Hi Scott, Are you running Server 2000 or 2003? Generally the syc can take approx an hour to sync up with an external time source. Coraleigh "Scott" <NoSpan-Scott.Xe@GMail.com> wrote in message news:uBjQDL74HHA.2312@TK2MSFTNGP06.phx.gbl... > Coraleigh, > > Thanks for your advice. I have further queries for you. > > Do I need to run NET TIME regularily to maintain the clock accuracy? If > so, I may need to have run it schedulelly. > > I tried to run it on server. Before I did it, I changed the time behind > one hour. The command ran successfully but the time was not changed > immediately. How long would it take to correct the time? > > Your further advice is appreciated. > > Scott > > "Coraleigh Miller" <CoraleighMiller@yahoo.com> wrote in message > news:uaZdPr54HHA.4184@TK2MSFTNGP06.phx.gbl... >> Hi Scott, >> >> On your PDC Emmulator, from a command prompt type: >> NET TIME /SetSNTP:<ServerName> >> The server name should be the name of an external time server such as >> bigben.cac.washington.edu or one of these >> http://support.microsoft.com/kb/262680 >> >> Your other servers and workstations should already have this registry >> key, is its added when joining a domain... >> HKLM\System\CurrentControlSet\Services\W32Time\Parameters >> Key 'Type' is NT5DS >> >> ...but you may want to check to confirm as this key insures that these >> machines sync with your PDC Emmulator. >> >> Restarting the w32time service should then activate a sync on your >> machines. >> >> This doc explains some available NET TIME switches. >> http://technet2.microsoft.com/windowsserver/en/library/396e2cab-b011-459a-ac5c-326a562d42461033.mspx?mfr=true >> >> >> Coraleigh Miller >> >> >> "Scott" <NoSpan-Scott.Xe@GMail.com> wrote in message >> news:%23U7njY54HHA.1204@TK2MSFTNGP03.phx.gbl... >>> The server clock seems to run freely. Can someone advise how to >>> maintain the server accurate and the workstations linked to the server. >>> >>> Thanks, >>> >>> Scott >>> >> >> > >
Guest Coraleigh Miller Posted August 21, 2007 Posted August 21, 2007 Re: Clock accuracy The reason I asked about your version is if you were running 2003 then you could run the w32tm /resync /rediscover command on the PDCe which would immediately resync your time from the external source. I am unaware of a command to do the same in 2000 though. Also if you wish there are a few more settings you can set on your time server to bring it closer to accuracy. The following MS articles descibe their configuration... For Windows Server 2000: http://support.microsoft.com/kb/216734/en-us For Windows Server 2003: http://support.microsoft.com/kb/816042/ Coraleigh Miller "Coraleigh Miller" <CoraleighMiller@yahoo.com> wrote in message news:ubSqzQ84HHA.3716@TK2MSFTNGP03.phx.gbl... > Hi Scott, > > Are you running Server 2000 or 2003? > > Generally the syc can take approx an hour to sync up with an external time > source. > > Coraleigh > > > "Scott" <NoSpan-Scott.Xe@GMail.com> wrote in message > news:uBjQDL74HHA.2312@TK2MSFTNGP06.phx.gbl... >> Coraleigh, >> >> Thanks for your advice. I have further queries for you. >> >> Do I need to run NET TIME regularily to maintain the clock accuracy? If >> so, I may need to have run it schedulelly. >> >> I tried to run it on server. Before I did it, I changed the time behind >> one hour. The command ran successfully but the time was not changed >> immediately. How long would it take to correct the time? >> >> Your further advice is appreciated. >> >> Scott >> >> "Coraleigh Miller" <CoraleighMiller@yahoo.com> wrote in message >> news:uaZdPr54HHA.4184@TK2MSFTNGP06.phx.gbl... >>> Hi Scott, >>> >>> On your PDC Emmulator, from a command prompt type: >>> NET TIME /SetSNTP:<ServerName> >>> The server name should be the name of an external time server such as >>> bigben.cac.washington.edu or one of these >>> http://support.microsoft.com/kb/262680 >>> >>> Your other servers and workstations should already have this registry >>> key, is its added when joining a domain... >>> HKLM\System\CurrentControlSet\Services\W32Time\Parameters >>> Key 'Type' is NT5DS >>> >>> ...but you may want to check to confirm as this key insures that these >>> machines sync with your PDC Emmulator. >>> >>> Restarting the w32time service should then activate a sync on your >>> machines. >>> >>> This doc explains some available NET TIME switches. >>> http://technet2.microsoft.com/windowsserver/en/library/396e2cab-b011-459a-ac5c-326a562d42461033.mspx?mfr=true >>> >>> >>> Coraleigh Miller >>> >>> >>> "Scott" <NoSpan-Scott.Xe@GMail.com> wrote in message >>> news:%23U7njY54HHA.1204@TK2MSFTNGP03.phx.gbl... >>>> The server clock seems to run freely. Can someone advise how to >>>> maintain the server accurate and the workstations linked to the server. >>>> >>>> Thanks, >>>> >>>> Scott >>>> >>> >>> >> >> > >
Guest Scott Posted August 21, 2007 Posted August 21, 2007 Re: Clock accuracy Coraleigh, Thanks a lot of useful advice. I am using Windows Server 2003. It seems so intellege that I need to type the command once and the system will automatically sync regularily. How can I observe this activity - in event viewer? Thanks, Scott "Coraleigh Miller" <CoraleighMiller@yahoo.com> ¦b¶l¥ó news:%23NOlsG94HHA.4928@TK2MSFTNGP05.phx.gbl ¤¤¼¶¼g... > The reason I asked about your version is if you were running 2003 then you > could run the > w32tm /resync /rediscover > command on the PDCe which would immediately resync your time from the > external source. I am unaware of a command to do the same in 2000 though. > > Also if you wish there are a few more settings you can set on your time > server to bring it closer to accuracy. The following MS articles descibe > their configuration... > > For Windows Server 2000: http://support.microsoft.com/kb/216734/en-us > For Windows Server 2003: http://support.microsoft.com/kb/816042/ > > Coraleigh Miller > > > "Coraleigh Miller" <CoraleighMiller@yahoo.com> wrote in message > news:ubSqzQ84HHA.3716@TK2MSFTNGP03.phx.gbl... >> Hi Scott, >> >> Are you running Server 2000 or 2003? >> >> Generally the syc can take approx an hour to sync up with an external >> time source. >> >> Coraleigh >> >> >> "Scott" <NoSpan-Scott.Xe@GMail.com> wrote in message >> news:uBjQDL74HHA.2312@TK2MSFTNGP06.phx.gbl... >>> Coraleigh, >>> >>> Thanks for your advice. I have further queries for you. >>> >>> Do I need to run NET TIME regularily to maintain the clock accuracy? If >>> so, I may need to have run it schedulelly. >>> >>> I tried to run it on server. Before I did it, I changed the time behind >>> one hour. The command ran successfully but the time was not changed >>> immediately. How long would it take to correct the time? >>> >>> Your further advice is appreciated. >>> >>> Scott >>> >>> "Coraleigh Miller" <CoraleighMiller@yahoo.com> wrote in message >>> news:uaZdPr54HHA.4184@TK2MSFTNGP06.phx.gbl... >>>> Hi Scott, >>>> >>>> On your PDC Emmulator, from a command prompt type: >>>> NET TIME /SetSNTP:<ServerName> >>>> The server name should be the name of an external time server such as >>>> bigben.cac.washington.edu or one of these >>>> http://support.microsoft.com/kb/262680 >>>> >>>> Your other servers and workstations should already have this registry >>>> key, is its added when joining a domain... >>>> HKLM\System\CurrentControlSet\Services\W32Time\Parameters >>>> Key 'Type' is NT5DS >>>> >>>> ...but you may want to check to confirm as this key insures that these >>>> machines sync with your PDC Emmulator. >>>> >>>> Restarting the w32time service should then activate a sync on your >>>> machines. >>>> >>>> This doc explains some available NET TIME switches. >>>> http://technet2.microsoft.com/windowsserver/en/library/396e2cab-b011-459a-ac5c-326a562d42461033.mspx?mfr=true >>>> >>>> >>>> Coraleigh Miller >>>> >>>> >>>> "Scott" <NoSpan-Scott.Xe@GMail.com> wrote in message >>>> news:%23U7njY54HHA.1204@TK2MSFTNGP03.phx.gbl... >>>>> The server clock seems to run freely. Can someone advise how to >>>>> maintain the server accurate and the workstations linked to the >>>>> server. >>>>> >>>>> Thanks, >>>>> >>>>> Scott >>>>> >>>> >>>> >>> >>> >> >> > >
Guest Coraleigh Miller Posted August 21, 2007 Posted August 21, 2007 Re: Clock accuracy Event Viewer will generate logs telling you that it is operating or not operating correctly. FYI- Occationally you may see an event log saying that your time server is not able to contact your external source which could be due to high load on the ext source. If it is more than a couple logs and/or accompanied by other time server error logs you should try changing the ext source time server and/or investigate the problem. http://www.eventid.net is a fantastic site for explaining what your event log id's mean and suggests possible solutions. To find out what your exact time offset is between your PDCe and external source you can run the w32tm /monitor /computers:[name of your external source]. To test between your other servers or clients you would just need to run w32tm /monitor as the client should know to sync with its PDCe. Here is a MS article describing the various w32tm command switches you can use. http://technet2.microsoft.com/windowsserver/en/library/de98cbdd-7d89-4896-9446-0df8f731b0381033.mspx?mfr=true Coraleigh Miller "Scott" <NoSpam-Scott.Xe@GMail.com> wrote in message news:%23Q1xi5$4HHA.2752@TK2MSFTNGP06.phx.gbl... > Coraleigh, > > Thanks a lot of useful advice. I am using Windows Server 2003. It seems > so intellege that I need to type the command once and the system will > automatically sync regularily. How can I observe this activity - in event > viewer? > > Thanks, > > Scott > > "Coraleigh Miller" <CoraleighMiller@yahoo.com> ¦b¶l¥ó > news:%23NOlsG94HHA.4928@TK2MSFTNGP05.phx.gbl ¤¤¼¶¼g... >> The reason I asked about your version is if you were running 2003 then >> you could run the >> w32tm /resync /rediscover >> command on the PDCe which would immediately resync your time from the >> external source. I am unaware of a command to do the same in 2000 though. >> >> Also if you wish there are a few more settings you can set on your time >> server to bring it closer to accuracy. The following MS articles descibe >> their configuration... >> >> For Windows Server 2000: http://support.microsoft.com/kb/216734/en-us >> For Windows Server 2003: http://support.microsoft.com/kb/816042/ >> >> Coraleigh Miller >> >> >> "Coraleigh Miller" <CoraleighMiller@yahoo.com> wrote in message >> news:ubSqzQ84HHA.3716@TK2MSFTNGP03.phx.gbl... >>> Hi Scott, >>> >>> Are you running Server 2000 or 2003? >>> >>> Generally the syc can take approx an hour to sync up with an external >>> time source. >>> >>> Coraleigh >>> >>> >>> "Scott" <NoSpan-Scott.Xe@GMail.com> wrote in message >>> news:uBjQDL74HHA.2312@TK2MSFTNGP06.phx.gbl... >>>> Coraleigh, >>>> >>>> Thanks for your advice. I have further queries for you. >>>> >>>> Do I need to run NET TIME regularily to maintain the clock accuracy? >>>> If so, I may need to have run it schedulelly. >>>> >>>> I tried to run it on server. Before I did it, I changed the time >>>> behind one hour. The command ran successfully but the time was not >>>> changed immediately. How long would it take to correct the time? >>>> >>>> Your further advice is appreciated. >>>> >>>> Scott >>>> >>>> "Coraleigh Miller" <CoraleighMiller@yahoo.com> wrote in message >>>> news:uaZdPr54HHA.4184@TK2MSFTNGP06.phx.gbl... >>>>> Hi Scott, >>>>> >>>>> On your PDC Emmulator, from a command prompt type: >>>>> NET TIME /SetSNTP:<ServerName> >>>>> The server name should be the name of an external time server such as >>>>> bigben.cac.washington.edu or one of these >>>>> http://support.microsoft.com/kb/262680 >>>>> >>>>> Your other servers and workstations should already have this registry >>>>> key, is its added when joining a domain... >>>>> HKLM\System\CurrentControlSet\Services\W32Time\Parameters >>>>> Key 'Type' is NT5DS >>>>> >>>>> ...but you may want to check to confirm as this key insures that these >>>>> machines sync with your PDC Emmulator. >>>>> >>>>> Restarting the w32time service should then activate a sync on your >>>>> machines. >>>>> >>>>> This doc explains some available NET TIME switches. >>>>> http://technet2.microsoft.com/windowsserver/en/library/396e2cab-b011-459a-ac5c-326a562d42461033.mspx?mfr=true >>>>> >>>>> >>>>> Coraleigh Miller >>>>> >>>>> >>>>> "Scott" <NoSpan-Scott.Xe@GMail.com> wrote in message >>>>> news:%23U7njY54HHA.1204@TK2MSFTNGP03.phx.gbl... >>>>>> The server clock seems to run freely. Can someone advise how to >>>>>> maintain the server accurate and the workstations linked to the >>>>>> server. >>>>>> >>>>>> Thanks, >>>>>> >>>>>> Scott >>>>>> >>>>> >>>>> >>>> >>>> >>> >>> >> >> >
Guest Scott Posted August 22, 2007 Posted August 22, 2007 Re: Clock accuracy Coraleigh, Many thanks for your useful information and advice. Scott "Coraleigh Miller" <CoraleighMiller@yahoo.com> ¦b¶l¥ó news:%23o0Bf7B5HHA.5160@TK2MSFTNGP05.phx.gbl ¤¤¼¶¼g... > Event Viewer will generate logs telling you that it is operating or not > operating correctly. FYI- Occationally you may see an event log saying > that your time server is not able to contact your external source which > could be due to high load on the ext source. If it is more than a couple > logs and/or accompanied by other time server error logs you should try > changing the ext source time server and/or investigate the problem. > http://www.eventid.net is a fantastic site for explaining what your event log > id's mean and suggests possible solutions. > > To find out what your exact time offset is between your PDCe and external > source you can run the w32tm /monitor /computers:[name of your external > source]. To test between your other servers or clients you would just need > to run w32tm /monitor as the client should know to sync with its PDCe. > > Here is a MS article describing the various w32tm command switches you can > use. > http://technet2.microsoft.com/windowsserver/en/library/de98cbdd-7d89-4896-9446-0df8f731b0381033.mspx?mfr=true > > > Coraleigh Miller > > > "Scott" <NoSpam-Scott.Xe@GMail.com> wrote in message > news:%23Q1xi5$4HHA.2752@TK2MSFTNGP06.phx.gbl... >> Coraleigh, >> >> Thanks a lot of useful advice. I am using Windows Server 2003. It seems >> so intellege that I need to type the command once and the system will >> automatically sync regularily. How can I observe this activity - in >> event viewer? >> >> Thanks, >> >> Scott >> >> "Coraleigh Miller" <CoraleighMiller@yahoo.com> ¦b¶l¥ó >> news:%23NOlsG94HHA.4928@TK2MSFTNGP05.phx.gbl ¤¤¼¶¼g... >>> The reason I asked about your version is if you were running 2003 then >>> you could run the >>> w32tm /resync /rediscover >>> command on the PDCe which would immediately resync your time from the >>> external source. I am unaware of a command to do the same in 2000 >>> though. >>> >>> Also if you wish there are a few more settings you can set on your time >>> server to bring it closer to accuracy. The following MS articles descibe >>> their configuration... >>> >>> For Windows Server 2000: http://support.microsoft.com/kb/216734/en-us >>> For Windows Server 2003: http://support.microsoft.com/kb/816042/ >>> >>> Coraleigh Miller >>> >>> >>> "Coraleigh Miller" <CoraleighMiller@yahoo.com> wrote in message >>> news:ubSqzQ84HHA.3716@TK2MSFTNGP03.phx.gbl... >>>> Hi Scott, >>>> >>>> Are you running Server 2000 or 2003? >>>> >>>> Generally the syc can take approx an hour to sync up with an external >>>> time source. >>>> >>>> Coraleigh >>>> >>>> >>>> "Scott" <NoSpan-Scott.Xe@GMail.com> wrote in message >>>> news:uBjQDL74HHA.2312@TK2MSFTNGP06.phx.gbl... >>>>> Coraleigh, >>>>> >>>>> Thanks for your advice. I have further queries for you. >>>>> >>>>> Do I need to run NET TIME regularily to maintain the clock accuracy? >>>>> If so, I may need to have run it schedulelly. >>>>> >>>>> I tried to run it on server. Before I did it, I changed the time >>>>> behind one hour. The command ran successfully but the time was not >>>>> changed immediately. How long would it take to correct the time? >>>>> >>>>> Your further advice is appreciated. >>>>> >>>>> Scott >>>>> >>>>> "Coraleigh Miller" <CoraleighMiller@yahoo.com> wrote in message >>>>> news:uaZdPr54HHA.4184@TK2MSFTNGP06.phx.gbl... >>>>>> Hi Scott, >>>>>> >>>>>> On your PDC Emmulator, from a command prompt type: >>>>>> NET TIME /SetSNTP:<ServerName> >>>>>> The server name should be the name of an external time server such as >>>>>> bigben.cac.washington.edu or one of these >>>>>> http://support.microsoft.com/kb/262680 >>>>>> >>>>>> Your other servers and workstations should already have this registry >>>>>> key, is its added when joining a domain... >>>>>> HKLM\System\CurrentControlSet\Services\W32Time\Parameters >>>>>> Key 'Type' is NT5DS >>>>>> >>>>>> ...but you may want to check to confirm as this key insures that >>>>>> these machines sync with your PDC Emmulator. >>>>>> >>>>>> Restarting the w32time service should then activate a sync on your >>>>>> machines. >>>>>> >>>>>> This doc explains some available NET TIME switches. >>>>>> http://technet2.microsoft.com/windowsserver/en/library/396e2cab-b011-459a-ac5c-326a562d42461033.mspx?mfr=true >>>>>> >>>>>> >>>>>> Coraleigh Miller >>>>>> >>>>>> >>>>>> "Scott" <NoSpan-Scott.Xe@GMail.com> wrote in message >>>>>> news:%23U7njY54HHA.1204@TK2MSFTNGP03.phx.gbl... >>>>>>> The server clock seems to run freely. Can someone advise how to >>>>>>> maintain the server accurate and the workstations linked to the >>>>>>> server. >>>>>>> >>>>>>> Thanks, >>>>>>> >>>>>>> Scott >>>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>> >>>> >>> >>> >> > >
Guest Coraleigh Miller Posted August 22, 2007 Posted August 22, 2007 Re: Clock accuracy You welcome Scott. :-) Coraleigh "Scott" <NoSpam-Scott.Xe@GMail.com> wrote in message news:uUp$PkN5HHA.5360@TK2MSFTNGP03.phx.gbl... > Coraleigh, > > Many thanks for your useful information and advice. > > Scott > > "Coraleigh Miller" <CoraleighMiller@yahoo.com> ¦b¶l¥ó > news:%23o0Bf7B5HHA.5160@TK2MSFTNGP05.phx.gbl ¤¤¼¶¼g... >> Event Viewer will generate logs telling you that it is operating or not >> operating correctly. FYI- Occationally you may see an event log saying >> that your time server is not able to contact your external source which >> could be due to high load on the ext source. If it is more than a couple >> logs and/or accompanied by other time server error logs you should try >> changing the ext source time server and/or investigate the problem. >> http://www.eventid.net is a fantastic site for explaining what your event log >> id's mean and suggests possible solutions. >> >> To find out what your exact time offset is between your PDCe and external >> source you can run the w32tm /monitor /computers:[name of your external >> source]. To test between your other servers or clients you would just >> need to run w32tm /monitor as the client should know to sync with its >> PDCe. >> >> Here is a MS article describing the various w32tm command switches you >> can use. >> http://technet2.microsoft.com/windowsserver/en/library/de98cbdd-7d89-4896-9446-0df8f731b0381033.mspx?mfr=true >> >> >> Coraleigh Miller >> >> >> "Scott" <NoSpam-Scott.Xe@GMail.com> wrote in message >> news:%23Q1xi5$4HHA.2752@TK2MSFTNGP06.phx.gbl... >>> Coraleigh, >>> >>> Thanks a lot of useful advice. I am using Windows Server 2003. It >>> seems so intellege that I need to type the command once and the system >>> will automatically sync regularily. How can I observe this activity - >>> in event viewer? >>> >>> Thanks, >>> >>> Scott >>> >>> "Coraleigh Miller" <CoraleighMiller@yahoo.com> ¦b¶l¥ó >>> news:%23NOlsG94HHA.4928@TK2MSFTNGP05.phx.gbl ¤¤¼¶¼g... >>>> The reason I asked about your version is if you were running 2003 then >>>> you could run the >>>> w32tm /resync /rediscover >>>> command on the PDCe which would immediately resync your time from the >>>> external source. I am unaware of a command to do the same in 2000 >>>> though. >>>> >>>> Also if you wish there are a few more settings you can set on your time >>>> server to bring it closer to accuracy. The following MS articles >>>> descibe their configuration... >>>> >>>> For Windows Server 2000: http://support.microsoft.com/kb/216734/en-us >>>> For Windows Server 2003: http://support.microsoft.com/kb/816042/ >>>> >>>> Coraleigh Miller >>>> >>>> >>>> "Coraleigh Miller" <CoraleighMiller@yahoo.com> wrote in message >>>> news:ubSqzQ84HHA.3716@TK2MSFTNGP03.phx.gbl... >>>>> Hi Scott, >>>>> >>>>> Are you running Server 2000 or 2003? >>>>> >>>>> Generally the syc can take approx an hour to sync up with an external >>>>> time source. >>>>> >>>>> Coraleigh >>>>> >>>>> >>>>> "Scott" <NoSpan-Scott.Xe@GMail.com> wrote in message >>>>> news:uBjQDL74HHA.2312@TK2MSFTNGP06.phx.gbl... >>>>>> Coraleigh, >>>>>> >>>>>> Thanks for your advice. I have further queries for you. >>>>>> >>>>>> Do I need to run NET TIME regularily to maintain the clock accuracy? >>>>>> If so, I may need to have run it schedulelly. >>>>>> >>>>>> I tried to run it on server. Before I did it, I changed the time >>>>>> behind one hour. The command ran successfully but the time was not >>>>>> changed immediately. How long would it take to correct the time? >>>>>> >>>>>> Your further advice is appreciated. >>>>>> >>>>>> Scott >>>>>> >>>>>> "Coraleigh Miller" <CoraleighMiller@yahoo.com> wrote in message >>>>>> news:uaZdPr54HHA.4184@TK2MSFTNGP06.phx.gbl... >>>>>>> Hi Scott, >>>>>>> >>>>>>> On your PDC Emmulator, from a command prompt type: >>>>>>> NET TIME /SetSNTP:<ServerName> >>>>>>> The server name should be the name of an external time server such >>>>>>> as bigben.cac.washington.edu or one of these >>>>>>> http://support.microsoft.com/kb/262680 >>>>>>> >>>>>>> Your other servers and workstations should already have this >>>>>>> registry key, is its added when joining a domain... >>>>>>> HKLM\System\CurrentControlSet\Services\W32Time\Parameters >>>>>>> Key 'Type' is NT5DS >>>>>>> >>>>>>> ...but you may want to check to confirm as this key insures that >>>>>>> these machines sync with your PDC Emmulator. >>>>>>> >>>>>>> Restarting the w32time service should then activate a sync on your >>>>>>> machines. >>>>>>> >>>>>>> This doc explains some available NET TIME switches. >>>>>>> http://technet2.microsoft.com/windowsserver/en/library/396e2cab-b011-459a-ac5c-326a562d42461033.mspx?mfr=true >>>>>>> >>>>>>> >>>>>>> Coraleigh Miller >>>>>>> >>>>>>> >>>>>>> "Scott" <NoSpan-Scott.Xe@GMail.com> wrote in message >>>>>>> news:%23U7njY54HHA.1204@TK2MSFTNGP03.phx.gbl... >>>>>>>> The server clock seems to run freely. Can someone advise how to >>>>>>>> maintain the server accurate and the workstations linked to the >>>>>>>> server. >>>>>>>> >>>>>>>> Thanks, >>>>>>>> >>>>>>>> Scott >>>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>> >>>> >>> >> >> >
Recommended Posts