This is from the help file, is this what you are looking for?
Creating custom computer names
The Naming convention page of the OS Deployment/Migration Tasks wizard lets you create computer names based on MAC addresses, text you enter, and counters (nnn...). You can also create names based on inventory data for asset tags, serial numbers, and login names by creating a COMPUTERNAME.INI file.
The values returned by the .INI file substitute for the $MAC token in the wizard's naming convention page.
You can only use the above three inventory values in the file. OS deployment checks the options in the numeric tok<x> order. All three of the above tokens don't have to be in the file. The first tok<x> option found that has an equivalent database entry substitutes for the $MAC token for the device being imaged. For example, in the case above, if there were no asset tag or serial number entries in the database, but there was a login name, the login name would be used for the $MAC token. If none of the options match, the MAC address is used for the $MAC token.
The login name option returns the login name returned by the most recent inventory scan.
Using the nnn computer name token
The Naming convention page of the OS Deployment/Migration Tasks wizard includes an nnn option that substitutes for a 3-15 digit number, depending on how many n characters you specify. For each computer name template you use in the wizard, OS deployment keeps a running counter of the numbers used. This way, subsequent jobs continue where the last job left off.
Every unique template has its own counter. If you always use the same template, the counter will span jobs. If you change your template after deploying some devices and later decide to go back to the template you originally used, the counter remembers where you left off for that template and continues counting.
Customizing the SYSPREP.INF [RunOnce] section with tokenized inventory values
The SYSPREP.INF file contains a [RunOnce] section that specifies programs to run after the device boots for the first time. If you add your own programs to that section, you can include database tokens on the program command line if they're useful to the program you're running. OS deployment substitutes the token you specify with corresponding information from the core database.
%Computer - Device Name%
%Computer - Login Name%
%Computer - Manufacturer%
%Computer - Model%
%Computer - Type%
%Computer - BIOS - Asset Tag%
%Computer - BIOS - Service Tag%
%Network - TCPIP - Address%
%System - Manufacturer%
%System - Model%
%System - Serial Number%
%Processor - Processor Count%
%Computer - Workgroup%
%Computer - Domain Name%
You can chain multiple tokens together. For example, to separate two tokens by a colon: %Computer - Workgroup%:%Computer - Device Name% could return MyWorkgroup:MyComputer.
NOTE: You should only use tokens that return a single value.
Sorry to be such a newbie but where do I save this computername.ini file so that Landesk uses it?
Here is some more info: http://community.landesk.com/support/docs/DOC-1431
"Changing the value $MAC evaluated to is done by creating a COMPUTERNAME.INI file in the same directory as CustJob.exe, which is the ManagementSuite directory or LDMain share on the Core Server."