Posted by admin on 11/17/2010 9:38 PM | Comments (0)

The information below is not an attempt to generalize how to set up powershell remoting.  It's a single experience I've had in a test environment; it might help someone else, and it might not.  Be warned.

Environment

Client

Client machine was Windows 7 64-bit

No software needed to be uninstalled or installed

Server

Server machine was Windows Server 2008 64-bit

I uninstalled Powershell feature, as per this article, http://technet.microsoft.com/en-us/library/dd351188.aspx, thinking I would then install Windows Management Framework Core package as per this article, http://support.microsoft.com/?kbid=968930.  However, after removing the Powershell feature as per the first article, I then tried to install the core package.  It kept saying I didn't need the update.  I checked further, and it turns out the core package was already installed.  Must have been an automatic update or something.

Test

After getting the right software installed, I fired up powershell on both machines.  I immediately tried to get my computer name on the local machine, jwestp14, and the remote server, sv1.  You can see the error I got when I tried it for sv1.

509e0201-48bc-4f77-9db2-0c335ef22f90

So, I did a little research and found this article, http://www.computerperformance.co.uk/powershell/powershell_wsman.htm.  I'll summarize what I did here:

Setting up the client

At the powershell prompt, enter the following:

cd wsman::localhost\client

- I got prompted to start the winrm service, which i did.

set-item trustedhosts sv1

- this gave me the result below.  Note I had to confirm modifying the trustedhosts list.

restart-service winrm

- this restarted the service, obviously.

Ok, so this set up my client correctly.  I tried to get the remote computername again, and got this new error.

fdff333d-7345-4aa5-aa0e-3bd4308ac516

The most amazing thing is how verbose a lot of the powershell errors are.

Setting up the server

I went to the server and ran the following command:

winrm quickconfig

I got the following result.

1321bf4b-2e7e-41aa-a43b-864c03f50022

Successful result

I then went back to my client and ran the following command.

b71dff2f-0ee7-4150-93d4-9b8243b3dc5a

Voila!

Add comment

  Country flag

biuquote
  • Comment
  • Preview
Loading