mirror of
https://github.com/amidaware/community-scripts.git
synced 2026-04-26 06:25:54 +03:00
[GH-ISSUE #242] Defender Status - script lies. Defender NOT Healthy #313
Labels
No labels
enhancement
good first issue
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/community-scripts#313
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @bbrendon on GitHub (Jul 26, 2024).
Original GitHub issue: https://github.com/amidaware/community-scripts/issues/242
I wouldn't usually create an issue in community scripts but considering you can disable defender and this script will still say its HEALTHY seems like a huge missing.
github.com/amidaware/community-scripts@116e51dcfa/scripts/Win_Defender_Status_Report.ps1 (L35)@dinger1986 commented on GitHub (Jul 26, 2024):
I'll look into that
@silversword411 commented on GitHub (Jul 27, 2024):
Why not?
@cdp1337 commented on GitHub (Jul 27, 2024):
Before
Write-Output "Windows Defender Status Report:":Then swap the 2 corresponding lines in the output with:
Fixes
Full Scan Age: 4294967295 Days agofrom being displayed."Never Ran?" "Never Run?" One of the two is correct, I never remember which is grammatically correct.
@dinger1986 commented on GitHub (Jul 27, 2024):
Never ran would be grammatically correct.
I was thinking also if it's over a high number to make it never ran. Probably over 6 years (2,190 days) then it's never ran?
Does that make sense?
@cdp1337 commented on GitHub (Jul 27, 2024):
Yeah, that would work too. One of my boxes reported that specific number as did Silversword's, so that's just what I used. If it's 2190 days, that should be sufficiently useful too.
@dinger1986 commented on GitHub (Jul 27, 2024):
on the back of this updated the defender enable script
@silversword411 commented on GitHub (Jul 27, 2024):
For Defender Status 1.4 Added WarnOnMissedScans switch and date on scan stuff
@dinger1986 commented on GitHub (Jul 27, 2024):
why? already done, if you set days to 0 then it disables the check unless its felt it should be more obvious, just trying to keep it tidy and variables to a minimum. I have deleted the original as that might have been confusing, also deleted my v2 and left v3 below
@dinger1986 commented on GitHub (Jul 27, 2024):
completed status script, any comments welcome
@bbrendon commented on GitHub (Jul 27, 2024):
i feel like some of the settings you're looking at are somewhat subjective. like CloudExtendedTimeout, CloudBlockLevel, FullScanAge
I see some of it is optional as well which is fine.
I havent messed with Get-MpThreat much but I think for that you want (Get-MpThreat).IsActive.
@dinger1986 commented on GitHub (Jul 28, 2024):
It's all stuff that the enable script enables so makes sense to check for it, ie full scans etc.
A lot does have params to enable/disable to make things easier and allow it to be customised.
I'll look at get threat and get that added to the script.
@dinger1986 commented on GitHub (Jul 28, 2024):
yeah added get-mpthreat and works fine, any other comments?
Should we make checking for full and quick scans default to 0? So it doesnt alert on them
@silversword411 commented on GitHub (Jul 28, 2024):
Yes, that was one of the two changes I made above :)
@dinger1986 commented on GitHub (Jul 28, 2024):
yeah I changed it all since then :) added in more stuff, if anyone wants to test it and give feedback that would be great