kelvintegelaar / azwarrantyupdate

Hi there 👋

I'm Kelvin Tegelaar, Also known as "Lime" or Lime-TeGek" in some parts. I enjoy long walks on github pages and PowerShelling a lot.

• 🔭 I’m currently working on ... My PowerShell blogs on https://cyberdrain.com
• 👯 I’m looking to collaborate on ... Any project I have on my Github. I love collabing!
• 💬 Ask me about PowerShell, Monitoring, Automation, and how much fun it is to run a MSP.
• 📫 How to reach me: kelvin {at} cyberdrain.com or twitter @KelvinTegelaar
• ⚡ Fun fact: I specialize in monitoring using RMM systems, they actually are a big hobby of mine. This is also why I like speaking at events such as Dattocon, Solarwinds Empower MSP :)
• 😁I'm proud of the following projects:
  • my RunAsUser Module, which allows you to execute scripts as the currently logged on user, while the script host was started as SYSTEM.
  • My AutotaskAPI project for creating a fast method of connecting to the REST API
  • My Automatic Documentation blogs, as I strongly believe that automatic documentation is the only correct documentation.
  • And a lot more projects to mention here... :)

azwarrantyupdate's Issues

Turn off overwrite warranty in App Configuration

HI Kevin,

By default the script Overwrites Warranty. Currently it seems not to be possible to add OverwriteWarranty as an App Configuration so you can use the value FALSE. In our case we don't want current values in IT Glue to be overwritten but only if there is no Expire set it should add.

The option is included in the powershell module, but I think it is hard coded to True in this AzureFunction.

Can this be added that eg Overwrite is on by default unless the value is specified in Configuration with false? In this way, already installed instances will not be affected.

Thank you for thinking along!

Perry

Incorrect warranty dates for Dell machines

Firstly, I must say a huge thank you for making this so easy to deploy, I've been manually running the PowerShell script up until now.

Noticed that when I first deployed this script, it made quite a number of changes to warranties that were already correct. A couple of example service tags, and the date the script has updated them to and then the correct date from the Dell website (manually looking up):

Dell Precision 5720 AIO 877X9P2 April 4, 2018 April 5, 2021
Dell XPS 13 9365 DS9CST2 Jan 20, 2019 Jan 22, 2021

The date it was updated to is the ship date, so my presumption is that it's grabbing the wrong field in the response from the Dell API.

Tried looking through the source code, but I couldn't find the configuration of Update-WarrantyInfo - not knowing / having looked too much into Azure Functions I presume this run from a separate repo / function that I as a user cannot see / interrogate.

Extended warranty not being recognised

It seems to now be updating with the expiration of the base warranty, but not if it was extended... see below:

For clarity, I would expect that the expiration date would be updated to Oct 11, 2021.

Originally posted by @teejayen in #2 (comment)

$ResumeLast not evaluating as $true when Get-WarrantyCWM checks it.

Run.ps1 file checks for the existence of devices.json and assigns it to $ResumeLast. This is working properly and I added a Write-Host to confirm in the Function logs.
$ResumeLast = test-path 'Devices.json'

Then it runs the Start-WarrantySync function > Update-WarrantyInfo > Get-WarrantyCWM.
Get-WarrantyCWM is the only other script in this series that evaluates $ResumeLast, but it evaluates as $false and goes straight to pulling devices from CWM in the Else {} section instead.

Checked the contents of devices.json using Kudu and it looks valid, also tried uploading a handful of devices manually to the file, but it still evaluates as $false by the time Get-WarrantyCWM is run.

Not sure if this affects the other vendor Get-WarrantyXYZ scripts or not.