Is your server running slowly?  Check with SolarWinds ipMonitor.

Get your free evaluation copy of ipMonitor here

---

Guy's Top 10 Free Tools

1) FreePing
2) Network Monitor
3) Xobni
4) PuTTY (UNIX)
5) IP SLA Monitor
6) BgInfo
7) Net-SNMP
8) CatTools 
9) Exchange Monitor
10) WinDiff

Windows PowerShell WinRm and WSMan

Windows PowerShell WinRm and WSMan

To get PowerShell's remoting capability working fully, you need the extra shell which is supplied by WinRm.  Even after the WinRm install completes successfully, you often need to tweak its config settings before the remote sessions become operational.

Remoting in Microsoft PowerShell with WinRm and WSMan

• Preliminary Discussion of WinRm
• WinRm Problem - WSMan Solution
• WSMan Example which Connects to the Client Sub-folder
• Basic PowerShell Remoting Commands

 ♣

Preliminary Discussion of WinRm

WinRm is the underlying engine or resource for PowerShell remoting; it is also the name of the additional executable that you need to download from the Microsoft Connect site.  Once installed, you can access WinRm directly from the 'DOS' command line, or better still, check and amend settings with PowerShell's own WSMan: provider.

WinRm Problem - WSMan Solution

In order to get the PSSession part of PowerShell's 'remoting' up and working you need to change WinRm settings such as TrustedHosts.  To achieve this goal we need to enter what PowerShell calls the WSMan namespace.  (The other alternative is to use cmd and call for WinRm -?)

Preamble: As a preliminary you could practice with 'cd' (Change directory) at the PowerShell command line, for example:
cd c:
or
cd c:\windows

Entering WSMan namespace

cd wsman  (Fails we need that colon)

cd wsman:  (Succeeds now we can access the wsman 'area', 'namespace' or 'drive'.)

WSMan Example which Connects to the Client Sub-folder

Rather than a succession of short steps, first to localhost, then to client, we could use one longish path statement.  Dir displays the settings stored in the client sub-folder.

TrustedHosts Goal:  To set, or change TrustedHosts so that any machine can connect remotely.

cd wsman:
cd localhost\client
dir

A more restrictive approach would be to set the value for TrustedHosts to a named machine.

Set-Item TrustedHosts BigServer

Troubleshooting Remote Connection

One common problem is ERROR: Access is denied.
Solution: Launch PowerShell with elevated rights, in simple language: Run as administrator.

Summary of Windows PowerShell WinRm and WSMan

To make sure that PowerShell's remoting is not restricted we often need to check the client settings. For this we can use cmd and WinRm, or better, PowerShell and WSman.  A common use of this technique is to change the TrustedHosts from nobody to everybody. 

See more Microsoft PowerShell tutorials

• PowerShell Home  • Introduction  • Dreams  • 3 Key Commands  • Cmdlet scripts  • Real life tasks

• Remote PowerShell  • -Online  • WinRm and WSMan  • Invoke-Command  • Jobs  -asJob   • PowerShell

Please write in if you see errors of any kind.  Please report any factual mistakes, grammatical errors or broken links, I will be happy to not only to correct the fault, but also to give you credit.

 *