Secrets of PowerShell Remoting

Secrets of PowerShell Remoting

Remoting Basics

1. What is Remoting?
2. Examining Remoting Architecture
3. Enabling Remoting
4. Test Environment
5. Enabling Remoting
6. Core Remoting Tasks
7. Remoting Returns Deserialized Data
8. Enter-PSSession vs. Invoke-Command

Accessing Remote Computers

1. Setting up an HTTPS Listener
2. Certificate Authentication
3. Modifying the TrustedHosts List
4. Connecting Across Domains
5. Administrators from Other Domains
6. The Second Hop

Working with Endpoints (aka Session Configurations)

1. Connecting to a Different Endpoint
2. Creating a Custom Endpoint
3. Security Precautions with Custom Endpoints

Diagnostics and Troubleshooting

1. Diagnostics Examples
2. Standard Troubleshooting Methodology
3. Summary

Session Management

1. Ad-Hoc vs. Persistent Sessions
2. Disconnecting and Reconnecting Sessions
3. Session Options

PowerShell, Remoting, and Security

1. Neither PowerShell nor Remoting are a “Back Door” for Malware
2. PowerShell Remoting is Not Optional
3. Remoting Does Not Transmit or Store Credentials
4. Remoting Uses Encryption
5. Remoting is Security-Transparent
6. Remoting is Lower Overhead
7. Remoting Uses Mutual Authentication
8. Summary

Configuring Remoting via GPO

1. GPO Caveats
2. Allowing Automatic Configuration of WinRM Listeners
3. Setting the WinRM Service to Start Automatically
4. Creating a Windows Firewall Exception
5. Give it a Try!
6. What You Cant Do with a GPO