New systems 50/50 chance of going into lost and found
We have AD sync with the system tree and when new sytems and imaged there is a 50/50 chance the system object will go into the lost and found branch when it communicates to ePO instead of the branch that maches in the OU.
Sometimes it works as expected and the new object goes where it should.
In the system tree branch where managed object should be is an "unmanaged" object detected by ad sync and the managed object goes to lost ahd found.
To fix it, we have to delete the unmanaged object and drag the managed object into its place in the system tree.
What can we do to ensure new systems go into the correct branch and are not blocked by unmanaged objects?
Is it better if AD sync detecting the computer object happens before or after the client first contacts ePO?
Don't forget, when your helpful posts earn a kudos or get accepted as a solution you can unlock perks and badges. Those aren't the only badges, either. How many can you collect? Click here to learn more.
Community Help Hub
New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.