Policy shows failed if machine is already bound to AD

[sinnottd]

Hi,

I've got an enrollment policy that binds machines to AD, however some of our machines are already bound. When I tested the enrollment on a machine that is already in AD, it comes back that the policy has failed. Is there a way to ignore the directory bind if its already there?

Thanks

Dave

[nessts · Accepted solution]

if it were me i would probably create a smart group that contains machines that are not bound to AD and only run that policy against those machines. under smart group criteria there should be an active directory status, and you can choose not bound as one of the states to match to.

[sinnottd]

Worked a treat, thanks!