In the early days of my career, I had the epiphany that “Best Practices” really do not exist or apply to most scenarios. It should be all driven by logic and common sense in the end. What makes much more sense is to find the standard /common practice compares to the mythological unicorn of “best practices” and see if has value and benefit in a specific case. Continue reading “PowerShell: When and Where Writing Logs Matters”
Does’t matter how good is your security and design in your environment with with complex spam filters, gateways and appliances… sooner or later you’ll need to remove some sort of unwanted communication from one or more mailboxes on your Exchange Server.
In a very common incident response scenario like this, PowerShell is a very useful tool, this time the cmdlet used is New-ComplianceSearch and is available on-premises and on cloud services for Exchange Server 2016.
Create a report and send it via email is easier than you think and it’s a really useful feature to automate recurring tasks. This particular example is inspired by another scripting library post about uptime, in fact, we will show you how to create a simple report with all servers bootup time and send it via email in few lines of code or even a oneliner if needed.