Discussion:
psexec could not start. access is denied
j***@cais.unimas.my
2010-05-20 04:16:20 UTC
Permalink
-------------------------------------------------------------------------
wpkg-users mailing list archives >> http://lists.wpkg.org/pipermail/wpkg-users/
Troy Hamilton
2010-05-20 15:35:02 UTC
Permalink
Hello list,
\\myserver\wpkg\wpkg.js /qb SETTINGSFILE=\\myserver\settings.xml
BUT it prompted me psexec could not start \\myserver\wpkg\wpkg.js on
mycomputer. Access is denied.
How to troubleshoot this matter?? Pls help.. Thanks
Gloria,

Does the "Domain Computers" group have read and execute permissions at both
the share and filesystem level for "\\myserver\wpkg"? At least on an Active
Directory domain, the "Everyone" or "Domain Computers" group needs
read/execute access at the share level, and the "Everyone" or "Domain
Computers" group needs read/execute access for the "wpkg" directory (ntfs
permissions).

In order to test this, open a command prompt running as the SYSTEM user on
one of your workstations: http://wpkg.org/SYSTEM_user_Command_Prompt

Then, try to list the directory in which wpkg.js resides:

dir \\myserver\wpkg

If you get "Access is denied," then the permissions are not set correctly.

Cheers,

--Troy
Tomasz Chmielewski
2010-05-21 18:34:42 UTC
Permalink
Post by Troy Hamilton
In order to test this, open a command prompt running as the SYSTEM user
on one of your workstations: http://wpkg.org/SYSTEM_user_Command_Prompt
dir \\myserver\wpkg
If you get "Access is denied," then the permissions are not set correctly.
And when permissions are fixed, it still will not work I think?

I.e. \\myserver\wpkg\wpkg.js should be started with "cscript" interpreter.
--
Tomasz Chmielewski
http://wpkg.org
-------------------------------------------------------------------------
wpkg-users mailing list archives >> http://lists.wpkg.org/pipermail/wpkg-users/
Troy Hamilton
2010-05-21 21:20:35 UTC
Permalink
Post by Troy Hamilton
In order to test this, open a command prompt running as the SYSTEM user
Post by Troy Hamilton
on one of your workstations: http://wpkg.org/SYSTEM_user_Command_Prompt
dir \\myserver\wpkg
If you get "Access is denied," then the permissions are not set correctly.
And when permissions are fixed, it still will not work I think?
I.e. \\myserver\wpkg\wpkg.js should be started with "cscript" interpreter.
Yes, wpkg.js should still be executed by the cscript interpreter. In my
case I use the recommended wpkg.bat included in the wpkg download.

In my environment, when the permissions are set correctly, the SYSTEM
account is able to list the share's directory contents with the dir
command. We have, however, explicitly added all of our fileservers "trusted
domains" list under
HKLM\SOFTWARE\Policies\Microsoft\Windows\CurrentVersion\Internet
Settings\ZoneMap\Domains, so that might be why others would have different
results.

Cheers,

--Troy

Loading...