>>Side note to Bruce: Is your LAN Central also going to check for the Shell.Application object? It can do many of the same things that the WSH did. What would they do in that case? They can't rename Shell32.dll.
>
>No, they didn't ostracize that. It is in use already anyway, so they can't disallow it. They did run a check to make sure no one was actively using WSH in a real-time app yet, before disabling it.
>
>You guys are right, the IT Secure people are really acting paranoid lately. Blocking websites, disabling WSH, trying to force NT lockdowns (but no one will move to NT on the main network while that rule exists).
>
>The politics of it all seems to be they are trying to force us into independent subnets, for whatever reason. That will cost a lot in money and network communication capability, but we will eventually gain more freedom, also.

Bruce,

I feel for you and your fellow department members. By simply removing the WSH they've deprived you of a tool that could be used to make your job easier, and you and your users more productive. I really sympathize.