Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I've been struggling with this for a few hours and can't figure this out. I have two Windows 7 computers. One is my workstation that is using Powershell to do administrative maintenance. The other is the machine I'd like to use Powershell remoting on to execute remote Powershell cmdlets on.

On both computers, I've enabled Powershell remoting and added all computers to TrustedHosts with the * value. On the remote computer, I've started the Remote registry service and ensured that the DCOM, Winmgmt and the Winrm services are running. Firewall is disabled on remote machine too.

The cmdlet I try to run is:

Get-Process -ComputerName $name

Where $name is the name of the remote machine. I keep getting an error saying that it could not connect to the remote PC. I've also tried using the IP and I get the same error. These PCs are not in a domain.

I am able to do the following successfully:

Invoke-Command {get-Process} -ComputerName $name -Credential $creds

Where $name is the machine name and $creds is the user name and password for the remote computer's local Admin account. This gives me the same output I would expect.

While this is an acceptable workaround, I am curious, why doesn't using get-process with remoting work as it should? I've seen a few articles on the web suggesting people have had success with it on its own.

Each time I am using Powershell on my workstation with elevated privileges.

Any ideas?

share|improve this question
up vote 2 down vote accepted

Well, I'm afraid you're giving away the answer yourself.

Your admin account on the local machine, does not have admin privileges on the remote machine.

Get-Process doesn't accept credentials, so when you run

Get-Process -ComputerName remoteMachine 

you're authenticating as localMachine\Administrator, but when you invoke it and supply credentials, you're authenticating as remoteMachine\Administrator

share|improve this answer
Well the, I guess that was easy!! Thanks!! – amandion Nov 28 '12 at 13:59

Start the Remote Registry service, that worked for me on Win7.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.