We have a separate Bare Metal scope setup and give all of the techs access to that scope as well as their local scopes. Sometimes they have to refresh the scope, but they are able to provision the machines without a problem.
I'm not entirely convinced that your problem is immediately related to scopes as such - scopes tend to be resolved once per hour in the background (unless you're logging on as an admin). There could be all manner of comms that are causing you grief.
So - first of all ... a bunch of troubleshooting related articles:
- How to troubleshoot Provisioning Template Actions - Video
- How To: Troubleshoot Provisioning Template Action Handlers
- How to enable XTrace Diagnostic logging in LANDESK 9.6 Core and Clients -https://community.landesk.com/support/docs/DOC-32532
Then there's also SP3 for 9.5 (since you're on SP2, which is a rather old level), as well as post SP3 patches.
Generally / really, I'd suggest moving to an actively supported version (9.5 has been EOL'ed (End Of Life'd) back in December 2015), as 9.5 isn't getting any patches / security updates any more. But you can still request the "latest" post SP3 component patches (you'll want BASE for provisioning) from support if need be .
In addition, you want to look at the IIS logs (it's possible that it's actually IIS that's acting up) and it just so happens that your clients are timing out when altering the scopes.
- IIS Troubleshooting and LANDESK Management Suite: 101
- How to troubleshoot IIS using Log Parser Studio from Microsoft
... so - long story short - I don't think you're doing something "wrong" (your scope looks fine), but are running into an actual tech issue (be it IIS-side, network, or something else), and I think the scopes are more likely to be an unintentional red herring potentially. You may want to get in touch with support either way (if only to get the "latest" post SP2 patches if need be).
Sorry, typo. I'm on 9.5 SP3 and soon to upgrade to 2016. I think I resolved the issue. In my scope query I listed above I added the following "or statement"
Or "Computer"."OS"."PreBoot OS" = "WinPE"
I can now see the bare metal device in my scope before they are named and typed.
Awesome - glad to hear you figured it out .
In case you end up needing to add devices "on the quick" & force a re-resolution of scopes, you can do that via the MBSDK (as it has a method to do that).
How does one use the MBSDK? Here's an article all about that (with examples) - Getting Started with the MBSDK (Example Scripts Included) - and since the LD 2016 BOOT.WIM's in LD 2016 come with both PowerShell & .NET as well as being bumped to Windows 10 PE, you've got quite a bit of freedom in how you want to script such an operation.