does it give you that "command prompt has been disabled by the admin" message when you open it?
if so there is a very easy way to get past that
Yes, the users get that message, and no, it isn't as easy as you think, plus I'm not willing to circumvent a corporate security policy and get my ass fired.
Rathe, using RunAs and running the scripts as an administrator is not an option as they are going to be run as a regular user. If it's a script that
I use to automate a few tasks, it doesn't matter because I still have access to the command prompt.
To give you an axample of what some of the scripts do (they are very simple), one I want to translate is called Where Am I? and it echos back to the user things like their username, their PC Name, the domain they are logged on to, which domain controller authenticated them, their version of Windows, uptime, IP Address and a couple of other little things if I remember correctly. It may not sound like much, but it's very useful.
Another script that was in the works before this all happened was really just using xcopy to copy changed files from a network share to a tech's laptop so he has access to these files while he's out on the road, replacing the current method of me burning 15-20 CD's every couple months and wasting my time.
Beyond all of these specific purposes,
I just want to learn it. I'm pretty good with batch scripting, I just kind of need something to bridge that knowledge into VBScript. Let's face it, batch scripts are a dying breed. With Monad coming (aka Windows Power Shell), it will be even deader.