We can configure Windows Defender scans using Windows PowerShell as an alternative to configuring them through the graphical user interface. This allows us to integrate Windows Defender features into PowerShell scripts, and configure settings that are not available through the graphical user interface.
While Windows Defender can be configured at a high level through the graphical user interface, we can instead configure Windows Defender using group policy which gives us more control and allows us to roll out the settings to the whole domain from a central location.
It’s important for Windows Defender to stay up to date so that new known variants of malware can be detected. This can be achieved if we integrate Windows Defender with WSUS and Windows update, which we’ll show you how to do here in Windows Server 2016.
This post will cover the 70-744 exam objective “implement antimalware solution with Windows Defender”, we’ll show you how to work with Windows Defender in Windows Server 2016.
By default Windows Server 2016 comes with Windows Defender installed and running. This is an improvement over Windows Server 2012, which had nothing by default although with some work you could install Windows Defender manually, however this solution was of course not officially supported.