Creating and Populating Local Groups on Remote Computers

Getting the Needed Information
NewLocalGroup.vbs uses a command-line argument to obtain the names of the computers to which to connect. However, the script relies on hard-coded values for the name of the local group and the name of the global group. I followed this approach because you'll likely connect to different computers each time, but you probably won't change the local group or global group that often.

NewLocalGroup.vbs determines which computers to connect to when you launch the script. To run the script, you use the command

NewLocalGroup.vbs [argument]

where argument can be one of the following:

• one or more computer names
• the word all (to run the script against all the servers in AD)
• the word file (if you want to use an input file to provide the computer names)

If you want the script to run on only the local computer, you don't need to include an argument. I devised this system for a script that I discussed in "Check Service Status on Local or Remote Servers," March 2004, InstantDoc ID 41670. This article is available for public viewing if you'd like more information about that system. . . .