Jump to content

DarrenDK

Members
  • Content count

    8
  • Joined

  • Last visited

  • Days Won

    2

DarrenDK last won the day on July 11

DarrenDK had the most liked content!

Community Reputation

8 Neutral

My Information

  • Agent Count
    1500+

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)

    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.
  2. 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.
  3. 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.
  4. Ensure PowerShell version 4.0 or higher is installed on the LabTech Server itself (Needed for Invoke-RestMethod to not prompt for credentials) Extract LabTechWarrantyUpdaterModules.zip to C:\Program Files\WindowsPowershell\Modules 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 LabTechWarrantyUpdaterModules.zip Update-MissingWarranties.xml
×