Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


DarrenDK last won the day on January 21

DarrenDK had the most liked content!

Community Reputation

12 Good

My Information

  • Agent Count

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. DarrenDK

    Computer Warranty Updater (HP/Dell/Lenovo)

    When you pulled the warranty information manually, were there other expirations listed? If you want to PM me the service tag I can dig into it. There was someone else saying the warrantyend dates were inaccurate but I haven't found a test case yet.
  2. DarrenDK

    Computer Warranty Updater (HP/Dell/Lenovo)

    Can you provide me the service tag that is giving you the issue? I had a similar issue recently because I was filtering the "AssetEntitlementData" to only show standard warranties so it wasn't including ProSupport. I removed the filter but evidently this has allowed for Digital Delivery to sneak in.
  3. DarrenDK

    Computer Warranty Updater (HP/Dell/Lenovo)

    Word on the street is that the WarrantyEnd field is being deprecated and maybe that is why it no longer syncs. Doing an EDF would be relatively trivial to add to this codebase. Basically just add to the extrafield table a warranty end field, and then upsert entries into the extrafielddata table for each computer. There should be enough reference code inside the Powershell of the script for you to get a feel for how I'm running sql against the database. I'm probably not going to get to this for a while, but if someone wants to take a stab at it and send it to me, I'd happily update this post with it.
  4. DarrenDK

    Computer Warranty Updater (HP/Dell/Lenovo)

    Hey guys, I just updated the script to include this change, and also fix an issue where I was filtering out non-Next Day warranties on Dell computers (it was filtering out ProSupport warranties) Just download and import the .xml from the first post.
  5. DarrenDK

    Computer Warranty Updater (HP/Dell/Lenovo)

    Hey Matt, I removed immense.net, it was unnecessary. The purpose of that script is what it says, to run PowerShell on the LT server. As you can see, the logic is written in PowerShell and needs a place to execute. I couple that with my custom labtech PowerShell module, and it allows me to interact with the database in PowerShell rather than within the rather clumsy LT scripting language. With regards to your specific issue, it looks like for whatever reason the Dell API didn't return a result. Perhaps the service tag(s) it was passing in were invalid?
  6. DarrenDK

    Computer Warranty Updater (HP/Dell/Lenovo)

    I just posted another update that should fix the HP thing once and for all. It's going to update HP warranties in chunks of 25.
  7. DarrenDK

    Computer Warranty Updater (HP/Dell/Lenovo)

    Hey guys, The HP issues should be fixed. I've also embedded the Lenovo logic into the script so the Lenovo module doesn't need to be installed anymore. You still need my LabTech module. Please reference the initial post, I have edited it to have the latest versions. Let me know if this helps!
  8. DarrenDK

    Computer Warranty Updater (HP/Dell/Lenovo)

    OK, so chances are the HP API is not working as expected. The way to debug this is to first save the file in ISE, then it will let you set breakpoints (F9). You can put a breakpoint on the offending line number (248) and inspect the variables by hovering over them to see what they contain. What you'll likely find is that I'm not checking to make sure the results from the HP API are not null before attempting to insert them into database.
  9. DarrenDK

    Computer Warranty Updater (HP/Dell/Lenovo)

    Michael, You don't have to have Manage for this to work. The script will update the warrantyend and assetdate fields in the computers table of the Automate database. The problem is that the WarrantyEnd field doesn't appear to be exposed in the UI of Automate. However, I believe there are reports you can run that will expose this data. Or you can just make your own that use those fields.
  10. DarrenDK

    Computer Warranty Updater (HP/Dell/Lenovo)

    The Powershell that does the magic is inside of the LT script called "Update-Missing Warranties" which is under Immense Networks Scripts folder. You will find the API keys towards to bottom of that script. I'm not sure if it is 100% necessary to get your own key. I'm pretty sure Warranty Master is just using one key for all their clients. I think that's sort of the concept behind giving them to developers. Y'all can just use my keys until they shut us down lol.
  11. DarrenDK

    Computer Warranty Updater (HP/Dell/Lenovo)

    If you are getting this credential prompt, upgrade Powershell to version 5, or at least 4 but you might as well use 5. This is a known bug in Powershell 3.0 that ships with Server 2008 R2.
  12. DarrenDK

    Computer Warranty Updater (HP/Dell/Lenovo)

    My logging here could be better. I may update the script to include more verbose output. The HP API is the one that has the most anal rate limits. Basically you submit all the serial numbers you want to it as a batch job, then it tells you about how long the job will take, and you're not supposed to poll the API again until that time has elapsed, otherwise it will rate limit you and the job gets cancelled. I don't think this will be a problem but if it turns out to be I'll post instructions on how to get these keys. OK so the funny part about this is that I also can't find where it puts the warranty end date in the interface! This is why I decided to include the bit about syncing it to Manage. You can then use existing expiration workflow rules to trigger tickets opening or whatever you want. I have custom reports that pull these fields for QBRs. If you open a computer and click Show Details on the top, you can find Asset Date which is going to be the purchase date. I looked at this from the perspective of the database and placed the data in the fields that seemed to make the most sense.
  13. Ensure PowerShell version 4.0 or higher is installed on the LabTech Server itself (Needed for Invoke-RestMethod to not prompt for credentials) Create the folder C:\Program Files\WindowsPowershell\Modules\LabTech on your LabTech server and place LabTech.psm1 in it Import Update-MissingWarranties.xml script into Automate, ignore warnings about version mismatch 11 - Tools->Import XML Expansion 12 - System->General->Import->XML Expansion Unrestrict the script execution policy on your LabTech Server Set-ExecutionPolicy Unrestricted -Confirm:$false -Force Open Immense Networks Scripts->Update-MissingWarranties, copy the value of the PowershellCode variable into Powershell ISE on the LabTech server and run it. There should be no errors about script execution or modules not found. You may get a rate limit error from the API, but that's relatively normal. Open your _System Automation->Onboarding->Initial System Configuration - Partner Script and insert a Script Run step that runs the Immense networks Scripts->Update-MissingWarranties script Open the Manage Plugin 11 - Click the Connectwise button on the top of the main LabTech Interface 12 - System->Manage Integration Set Manage Plugin to map the following fields (See screenshot below) PurchaseDate to Computer.Asset.TagDate WarrantyExpiration to Computer.Asset.WarrantyEndDate Update 2018-11-09: Refactored code, implemented bulk lookups with Dell API. Attempted to fix HP lookups. Works in small batches. Updated 2018-11-26: Fixed issue with function responsible for breaking computers into chunks of 100. It was returning a flat array with all objects. Modified trim functionality to only trim serial numbers that require trimming. LabTech.psm1 Update-MissingWarranties.xml
  14. DarrenDK

    Help to Monitor a text file for an error

    It occurred to me that if it does disconnect once, even if you resolve it, the monitor will continue to restart the service every time it runs. Are you sure there isn't a better way to test this thing? Perhaps do a netstat -ano and see if the port is listening? Just a thought