>I was called yesterday by the base data security officer and asked to attend a meeting about eliminating WSH base wide.
>
>My first question is, can this really be done? Eliminating WSH from everyones computer?
>

Yes, you can remove the WSH from all systems. It's done via the Add/Remove Programs applet in Control Panel.

>My second question is to anyone who is familiar with WSH is, would this cripple windows in anyway?
>

Big time. If you use IIS, many features of ASP will refuse to run. Many VB applications use the Scripting.FileSystemObject to perform their file system operations. Forget access to a regular expression parser in a batch process. Win2K relies on the WSH services heavily. So do client-side services - WSH handles JScript (not the same thing as Java) as well as VBScript. I suggest taking a run out to the Win32 Scripting Journal web site in my sig block.

>Third, would this cause future problems when upgrading any windows product?
>

I'm not absolutely certain of this, but I think that the WIndows Installer used by O2K and other products leverages WSH; I am not positive that this is the case, since it might rely on the underlying APIs which WSH exposes.

>Since I have just started to look at WSH and how it can help me in VFP, the division thought it would be beneficial if I went to the meeting.
>

I suggest bringing firearms and lots of ammo. Once you see how easy WSH makes your life, it'd be easy to plead justifiable pesticide, or temporary insanity. Use hollowpoint ammo; .45ACP or 9mm, especially the kind that explodes when it hits something should get your point across.