As we’ve started using LabTech in our office we wanted to integrate it as much as possible within Autotask.
Here’s a list of the things we discussed with LabTech which should be ready by Early May. This article is also VERY helpful about to any company considering the products in that it explains exactly what the integration does RIGHT NOW 4/13/2011.
CI are created when the “Update Computers to Autotask” selection is made from the pull down menu “Tools”. This is run every 12 hours if the option to automate CI is selected in the integration.
AutoTask Configurations = To LabTech Computers
- Name (ProductID) = ServerID or WorkstationID – LT -> AT (ALWAYS OVERWRITTEN)
- FUTURE: No update if exists
- FUTURE: On Create: OPTION: DEFINED PRODUCT TYPE, Create Product (CURRENT)
- Active = 1 - LT -> AT (ALWAYS OVERWRITTEN)
- CI Type = DeviceType from autoTask -> Uses “LabTechDevice” by default, does not update after creation
- InstallDate = AssetDate -> On auto create it will match the date, after creation it will not over write it.
- Location = LocationName -> Will overwrite AT information with LT information
- Notes = User Notes -> Only added from LT -> AT on creation of the device
- ReferenceNumber = Computer Name -> WRONG, uses Reference Title = Computer Name
- FUTURE: OPTION: LT Computer Name -> Ref Title, LT Computer Name -> Ref Num (The field that is not updated should not be edited)
- SerialNumber = BIOSFlash SN: String -> Doesn’t enter anything in AT
- FUTURE: LT -> AT !! NOT AS CRITICAL AS OTHER ISSUES ABOVE !!
FUTURE: AT CI Live Link direct to the LT machine interface.
There was a concern from a partner that tickets closed in AT were not closing in LT. We have not duplicated this problem.
The current time frame for these changes is early May.
Further information on the integration is here.
If there is something important to your firm regarding the LabTech Autotask integration please let us know!
If you are a company that uses Autotask and you’re interested in LabTech fill out this form for a free consultation with one of our experts.
