So I have seen a number of people (me included) have seen this "access is denied" error message when trying to run scripts via a network drive.

So, is there anyone that knows how to turn off this security "feature", if in fact that is what this is.

Edited November 30, 200619 yr by Jazkal

I thought it may have been the the firewall, so I ran:

wpeutil disablefirewall

But that didn't resolve the error.

Jazkal,

I am having the same issue here. This needs to get fixed because I need to be able to run our scripts from the network as part of our corporate deployment strategy.

Post back if you hear anything.

I'll do the same

Edited November 30, 200619 yr by styxx_78

I'm trying to track it down. I'm wondering if it isn't some kind of IE7 security config issue built into Vista (Which PE2 is built on).

If I find a solution, I will post it here.

I wonder is User Access Control (UAC) is also incorporated into WinPE 2.0?

If so, I wonder if that could be the culprit and if it can be disabled. (It's soo annoying)

I just tested a WinPE 2 build with UAC disabled (assuming the reg key is the same as Vista) , and that didn't effect the Access is denied errors.

Edited November 30, 200619 yr by Jazkal

Ok, I think I have a working solution for the "access is denied" problem.

What I tested, and it works:

Trying to run a VBS script off a network mapped drive: z:\test.vbs

What needs to be changed:

Once you have your WinPEv2 wim mounted, you have to load the registry so you can make the changes.

example:

reg load HKLM\PE-SFT %MOUNTROOTDIR%\Mount\Windows\system32\config\software

Then load regedit and make these changes, you will have to add them because they aren't there.

[HKEY_LOCAL_MACHINE\PE-SFT\Microsoft\Windows\CurrentVersion\Policies\Associations]
"LowRiskFileTypes"=".com;.exe;.vbs"

Then unmount the reghive with:

reg unload HKLM\PE-SFT

Then you can continue on with your PE creation.

I have not tried what you posted above yet but here is what I have found.

I have been able to run .vbs scripts with no modification to my WinPe image so far.

Try specifying wscript as your script engine as follows.

c:\>wscript <script name>.vbs

Also, i was having trouble running .HTA files from a network location. I have made it further but it still is not working perfectly yet.

mshta.exe file.hta <username> <password>

By specifying mshta.exe to load, along with my credentials it seemed to load a partial HTA window, but it was completely grey. I am still not sure if it is a coding issue or the way it is being handled.

Jazkal,

Have you tried loading an hta from a network shre yet? Have you been successful?

Yes, I load a HTA file from a mapped network drive:

mshta.exe z:\hta\file.hta

This works without issues for me.

I do know that WinPE v2 has problems with running scripts/HTA's over a UNC network path. Meaning it won't allow it by design.

What components did you load when you created your WinPE?

WinPE-HTA-Package

WinPE-Scripting-Package

WinPE-XML-Package

WinPE-MDAC-Package

WinPE-WMI-Package

MDAC is the only one I did not load yet. I will try loading that one and try again.

I have actually opened a Premiere Support call with Microsoft on this one because I do not want to spend a lot of time on it. I hope they can help.

MDAC shouldn't have anything to do with it, unless your making SQL calls from within the HTA.

Have you tried loading just a basic HTA? see if that works?

I'm going to try that right now. The hta I was using does have componenets in it that do adress an SQL database that houses all of our software command lines.

then you do need the MDAC component.