HP Warranty scan - broken for some products

Moopere · ‎11-21-2019

Hello Folks,

Looks like scanning HP warranty on some devices is broken when we're scanning against the HPE database.
See this:

Parsing error: Cannot parse 'https://support.hpe.com/hpsc/wc/public/find?lang=us&rows%5B0%5D.item.countryCode=US&rows%5B0%5D.item.serialNumber=CNB7G7W36J'

If I manually copy the URL above and end up at the HPE site it states that:

"The information you provided does not match our records. Please review your entry again and make any necessary edits or contact HPE for more assistance."

If one uses the HP warranty check site (not HPE):

https://support.hp.com/us-en/checkwarranty

Its happy and doesn't produce any error, just provides the correct warranty details.

Is there a way to add an alternative warranty check URL to lansweeper?

zaty · ‎02-21-2020

Hi,
i wrote for myself Powershell script to get all HP computers/laptop assets from DB, use Powershell module to get warranty info thru SOAP API and update asset in DB.

You will need these PS1 modules:
https://github.com/dotps1/HPWarranty
https://docs.microsoft.com/en-us/sql/powershell/download-sql-server-ps-module?view=sql-server-ver15


$assets = Invoke-Sqlcmd -ServerInstance servername -Database lansweeperdb -Username lansweeperuser -Password 'password' -Query @"
SELECT a.AssetID, a.AssetName, b.Serialnumber, b.SystemSKU
FROM lansweeperdb.dbo.tblAssets a, lansweeperdb.dbo.tblAssetCustom b
WHERE a.AssetID = b.AssetID AND
a.Assettype = -1 AND
b.Warrantydate is NULL AND
b.Manufacturer in ('HP','Hewlett-Packard');
"@

foreach ($asset in $assets) {
    $assetId = $asset.AssetID
    $assetName = $asset.AssetName

    $warranty = ((Get-HPIncWarrantyEntitlement -SerialNumber $asset.SerialNumber -ProductNumber $asset.SystemSKU).OverallEntitlementEndDate | Measure-Object -Maximum).Maximum
    Write-Output "$assetID  $assetName  $warranty"

    Invoke-Sqlcmd -ServerInstance servername -Database lansweeperdb -Username lansweeperuser -Password 'password' -Query @"
    UPDATE dbo.tblAssetCustom
    SET Warrantydate = '$warranty'
    WHERE assetID = $assetId
"@
}

View solution in original post

TBMPS · ‎01-04-2021

I am not looking at my servers. I am looking at my desktops and laptops.

TBMPS · ‎10-24-2020

Trying out the script in #12. However it is only putting the date "1900-01-01" in the warranty. When I run the script, there is no error. Is there something that might need to be done to get this to work correctly, or has this script been shutdown too?

Thanks.

zaty · ‎11-09-2020

TBMPS wrote:
Trying out the script in #12. However it is only putting the date "1900-01-01" in the warranty. When I run the script, there is no error. Is there something that might need to be done to get this to work correctly, or has this script been shutdown too?

Thanks.

Hello,
unfortunately, it works only for HP assets (desktops, laptops) but not for HPE assets (servers, switches etc) 😞

filip_heens · ‎08-10-2020

So strange that reply #12 from zaty works perfectly (in my environment) but that Lansweeper can't seem to get it working.
Well thanks zaty as I can use your work around for the time being 😉

Bruce_B · ‎08-10-2020

No news to share as of this moment unfortunately.

filip_heens · ‎08-10-2020

Are there any updates on this.
I know that Lansweeper was working on this, but I can't find any updates...

mwrobo09 · ‎07-08-2020

This should be made a high priority. This has not been working for some time, and I am trying to do planning for next year and many of my devices have not been pulled in a long while. I am manually going through 1000 devices trying to enter the information.

Please fix ASAP.

FrankSc · ‎07-02-2020

Hello,

We are indeed looking into this. We realize that warranty scanning is a valuable feature.
As this issue was initiated by changes made to the HP Warranty API, we are currently in communication with HP to find a solution to get this working again.

jan_prins · ‎07-01-2020

DearSupport

Are you currently investigating thsi issues? I have also submitted a ticket for this but no respnse.

I think 6 months of waiting is not good enough.

HP Warranty scan - broken for some products

New to Lansweeper?

Try Lansweeper For Free