1 of 1 people found this helpful
Sounds like the problem is that yoru ThinClients arent reporting their info through WMI correctly. What model are they?
I've seen something similar happen on some odd-ball hardware. The serial number was too long for the LANDesk Database and it failed. Your problem is kind of the reverse of that.
Trying to think of a way to use different data as the identifier.....will get back to you if I can think of it. in the mean time, if you want to get around it, there might be a way.
If you already have a record of these devices in LANDesk (or some other source)....you can pull the MAC addresses and enter them as BareMetal devices. Then pre-scchedule the provisioning jobs. In this way, the LANDesk core will provide an identifier, rather than at run time. (I think!)
Of course if those devices already exist in LANDesk you'd have to delete them first.....
Thanks for your help. They are new thimclients of type wyse RELEW.
I will test your workaround on monday, but i hope it gives a better way to resolve.
Also, please log this problem with support so that we can get a defect request on it. Things that are customer reported have much better visibility in the way we track and work on defects.
The only way i have found is to use OSD :/ Support ticket couldn't help me
This is 'by design'. The only way i got it working is to 'hack' WinPE to disable WMI right before starting the Provisioning job, and to restore WMI as first action as to not interfere with the remaining of the provisioning actions.
Great idea, how do you disable WMI? Is this a service in WinPE?
Yes, but just stopping the service isnt't enough...
I added this to the startnet.cmd:
copy /y x:\windows\system32\wbem\*.dll x:\windows\system32\wbem\*.org
copy /y x:\windows\system32\wmi*.dll x:\windows\system32\*.org
net stop winmgmt
And than as first provisioning action a command file with:
copy /y x:\windows\system32\wbem\*.org x:\windows\system32\wbem\*.dll
copy /y x:\windows\system32\*.org x:\windows\system32\*.dll
net start winmgmt
Please note that I tested this on workstations that had the same serialnumber hardcoded in the BIOS and it worked fine. You still have to test carefully and document this in your environment.