As we discussed in an earlier column, Wscript.Shell represents the local execution environment: the Registry, shortcuts, environment variables such as TMP and other aspects of the Shell. You'll use this object to find out more about the environment, to read from or write to the Registry, send keystrokes to an application or even to record what your scripts did in Event Log entries. .
Now, let's look at how to read the Registry and record the value of a key in the Event Viewer.
Scripting School: Tuning the environment with WshShell
- Contents of WshShell
- Viewing and editing the Registry
- Reading and writing to the Registry
- Recording the change
Read all of Christa's scripting 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
October 2005: Scripting School: Tuning the environment with WshShell
ABOUT THE AUTHOR:
A Terminal Services MVP, Christa Anderson is the strategic technology manager for visionapp She formerly was program manager for the Microsoft Terminal Services team. She is an internationally known authority on scripting, the author of Windows Terminal Services, The Definitive Guide to MetaFrame XP, and co-author of the book Mastering Windows 2003 Server. If you have a scripting question for Christa, please e-mail her at editor@SearchWincomputing.com. She often uses these emails as fodder for her scripting columns.