Layman’s Guide to PowerShell 2.0 remoting

Layman’s Guide to PowerShell 2.0 remoting (PDF)

Layman's guide to PowerShell 2.0 remoting 29713 downloads

This eBook got an update from the initial release. Here are the additions in the update.

Chapter 2
Enable remoting for only a specific network adapter
Remoting in an Enterprise

Chapter 3
Run script files on remote computers

Chapter 9
Added a note on Domain controller credential delegation
Updated a note on Windows XP/2003 support for CredSSP

Appendix A
Added some more FAQ

Appendix B
Remoting in an Enterprise by Jan Egil Ring

Errata

Nothing as of today. Please leave a comment here if you find errors in the guide.

21 Responses

Page 1 of 1
  1. eBook: Layman's guide to PowerShell 2.0 remoting

    [...] PowerShell.com’s Administrator’s guide to PowerShell remoting and wondering how is this new eBook different from what they released. Well, both these guides are same in the sense that they talk [...]

  2. Nigel Thomas
    Nigel Thomas at |

    I don’t have a comment

  3. Brecht Monkerhey
    Brecht Monkerhey at |

    excellent guide, clear and to the point.
    thanks!

  4. Tweets that mention Layman’s Guide to PowerShell 2.0 remoting – Ebook -- Topsy.com

    [...] This post was mentioned on Twitter by ShayLevy and Jim Poshible, Niklas Goude. Niklas Goude said: be sure to check out A Layman's Guide to #PowerShell V2 Remoting: http://bit.ly/ctAivK [...]

  5. Kindle for PowerShellers. Part 1. Notes and Highlighting « PowerShell In GUI Blog

    [...] 1. Layman’s Guide to PowerShell 2.0 remoting [...]

  6. Using the View PowerCLI cmdlets from another machine « « Virtu-AlVirtu-Al

    [...] Layman’s Guide to PowerShell 2.0 remoting [...]

  7. bbnetman.com » Blog Archive » From Ravikanth Chaganti

    [...] Layman’s Guide to PowerShell 2.0 remoting [...]

  8. Peruri
    Peruri at |

    getting access denied to the farm or you dont have permission when you have interactive remoting  and persistent session.
    on get-spsite.When checked on the sharepointserver eventlog on the remove server that I had session with I see the following error. SQL database login for ‘Dev_SharePoint_Configuration_Database’ on instance ‘SP2010SQLDEV’ failed. Additional error information from SQL Server is included below.

    Login failed for user ‘NT AUTHORITYANONYMOUS LOGON’.However, if i run the same command on the server, I get the results. It looks to me that the credentials are not being passed properly. What am I missing?

    When checked on the sharepointserver eventlog on the remove server that I had session with I see the following error.

    SQL database login for ‘Dev_SharePoint_Configuration_Database’ on instance ‘SP2010SQLDEV’ failed. Additional error information from SQL Server is included below.

    Login failed for user ‘NT AUTHORITYANONYMOUS LOGON’.

    However, if i run the same command on the server, I get the results.

    It looks to me that the credentials are not being passed properly. What am I missing?

  9. Ravikanth
    Ravikanth at |

    You need to use CredSSP for the SharePoint farm. Check this: http://www.ravichaganti.com/blog/?p=1230

  10. Get Full Control over your Exchange remote PowerShell session | Challenging Complexity...

    [...] for Remoting – Part 2 (Fan-In) Administrator’s Guide to Windows PowerShell Remoting Layman’s Guide to PowerShell 2.0 remoting Deep Dive video: Constrained PowerShell Endpoints – Aleksandar Nikolic Book: Microsoft Exchange [...]

  11. Get Full Control over your Exchange remote PowerShell session - Shay Levy

    [...] for Remoting – Part 2 (Fan-In) Administrator's Guide to Windows PowerShell Remoting Layman’s Guide to PowerShell 2.0 remoting Deep Dive video: Constrained PowerShell Endpoints – Aleksandar Nikolic Book: Microsoft Exchange [...]

  12. Бесплатные книги по PowerShell - wAdmin.ru

    [...] Автор – Ravikanth Chaganti Layman’s Guide to PowerShell 2.0 Remoting Скачать [...]

  13. Nine PowerShell eBooks - All completely free!

    [...] [...]

  14. Citrix and Powershell Remoting | Aman Dhally's Blog

    [...] MVP Ravikanth’s “Layman’s Guide to PowerShell Remoting” [...]

  15. New-RemoteProcess | rambling cookie monster

    [...] but collecting and perhaps acting upon the output might require a bit of work.  If you have PowerShell remoting set up in your domain and all systems have PowerShell, that might be a better [...]

  16. Free e-books for Windows administrators (updated) - 4sysops

    [...] Layman’s Guide to PowerShell 2.0 remoting [...]

  17. Keith Young
    Keith Young at |

    Ravi,

    First, thank you for putting together this ebook. I have found it quite useful and keep it nearby for reference when I am doing remoting with PowerShell.

    A comment about the ebook… Perhaps add a version/revision number in case you make updates to the ebook, that way people can cite which version they are asking questions about (I don’t know if you have ever updated it or not).

    And to my main question, quoting from your ebook:

    “By default, WinRM only enables http transport for accepting remoting requests. You can manually
    enable https transport using either winrm command or New-WSManIntance cmdlet. For now, let us not
    overwhelm with so much information. We will look at this in part 2 of this guide”

    [bold mine]

    Nowhere in the ebook do you cover off configuring of SSH transport. Was there supposed to be a second, separate book, or were you going to add another Part/Appendix to this one? Do you have plans to do so?

    Thanks again for this ebook!

    Cheers!

  18. santhosh
    santhosh at |

    Hi Ravi,

    I get the following error when i try to run a command on a remote computer, i have followed all the steps mentioned in your guide, Local and the remote machines are of WIN XP SP3 OS.

    [10.60.22.45] Connecting to remote server failed with the following error message : The WinRM client cannot process the

    request. Default authentication may be used with an IP address under the following conditions: the transport is HTTPS

    or the destination is in the TrustedHosts list, and explicit credentials are provided. Use winrm.cmd to configure Trust

    edHosts. Note that computers in the TrustedHosts list might not be authenticated. For more information on how to set Tr

    ustedHosts run the following command: winrm help config. For more information, see the about_Remote_Troubleshooting Hel

    p topic.

    + CategoryInfo : OpenError: (:) [], PSRemotingTransportException

    + FullyQualifiedErrorId : PSSessionStateBroken

    Thanks,

  19. Granular access via PowerShell Remoting | rambling cookie monster

    [...] Layman’s Guide to PowerShell Remoting; Ravikanth Chaganti [...]

Comments are closed, but trackbacks and pingbacks are open.

%d bloggers like this: