The problem is: We find some Macs out at one of our properties, we tell them how to self-enroll into Casper, and they get a message that the quickadd package has failed. The reason it failed is because it's trying to bind these Macs to AD but they are already bound, so it attempts to bind 5 times and then fails out.
The rest of the process actually worked, the Mac is enrolled, the polices have taken effect, but on the client side the installer says it failed. And nothing is actually wrong, I mean as long as it's already bound to AD then mission accomplished.
So my question is how can I prevent the installer from failing out if the Mac is already bound to AD? I tried setting up a smart group that checks if the Mac is already bound to AD but then it becomes a chicken or the egg problem - the smart group is only comprised of Macs already enrolled into Casper, and this is an issue AS the enrollment process is happening so it won't see the Mac we're trying to enroll when it checks to see if it's bound to AD or not, because it's not checking on the Mac itself, it's checking against the Casper smart group.
So would the solution be somehow getting the AD policy, or maybe a script, to check to see if the Mac itself is bound to AD before attempting to bind it? Or is the solution more along the lines of suppressing failure warnings? Suppressing it is fine, I don't care as long as it's bound to AD one way or the other. I just don't want the installer to fail out because of it.
