LabMice.net - The Windows 2000\XP\.NET Resource Index

Home | About Us | Search

Last Updated December 24, 2003

BackOffice
Book Reviews
Career Tools
MCSE Toolkit
Networking
Resource Centers
Scripting
  Batch Files
  Env. Variables
  Command Line
  Logon Scripts
  Perl
  Visual Basic
  WSH
Security
Utilities
Cybercheese

________________

 

 

 

Windows Scripting Host Resources

The Microsoft Windows Script Host (WSH) is a tool that will allow you to run Visual Basic Scripting Edition and JScript natively within Windows 2000 by clicking a script file on the Windows desktop, or by typing the name of a script file at the command prompt. Windows Script Host supports scripts written in Visual Basic Scripting Edition (VBScript) or JScript. There are two versions of the Windows Script Host: a windows-based version (wscript.exe) that provides a windows-based property sheet for setting script properties, and a command prompt-based version (cscript.exe) that provides command line switches for setting script properties. You can run either of these by typing wscript.exe or cscript.exe at the command prompt.
Main Resource Links
Born's Windows Scripting Host Bazaar
A great WSH resource by author Gunter Born. Includes FAQ, samples, Active X controls, book recommendations, and tools.

Ian Morrish's Windows Script Host FAQ
This site provides a comprehensive resource for WSH, OLE Automaton and COM objects that you can use to develop your own powerful scripting solutions.

Microsoft Windows Script Technologies Homepage
The official home page for WSH at MSDN. Includes documentation, FAQ's, samples,

PrimalSCRIPT 2.0
PrimalSCRIPT for Windows is a powerful scripting editor that handles all of your daily script editing needs on both your local Windows based system AND remote NT or UNIX servers. Files are edited in-place without the need to stop and transfer files back and forth between systems. As a result, ALL of your scripting is handled by ONE easy to use graphical Windows based editor.

Win32 Scripting
Everything you need to get up and running, Downloads, sample scripts, reference materials, and technical support via an online discussion lounge

Windows Scripting Guide
Provides technical resources, information and source code to help you automate the Windows operating system using Windows Script Host (WSH) and the VBScript and JScript scripting languages.

Win32 Scripting Journal
Brought to you by Windows NT Magazine, Win32 Scripting Journal is a scripting and task automation journal for Windows NT/95 system administrators. We cover scripting for a variety of technologies, including Windows NT, Exchange, SQL Server, IIS, IE, MS Office, SMS, ADSI, and COM/OLE automation. Languages covered include WSH, VBA, VBScript, JScript, Perl, PerlCOM, WinPerl++, Perl/Tk, Tcl/Tk, Python, ASCI, XLNT, FastLane FINAL, Windows NT Command Language, KiXtart, and WinBatch.

Winscripter.com
Windows Scripting Host with a focus on JScript and COM development. Lots of example scripts to get you started.

JScript Language Reference
The official reference from MSDN Online

VB Script Language Reference
The official reference from MSDN Online

Where to Start
Born's Windows Scripting Host FAQ Page

Introduction to Windows Scripting
Windows scripting is easy. This may sound like a bold statement, but spend a few hours playing with it, get your feet wet and I think you©ll agree. To get started using WSH begin with this introduction tutorial.

NT Gains Scripting Muscle
An introduction to Windows Script Host by Bob Wells Source: Windows & .NET Magazine

Overview of Windows Script Host in Windows 
Microsoft Knowledge Base Article: 232211 -  Windows Script Host (WSH) enables scripts to be run directly in Windows by double-clicking a script file or by typing the name of a script file at a command prompt. Like Microsoft Internet Explorer, WSH serves as a controller of ActiveX scripting engines. WSH has very low memory requirements and is ideal for both interactive and non-interactive scripting needs (such as logon scripting and administrative scripting). ( updated 10/18/2001)

Scripting 101
A 4 part series on how to create and structure WSH scripts. Source: Windows 2000 Magazine (June 1999)

Windows Scripting Host 2.0
WSH has undergone many improvements that make writing, editing, and debugging scripts easy - even using multiple languages. Source: Windows & .NET Magazine (Dec 1999)

VBScript Reference Guide
Learn about the functions, procedures and variables available when using the VBScript language. Source: WinGuides.com

WSH Reference Guide
Learn about the objects, methods and properties available when using the Windows Script Host (WSH). Source: WinGuides.com

WebCast: Microsoft Windows: System Administration Scripting in the Windows Environment
Level:100 A powerful scripting environment is an indispensable tool in the fight to reduce total cost of ownership (TCO) by automating system and network administration tasks. Windows Script Host (WSH), when used in conjunction with ADSI and the WMI scripting library, provides just such a scripting environment. In this presentation, you will learn what scripting is, how it might be useful to you, and how to write and run a script. You will then see the development of two example scripts. The first example will demonstrate some useful basics, while the second example will introduce some functionality that is a little more advanced and very powerful. At the end, you will hear about the new resource kit System Administration Scripting Guide and receive pointers to other useful system admin scripting information

How to....
A Scripted Solution for Complex Networking Problems
Using unattended installation scripts and system policies helped the IT staff at a major hospital create a multitasking environment for clinicians while keeping administration manageable. Source: Windows 2000 Magazine (Oct 1999)

Automating Exchange 2000 Management with Windows Script Host
This white paper illustrates how Exchange 2000 technologies can be helpful for management purposes. It examines existing scriptable COM technologies and provides server-centric samples developed under Windows Script Host (WSH) to help users with Exchange 2000 management tasks. Source: Microsoft.com (June 2002)

Basic User Account Creation with ADSI Scripting 
Microsoft Knowledge Base Article: 230750 - The Active Directory Services Interface (ADSI) tool provides a single consistent set of interfaces that can be called in scripts using the Microsoft Windows Script Host, or other scripting languages (VBScript and JScript are supported natively).

HOWTO: Enable DHCP Automatically Using WSH VBScript
Microsoft Knowledge Base Article: 197424 - Describes how to create a VBScript file that automatically enables DHCP under Windows 98 or Windows 95 using Windows Script Host. IMPORTANT: This procedure is not intended for home users with a few computers.

Real-World Scripting: Locating Long Paths in a Directory
This monthly column offers practical scripts for systems administrators. This month's script automatically locates and reports the names and locations of files whose paths exceed the Windows' path-length limit (or another threshold you specify). Source: Windows Scripting Solutions (January 2000)

Real-World Scripting: Testing and Changing Administrator Account Passwords
This monthly column offers practical scripts for systems administrators. The November column shows you how to create two scripts that ensure the accuracy and consistency of administrator passwords. Source: Windows Scripting Solutions (November 1999)

Shell Scripting 101, Lesson 1
In this 10-part series, you©ll learn the basics of shell scripting. In this first lesson, you?ll learn how to set up your scripting environment and learn about the Echo and Rem commands. Source: Windows Scripting Solutions (January 2000)

Shell Scripting 101, Lesson 2
In Lesson 2 of this 10-part series, you'll learn how to hard-code information into scripts. You'll also learn how to use environment variables to access information about your computer. Source: Windows Scripting Solutions (January 2000)

Shell Scripting 101, Lesson 3
In this lesson, you'll learn how to create an environment variable to represent a specified value. You also learn how to use an environment variable to temporarily hold a value so that you can pass information to a script as an argument. Source: Windows Scripting Solutions(January 2000)

Setting the Default Scripting Engine
Microsoft Knowledge Base Article: 245254 - Depending on the scripts you are running, you may want to change the default script engine from WScript to CScript so that it is not necessary to type "cscript" before each file (or vice versa). This article describes how to change the default scripting engine. 

The Pros and Cons of Perl and VBScript
Deciding whether to use Perl or Visual Basic Script (VBScript) depends on personal preference. Here are some issues to consider. Source: Windows Scripting Solutions (January 1999)

Microsoft Windows Management Instrumentation Scripting
Presents brief overviews of the Common Information Model (CIM) and the Windows Management Instrumentation (WMI) architecture. Includes an in-depth discussion on the WMI scripting API and sample scripts through WSH. Source: Microsoft. 

WSH Logon Scripts
If you're looking for a reason to deploy WSH, look no further than your logon scripts. Source: Windows 2000 Magazine (Feb 1999)

 

Watch Out for Possible Problems with Task Scheduler, Cacls, and Xcacls
If you're experiencing problems with Task Scheduler, Cacls, or Xcacls, you're not alone. Learn about the problems and the available hotfixes. Source: Windows Scripting Solutions (January 2000)


Entire contents
© 1999-2003 LabMice.net and TechTarget
All rights reserved

This site and its contents are Copyright 1999-2003 by LabMice.net. Microsoft, NT, BackOffice, MCSE, and Windows are registered trademarks of Microsoft Corporation. Microsoft Corporation in no way endorses or is affiliated with LabMice.net. The products referenced in this site are provided by parties other than LabMice.net. LabMice.net makes no representations regarding either the products or any information about the products. Any questions, complaints, or claims regarding the products must be directed to the appropriate manufacturer or vendor.