Hi, I am trying to execute psexec command to remote machine. My command is psexec -u domain\user -p password \\machineName -c abc.bat I am trying from windows 7(64 bit) machine. The remote machines are xp and windows 7(32 and 64 bit). In XP machines, it is working and also in some windows 7 machines. But in some windows 7 machines it give message- "Could not start PsExec service on target machine. Access is denied." If I try to execute psexec command from XP machines, it works to all machines. Suddenly what happen I do not know but one of the windows 7 machine( where psexec was not starting) , psexec started. but not in other machines. Now I am very much confuse here exactly what happen. and what is the issue. Please help. It urgent. Thanks.

Hi, When opening the Command Prompt, please right click it and run as Administrator. Meanwhile, make sure the user has administrator privileges on target PC. If the issue persists, try to disable UAC on both sides. As far as I know the Security Level on Windows 7 is higher than the level on Windows XP. Therefore, 'psexec' works to all machines. Best Regards, Niki Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Hi, When opening the Command Prompt, please right click it and run as Administrator. Meanwhile, make sure the user has administrator privileges on target PC. If the issue persists, try to disable UAC on both sides. As far as I know the Security Level on Windows 7 is higher than the level on Windows XP. Therefore, 'psexec' works to all machines. Best Regards, Niki Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Hi, I had exacly the same issue today, only that I had many servers (2003, 2008 nad 2008 R2) Run command exacly as yours, from W7 SP1 and a elevated command window. It worked on 80% of the servers but on some it didn't work, I investigated it closer and found that all Server 2008 R2 rejected my calls in security log - with my login name from W7, not domain\user from the command. I loged in to my workstation with domain\Administrator and now the command was acceptet by all 200 servers without any problem. Hope this can help you in your investigation, it solved my issue. regards.

Hi, I had exacly the same issue today, only that I had many servers (2003, 2008 nad 2008 R2) Run command exacly as yours, from W7 SP1 and a elevated command window. It worked on 80% of the servers but on some it didn't work, I investigated it closer and found that all Server 2008 R2 rejected my calls in security log - with my login name from W7, not domain\user from the command. I loged in to my workstation with domain\Administrator and now the command was acceptet by all 200 servers without any problem. Hope this can help you in your investigation, it solved my issue. regards.

It's not going to work with UAC enabled for the account on the target machine.

JS2010 I don't believe that is true. All machines in my enviroment have UAC turned on and no user has Admin rights to the machine and I can access all machines. The solution is the one provided by Niki Han Even though you stating which user account to execute the command on the remote system it excutes the psexec command as the user that opened the command window. Right-clicking on cmd and hitting run as administrator then using the string with -u and specifying a user with admin rights to the machines you are attached to should work 90% or more of the time. I have come accross a few computers that even this didn't work and those machines actually had system errors that we had to fix. Thanks SeanMCTS: Windows 7

Shrug. Even if I try to use a remote account in the Administrators group, psexec will say 'Access is denied.' I would have to enable the remote literal 'Administrator' account to use psexec on it. But I don't use active directory, and UAC is at the default settings. Maybe there's some other policy I didn't change. The machine I'm launching psexec from is also Windows 2003.

Running psexec from an XP/Win2k3 PC against a Win7/Win2K8 target will work fine if you download Ver. 1.98 of PsExec with the new "-h" param. Unfortunately, it seems that running PsExec from a Win7/Win2K8 machine against a Win7/Win2K8 target, regardless of the "-u" and "-p" params on the PsExec command-line, those params are ignored and PsExec is being executed remotely with whatever user credentials I happen to be logged in locally with. I confirmed this by logging in locally on a Win7 PC with an account that has local admin privs on the remote Win2K8 target and I didn't even need to include the -u or -p params to successfully start the PsExec service on the remote system. The -u and -p params are totally ignored. The only solution anyone seems to be offering is to use the "Runas" command to execute PsExec and forget the -u -p params. Unfortunately, Runas won't accept a password param and I use it iteratively in my script to connect to - in some cases - 60 different systems. Typing in the password 60 times in a row is a real bummer and using the Runas /savecred param is just plain frightening. Hopefully, someone has a better solution.

any solution about it ? thxShould "Hi", "Thanks" and taglines and salutations be removed from posts? http://meta.stackoverflow.com/questions/2950/should-hi-thanks-and-taglines-and-salutations-be-removed-from-posts

Running psexec from an XP/Win2k3 PC against a Win7/Win2K8 target will work fine if you download Ver. 1.98 of PsExec with the new "-h" param. Unfortunately, it seems that running PsExec from a Win7/Win2K8 machine against a Win7/Win2K8 target, regardless of the "-u" and "-p" params on the PsExec command-line, those params are ignored and PsExec is being executed remotely with whatever user credentials I happen to be logged in locally with. I confirmed this by logging in locally on a Win7 PC with an account that has local admin privs on the remote Win2K8 target and I didn't even need to include the -u or -p params to successfully start the PsExec service on the remote system. The -u and -p params are totally ignored. The only solution anyone seems to be offering is to use the "Runas" command to execute PsExec and forget the -u -p params. Unfortunately, Runas won't accept a password param and I use it iteratively in my script to connect to - in some cases - 60 different systems. Typing in the password 60 times in a row is a real bummer and using the Runas /savecred param is just plain frightening. Hopefully, someone has a better solution.

Confirmed...do a "run as" for your command prompt (with the account you will need on the remote system) and use the -h param for psexec and don't even bother with the -u and -p params.

I know You already have your answer, but you should also try -h key. For example: psexec -u Domain\Username -p password \\targetmachine -c -h program.bat