Cindy.vbs

A WMI-based documentation script for Windows systems
Tested with Windows Server 2012 R2, Windows 8.1 and all predecessors down to Windows XP. This script will not run in Windows RT.
The script does not change anything, it only reads and displays data
For local reports, user rights are sufficient. You need admin rights on the target computer if you run the script remotely.

Usage:
- Open a CMD window
- Run Cindy with cscript. It is best to redirect the output to a file. 
  Example:
    cscript //nologo cindy.vbs>report.txt
- If you want to report on a remote computer simply add its name as an argument. 
  You need admin rights on the remote machine to create a report remotely.
  Example:
    cscript //nologo cindy.vbs DC01>DC01.txt
- new in v1.1: add the /mode:all switch to perform all queries, including the long-running ones (such as local users, products, and some more)
  Example:
    cscript //nologo cindy.vbs /mode:all DC01>DC01.txt
- new in v1.2: add the /mode:basic switch to only get a small list of basic information about the computer.
  Example:
    cscript //nologo cindy.vbs /mode:basic>basic-data.txt

To easily create a local report simply run Cindy-LocalReport.bat which will run both quick and basic reports and create report files named by domain, computer, and date, in a folder named by domain and computer.
Remote reports may be created with Cindy-RemoteReport.bat. Append the remote computer name and make sure you have local admin rights on the target computer (only necessary for remote reports).
The batches with -All in their names will also create the Verbose reports which takes much longer and might cause script errors in some rare cases (but will not be harmful to your systems).

You may extend or alter the source code. I only ask you to keep a reference on the original author and on faq-o-matic.net.

No warranties, no support. Use at your own risk.

Nils Kaczenski, March 2014
faq-o-matic.net
