We had a child OU that was put beneath the incorrect parent OU. We LOCKED all (756) computers in that child OU because there were two actions started that targeted the parent OU (much more than 756 computers).
Now that the computers from the Child OU were moved to the correct parent OU, these 756 computers are still showing as “valid” targets for two actions. We need to UNLOCK the 756 PCs.
Should I stop the actions and re-create them? Or if we unlock them, will the 756 not run the two actions because the OU has changed?
The old child OU no longer exists in Active Directory Computers & Users, but still shows in the console with computers that have not reported in for a few months. Should we remove those computers from the database?
If I understand your question properly, I think the agents will NOT run the action when you unlock them because they are no longer in the OU (which you can double-check before unlocking them). The agents will always double-check their relevance and targeting right before running the action and if something is no longer true, then the agent won’t run the action.
You might want to test it with a couple agents so you can feel more comfortable.
Yes. The BES Console will show the last reported AD OU paths for any computer that is currently in the database. If you have old/retired computers that are still reporting that AD OU and you want to get rid of the AD OU path in your console, you can remove the agents reporting that value.