mirror of
https://github.com/amidaware/tacticalrmm.git
synced 2026-04-26 06:55:52 +03:00
[GH-ISSUE #1587] feature request #992
Labels
No labels
In Process
bug
bug
dev-triage
documentation
duplicate
enhancement
fixed
good first issue
help wanted
integration
invalid
pull-request
question
requires agent update
security
ui tweak
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/tacticalrmm#992
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 @feliperocp on GitHub (Aug 7, 2023).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/1587
Is your feature request related to a problem? Please describe.
no
Describe the solution you'd like
I would like a feature that allow to get the number of the Windows reliability , that can say a lot about the windows health, this will be very helpfull if can show this information on the main dashboard.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
@dinger1986 commented on GitHub (Aug 7, 2023):
Can you please explain this in more detail?
Thanks
@feliperocp commented on GitHub (Aug 7, 2023):
For sure, There is a "magic" number in Windows, the Historic Reliability Index, it ranges from 1 to 10, this number allows a technician to quickly assess the overall health of Windows.In my company, for example, the support staff uses this number to decide whether or not a computer should be formatted, after receiving a call from someone reporting slowness, they evaluate, if the reliability history index is greater than 8, they they just check for errors, etc. If it's below 8, it's worth formatting the PC. It would be very useful if TRMM brought this information on the Dashboard, or at least had a script that allowed to get this number on the PCs.
thanks for your attention.
Can you please explain this in more detail?
Thanks
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>
@dinger1986 commented on GitHub (Aug 7, 2023):
Sounds like a script check could cover this nicely and could be proactive and action rebuilds on unreliable machines prior to the customer even phoning in?
@dinger1986 commented on GitHub (Aug 7, 2023):
Like this
@feliperocp commented on GitHub (Aug 7, 2023):
Thanks a lot, works perfect for us.
Is there any repository of scripts like this available? in addition to those already available within the tool..
Like this
<#
.SYNOPSIS
This will gather the average Windows Reliabilty Score
.DESCRIPTION
Gather and then check average Windows Reliabilty Score
.PARAMETER Unreliable
.EXAMPLE
-Unreliable 5
#>
param (
[string] $Unreliable = "8"
)
$wrs = (Get-Ciminstance Win32_ReliabilityStabilityMetrics | Measure-Object -Average -Maximum -Minimum -Property systemStabilityIndex).Average
$compname = $env:computername
if ($wrs -lt $Unreliable) {
write-output "$compname is unreliable and at $wrs below $Unreliable."
Exit 1
}
else {
write-output "Windows Reliability is fine $wrs."
Exit 0
}
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>
@dinger1986 commented on GitHub (Aug 7, 2023):
loads available in https://github.com/amidaware/community-scripts wip and staging still need work done to them but fine to copy and paste to use yourself, also if you can add any please do!
@jacksonsystems commented on GitHub (Aug 8, 2023):
I wonder if this could be expanded on and anything with a X gets marked as a check or a custom field?
@silversword411 commented on GitHub (Aug 8, 2023):
What does that mean?
@jacksonsystems commented on GitHub (Aug 9, 2023):
The tool that gives you the score will show a Red X of things that are causing an issue, might be worth seeing if we can report that part of it as well via A Check.
@dinger1986 commented on GitHub (Aug 9, 2023):
would need to do checks for every part of it
@jacksonsystems commented on GitHub (Aug 9, 2023):
Very true that, would get quite cumbersome!
For now I am just having the Score go to a custom field.
@dinger1986 commented on GitHub (Aug 9, 2023):
why not just an alert come up if its below a threshold?
Could change it to a collector task by doing:
Then create a custom field and collector task running the above script.
@NiceGuyIT commented on GitHub (Feb 21, 2024):
Can someone please change the title to something a little more descriptive than "feature request"?
@dinger1986 commented on GitHub (Mar 10, 2024):
should we just close this?
@bbrendon commented on GitHub (Mar 11, 2024):
Yes, this could be a script.