>>Install WSH first, and then launch things wrapped in WSH scripts! This lets you use some of the command line switches when installing the Setup Wizard install, and gives you a mechanism for pre-setup executables! You should also check on things like DCOM that might be required. And while you're at it, use the Drives collection of Scripting.FileSystemObject to sniff out the local drive with the most free diskspace, and use the FSO's TextFile operations to roll your CONFIG.FPW based on what you sniff out...the more you use it, the more you'll appreciate the strength of having a lightweight scripting tool for installation adjunct operations. You'll want to pick up Windows Script Host Programmer's Reference, and possibly VBScript Programmer's Reference, both from Wrox Press - see FAQ #7885 for my recommendations on WSH sources.
>
>Uh-oh, I sense some fervor here :) Okay, I'll look into it. It is definitely neat so far with the shortcut stuff. I still can't spend any budget money, can you believe it? The fiscal year started in October, and we still haven't gotten clearance...
>
>I have no problem with DCOM, everyone has that. What's a good way to check to see if WSH is installed? I suspect it's already on some machines, since I already had it on one of my two - and I guess while I'm at it, do I need to check version?

HKEY_CLASSES_ROOT\Scripting.FileSystemObject and HKEY_CLASSES_ROOT\Wscript.Shell in the registry. I do not see a reason not to deploy the self-installer unless someone is using the new beta. I'd upgrade them to the current 5.1 release to get the latest VBScript and WSH 2.0 versions. If you want to use Script Components (you can build COM Objects from WSH scripts that can sink and surface events) you'll want to download the compiler and debugger and the one added runtime component. The site is well-documented and has all you'll need to get started, including some simple tutorials.