ObjShell.Run "CmdKey /Add:ServerName /User:DOMAIN\serviceAccount "PsExec \\ServerName /H /S /U DOMAIN\serviceAccount C:\DIR\start. It worked for me being an admin, but a standard user WMI worked, but they wanted to see the entire start-up process (huge CMD files on server, gotta love IBM's Java stuff.), and PsExec does that. Give them local Admin on their computers or the servers.
There is also a WMI-driven GUI to view the service states. When complete, the PsExec Windows service will be stopped and removed. Execute the program under a parent process of psexesvc. Create and start a Windows service on the remote computer called PsExec. I created an HTA application to allow non-Administrator users to start or stop certain services on an application server. How PsExec Works on Remote Computers Create a PSEXESVC. Psexec.exe \\MACHINE_NAME_HERE -i notepadĪwesome! Thank you for this one. According to this thread, you can cache credentials before executing psexec:Ĭmdkey.exe /add:MACHINE_NAME_HERE /user:MACHINE_NAME_HERE\Administrator /pass:PASSWORD_HERE This is because psexec still tries to access the ADMIN$ share with your local credentials, before executing your command as another user. Here i found the working way - thanks JelmerS: Disabling UAC (EnableLUA=0, ConsentPromptBehaviorAdmin=0, LocalAccountTokenFilterPolicy=1) did not work, turning off the Firewalls did It took me hours to find a working way to PsExec between 2 Windows 7 Computers with non-Admin user starting PsExec.
#Psexec could not start cmd c password
Instead of using /savecred I save the password to a temp file and then redirect that to input of runas, like this: echo "password" > pwdrunas /env /netonly /user:Domain\username "psexec.exe cmd.exe" < pwddel pwd Hopefully, someone has a better solution.
Typing in the password 60 times in a row is a real bummer and using the Runas /savecred param is just plain frightening. Unfortunately, Runas won't accept a password param and I use it iteratively in my script to connect to - in some cases - 60 different The only solution anyone seems to be offering is to use the "Runas" command to execute PsExec and forget the -u -p params.
#Psexec could not start cmd c Pc
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. Ignored and PsExec is being executed remotely with whatever user credentials I happen to be logged in locally with. 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 Running psexec from an XP/Win2k3 PC against a Win7/Win2K8 target will work fine if you download
0 kommentar(er)
