While building my new Configuration Manager server, MECM, I took screenshots of the default antimalware policy settings in the event settings in it ever got changed. The default should not be changed. A new policy should be created and deployed.
20 April 2020
Home »
» Configuration Manager Default Antimalware Policy
Configuration Manager Default Antimalware Policy
Related Posts:
Install Dell Command Configure in WinPE Dell Command | Configure can be of great use in the WinPE environment. It allows you to configure and/or query the BIOS before an operating system is laid down. This is easy to do. The first thing is to determine the archit… Read More
Profile Size Reporting While in the middle of the planning phase for the Windows 10 rollout, we wanted a report on the size of the My Documents and Desktops of all users. These will be the folders we have decided to back up. USMT is not possible … Read More
Deleting Previous MDT Build Logs with this PowerShell One-Liner If you have the SLShare variable defined in MDT to write logs to the specified UNC path and the SLShareDynamicLogging defined to write to the same path including the %ComputerName%, you have probably run into the issue of t… Read More
TPM Readiness Verification A while back, I posted a PowerShell script that verified if the TPM was ready for BitLocker to be applied in a build. Recently, the script stopped working. I decided to decipher the code I had borrowed to make the script wor… Read More
Cleaning Up and Automating the Backup of Bitlocker Passwords to Active Directory Recently, I was reviewing the bitlocker recovery password backups. We still use active directory to store them, and yes, we are planning on moving to MBAM. That is a ways off as we're in the process of the Windows 10, Exchan… Read More
0 comments:
Post a Comment