Guy's Scripting Ezine - 97 Net Time /setsntp
|
Guy recommends this: 
Guy's Top 10 Free Tools
1) FreePing Contents for Ezine 97 - Net Time /setsntpIntroduction to 2006 EzinesThe New Year is a classic time for fresh initiatives, coupled with reflections on the previous 12 months. As far as this ezine is concerned, the new initiative is a 10 part series specializing in the basis and basics of VBScript. As far as looking to the past, I just want to say that this ezine will continue with the twin aims of providing working script examples, while giving general learning points to help you adapt my scripts to your environment. Occasionally, I will feature CSVDE, LDIFDE or DS Services. The other reason to retain your free ezine subscription is that I send out complimentary ebook whenever I write a new ebook, or update an existing one.
This Week's SecretAbout five years ago, when this site was just a few pages, I noticed that the Logon Script page had more hits than all the rest of the pages added together. Realising the interest in VBScript for Windows, I developed a whole scripting section. Two years ago, I started this ezine primarily as a way of giving those who bought my ebooks an after sales service. From the first ezine, my specialty has been getting people started. So for the next ten editions I am going to concentrate on the basics of VBScript. I will be choosing real world examples for you to copy and paste, but my real objective is to explain how scripts are put together. In particular, I want to explain which elements of the script you can and should change, and which elements are fixed terms have fixed names that you should learn, apply, but never change. This Week's MissionThis week's mission is to configure your machine to synchronize with an internet time server. Trust me, accurate time is important on a server. As yet, no-one can explain to my satisfaction, why left to its own devices, my $1,000 computer regularly loses nearly a minute every week. Especially when my 10 year old, $5, 'Mickey Mouse' watch keeps perfect time. Theory that it's helpful to know.
Important Scripting PrincipleIf we look at the big picture, then we realize that almost all scripts mimic actions that you can perform manually. The secret of success is to perfect the manual steps then convert them to lines of VBScript code. In this instance we want to create a cmd session by: Clicking on the Start Button, typing: run, cmd. From the black 'dos box', we now type, net time /? to check the switches. Try: net time /querysntp. I was surprised that Windows Server 2003 returned time.windows.com, 0x1, as its time server. We want to change this to an internet time server such as: time-a.nist.gov. The crucial command is: net time /setsntp:time-a.nist.gov Pure Scripting Learning PointsWe have established the need for a command shell, which will run our net time instructions. Therefore, we create turn to our VBScript skills and create a shell object called objShell. The instruction is: objShell=CreateObject("Wscript.Shell"). My learning point is that you can call this object zpv23K instead of objShell. However, VBScript would not understand makemeobj("Wscript.Shell"), it has to be precisely, CreateObject("Wscript.Shell"). WScript is VBScript's underlying program or host, more of that another time, suffice to say that here we specify a .Shell type of object. In other scripts we will create .Network objects, which support different WScript properties or 'handles'. The focal point of our script is ObjShell. We will utilize two of its methods, .Run to create a cmd session and .SendKeys to mimic keystrokes that we enter at the cmd prompt. I also use the .Sleep method, principally to tell the script to wait, so that I can see what is happening. Such scripts rarely work perfectly first time and I need to see if the instructions are going according to plan. Note: Both .SendKeys and .Sleep are interesting and useful for learning or applying 'sticking plaster' to broken scripts, however, in production scripts seek alternative methods. As you get to know me, you will realise that I have an addiction to WScript.echo messages. Many readers say that I am obsessed with calling for WSH boxes to confirm that my code has produced action. What I reply is that in production scripts, or if the messages annoy you, just ' Rem out the WScript.echo lines using a ' single quote. If you are looking for handy network utilities, try some of the free downloads at Tools4Ever Example 1: VBScript to Set the Time ServerIn Example 1, we will employ SendKeys set the Server's time server. This method is more long-winded than Example 2, my reason for showing you this method is to demonstrate how scripts mimic normal GUI or command line actions. Instructions for setting the Time Server This script is designed for servers, but should work fine on an XP machine.
VBScript Tutorial - Learning PointsNote 1: Option Explicit forces me to declare all my variables. This is why I have Dim statements at the top of my scripts, to dimension variables such as strTimeSrv. Note 2: The defining command is : Set objShell = CreateObject("WScript.Shell"). Here is where we create a shell object that we can use to execute the net time command. Note 3: Compare how Sendkeys passes instructions to the CMD prompt with how you may issue the net time command manually. Note 4: Observe how the carriage return command {Enter} is encased in curly brackets. ˆ Challenges
Example 2 Set the Time Server using .RunThis script is more efficient than Example 1, moreover, it does not rely on the SendKeys method. Once again, the WScript.echo command is merely to demonstrate that the script has actually executed. '===============================================
Summary of Net time /setsntpOur mission is to keep the server's time synchronized with an external time source. From a scripting point of view, we create a shell object, and then send instructions via the .Sendkeys method.
|
*
|
|
|
|
Home Copyright © 1999-2010 Computer Performance LTD All rights reserved Please report a broken link, or an error. | |
