The purpose of this document is to cover the best known methods for ensuring that the custom LANDesk Data Analytics Data (LDDA) inventory data is retained after a full sync inventory scan is ran on a device.
This document is designed to provide an experienced LDDA Administrator with the information they need to ensure that they can retain the custom inventory Data that have created
This document will cover:
- Step that need to be taken to ensure this data is maintained throughout the inventory life cycle
This document assumes that:
- The reader is familiar with LANDesk® Management Suite in combination with LDDA and their concepts and use.
- The reader is able to access and make changes to their Database.
What is Discovery Services?
Discovery Services is part of LDDA and helps an administrator gather information about unmanageable devices for which LANDesk does not offer and agent. These kinds of devices currently have either a very minimal amount of information and are stored in Unmanaged Devices. Using Discovery Services, along with Asset Control, lets the LANDesk administrator gather and store information about these other network connected devices, such as printers, switches and routers, and have that information accessible via the traditional LANDesk console. Discovery Services use network protocols, currently SNMP and WMI, to connect to these network devices and gather available information about them. Using Data Translation Services, this data is then converted into something that is understandable and stored in Asset Control. Items in Asset Control can then be used to display and/or queries created to display this information.
A configuration is the combination of the options in within the red square in the image above. This discovery configuration can either be scheduled or manually ran.
Discovery services can use UDD scan results, from these scan results you can target devices and add them to Asset control. Most of the groups listed above are automatic created, but custom ranges can be added to be scanned for as well.
The option above is using a custom IP address Range.
One could also use the printers UDD group that automatically created (Automatically created UDD group #7 in the discovery services image)
Add Logins if need in environment.
- To add a Login Right click on the word Login.
- Select type of Login in either SNMP (Left image above) or Windows(right Image above).
- By default many devices use the public SNMP String
- Logins will be tried in order from top down
- The options for MIBs are Load, Export or Import(exported file)
- Chose the option that best fits your needs(if any)
- Most discovery Configurations simply use the defaults.
Using Discovery services to find Printers
The examples below will cover how to find an add printers to Asset control.
Step 1) name the configuration and choose SNMP or WMI( for this example SNMP was used)
Step 2) Click next
Step 3) Add the Address(es) (UDD group was used)
Step 4) Click next
Step 5) Add Login(s) (Public SNMP shown above)
Step 6) Click next
Step 7) Default is fine for this example(adjust if needed)
Step 8) Click next
Step 9) Click Finish
NOTE:If remote scanner is needed for network constrains check that option prior to clicking finish
Step 10) If needed Deploy remote scanners, One per subnet
The remote scanner are deployed via a SWD package found under all Packages --> all Packages--> Data Analytics-->Discover services Remote agent
Step 11) Run or schedule Configuration created to run
Step 12) Open Asset Control
Step 13) click refresh (red and blue arrows, Far left Icon on the tool bar)
Step 14) Drill down in Asset to printers.