If I bring up a machine in OU=A, Prism creates an OU=A and puts the machine into it. Then I move that machine to OU=B, Prism creates OU=B, and a new object for the machine is created in B, but the old one in A isn't removed, so now the machine installs applications assigned to both OUs. This seems like a flaw to me. In AD, a machine can only exist in one place, so why in the AD replicated portion of the managed machines should it be able to exist in two? It would make sense to me that if Prism Console detected the exact same computer name appearing in a new location, it should remove the older computer object with the same name. This of course would only be within the AD structure that Prism Console is replicating, it should still remain in any manually assigned groups. The way it stands, I now have to managed machines from two locations, instead of one, ruining much of my initial excitement over the Active Directory integration. Am I using it wrong or missing something?