Cybercriminals are increasingly turning toward using PowerShell as an attack tool because it’s powerful and tightly integrated into the Windows operating system. Although disabling PowerShell probably isn’t an option, you have some things that you can do to reduce the chances of a cybercriminal using it against you.
GUI-based Windows management tools are specifically designed to avoid exposing passwords. Even so, it’s sometimes possible to use PowerShell to help reveal a password. This article explores some techniques for doing so.
Learn how you can use the Read-Host cmdlet in PowerShell to prompt for and get user inputs. In this article, I talk about the different parameters that you can use with this cmdlet along with some code examples of how you can use them.
Microsoft created Strict Mode for PowerShell to enforce the use of coding best practices. It’s possible to compose scripts without Strict Mode, but doing so offers certain advantages. In this article, we explore the pros and cons of using Strict Mode.
Even if a PowerShell script is error-free, it can still produce errors due to an external condition such as a failed network connection. This article explains how to build simple tests into your scripts to reduce the possibility that an external condition will cause a script to fail.
In this article, you’ll get a step-by-step guide on how to connect to Exchange Online via PowerShell. You’ll also learn ways to troubleshoot common problems, so you can connect to Exchange Online and manage problems through PowerShell.
Read through this article to understand what a ForEach loop is in PowerShell coding and how you can use it to your advantage. We’ll explain 3 ForEach implementations with examples. You’ll also learn about the scenarios where one option is better than the others.
AppDynamics is a tool to monitor application performance, health, and data. This article shows you how to write a custom script in PowerShell and use it as a task in the Azure DevOps pipeline. This logs the deployment event and lets AppDynamics users know when the applications have been successfully deployed to various environments.
Sometimes PowerShell scripts do not behave as expected and it can be difficult to figure out why a complex script has done what it has. Tracing allows you to step through a script and find the point at which the script fails.
It’s a relatively common practice for PowerShell developers to create modules containing custom cmdlets. That said, such cmdlets normally provide only the most basic help. Yet, you can augment a custom cmdlet so that it works with Get-Help, just as a native cmdlet does.
