As requested, here is the PDF version of this site:
New PDF version of this site minus tutorial(?.?MB)
Outdated PDF version of this site minus tutorial(1.8MB)
Really outdated PDF version of this site minus tutorial(1.3MB)
Outdated PDF version of the tutorial (1.6MB)
Really outdated PDF version of the tutorial (1.4MB)
NOTE: You will need a PDF viewer to view these docs but I
guess you know that already.
Ever had 2 PCs in similar or "Suppose to be similar" environments and things run differently. You suspect it's GPO-related but how can you prove it. MS' GPO testing utils will only tell you that GPO A,B and C were "applied" but nothing to check the actual changes in the registry. This program solve the "I swear the GPOs are the same on both machine" question.
This program does most of the grunt work by recording the registry values that are possible listed in the ADM files. As it runs your CPU near 100% for 10 minutes, it spits out a Log file for that machine. Do this on 2 machines and then you can compare and check for differences. How YOU compare the 2 log files will be up to YOU. (Hint: Windiff )
**** DISCLAMER: Like all free things: Run at your own risk. *****
At some point you will have to do some VBS editing. This will get you by:
The same people have a slightly updated 2.0 version that includes debugging for free for upto 25 lines. More than that they want ca$h. Since most scripts I do are less than 25 lines it's ok but the nag screen is annoying but at least it's not useless like their v3.0 demo. http://www.adersoft.com/vbsedit/vbsedit.msi
http://www.adersoft.com/ have an updated editor (v3.0) but it is a pain to tryout because it is 100% nagware. Try to debug anything and you'll see what I mean.
If you know of a Free VBS editor with debugging, let me know.
I was tired of wadding through all the images, going through
the same motions everytime.
This creates an updated menu of all images you have everytime you run the batch file.
It will look something like this:
**** DISCLAMER: Like all free things: Run at your own risk. *****
See the readme.html inside for installation instructions.