Dell Warranty Check Multiple Service Tags

Dell Warranty Check Multiple Service Tags For Sale
Dell Warranty Check Multiple Service Tags Phone Number
Dell Laptop Warranty Check

The official Dell website allows you check the warranty status of any product that you have purchased online and offline. From Laptop to printer or monitor, you can find the status within moments. All you need is the Service Tag, which comes with all Dell products. You can find the Service Tag on the sticker pasted on the product’s body. How can a list status of warranties of multiple service tags We have multiple Dell Servers, Switches and Computers that I was to list the status of warranties by their service tags. I do not want to look up one at a time. Remove bezel and locate removable EST tag or look on the back of the system. Blade Server: Locate black label in bottom right corner of handle trim part or on the side of the system. Invalid Service Tag Please try re-submitting the same service tag if you are getting 'INVALID SERVICE TAG' message for a valid service tag. Function to check Dell warranty. Feel free to expand on this. Just sharing a function I wrote to pull down a Dell machine's warranty info. It'd be great if this could take in a CSV, get info for each service tag within that CSV, and then return another CSV with all that info for. I finally check the monitors and have a service tag. Dell warranty check indicates the warranty it's valid until june 2020. Glad to hear everything worked out!:) Oh yes! We are glad to see some monitors now have service tags on them!

Learning has never been so easy!

I use Dell workstations and servers. I like to be able to track when my warranties and system service dates expire. I'm lazy, so if its not automated then it is worthless to me. I have been using this retrieval method for about a year in other reports and decided to integrate it into my Spiceworks implementation.

11 Steps total

Step 1: Download and install the SQLLite ODBC Drivers

Grab them from here:
http://www.ch-werner.de/sqliteodbc

If you want to use MSAccess to verify connectivity then you will need to create an ODBC connection. The script does not require this.
- Admin ToolsODBC Connections
- System DSN
- Add, Choose 'SQLLite 3 ODBC Driver'
- Data Source Name = Spiceworks
- Database Name =

Step 2: Download the script

- Create a folder somewhere on your spiceworks server
- Download the script. Since I can't add an attachment to a How-To, get it from my server at home...
. . . . . http://dave.newbern.org/spiceworks/service.zip

- Unzip and save the script to a folder.
- Open a command prompt and CD to the folder.

Step 3: Execute the script

From your command prompt, type service.vbs

If your default command interpreter isn't cscript, it will re-launch itself with cscript anyway. Interactively this is okay but if you use a batch scheduler that used PIDs to monitor the job, you may want to either:
- Change the default script interpreter to cscript. (a good idea when you manage a server that runs automation scripts anyway.)
cscript.exe //h:cscript

- Launch as an argument to cscript.exe
cscript.exe service.vbs

Dell Warranty Check Multiple Service Tags

Step 4: Custom Attributes

This script adds a few custom attributes to spiceworks. It may seem that they are not available immediately from within the interface. It may take a network scan before they appear or you may need to restart spiceworks. You can check for there existence by looking here: SettingsAdvancedCustom Attributes.

Even if you don't see them the script should populate them just fine.

Step 5: Add it to the Scheduled Tasks

Control PanelScheduled Tasks
- Right click, New
- Give it a name
- Right-click, Properties
- in the Run box, you need to give the full path to an .exe.. so use something like:

c:windowssystem32cscript.exe c:binservicedatesservice.vbs

Enter credentials to run the task and schedule it how ever you want.

Step 6: Notes...

The script essentially queries Spiceworks for Dell branded computers. It then issues a web request based on the service tag (serial_number), captures the html and starts looking for data. It inserts Ship Date into the Spiceworks c_purchase_date and the takes the largest date in the warranty section (in case you extend warranties) and enters it into the Spiceworks c_warranty date.

The documentation is light. The script is fairly basic. The SQLite/ODBC is a little finicky and it doesn't seem to like all data access methods. If you modify then you may have to play a little. Whatever.. it works.

Step 7: UPDATE - Sep 4, 2009

Hi everyone.

Robert from Spiceworks was kind enough to go digging through this script and seems to have figured out the problem with the date in the reporting. (Thanks Robert.) If you need to clear your service info to reload it then this script is what you need.

http://dave.newbern.org/spiceworks/cleardates.zip

Step 8: Update - Sept 30 - x64 notes

Some of you have had problems getting this to work on x64 based machines. There are 2 things that you should need to look out for.
- Make sure you get the 64 bit version of the SQLite driver.
- Make sure that the path (in the script) has the correct path. You will need to change 'Program Files' to 'Program Files (x86)'

Step 9: Update - Oct 22

- Changed to regular expression handling to grab dates. It is simply better and provides more accurate results..
- Ignores service tags that aren't 5,6, or 7 digits in length.
- Reorganized the code to make it easier to add in support for other manufacturers.
- - - HP support?. If you want support for this, go vote on this feature Request to get SW to pull the Product Number
- - - http://community.spiceworks.com/feature_request/show/Inventory/352
- Automatically detects the correct internet component.
- Automatically creates the c_warranty and c_warrantytype fields.
- Thanks to a contribution from Hendrik it now grabs the Service type as well as the dates.
- Added a little more error checking in hopes of working around some of the inconsistencies of the Dell support page.
- If the script is called with wscript.exe, it will re-launch with cscript.exe instead.

Step 10: Nov 12 - Working on HP (beta?) - want to test?

We are moving our office/datacenter tomorrow and I had some 'calm before the storm' time to work on this a little. Since I don't have a lot of HP systems in inventory, I could use your help.

** Please keep the testing feedback off of the main thread. It will just clutter it up with crap. Please PM questions/responses. **

Notes:
- Both of these scripts will create a c_product_number field on your SW.

- This is new for me but I had to bounce SW today before I could see product numbers and warranty dates in the web gui. Keep it mind. I should have checked to see if they showed up in a report while they were hidden from the gui. Webserver cache perhaps?

- I have had to switch the HTML component used due to the way the HP website communicates. If you get an error like 'can not create component ServerXMLHTTP' then try installing the MSXML components from Microsoft.

Download files: http://dave.newbern.org/spiceworks/hp_beta.zip

hp_service.vbs - This is the modified service.vbs file that will check for HP systems. It requires a product number that looks like 000000-000 in order to process it.

hp_helper.vbs - this will query your SW database looking for HP systems. It will try to connect to the system to look up the product number via WMI. You will need to execute this script with an account that has sufficient access (domain admin would be good.) If it finds a product number that looks right it will store it in SW. For me, this seems to work on G5 systems but not earlier. Your mileage may vary.

Currently it only pulls the warranty date (the largest date on the page.) Are all of the warranties formatted like this? (see right.) What would you consider to be a warranty type? Are there key words that I can pick up on here that would indicate? Is 'Base Warranty' it? Are you looking to see everything in Service level? I presume only under the Maintenance support section?

Step 11: Dec 10 - a 64 bit hack

Thanks to Park8751 letting me hack a little bit on his server I was able to get the script to run using the 32 bit ODBC drivers and the 32 bit WOW environment (on your 64 bit server.) I don't know why it works on my 64 bit test system without these changes but if you want to stay 64 bit, try this.