Automating with PowerShell: Warranty lookups

A while back I’ve made a PowerShell module called PsWarranty that allows you to look up the warranty for all major vendors. I’ve integrated this module with many different RMM systems, documentation platforms, and PSAs. Lately, I’ve been getting some more questions about this module in regards to automatically updating the warranty information. Most people like reporting from their own tooling and rather just update the systems.

There’s loads of ways to tackle this, but my prefered method of running scheduled scripts is Azure Functions. Now Azure functions currently only have a maximum runtime of 10 minutes in the consumption model. To make sure that the job continues I’ve added a stop-resume logic to the PowerShell module, that way it automatically picks up where it left off when the script is stopped.

I also understand there’s no reason to update all warranty information every hour of course, so I also added logic that if the warranty for all devices in the first run have been updated, the script won’t run for another 7 days. That means that every week the Azure Function will perform a warranty update for all devices in your chosen system. Just to make life easy and keep costs down. We’ve been running this function for somewhere around a year now, and are paying 40 cents a month.

Deploying

As this was all built with my own systems and procedures in mind, I’ve created a couple of ways for others to deploy this as well. I made some quick and dirty code that you can chose to copy and paste to your own Azure Functions here.

I’ve also made some simple “Deploy to Azure” buttons for the most used applications. Clicking these will create the function app, enter the right credentials for your applications and off you go. You can find these deployment templates here. If there’s any other applications you’d like to see integrated, feel free to send me a Pull Request at this repository

Datto RMM

Autotask PSA

IT-Glue

Hudu

Connectwise Manage

N-Able N-Central

Finally

When you click the buttons, you’ll be asked for your credentials which will be stored inside the application. The Function App will them use my PowerShell module to sync the warranty with the selected system and overwrite it with the latest currently found warranty. If you feel like you could help improve on these projects, feel free. I’ve mostly made them to show how it could be done. As always there are not guarantees or rights you have when deploying these apps and you should have the knowledge to maintain these yourself.

As always, Happy PowerShelling.

12 Comments

  1. Jason March 29, 2021 at 11:58 pm

    Hi Kelvin,

    Thank you very much for creating this code, I am looking forward to testing it.

    Just have a quick question on recommendation for where to synchronize to between IT Glue, Datto RMM & Autotask PSA if all are of them are in use and integrated/synchronizing between each other?

    Is it best to Synchronize to the PSA as the central piece, I’m not sure if any particular tool has better integration with the scripts you’ve made, thank you.

    1. Kelvin Tegelaar March 30, 2021 at 9:02 am

      I always have a personal preference to update the PSA, and let that trickle down to integrated tools. 🙂

  2. Dennis Hansen March 30, 2021 at 8:50 am

    We are using scalepad/warrentymaster and they have a purchased date with their reports.
    Are this script updating the purchased date also or only warrenty expire?

  3. Sten May 11, 2021 at 1:11 pm

    Hello,
    where do we get the DELL API key from?

    Greets
    Sten

  4. Ewan May 30, 2021 at 11:21 am

    Hi Kelvin,

    Ik maak gebruik van de Autotask Azure function en krijg de volgende foutmelding “Timeout value of 00:05:00 exceeded by function ‘Functions.Updater’ (Id: ‘879cf098-cac9-49d0-8b68-69044a518412’). Initiating cancellation.” Enig idee wat er mis gaat?

    Groet,

    Ewan

  5. Jason July 13, 2021 at 7:41 am

    Hi Kelvin,

    Just trying to get the Azure deployed and I noticed in the Autotask deployment package you have “AutotaskHostName” parameter with a description of “Your current Datto RMM API URL”

    Is this correct it’s needing the Datto API URL or is this supposed to be the Autotask API URL?

    Thank you!

  6. Wilm July 22, 2021 at 8:48 am

    Hi Kelvin,

    I get an error when retrieving the Azure Function deployment for N-Able N-Central

    https://raw.githubusercontent.com/KelvinTegelaar/AzureDeploy/master/Nable.json

    There was an error downloading the template from URI ‘https://raw.githubusercontent.com/KelvinTegelaar/AzureDeploy/master/Nable.json’. Ensure that the template is publicly accessible and that the publisher has enabled CORS policy on the endpoint. To deploy this template, download the template manually and paste the contents in the ‘Build your own template in the editor’ option below.

  7. Shane O'Connor September 3, 2021 at 4:30 pm

    Hi Kelvin,

    I deployed the Datto RMM function to Azure using the link above. It said that it was successful approximately an hour ago and I can see the 3 resource groups it created. Based on your experience how long should it take for the data to become available? Does it populate the Warranty field in Datto RMM or should I look elsewhere for the output?

    Regards,

    Shane.

    1. Shane O'Connor September 7, 2021 at 12:10 pm

      A little bit of further information here. After some time a small number of Dell devices updated their warranty information, but in the 3 days since I deployed to Azure the total number of devices updated is under 60. We currently have over 4,500 Dell devices in our RMM platform. Given that some have updated, it would suggest that the API keys are correct and your code is calling them correctly. Is it possible that Dell is limiting the number of requests that can be made? Have you encountered this issue before?

      Regards,

      Shane.

Leave a comment

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.