Forums
New posts
Search forums
News
Security News
Technology News
Giveaways
Giveaways, Promotions and Contests
Discounts & Deals
Reviews
Users Reviews
Video Reviews
Support
Windows Malware Removal Help & Support
Inactive Support Threads
Mac Malware Removal Help & Support
Mobile Malware Removal Help & Support
Blog
Log in
Register
What's new
Search
Search titles only
By:
Search titles only
By:
Reply to thread
Menu
Install the app
Install
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Forums
Software
Security Apps
Microsoft Defender
How to configure Microsoft Defender with Local Group Policy Editor
Message
<blockquote data-quote="Andy Ful" data-source="post: 893803" data-attributes="member: 32260"><p>ConfigureDefender uses the native PowerShell cmdlets so it is supposed to work on any new Windows version (GPO too). Applying GPO is a different method and it does not use the native WD settings but configures the policies that override (but not overwrite) the native Windows settings. Both ConfigureDefender and GPO use the methods promoted by Microsoft, but ConfigureDefender is focused on the most important settings. The main difference is that ConfigureDefender is not a native front end and it is much easier than GPO for most users. There is no need to use ConfigureDefender on Windows Pro when one knows how to do it via GPO, does not change frequently the settings, and can customize the Event Log View to see the WD events.<img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite130" alt="(y)" title="Thumbs up (y)" loading="lazy" data-shortname="(y)" /></p><p></p><p>Edit.</p><p>The main functionality of ConfigureDefender can be reproduced by a PowerShell script.</p></blockquote><p></p>
[QUOTE="Andy Ful, post: 893803, member: 32260"] ConfigureDefender uses the native PowerShell cmdlets so it is supposed to work on any new Windows version (GPO too). Applying GPO is a different method and it does not use the native WD settings but configures the policies that override (but not overwrite) the native Windows settings. Both ConfigureDefender and GPO use the methods promoted by Microsoft, but ConfigureDefender is focused on the most important settings. The main difference is that ConfigureDefender is not a native front end and it is much easier than GPO for most users. There is no need to use ConfigureDefender on Windows Pro when one knows how to do it via GPO, does not change frequently the settings, and can customize the Event Log View to see the WD events.(y) Edit. The main functionality of ConfigureDefender can be reproduced by a PowerShell script. [/QUOTE]
Insert quotes…
Verification
Post reply
Top