With what you have given thus far, this is a long shot. I'm not sure if this will help or not, but the thing that comes to my mind would be to have you verify that you do not have conflicting sort criteria.
Sync type: Active Directory
Synchronize: Systems and container structure
Systems elsewhere in the tree: Move systems from their current System tree location to the synchronized group.
AD domain: You are utilizing an AD server that is a Global Catalog
If you could give us some more info, we may be able to better help you?
1.) Has this ever worked correctly?
2.) Is there any commonality to the systems that do go to L&F? (e.g., same IP subnet, same role, similar naming convention, etc...)
That should get us started.
sorry for the lack of info was waiting on hold with McAfee over an Encryption issue....anyway
Sync type: Active Directory Correct
Synchronize: Systems and container structure Correct
Systems elsewhere in the tree: Move systems from their current System tree location to the synchronized group. Correct
AD domain: You are utilizing an AD server that is a Global Catalog Correct
The system here before was a single sync and then manually updated, when I enable system tree sorting on the clients that are synced they all go to L&F when they check in, and any system that has system tree sorting enabled will seem to go to L&F when thwey check in after a sync.
The sync is happening in a group created under My Org.
So this is a new group with a new Sync and it hasnt worked properly since it was setup. I'm just going to reset the sorting status to allowed and resync AD to see what happens.
I've also checked tasks and there is nothing there to resort the systems based on tags, IP address, names or anything so I can only think there is something squiffy witht the sync process.