>This is not a bad option and have considered it. Have you ever ran into a customer that would not allow wsh on the computers for security reasons? This was my only concern with going this route.
>

I've had users complain about it, until I demonstrated that you don't need to allow VBScript to be run in order to have the WSH COM objects available, and most generally accepted that disabling the WSH doesn't disable the functionality that makes it dangerous.