Ah... here's the distinction!
I was referring to administrative scripts on my servers. We have no scripts on workstations - in fact, we have no workstations that we support! I've never enabled scripting on a user workstation (other than login scripts, and then the KIX executable is usually on the login server). I always utilize scripts on the servers for the admins that support them, however. They're restricted to admin access for execute.
We're effectively an ASP - we have a few hundred servers that we manage, and often utilize scripting tools - .KIX and .PL - to accomplish and automate our tasks. Only people on the administrative staff have access to these systems (via console - all other access is via application such as web, SQL, and such). The only user's we have that can log on to the server and possibly execute these commands are our own admin and support staff. Further, the KIX executable is in the same folder (with same access perms) as the scripts, so a "rogue" script should be of little consequence.
Does this change your perspective any?
Glenn
_________________________
Actually I
am a Rocket Scientist!
