I forgot to tell you the error code in provisioning at the client
Error code: 80001803H
I had the same issues with CTOS so I took a different approach. I left "Insert unique ID" unchecked and instead used a variable in my sysprep.inf file. The variable you want to use is %ldHostname%. But before you use it, open your public variables window and change ldHostname from "Computer"."Device Name" to "Computer"."Display Name". Don't forget that variables are case sensitive! :-) Below is an example of what the UserData section of your sysprep.inf file will look like.
OrgName="Put Your Company Name Here"
Let me know if you have any problems with this method. Good Luck!
EDIT: By the way, if you still have issues with duplicate devices after using this method, we might need to take a look at how you have your core configured to handle duplicate devices.
first i want to thank you for the help, but it doesn't work....the provisioning runs without any error, but the machines are 2times in the database
here are the lines in the sysprep
and i put a screenshot from my public variables with this answer.....maybe the core is not configured right....can you help me
1 of 1 people found this helpful
There are two things here. First, making sure your duplicate device detection is setup right.
1. Go to Configure and then Services.
2. Choose the Inventory tab.
3. Click on the Devices button.
4. Both device names and MAC addresses match should be check and Restore old Device IDs should be unchecked. Click Ok.
5. Click on the Device IDs button.
6. Identity Attributes should be Computer.Device Name and Computer.Network.NIC Address.
7. Reject Duplicate Identities should be checked and Identity Attributes change should be set to 2.
If you have your core configured this way, then each evening when the core performs database maintenance, it will clean out any duplicates that have been generated due to imaging. The second thing to consider, and I honestly don't know the answer to this, is whether or not what i just described is the way LANDesk is supposed to work. I've always been ok with imaging creating duplicate devices because like I said, they're cleaned out each evening. If someone else can tell us a way to prevent the duplicate from being generated after imaging, please do so!
okay my core is exactly configured like this....then i'll wait till tomorrow and will have a look at this machines.....when the core server will delete the duplicate ones then everything is perfect.....i will give you an feedback tomorrow....thank you very much
okay you were right and today in the morning there were only one of the duplicate machines in the database....Landesk did a good job this night ;-)
so this is perfekt for me now.....thank you very much for your help and i wish you a good day
maybe i will come back with other problems ;-) but i do not hope so
Good deal! Thanks for following up and please do come back. This site has a wealth of knowledge and a lot of LANDesk customers and employees that are more than willing to help when you post questions!