Unprovision "Unknown"and "Detected" machines remotely

We are using in-band provisioning for our out of band management.  On the whole it seems to work fine, however, there are a significant number of machines (around a third) where SCCM sees the clients as "Unknown" or "Detected".  The oobmgmt.log files on these clients all show "!! Device is already provisioned".

I booted into the Mbex bios (CTRL P).  Unprovisioned a couple of the machines.  SCCM then displayed these as "Not Provisioned".  To get them to provision again I had to re-install the SCCM client on the machines.  They then provisioned no problem.

Was wondering if anyone knows an easy way to automate the unprovisioning in the Mbex bios so that it isn't necessary to log onto all the machines with this issue.


June 6th, 2013 1:37pm


We are running into the same issue (Device is already provisioned in the client logs, and SCCM gives Unknown status)with a relatively small number of systems, which is annoying. 

There is a tool from Intel for unprovisioning systems remotely, but I have not had luck with the systems in this state thus far (but I have not had a chance to look at what the AMT has eaten): Intel AMT Unprovision Utility

Were you able to figure out how to fix this in a more automagic way than going into the Mbex Bios?

Best regards,


Free Windows Admin Tool Kit Click here and download it now
January 9th, 2014 6:09pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics