CA Client Automation

  • Private Community

  • 1.  psexec not recognised

    Posted Apr 25, 2016 10:45 AM

    Hello All,

    Good day and trust this email meet you well.

    I'm having some troubles when I deployed DSM Agent to number of machines and after successful deployment, I tried to access the machine's cmd remotely using the psexec command but I keep getting error "psexec is not recognized as an internal or external command, operable program or batch file".Prompt answers/workaround would be appreciated as soon as humanly possible.

     

    Thanks and Regards,

    Amosu



  • 2.  Re: psexec not recognised
    Best Answer

    Broadcom Employee
    Posted Apr 25, 2016 10:51 AM

    That has nothing to do with client auto is psexex installed or is it's install path in the path on the machine you are running psexex from.

     

     

     

    Sent from my Verizon, Samsung Galaxy smartphone



  • 3.  Re: psexec not recognised

    Posted Apr 25, 2016 10:56 AM

    Psexec is a Microsoft utility which must be downloaded and installed. It is not part of the ITCM client or manager.

     

     

     

     

    Steve McCormick, ITIL

    CA Technologies

    Principal Services Consultant

    Tel: +1-731-676-4223

    Stephen.McCormick@ca.com<mailto:Stephen.McCormick@ca.com>



  • 4.  Re: psexec not recognised

    Posted Apr 25, 2016 10:59 AM

    Hello Richard,

    Thanks for the prompt response. I will do the needful.

    Warm Regards,

    Amosu



  • 5.  Re: psexec not recognised

    Posted Apr 25, 2016 04:08 PM

    I dude.. I have used psexec in my environment.. Are you sure you've installed psexec before running it from cmd? search the .exe and try running it. It will show a "licensing" message.. Then, you'll be able to run it in you desktop.. it will rising a services on destination machine.

     

    Please, attach some images..