Windows PowerShell Remoting:Definitely NOT Just for Servers

Don JonesSenior Partner and Principal TechnologistConcentrated Technology, LLC

WCL321

Agenda

Why Remoting?The Many Forms of Remote ControlWinRM / WS-MAN: The Enabling TechnologyEnabling and Configuring Remoting1-to-1 Remoting1-to-Many Remoting and Deserialized ObjectsBackground JobsSessions, Session Options, and MoreImplicit RemotingDemo-Heavy Session!

2

Why Remoting?

Strategic way to move from single-machine management to multi-machine managementUsable on client and server computersAvailable for Windows XP and later (with Windows PowerShell v2 installed); installed by default on Windows 7 and later (not enabled)Many different modes of use

The Many Forms of Remote Control

Windows Management Instrumentation (WMI)Utilizes RPCs for communicationsPrimarily for retrieving management info

A –computername parameterE.g., Get-Service and Get-ProcessUtilizes underlying technology for communicationsAvailable on only a few cmdlets

PowerShell RemotingGeneric, good for all commandsUtilizes WinRM / WS-MAN for communications“The New Standard”

WinRM and WS-MAN

WS-MAN is the protocolWinRM is the implementing serviceWSMAN: drive in PowerShell exposes configurationEasy to set up in a domain environment; a bit tricky in a non-domain environment

Help about_remote_troubleshootingWinRM is a “traffic director;” must register endpoints that will receive WinRM traffic

Any given app can register multiple endpointsWinRM traffic occurs over HTTP by default (not port 80)

Troubleshooting

WinRM can be a complex beast to troubleshoot During the demo we’ll also look at the PSDiagnostics module and how you can gather detailed troubleshooting / diagnostic information on WinRM activities

Security

Remote connections are logged as a Network Login – like accessing a client’s C$ shareActivity within the shell itself is not captured to a log

Difficult to fake out because profiles don’t run under a remote connectionPretty much requires you to trust your trusted Administrators

Only open to admins by defaultGPO settings provide some nice options

Requirements

Windows XP*, Windows Vista*, Windows 7Windows Server 2003*, Windows Server 2008*, Windows Server 2008 R2.NET Framework v2 (v3.51 is good, having v4 installed is fine also)*Must install Management Framework Core; see Q968930

Client-Specific Applications

Troubleshooting (TroubleshootingPack module on Windows 7 and beyond)File, folder, and registry managementCollecting inventory (more efficient than pure WMI)Anything that might otherwise require a manual visitWe’ll see all of these demonstrated in a moment!

It’s All Demo From Here

Let’s spend some time working with WinRM and remotingPlease raise any questions as we go!

demo

Remoting: All There is to Know

Get the Book!

Learn Windows PowerShell in a Month of LunchesAvailable in the TechEd bookstoreAlso available with a Companion DVD that includes 99 HD narrated demos from the book’s chapters

Track Resources

Don’t forget to visit the Cloud Power area within the TLC (Blue Section) to see product demos and speak with experts about the Server & Cloud Platform solutions that help drive your business forward.You can also find the latest information about our products at the following links:

Windows Azure - http://www.microsoft.com/windowsazure/

Microsoft System Center - http://www.microsoft.com/systemcenter/

Microsoft Forefront - http://www.microsoft.com/forefront/

Windows Server - http://www.microsoft.com/windowsserver/

Cloud Power - http://www.microsoft.com/cloud/

Private Cloud - http://www.microsoft.com/privatecloud/

Resources

www.microsoft.com/teched

Sessions On-Demand & Community Microsoft Certification & Training Resources

Resources for IT Professionals Resources for Developers

www.microsoft.com/learning

http://microsoft.com/technet http://microsoft.com/msdn

Learning

http://northamerica.msteched.com

Connect. Share. Discuss.

Complete an evaluation on CommNet and enter to win!

Scan the Tag to evaluate this session now on myTech•Ed Mobile