starred/tacticalrmm

Fork 0

mirror of https://github.com/amidaware/tacticalrmm.git synced 2026-04-26 15:05:57 +03:00

[GH-ISSUE #982] Feature request: Warranty Lookup #596

New issue

Closed

opened 2026-03-02 02:17:32 +03:00 by kerem · 10 comments

kerem commented

2026-03-02 02:17:32 +03:00

Owner

Originally created by @adamjrberry on GitHub (Feb 21, 2022).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/982

Originally assigned to: @silversword411 on GitHub.

I have looked but don't see a similar request already. I think it would be great in the future for TRMM to have a field showing warranty status of a machine. It looks like some people have managed to bodge a similar solution with Powershell scripts but there are lots of limitations to this. Other RMM vendors have integrated warranty checks into their systems so it would be awesome if TRMM could in future!

Originally created by @adamjrberry on GitHub (Feb 21, 2022). Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/982 Originally assigned to: @silversword411 on GitHub. I have looked but don't see a similar request already. I think it would be great in the future for TRMM to have a field showing warranty status of a machine. It looks like some people have managed to bodge a similar solution with Powershell scripts but there are lots of limitations to this. Other RMM vendors have integrated warranty checks into their systems so it would be awesome if TRMM could in future!

kerem

2026-03-02 02:17:32 +03:00

closed this issue
added the
enhancement
label

kerem commented

2026-03-02 02:17:33 +03:00

Author

Owner

@dinger1986 commented on GitHub (Feb 21, 2022):

Bodged doesn't really do it justice as that's essentially what other RMMs have done they just display it differently.

Maybe your feature request is to display it on the machine or something?

@dinger1986 commented on GitHub (Feb 21, 2022): Bodged doesn't really do it justice as that's essentially what other RMMs have done they just display it differently. Maybe your feature request is to display it on the machine or something?

kerem commented

2026-03-02 02:17:33 +03:00

Author

Owner

@adamjrberry commented on GitHub (Feb 21, 2022):

Hey - perhaps 'bodged' wasn't the right term to use... The reason I said that is because there was some scripts out there that became quickly redundant because of changes to HP, Dell, Lenovo lookups and their API changes. Through those changes, other RMMs have managed to consistently show the warranty status, so I assumed that there was another way, outside of a powershell script, to get this information.
If anyone has a current working script, I'd really love to see it, as this is something I'm in need of. I'd like to just output the warranty expiry date to a custom field in TRMM.

@adamjrberry commented on GitHub (Feb 21, 2022): Hey - perhaps 'bodged' wasn't the right term to use... The reason I said that is because there was some scripts out there that became quickly redundant because of changes to HP, Dell, Lenovo lookups and their API changes. Through those changes, other RMMs have managed to consistently show the warranty status, so I assumed that there was another way, outside of a powershell script, to get this information. If anyone has a current working script, I'd really love to see it, as this is something I'm in need of. I'd like to just output the warranty expiry date to a custom field in TRMM.

kerem commented

2026-03-02 02:17:33 +03:00

Author

Owner

@dinger1986 commented on GitHub (Feb 21, 2022):

Are the current community scripts not working with url actions?

There are countless ways to do it including powershell, doesn't mean ones better than the other is what I meant.

Keeping up with manufacturers etc will be an ever evolving front and with the scripts could be easier for the community to maintain rather than just the devs.

Just realised you said about the date, hmmm ok that's maybe a harder one but then should be able to be done with powershell and then output to a custom field.

@dinger1986 commented on GitHub (Feb 21, 2022): Are the current community scripts not working with url actions? There are countless ways to do it including powershell, doesn't mean ones better than the other is what I meant. Keeping up with manufacturers etc will be an ever evolving front and with the scripts could be easier for the community to maintain rather than just the devs. Just realised you said about the date, hmmm ok that's maybe a harder one but then should be able to be done with powershell and then output to a custom field.

kerem commented

2026-03-02 02:17:33 +03:00

Author

Owner

@silversword411 commented on GitHub (Feb 21, 2022):

That data is only stored on the manufacturers website/database once you look a machine up by SN right?

@silversword411 commented on GitHub (Feb 21, 2022): That data is only stored on the manufacturers website/database once you look a machine up by SN right?

kerem commented

2026-03-02 02:17:33 +03:00

Author

Owner

@adamjrberry commented on GitHub (Feb 21, 2022):

Hey, thanks for the reply.
A community script would certainly do the job just fine if it works. I couldn't see one in the TRMM community scripts page, and the ones I found on other websites don't work any more.

Silversword, not sure quite what you mean? You can do a lookup of SN on the websites to get status, but it appears that the data is already there as previous scripts have managed to capture it.. That said, the ways of accessing the information seems to be ever changing.

@adamjrberry commented on GitHub (Feb 21, 2022): Hey, thanks for the reply. A community script would certainly do the job just fine if it works. I couldn't see one in the TRMM community scripts page, and the ones I found on other websites don't work any more. Silversword, not sure quite what you mean? You can do a lookup of SN on the websites to get status, but it appears that the data is already there as previous scripts have managed to capture it.. That said, the ways of accessing the information seems to be ever changing.

kerem commented

2026-03-02 02:17:34 +03:00

Author

Owner

@dinger1986 commented on GitHub (Feb 21, 2022):

so this one would work, you would collect your serial numbers, save them as custom fields then use the api to pull them out into an html page, or could put it back to notes or something:

https://www.cyberdrain.com/automating-with-powershell-automating-warranty-information-reporting/

@dinger1986 commented on GitHub (Feb 21, 2022): so this one would work, you would collect your serial numbers, save them as custom fields then use the api to pull them out into an html page, or could put it back to notes or something: https://www.cyberdrain.com/automating-with-powershell-automating-warranty-information-reporting/

kerem commented

2026-03-02 02:17:34 +03:00

Author

Owner

@plao commented on GitHub (Feb 22, 2022):

Nice feature! For me, absolutely +1!

@plao commented on GitHub (Feb 22, 2022): Nice feature! For me, absolutely +1!

kerem commented

2026-03-02 02:17:34 +03:00

Author

Owner

@silversword411 commented on GitHub (Feb 22, 2022):

I'll look at the script for now

@silversword411 commented on GitHub (Feb 22, 2022): I'll look at the script for now

kerem commented

2026-03-02 02:17:34 +03:00

Author

Owner

@dinger1986 commented on GitHub (Feb 22, 2022):

$serial = (gwmi win32_bios).SerialNumber
$brand = (gwmi win32_bios).Manufacturer

@dinger1986 commented on GitHub (Feb 22, 2022): $serial = (gwmi win32_bios).SerialNumber $brand = (gwmi win32_bios).Manufacturer

kerem commented

2026-03-02 02:17:34 +03:00

Author

Owner

@silversword411 commented on GitHub (Mar 12, 2022):

Added to wip

@silversword411 commented on GitHub (Mar 12, 2022): Added to wip

kerem referenced this issue

2026-03-02 02:24:18 +03:00

[PR #596] [MERGED] Submitting System Report Generator to Community Scripts #1680

kerem referenced this issue

2026-03-14 07:30:36 +03:00