From the course: PowerShell: Scripting for Advanced Automation

Unlock the full course today

Join today to access over 22,500 courses taught by industry experts or purchase this course individually.

Troubleshooting in Windows PowerShell

Troubleshooting in Windows PowerShell

From the course: PowerShell: Scripting for Advanced Automation

Start my 1-month free trial

Troubleshooting in Windows PowerShell

- [Instructor] Once you start implementing DSC, JEA, and other automation practices, it becomes especially important to get out in front of who or what needs to authenticate before they can do their task. Once you know these things, you can make sure that that access is granted. But even after user rights and permissions are perfect on the servers to be managed, there are still firewalls, remoting, local permissions, and other accepted authentication methods that all need to be worked out. There is one relatively easy solution that we've already discussed. If your tech department can use exclusively PowerShell for all administration, you can setup JEA for your entire network. That will allow you to close all administration ports on servers and firewalls, except port 5986 or 5985 if you're running without a certificate and need HTTP. All access is defined through JEA and the use of virtual accounts is a huge security plus. But, there's a reason that some people won't do this…

Contents