concept remote computer in category powershell

This is an excerpt from Manning's book Windows PowerShell in Action, Third Edition. Login to get full access to this book.

The core of PowerShell remoting is Invoke-Command (aliased to icm). This command allows you to invoke a block of PowerShell script on the current computer, on a remote computer, or on a thousand remote computers. Let’s see some of this in action. Microsoft releases patches for Windows on a regular basis. Some of those patches are critical, in that they resolve security-related issues, and as an administrator you need to be able to test if the patch has been applied to the machines for which you’re responsible. Checking a single machine is relatively easy—you can use the Windows update option in the control panel and view the installed updates as shown in figure 1.2.

PS> Invoke-Command -ScriptBlock {
  Invoke-Command -ScriptBlock {
    Get-Process lsass } -ComputerName W16DSC01
} -ComputerName W16TGT01

[W16DSC01] Connecting to remote server W16DSC01 failed with the following
   error message : WinRM cannot process the request. The following error
   with errorcode 0x8009030e occurred while using Kerberos authentication:
   A specified logon session does not exist. It may already have been
   terminated. Possible causes are:
  -The user name or password specified are invalid.
  -Kerberos is used when no authentication method and no user name are specified.
  -Kerberos accepts domain user names, but not local user names.
  -The Service Principal Name (SPN) for the remote computer name and port does not exist.
  -The client and remote computers are in different domains and there is no trust between the two domains.
 After checking for the above issues, try the following:
  -Check the Event Viewer for events related to authentication.
  -Change the authentication method; add the destination computer to the WinRM TrustedHosts configuration setting or use HTTPS transport.
 Note that computers in the TrustedHosts list might not be authenticated.
   -For more information about WinRM configuration, run the following command: winrm help config. For more
information, see the about_Remote_Troubleshooting Help topic.
    + CategoryInfo          : OpenError: (W16DSC01:String) [], PSRemotingTransportException
    + FullyQualifiedErrorId : 1312,PSSessionStateBroken
    + PSComputerName        : W16TGT01

copy

Figure 13.5. Workflow restarting a remote computer

13.1.4. Starting jobs on remote computers

PowerShell is designed for administering remote computers, so it follows that you can also create and manage jobs on remote computers.

This is an excerpt from Manning's book PowerShell Deep Dives. Login to get full access to this book.

WinRM has to spin up a runspace (a PowerShell process) on the remote computer. That includes setting several options for locale, timing, and so on, as shown in figure 7.

The technology called Performance Logs and Alerts (PLA) is both a protocol and a software component for logging diagnostic data on remote computers or on local computers as well. The software component is a set of DCOM interfaces. To summarize, PLA allows you to