I've seen this happen when the user trying to provision does not have access to the scope in which the computer resides.
Assuming you are using OSD and not Provisioning, what are your settings in the OSD script? Any more info you can provide would help.
Hi Jeremy G,
I could see the scope causing this, but how do you configure the scope in OSD? The only user account that is configured for the script appears to be used for mapping the drive to the image and imaging tool share. I am using a service account to do the mappings that does not have a scope defined for it in User Management.
Would I need to add this account and assign it a role? If so, which role should I assign to it?
Thanks for your help.
I'm not sure which settings are pertinent in this case, but I've attached the ini file for an OSD task that failed this morning.
I am using ImageW V2 as the imaging tool, but it does not get to that point. I determined that this problem was caused by an existing db entry from the log file that would reference a domain computer name instead of a MAC address that a fresh computer out of the box would show. Here is an example of the log file:
"SNTCW-XXXX","CBA_ERROR:-1917761387",-1917761387,0:30:02,6/27/2011 3:04:27 PM,6/27/2011 3:34:29 PM,"WINPE, TIMEOUT=1800"
; "Job Complete","0 Done","1 Failed","0 Off","0 Unknown"
What happens is after choosing the particular OSD script from the WinPE menu, the target machine will show the Landesk background and do nothing further. The log file will show the failure above. Remove the SNTCW-XXXX from the database and the same process flows smoothly.
I am using ImageW V2, but it does not kick of the imaging utility. If there is any other information you need, let me know.
Thanks for your help.
Admittedly I've only seen this happen in Provisioning, not in OSD, of course I dont use OSD much
But what actually happens when you attempt to start a provisioning job is that WinPE sends a mini-scan of the computer you're working on. Since the MAC address matches the MAC of a machine in inventory it assumes it is the same machine. (This makes sense.)
Then when you log in with your credentials, it sees if you have permissions to execute a provisioning job on that computer. If you dont have the scope, the job fails silently. (This doesnt make sense!)
Again, i do not know if this has anything to do with your issue, but just sharing experience.
Seen this before but only a few times quite some time ago. Does this happen every single time? I am assuming so. The CBA erros leads me to believe that is it trying to talk to the agent for some reason.
Btw, what version of LANDesk are you on? Also what, if any, MCP's have you installed?
Another thing, how are you treating your duplicate devices. In other words, what do you have set under Configure - Services - Inventory - Manage duplicates buttons, primarily "Devices" button.
D'oh... sorry, forgot the basics...
LD 9 SP2 MCP 3/24/2011
For Duplicate Devices:
Remove duplicate when: both device name and MAC address match
restore old device ID's is checked (other options are greyed out)
Duplicate Device ID -> Identity Attributes: Computer.Device Name and Computer.Network.NIC Address
Duplicate Device ID Triggers: log as duplicate device ID when 2 identity attributes change
Reject Duplicate Identities box is checked
I just tried putting a new drive into a computer that I imaged this morning and it went through without a problem. In the task log, it showed the machine name of one that I imaged in the morning. So, it does not appear to be a consistent issue which will make it harder to pin down.
I appreciate your input.
Yeah since it's not consistent it could be tricky to figure out. Try to uncheck "Restore old Device IDs" and see if that makes a difference. I don't use that setting.
1 of 1 people found this helpful
When an OSD task is started from the WinPE menu the client sends the core the MAC address of the client and the GUID of the OSD script it wants to run.
The core then needs to create a scheduled task that targets the machine and uses the OSD script. To do this it has to find the Computer ID from the MAC address, this is unpredictable when there is more than one machine with that MAC address.
What I suspect is happening is that you have more than one entry in the database with that MAC address. I see this most often when the same machine is imaged over and over in testing.
Deleting all the inventory records in the database that share the target's MAC address is one of the troubleshooting steps in this doc (which also contains more info on the calls made to resolve the MAC to computer ID): http://community.landesk.com/support/docs/DOC-3473
If there is only one entry in the database it might work, check to see if there are more than one system in the database with that MAC address and delete all of them but the one you want.
If the Inventory Service is backed up or not running this will also cause problems as we are expecting a mini-scan from the client when it boots to WinPE.