Client server remoting with PowerShell

11
Secrets of Client and Server Remote Control with Windows PowerShell Don Jones Concentrated Technology http:// ConcentratedTech.com

description

 

Transcript of Client server remoting with PowerShell

Page 1: Client server remoting with PowerShell

Secrets of Client and ServerRemote Control

with Windows PowerShell

Don Jones

Concentrated Technology

http://ConcentratedTech.com

Page 2: Client server remoting with PowerShell

This slide deck was used in one of our many conference presentations. We hope you enjoy it, and invite you to use it

within your own organization however you like.

For more information on our company, including information on private classes and upcoming conference appearances, please

visit our Web site, www.ConcentratedTech.com.

For links to newly-posted decks, follow us on Twitter:@concentrateddon or @concentratdgreg

This work is copyright ©Concentrated Technology, LLC

Page 3: Client server remoting with PowerShell

Title slide

• Why Remoting?• The Many Forms of Remote Control• WinRM / WS-MAN: The Enabling Technology• Enabling and Configuring Remoting• 1-to-1 Remoting• 1-to-Many Remoting and Deserialized Objects• Background Jobs• Sessions, Session Options, and More• Implicit Remoting

• Demo-Heavy Session!

3

Page 4: Client server remoting with PowerShell

Why Remoting?

• Strategic way to move from single-machine management to multi-machine management

• Usable on client and server computers• Available 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

Page 5: Client server remoting with PowerShell

The Many Forms of Remote Control

• Windows Management Instrumentation (WMI)● Utilizes RPCs for communications● Primarily for retrieving management info

• A –computername parameter● E.g., Get-Service and Get-Process● Utilizes underlying technology for communications● Available on only a few cmdlets

• PowerShell Remoting● Generic, good for all commands● Utilizes WinRM / WS-MAN for communications● “The New Standard”

Page 6: Client server remoting with PowerShell

WinRM and WS-MAN

• WS-MAN is the protocol• WinRM is the implementing service• WSMAN: drive in PowerShell exposes configuration• Easy to set up in a domain environment; a bit tricky in a

non-domain environment● Help about_remote_troubleshooting

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

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

Page 7: Client server remoting with PowerShell

It’s All Demo From Here

• Let’s spend some time working with WinRM and remoting

• Please raise any questions as we go!

• I will capture a transcript of my shell activity● Download next week from

ConcentratedTech.com (“Downloads”)

Page 8: Client server remoting with PowerShell

DEMOEnabling and Configuring Remoting

1-to-1 Remoting

1-to-Many Remoting

Background Jobs

Sessions and Session Configuration

Implicit Remoting

Page 9: Client server remoting with PowerShell

Final Q&A

• Text DONJ to 50500 for contact info

• See me for add’l resources

● Books● Workshop recordings● Demo videos● Etc

• Slide decks posted to ConcentratedTech.com by next week

Page 10: Client server remoting with PowerShell

Your Feedback is Important

Please fill out a session evaluation form drop it off at the conference registration

desk.

Thank you!

Page 11: Client server remoting with PowerShell

This slide deck was used in one of our many conference presentations. We hope you enjoy it, and invite you to use it

within your own organization however you like.

For more information on our company, including information on private classes and upcoming conference appearances, please

visit our Web site, www.ConcentratedTech.com.

For links to newly-posted decks, follow us on Twitter:@concentrateddon or @concentratdgreg

This work is copyright ©Concentrated Technology, LLC