Hi

just tested the script on some HP notebooks but the only result I get back is the serial number, all other fields stay empty.

Hey Michael,

I would first confirm the serial number is indeed able to return real data by going to https://support.hp.com/us-en/checkwarranty if so, if you provide me the serial in a private message, i can review.

Hi, 

HP warranty check works,

btw. how can I send a private message?

send me a private message by clicking "Contact Developer" on the main product page https://automationexchange.kaseya.com/products/964

Hi Michael,

The script has been fixed, there was a malformed exception with the date stamp. please try again.

I have a number of systems that are Lenovo desktop / workstations. The systems that aren't populating with anything other than a T in the Warranty Description field all begin with MJ.   The manufacturer is always Lenovo in the listing. Even for the ones that are working

I tried to run the powershell script through Kaseya but it failed to populate data. I then ran the script locally and received the following error.

"Failed to invoke SOAP request: Exception calling "GetResponse" with "0" argument(s): "The underlying connection was closed: An unexpected error occurred on a send."

I then checked on the VSA for "System Information" under the Machine Summary is completely blank with no data..... Any suggestions would be greatly appreciated.

Failed to invoke SOAP request has to do with HTTP failures. So probably your web content filter is killing it.

Hey Patrick, can you message me directly via "Contact Developer" along with an example serial number so i can test it?

I've got the same issue as Patrick...some are working great, some are just showing a T.  I'll do the same.

They are  looking at it now. Kyle, which systems are you trying to pull serials for? Lenovo or HP?

Good catch Loco,

Patrick, I am pulling HP info...or trying to.

The section for system information in Machine Summary is also blank any idea why that is?

Hi all

just tested the new script and it works for HP Notebooks and Desktops.

Any word on why some Lenovo systems are pulling the Serial number, but then just a T for the Description and no other information?

Did it work for Win 7 PCs?

testing is still underway Susan.

Cherian, this should work on any OS that supports later versions of powershell

The Registry is populated but VSa not updated only for Win 7 works fine with Win 10

Script works great but for HP we notice that when an endpoint has an extended warranty, it does not show this. It only shows the base warranty. Anyway around this?

Another thing, some HP devices require a product number to lookup the warranty. Any chance in having that included?

I fixed the issue with some HP products requiring a product number. See below:

$root='HKLM:\SOFTWARE\WOW6432Node\KaseyaWarrantyInfo'

$Bios = Get-WmiObject Win32_Bios -ComputerName $env:COMPUTERNAME -ErrorAction Stop

$ComputerSystem = Get-WmiObject Win32_ComputerSystem

$Manufacturer = $Bios.Manufacturer

$SerialNumber = $Bios.SerialNumber

$ProductNumber = $ComputerSystem.SystemSKUNumber

$ProductNumber = $ProductNumber.substring(0, $ProductNumber.lastIndexOf('#'))

Is the Lenovo API still open? $RequestResult.wiOutputForm keeps coming back null when I run the ps1. I know the AP is able to finish running because it creates the KaseyaWarrantyInfo entry in registry.

Hello everyone,

We have updated the suggested fixes in the HP request, however we have confirmed that Lenovo has closed its open API's. It is no longer possible to get lenovo warranty information without a client id. This procedure has been renamed to an HP warranty check.