Client server remoting with PowerShell

958 views

Published on

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
958
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
17
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Client server remoting with PowerShell

  1. 1. Secrets of Client and ServerRemote Controlwith Windows PowerShell<br />Don Jones<br />Concentrated Technology<br />http://ConcentratedTech.com<br />
  2. 2. 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.<br />For more information on our company, including information on private classes and upcoming conference appearances, please visit our Web site, www.ConcentratedTech.com. <br />For links to newly-posted decks, follow us on Twitter:@concentrateddon or @concentratdgreg<br />This work is copyright ©Concentrated Technology, LLC<br />
  3. 3. Title slide<br />Why Remoting?<br />The Many Forms of Remote Control<br />WinRM / WS-MAN: The Enabling Technology<br />Enabling and Configuring Remoting<br />1-to-1 Remoting<br />1-to-Many Remoting and Deserialized Objects<br />Background Jobs<br />Sessions, Session Options, and More<br />Implicit Remoting<br />Demo-Heavy Session!<br />3<br />
  4. 4. Why Remoting?<br />Strategic way to move from single-machine management to multi-machine management<br />Usable on client and server computers<br />Available for Windows XP and later (with Windows PowerShell v2 installed); installed by default on Windows 7 and later (not enabled)<br />Many different modes of use<br />
  5. 5. The Many Forms of Remote Control<br />Windows Management Instrumentation (WMI)<br />Utilizes RPCs for communications<br />Primarily for retrieving management info<br />A –computername parameter<br />E.g., Get-Service and Get-Process<br />Utilizes underlying technology for communications<br />Available on only a few cmdlets<br />PowerShell Remoting<br />Generic, good for all commands<br />Utilizes WinRM / WS-MAN for communications<br />“The New Standard”<br />
  6. 6. WinRM and WS-MAN<br />WS-MAN is the protocol<br />WinRM is the implementing service<br />WSMAN: drive in PowerShell exposes configuration<br />Easy to set up in a domain environment; a bit tricky in a non-domain environment<br />Help about_remote_troubleshooting<br />WinRM is a “traffic director;” must register endpoints that will receive WinRM traffic<br />Any given app can register multiple endpoints<br />WinRM traffic occurs over HTTP by default (not port 80)<br />
  7. 7. It’s All Demo From Here<br />Let’s spend some time working with WinRM and remoting<br />Please raise any questions as we go!<br />I will capture a transcript of my shell activity<br />Download next week from ConcentratedTech.com (“Downloads”)<br />
  8. 8. Enabling and Configuring Remoting<br />1-to-1 Remoting<br />1-to-Many Remoting<br />Background Jobs<br />Sessions and Session Configuration<br />Implicit Remoting<br />
  9. 9. Final Q&A<br />Text DONJ to 50500 for contact info<br />See me for add’l resources<br />Books<br />Workshop recordings<br />Demo videos<br />Etc<br />Slide decks posted to ConcentratedTech.com by next week<br />
  10. 10. Your Feedback is Important<br />Please fill out a session evaluation form drop it off at the conference registration desk.<br />Thank you!<br />
  11. 11. 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.<br />For more information on our company, including information on private classes and upcoming conference appearances, please visit our Web site, www.ConcentratedTech.com. <br />For links to newly-posted decks, follow us on Twitter:@concentrateddon or @concentratdgreg<br />This work is copyright ©Concentrated Technology, LLC<br />

×