Sorry . Honestly , most of what you have above doesn ' t really make sense at least not with more detail . AD Forest Discovery has nothing to do with collections . AD Forest Discovery simply discovers forests and configured IP Subnets . This in no way will help you create collections . Are you trying to create collections based on IP info of discovered systems that are or will be managed ? Create a limiting collection for what ? AD site information as well as OU information for discovered computers is gathered by AD System Discovery . As long as this is running successfully , then the info will be available in DB and for your query based rules . Also , the System Management container has absolutely nothing to do with any of this . Nothing in ConfigMgr truly depends on this container the purpose of this container is to help clients locate site information . Finally , why a secondary site at all ? Is bandwidth truly that limited between the two locations ? Why not just a standalone DP at the remote location ?