The machines have to show up in the user scope before they can do the provionsing on the machine. So if your engineer have access to the 32 bit console, after they do winpe provisioning, they need to make sure they can see the machine in their devices before they can start the provisioning process. They can click on the icon as shown in the attached screen shot to manually refresh their scope. Provisioning is tied into the users scope, as oppose to OSD which is not.
Capture.JPG 13.9 K
1 of 1 people found this helpful
We also had the same problem at our site. You need to have all devices scope to at least see bare metal devices. Perhaps it is best practice(we do it on our site), to create a seperate account with all devices scope, but only give it provisioning rights. Then you should use that account for provisioning.
The normal users accounts can be given rights to RC, send software and so on, but leave out provisioning.
The downside is that always the same user will pop up in the logs if something goes wrong.
Thanks for your reply.
I will use this workaround, because I need a fast solution.
However, is this the best of LANDesk?
How do others deploy workstations true PXE and using scopes?
Thanks for any feedback
Here is how I got around it in the past. When I imported the devices I added a custom data string called BareMetal. Then I created a query on that string and used that to create a scope. When the device provisions and the new agent is installed that custom data is wiped out so that device then falls out of the BareMetal Scope. Give everybody who will be using provisioning access to the newly created BareMetal Scope and your problem is resolved.