SCCM Get Dell warranty info v2

2011-07-11: This method is now deprecated please go here:

LAST UPDATED: 2010-09-22

UPDATE 2010-09-14: Dell have changed the layout to add an extra field in the contracts section so the scripts are broken

UPDATE 2010-07-09: I’ve noticed this page is getting a lot of hits, I haven’t had a chance to get this working yet so if anyone does please post a comment or drop me a mail using the contact page. I’ll try and get some time next week to look at it again.

These scripts are a work in progress and you should check back regularly for updates until I mark them as final.

This is an updated version of the “SCCM Get Dell warranty info

Basically the problem with the other script is that a user with admin privs must run it or the computer account must have access to the internet.

I have split the script in 2 and rejigged it slightly so that now 1 (user) script is run “When user is logged on with the users privliges” and the other (system) script is run 2nd “When user is logged on with administrative privliges”. You can use the “Run another program 1st” option in the program definition which should make it practically act like a single script.


  • Write System Script to run before the user script to create a directory with permissions for the user to write to work around windows 7 / vista permissions problems
  • Calculate the “Days Left” in code so that it is accurate when the Admin Script detects picks it up – Calculated in SQL now.
  • Get Admin script to bail if file is missing
  • Remove File at end of admin script.

Known Issues:

  • System script doesn’t seem to be working properly atm. 2 possible causes:
    • Script isn’t looking in correct %TEMP% dir when running from SCCM – it is when I run it as admin using win7
    • Script doesn’t like running the user script 1st for some reason.

Change Log


Version 0.2 – 2010-04-13

  • Calculates Days left on the fly in the report.

Version 0.1 – 2010-03-19

  • Initial Version

User Scripts:

Version 2.3 – 2010-09-22

  • Updated script to handle dells extra field in the warranty section, new field is placed in CSV

Version 2.2 – 2010-04-14

  • Script now dumps the csv file into the user’s %TEMP%
  • Logging enabled by default.

Version 2.1 – 2010-03-29

  • Better Logging
  • If file not found script now exits instead of crashing
  • changed “strErr” to “strLOG” as it was misleading.

Version 2.0 – 2010-03-19

  • Initial Version

System Script:

Version 2.4 – 2010-09-22

  • Updated script to handle dells extra field in the warranty section, new field is just ignored
  • Added extra logging for the INFILE location

Version 2.3 – 2010-04-14

  • Reads file from user’s %TEMP%

Version 2.2 – 2010-03-30

  • Remove csv file once read

Version 2.1 – 2010-03-29

  • Better Logging
  • If file not found script now exits instead of crashing
  • changed “strErr” to “strLOG” as it was misleading.

Version 2.0 – 2010-03-19

  • Initial Version


  • [download id=”4″]
  • [download id=”5″]
  • [download id=”2″]
  • [download id=”3″]



 wi.datescriptran0 AS [Timestamp data gathered],
 wi.ServiceTag0 AS [Service Tag],
 wi.SystemType0 AS [System Type],
 wi.provider0 AS [Provider],
 wi.shipdate0 AS [Ship Date],
 wi.Description0 AS [Description],
 wi.Startdate0 AS [Warranty Start Date],
 wi.Enddate0 AS [Warranty End Date],
 DATEDIFF(DAY,GETDATE(),wi.Enddate0) AS [Warranty Days Remaining],
 wi.WarrantyExtended0 AS [Warranty Extended],
 wi.dellIBU0 AS [Dell IBU]
FROM v_r_system as [SYS]
JOIN v_gs_Warranty_Info2 AS [WI]
ON sys.resourceid=wi.resourceid
ORDER BY sys.netbios_name0

9 thoughts to “SCCM Get Dell warranty info v2”

  1. Try increasing/decreasing the number at the end of v_gs_Warranty_Info until you get results.

    Or if you look in the report View list you will find the numbers to use.


    Can you privide details of how you got it to work / what OSes it is working on in your Environment?

  2. I have confirmed that the new class is created on all of the client machines, but I still get the error:
    Invalid object name ‘v_gs_Warranty_Info2’.
    Error Number: -2147217865
    Source: Microsoft OLE DB Provider for SQL Server
    Native Error:
    What process is suppose to create the SQL view?

  3. I placed them in a package and pushed from sccm. Using the run 1st option to run the user script before the system one.

    As stated in known issues this isn’t completely working yet. (Running them manually works iirc).

    But if you have time to play with them and get them too I would be happy to post the fully working method & scripts.


  4. How are you running the two vbscripts? Are you running these from a GPO as startup scripts or are they pushed from SCCM? Sorry, but I need a little more direction.

  5. Ok, Moved the comment again.. :D

    I think I have lost the plot here with the jumping, forums work so much better than blogs for this sort of stuff.

    Which scripts work/don’t work for you?
    Which OSs were involved for each script?
    Which OSs Worked/ Didn’t work?

    If you could post the info to the relevent blog posts that would be best for me to track, I’d rather work on 1 script at a time.

    I should point on the original script has never worked properly for me so I can give limited help on it.

    I’m sure you know but you can sort of speed up the detection process by runnning hardware scans on the machines you are testing on.


  6. Actually the last comment was meant to be for :)
    I have already tested this on couple of Dell servers with no success. However, since posting the last comment, I have also tested this on my desktop and it has actually worked – I was able to see my machine when I ran the report.
    My machine is running Windows 7. One of the servers is running Windows 2008 R2 and the other is Windows 2003 – All 64-bit OS’s.

  7. Lat, I moved your comment as you put it in the wrong post. :D

    If you uncomment lines 71 & 72 of the script, they will echo the directory that the csv file should be being created in.

    Most likely it is %temp%

    What OS are you using to test the script?

    If you had the very original working then:

    should just work for you..

    It is the original script broken down into functions & procedures and tweaked for the “new” layout of the dell site.

    The script in this post is intended to be a work around for those of us that cannot use the original script due to security/configuration restricitions


  8. No update yet sorry. I am the only person in work that manages this stuff and we just went through a merger which has doubled our size, so I haven’t even looked at it recently.

    There may be an interesting article on OSD localisation coming up as I am working on that at the moment.

    The known issues section outlines what I think the problems could be, so feel free to debug and update me if you find the actual problem and/or solution.

    I haven’t tested but in theory this should work fine on XP (most likely the user will need local admin). It’s the security model in Vista/7 that are foiling all of the potential work arounds I can think of.


Leave a Reply

Your email address will not be published. Required fields are marked *


This blog is kept spam free by WP-SpamFree.