Microsoft help

MS: Using PsExec to get a remote shell

We we were having remote login issues when trying to connect to a domain joined server, but even server manger was failing to provide us with any real option of administering this server.


So we called on PsExec to save the day.

Download it here, and for ease of use extract it to the system32 folder location:

Once installed you can run:
psexec \\favdbmid01 cmd

This will give you a cmd shell session on the remote machine. I needed to change the password on the remote machine in order to login:
net user user_name  new_password

This didn’t fix the login issue…so I checked to see if there was any space issues on the c drive.
fsutil volume diskfree c:

I discovered that it was basically out of space, moved some files and was able to RDP.



2 thoughts on “MS: Using PsExec to get a remote shell”

  1. So, why did you opt for psexec when server 2012 has Powershell Remoting enabled out of the box? Sending credentials over the wire in cleartext via psexec is not state of the art anymore.

    The following command does the same but is secure due to Kerberos Tickets being used:
    Enter-PSSession -computername favdbmid01

    1. Hi megamorf,

      Thanks for the comment, but it’s not about the technology being new, it’s about the Enter-PSSession command not working – please see my post updated with an image of the problem.

      Kind regards.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s