Warranty Scan process questions and suggestion for future release.

Warranty Scan process questions and suggestion for future release.

Does the warranty scanning take place during the inventory scanning?


If so, may I suggest that this be a seperate user scheduable task?


From what I've seen, typically the most important information for warranty scan is gathered at the time that the agent is installed on the computer (it grabs the serial and model number of the computer).


Typically this does not change.


In my mind, the warranty scan tasks should be something that is scheduled for off prime hours, and only communicates back and forth with the manufacture's warranty site/database, with the information previously gathered from the agent.


With this scenario, the computer itself does not require to be online in order for the shipping and warranty information to be updated, as well as limiting the amount of data being trasmitted over the internet durring prime hours.


We mostly have HP laptops and Desktops in our organisation.


We have a few Toshiba's, Dell, LG's, Acer, Sony's etc as well but not many


For HP units, I have been importing the product numbers for the computers using a CSV in the format that was described in the manual.


Some units get their warranty information updated but not all - only about 1/8th are being "Scanned" and having their warranty updated (I believe this may be because either the units are turned off at the time the scan is happening, or because DesktopCentral automatically flagged it as having an expired warranty, despite no shipping/warranty information present).


Most of our units appear to be stuck with the flag of Warranty Expired.


As mentioned, there are other manufacture units there - where warranty status should also be automatically retrieved.

I noticed that some of these units are offline for quite sometime, but serial number/product number information has been retrieved - there is just no shipping or warranty information associated to the units, which is why I wonder if this may be due to the the warranty scan taking place during the Inventory scan task and its expecting the unit to be on at that time.
 
I was previously given a script to run in order to reset the warranty scan status, and this was performed and no errors were reported.
 
This seemed to work for a little bit, where is gathered warranty information for about 20 or 30 systems, but then it seemed to stop again after.
 
By default, if there is no shipping/warranty information - it should be in my mind, be flagged as Unknown status rather than automatically being dropped into the expired status.


Senior Client Technology Support Analyst
Bird Construction Inc
http://www.bird.ca
http://ca.linkedin.com/pub/carlo-piva/31/267/a5b





                  New to ADSelfService Plus?