DEP Disabled but still intercepting script files referenced on sha

Hello All,

Am hoping that someone here will be able to provide some insight on this
problem:
VBS scripts that run locally without issue (after DEP disabled) will not run
when referenced from their remote (file server share,
\\server\share\whatever.vbs) location. The DEP type message box pops up even
though DEP is disabled globally on the server via the boot.ini file.
When run within a scheduled job, the scripts just die silently and fail to
complain in any log file. On non SP1 2003 machines without DEP the scripts
function normally when referenced from their remote location as indicated
above.

Platform: Windows 2003 SP1, Intel XEON processors - Hardware DEP support,
DEP turned off with /AlwaysOff switch in boot.INI. Verified on server by
running wmic OS Get DataExecutionPrevention_SupportPolicy.

Anyone have any insight as to what I am missing here?

--
FourEyes
www.fixitcrew.com

mr_unreliable
Thu Jul 13 11:38:18 CDT 2006

hi FourEyes,

I don't have any answer, just some reinforcement.

I had an actX control that worked before "Data Execution Protection"
and not afterwards.

I tried turning dep off, as described in the microsoft documentation,
and that had NO EFFECT. That is, I continued to get the dep error.

The remedy I used was to change my code. Instead of executing code
in (vb) space allocated for data, I used an api call to allocate
some memory with both data and execute privileges, and then stored
my instructions in there. That worked.

This is not exactly the situation you describe, and I don't expect
that it will be helpful -- except to the extent that the only
remedy I could come up with was to hunt down what was causing the
error and change code to avoid it....

Good Luck, jw

FourEyes wrote:
> Hello All,
>
> Am hoping that someone here will be able to provide some insight on this
> problem:
> VBS scripts that run locally without issue (after DEP disabled) will not run
> when referenced from their remote (file server share,
> \\server\share\whatever.vbs) location. The DEP type message box pops up even
> though DEP is disabled globally on the server via the boot.ini file.
> When run within a scheduled job, the scripts just die silently and fail to
> complain in any log file. On non SP1 2003 machines without DEP the scripts
> function normally when referenced from their remote location as indicated
> above.
>
> Platform: Windows 2003 SP1, Intel XEON processors - Hardware DEP support,
> DEP turned off with /AlwaysOff switch in boot.INI. Verified on server by
> running wmic OS Get DataExecutionPrevention_SupportPolicy.
>
> Anyone have any insight as to what I am missing here?
>