Thanks for posting here.
Do you have any update on this you can share with the Community.
no solution yet. It seems as if there were issues with our database.
I had a similar issue, it had to do with user permissions. Does it work if you use a landesk admin account?
dgonzalez, your comment was pointing in the right direction.
I had the provisionin tasks created under my personal account. Even though I have admin rights, I have a limited scope. My scope includes PXE added devices, so I didn’t question that further.
Now we created a dedicated user with admin rights and no scope limitations and the templates are being picked up as expected.
I already had opened a support case a year ago, and the problem couldn’t get solved. I raised a new case recently, this time the support engineer saw the issue during our first web meeting.
Very annoying bug that caused a lot of frustration for a long time.
It looks like we are having the same issue, If I start the template with my credentials (has no scope limitations) and it works.
For a standard Landesk Operator with a scope limit, he cant provision and it goes to 40/40 template fail.
Did you get a reply from Landesk Support? a Fix perhaps!.
1 of 1 people found this helpful
Did these instruction not help? How to enable a console user limited by scope to provision new devices that do not have a scope
Also I have you tried creating a query and creating a scope based on that query that has Computer.OS.Preboot OS or you can use Computer.Network.PXEBoot or if your scopes are based on network "Computer"."LANDesk Management"."Agent Configuration Name" NOT EXISTS AND "Computer"."Device ID" = "Unassigned" AND "Computer"."Inventory Server" = "Your Core server name" AND ("Computer"."Network"."TCPIP"."Address" LIKE "Put in your Address Range" OR "Computer"."Network"."TCPIP"."Address" LIKE "Put in your Address Range")
Joe, the document you cite explains the way how to do it right.
What is frustrating for me is that the quality of the service depends very much on the people who work on your ticket. I had two guys working on my issue, one couldn't find the problem, the other one saw it straight away.