1 of 1 people found this helpful
The answer is partially "it depends", because you could be using CSVIMPORT to import mini-scans that have considerably more than just the "bare minimum" of information.
So things like various custom strings for instance (though this would rather greatly complicate matters if you were to try and batch this, since custom data is normally modelled "on the fly", and while you CAN do it manually, this is going to take quite a while to explain).
Which version of LDMS do you use?
If you use a miniscan such as mine:
Network - NIC Address = 000C290EF8D5 Network - TCPIP - Address = 010.010.010.092 Network - TCPIP - Subnet Mask = 255.255.255.000 BIOS - Serial Number = VMWARE-56 4D 33 FC B6 52 6C 91-3F 07 B7 C1 73 0E F8 D4 Device Name = MYMACHINE
Then the tables to look at are:
- COMPUTER (the master table for pretty much anything)
NOTE: If you're going the syntax route of using:
Network - TCPIP - Adapter 0 - Subnet Mask = 255.255.255.0
You're going to have unmodelled data (on account of the Adapter 0 stuff) - which makes thins A LOT more complicated if you want to do this 'by hand'). So I'll skip this for now eh .
P.S.: Best way to reverse engineer these things / find out definitive answers for your data is SQL traces .
LANDesk EMEA Technical Lead
LDSM is 8.8.
What though needs to be set in the database for a barebone provisioning task to kick off once the system is booted using PXE? Currently all we look at is the serial number and off it goes. Then after the base image is installed we run custom actions based on model and manufacturer of each system. These are then followed by a reinstall of apps that the user had installed on their old PC (this process also auto upgrades any older apps to the latest versions. i.e. Office 2003 is replaced with Office 2007 ect.).