Look at pstools from sysinternals. You can remotely execute an application
(or script) on any computer that you have the necessary rights and
permissions. If you dont' have these tools you're working too hard. Should
be in every admin's toolkit.
Look at pstools from sysinternals. You can remotely execute an application
(or script) on any computer that you have the necessary rights and
permissions. If you dont' have these tools you're working too hard. Should
be in every admin's toolkit.
I seem to recall that psexec will send clear text password. Correct me
if I am wrong. Also, I think the machines that the script will be
running on has to have file and sharing enable too? This might now work
for us as majority of our machines has F and P turned off.
Addition to last post. If you are logged in as a domain admin, you won't
need to send a password on the command line, you'll have admin rights on all
domain computers.
It's not documented but the remote execution of commands needs the
ADMIN$ share, so yes file and printer sharing is needed for this to
work. I ran into this problem myself "why doesn't this work?" when I
tried to use a remote execution/install of a piece of software...
You can safely enable F&P sharing though, since you can prevent any
changed to shares or the creation of shares on workstations through a
simple GPO setting on the DC.
Want to reply to this thread or ask your own question?
You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.
