PowerShell Master Class - PowerShell Remoting 

Awesome video. No one has covered RM in depth and in a simple manner so that everyone can understand. Greatly appreciated.

I would not mind paying for such an amazing stuff. Thank you John \m/

Thanks John! You exhaust the subject with every video! Cannot express how grateful I am. Cheers!

Next Level Mr S. Even though the PS Core is a little outdated it's all applicable. Thank you for sharing your knowledge and making all of us better.

Hey John, thanks for the time and effort on these walkthroughs. I think these courses are pretty amazing because you're giving foundational coverage. It's our proactivity in projects and use cases to evolve separate specialization skills in our own time. Keep up the great work! Really appreciate this quality of teaching.

Thanks for this video. It is super useful. Keep teaching us!

Exceptional tutorials ... really! Thank you very very much for sharing!!!

Thank you very much john so far! you are killin it

Thanks John! What a Gem of a video! Have to manage lot of Windows Server Firewall rules across many servers, and this might just help me out in the short term!!

Very good informative material. Thanks for sharing.

Thanks so much John - much appreciated for your great effort...

Thanks for valuable tutorials

hi John, very nice tutorial about powershell.

Thanks you so much for your help.

So informative! Thanks so much ❤

Many thx 🙏❤🌹 for sharing your knowledge....

Thank you! Superb detail tutorial

Outstanding sir, thank you lots.

John thank you for this, very helpful. One thing you can do instead of telnet for troubleshooting. You can use PowerShell = Test-NetConnection "HostName" -Port 5985

Awesome...I am more confident.

Is anyone else having trouble using CredSSP when remoting into a Server Core 2016 host? I can confirm that on the host the two cmdlets have been executed: Enable-PSRemoting -force Set-Item WSMan:\localhost\Service\Auth\CredSSP -value $True and the correct GPO is enabled, set appropriately (*.MyDomainName.local) and linked. Is there an additional step if the remote host is running Server Core?

Great course! Are you planning on any other courses?

I am grateful to you for your videos. It helps me a lot to know PowerShell. Your presentation is absolutely awesome though your accent makes me a bit upset in some parts of the videos.

been trying to install MS-PSRP in OSX (last version Mojave/10.14.6)... and access via OMI/WBEM... and also via SSH... The Powershell version I use is Core 6.2.3 (and tested with 7.0preview4)... but no luck... just cant "Enter-PSSession"... 1) remote OSX machine is accessible via ping (or VNC, or...) 2) no firewall in the remote machine 3) credentials are created for the user 4) can connect via SSH with noo problem (even forward -X for X-Eyes) ?what else can I do... ?can you provide-me a link for some guide/tutorial/video Thanks for this great presentation! ZEE

I have to configure the client machine for this remoting?

A question dear powershell friendz and students of this course, who are maybe further tham me. Should I do the extrawork of creating VMs with an domaincontroller etc. for continueing this course? Will it get kind of mandatory? Because I really want to type in all of that commands myself but in this video I was't able do do so anymore at some points. Thanks

1:15:10 this is fucking amazing!

Thank you for the fantastic tutorial! Somehow I am able to do a double-hop without using Credssp, I am just creating a session from computer A to computer B and another session from computer B to computer C. On all 3 machines, I have WinRM enabled and they all have each other added to Trusted hosts. All machines are on the same subnet, not in a domain, but in the same group. The firewall is also on. Why would I be able to do that? Also, it seems that I can only use Credssp in a domain, is that correct?

Trying to remote between 2 Windows 10 PC's on same LAN. Had troubles. Had to "$s = New-PSSession -ComputerName "User-PC" -Credential(Get-Credential)" then run commands like "Invoke-Command -Session $s -ScriptBlock { $env:COMPUTERNAME }"

You are amazing! Do you have like a tip jar?

Hi Sir, I have 3 servers, vm01--domain controller, vm02 and vm03 normal servers. I have added those servers in to the domain(vm02 and vm03) Now able to connect to the vm02 and vm03 through powershell remoting from vm01(dc), but not able to connect vice versa and also between vm02 and vm03. I am able to connect to the dc and between vm02 and vm03 from anyone by using credential with domain admin. I want to know why I am not able to connnect to the dc from vm02 and vm03 through remote ps without credentials. You told in the lecture, if we want to run against dc, we need to add our account in the builtin admin groups, now what can I add into it, I did not understand that point, like shall I need to add dc into admin groups or vm02 and vm03 into the admin groups? Please clarify this sir

i got this problem can you help me figuring out the problem invoke-command -computername " " {$var=10} [" "] Connecting to remote server " " failed with the following error message : WinRM cannot process the request. The following error with errorcode 0x8009030e occurred while using Negotiate 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: (" ":String) [], PSRemotingTransportException + FullyQualifiedErrorId : 1312,PSSessionStateBroken

Why use invoke-command when I can just do the commands directly in a pssession of the target computer?

Richard Ayoade before he was famous

John please provide online training for azure

I am running into an issue. Error Message after running "Invoke-Command -ComputerName mypcname {$var = 10}". Error Message: Connecting to remote server mypcname failed with the following error message : The WinRM client cannot process the request. If the authentication scheme is different from Kerberos, or if the client computer is not joined to a domain, then HTTPS transport must be used or the destination machine must be added to the TrustedHosts configuration setting. Use winrm.cmd to configure TrustedHosts. Note that computers in the TrustedHosts list might not be authenticated. You can get more information about that by running the following command: winrm help config. For more information, see the about_Remote_Troubleshooting Help topic. Any pointers with the error?

Oi you Big Unit, I can't get invoke-command -Scriptblock {get-winevent -logname security} | select-object -first 10 working PSVersion 7.1.3 winevent as PS 7 Local machine. I have installed. Install-Module -Name WindowsCompatibility -Scope CurrentUser Many thanks you King of Nerds You.