Recording the change |
 |
By Christa Anderson, Contributor
05 Oct 2005 | SearchWinSystems.com |
|
|
The last step of checking the Registry is logging the event so you have a record of the listening port and the change you made, if any.
To do this, you'll use WshShell's LogEvent method, which creates a record in the Application log. Its syntax looks like this: WshShell.LogEvent eventcode, strmessage [strtarget]
The eventcode argument specifies the type of event to record, the strmessage argument specifies the message that appears in the Application log, and the optional strtarget argument supplies the name of the computer on which to record the changes -- whether that's the local computer or a centralized TS management server you've created.
Although you can't control which log the record goes into or the application creating it, you can choose the type of event you want to register (e.g., critical, warning or a successful audit). In this example, we'll create an informational record by specifying type 4.
Script
'Tell the script to accept no undefined variables.
Option Explicit
'Define the variables to use.
Dim oWshShell, sValue
'Create an object representing the Windows graphical shell.
Set oWshShell = CreateObject("Wscript.Shell")
'Read the value in sValue.
sValue =
oWshShell.RegRead("HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp")
'Record the value and explanation in the current computer's Application log.
oWshShell.LogEvent 4, "Terminal Services is currently listening on port "& sValue & "."
Scripting School: Turning the environment with WshShell
 Introduction
Contents of WshShell
Viewing and editing the Registry
Reading and writing to the Registry
Recording the change
Summary
Read Christa's previous columns:
April 2005: Beginner's guide to scripting
May 2005: It's time to increase your scripting expertise
June 2005: Connect users to network resources
July 2005: More on connecting to network resources
August 2005: Find objects with Windows Scripting Host
September 2005: Windows Script Host arguments
| ABOUT THE AUTHOR: |
|
Christa Anderson
When Christa Anderson began working with Windows Server operating systems in 1992, she became increasingly interested in finding more efficient and flexible ways of performing routine tasks. Christa has written extensively about administrative scripting and taught technical sessions on the subject at conferences such as Comdex and CeBIT, helping people who had never done any scripting to write their own scripts in half a day. In addition to her interest in scripting Windows management, Christa is an authority on server-based computing and the program manager for Terminal Services licensing in Longhorn. If you have a scripting question for Christa, please e-mail her at scripting@SearchWinSystems.com.
|
|
|
|
|
|
