Have you tried manually kick off the Task via Websdk html forms as the user who have this problem?
Yeah, same result. Using the web form they can schedule the task and start it, but cannot add the bare metal device to it.
if the user could see the bare metal devices at the console and it is working as an admin user this should be a bug.
We are using LANDesk Process Manager to do this, maybe a solution for you.
I'll have to look into Process Manager. Thanks for the suggestion.
I also tried to use the "ScheduleProvisiong" command through the web MBSDK and tried to add the computer as the task was scheduled. That didn't work either.
I'll work with support to see if there's a way to get this to work without the user having access to "All Devices".
I think I figured out a way to do this in case anyone is interested. I ended up using the three separate commands, but connected using New-WebServiceProxy and specified two separate name spaces. This allowed me to use the tech's credentials to schedule the task and use our service account credentials to add the machine and start the task. Here's an example:
$ldWS = New-WebServiceProxy -uri http://$coreservername/MBSDKService/MsgSDK.asmx?WSDL -Namespace CreateTask -Credential $global:Credentials $ldWS = New-WebServiceProxy -uri http://$coreservername/MBSDKService/MsgSDK.asmx?WSDL -Namespace AddMachine -Credential $ServiceAccount
The only down side is that even though the device is added to the task, the tech can't see it until they manually refresh the scope. It does exist however and they can boot the machine to provisioning.
Does anyone know if there's a way to refresh a query based scope using the MBSDK? I tried the run query command, but that didn't seem to do much.