locked
Object replication from Central to Primary site and from primary to central??? RRS feed

  • Question

  • Hi,

    In our environment System Discovery is enabled in Primary sites only, now my question is how objects will replicate in

    console, it will first discovered in Central Site console or Primary site console or vice versa.

    According to my knowledge they should first discover in primary site as the system discovery is enabled in Primary site ,then it should replicate to central site as there in central system discovery and heartbeat discovery is disabled, only User group discovery and system group discovery is enabled on central site.

    Is there any other possibility according to which object will discover in primary first but will register in central first ,so they will replicate from central to primary site?????????

    Any help on this is appreciated


    Monday, February 17, 2014 10:02 AM

Answers

  • This doesn't answer all of your questions, but should help: http://myitforum.com/cs2/blogs/jgilbert/archive/2007/02/22/sms-2003-client-push-installation-method-explained.aspx

    Jason | http://blog.configmgrftw.com

    • Proposed as answer by Garth JonesMVP Saturday, December 27, 2014 10:45 PM
    • Marked as answer by Garth JonesMVP Saturday, January 3, 2015 4:11 PM
    Monday, February 17, 2014 2:15 PM

All replies

  • To answer your first question, please note that in sccm the discovery data always flows up in the hierarchy.... So it will be primary site and the information is passed up to Central site.. And there is no such thing like discovering in one site and processing it in another site unless it is primary-secondary, where the secondary site do not process the discovered item rather it will pass to primary for processing... IN your case, the primary will discover the resources and process it and the data is just passed up to the central site server...

    bluerail

    Monday, February 17, 2014 10:43 AM
  • Hi Bluerail

    thanks for reply , but when we are searching newly build machines they are reflecting in central first then in primary sites.

    that's why I m confused??????

    Monday, February 17, 2014 10:49 AM
  • Yes... The DDR processing for a record already in a database is processed at the primary site, whereas the DDR for a newly discovered resource will be processed in the top-most level in the hierarchy.... 

    DDRs for newly discovered resources that are not in the database are processed at the top-level site of the hierarchy. The top-level site creates a new resource record in the database and assigns it a unique identifier. DDRs transfer by file-based replication until they reach the top-level site.


    bluerail

    Monday, February 17, 2014 11:01 AM
  • the replication will always happen from Secondary to Primary and then primary to central.. If you have multiple primary sites.. we should be having a central site to manage them. so the info and replications will happen from Primary to Central.  the objects discovered by primary will be passed to central.

    ----Please vote if this is helpful----- -----Knowledge is Power-------- Ajo Abraham [MCP] [MCTS]

    Monday, February 17, 2014 11:19 AM
  • the replication will always happen from Secondary to Primary and then primary to central.. If you have multiple primary sites.. we should be having a central site to manage them. so the info and replications will happen from Primary to Central.  the objects discovered by primary will be passed to central.

    ----Please vote if this is helpful----- -----Knowledge is Power-------- Ajo Abraham [MCP] [MCTS]

    Actually, his concern is that the newly deployed systems are appearing in the central first., thats what since it is a new DDR record to be recorded in the database it probably would have appeared at the central first rite...

    bluerail

    Monday, February 17, 2014 11:34 AM
  • hey Bluerail

    again many thanks for your efforts

    can you provide me any technical links for this as we already come to know that newly build machine DDR will reflect in central first although it is processing in primary site

    The problem is that before new build we are deleting the existing objects from SCCM 2007R3 console and disabling the object in AD ,when the build starts we are enabling that object ,then it will come in unknown computers,with the help of that we are building new machine(unknown computer support)during build

    sccm client will also install but before that system discovery happens sccm already have one record Client=No

    and approved=N/A after that during task sequence sccm client installs then heartbeat-discovery happens 

    another object occurs Client=yes and approved=yes.

    Now i have already gone through this article http://blogs.technet.com/b/configurationmgr/archive/2011/08/17/known-issue-and-workaround-duplicate-records-when-you-use-unknown-computer-support-with-active-directory-delta-discovery.aspx

    According to this article if first object created by AD system discovery then you should delete that object and if it occurs after the object created by Heartbeat Discovery then it will merge later.

    OK no problem now we are manually Deleting objects from central Site, but if we are deleting it from central site it is reflecting in primary site, if we are deleting one object from central site then it should replicate to primary site. This is not happening ,every time we are building machine we are having the same problem ,which is described in article, although we have enough resources to delete objects manually from SCCM , we don't know ,which is the best way to do that .Its totally confusing we contacted Microsoft they are saying in your environment there is timing issue as in our central-site only securityGroup discovey is enabled and user group discovery is enabled but in primary site AD System discovery nad And AD system group discovery and HeartbeatDiscovey is enabled .they are saying in centarl discovery is happening every 4 hours and in primary it is happening every 12 hours, so its a timing issue(timing mismatch issue)due to which Duplicate entry problem happening.

    any workaround for timing issue in discovery ,as i am confused in SCCM centralSIte no system discovery is enabled, only security Group discovery and user Group discovery enabled.

    many thanks in advance..........



    Monday, February 17, 2014 2:08 PM
  • This doesn't answer all of your questions, but should help: http://myitforum.com/cs2/blogs/jgilbert/archive/2007/02/22/sms-2003-client-push-installation-method-explained.aspx

    Jason | http://blog.configmgrftw.com

    • Proposed as answer by Garth JonesMVP Saturday, December 27, 2014 10:45 PM
    • Marked as answer by Garth JonesMVP Saturday, January 3, 2015 4:11 PM
    Monday, February 17, 2014 2:15 PM
  • Hi Jason

    Thanks for this wonderful article it clears many things

    but in our scenario the problem is between Central and primary sites

    I am not able to find out any article which gives any info about Central and primary site Object replication

    due to which we are having Duplicate entry problem during New build machines.

    As i have already explained in my previous post that there is a difference of discovery timing in Central and primary sites.

    Thanks in advance

    Tuesday, February 18, 2014 9:25 AM
  • This doesn't answer all of your questions, but should help: http://myitforum.com/cs2/blogs/jgilbert/archive/2007/02/22/sms-2003-client-push-installation-method-explained.aspx

    Jason | http://blog.configmgrftw.com

    HI Jason

    Sccm 2007R3 have duplicate computer object problem due to Unknown computer support and Delta discovery

    according to this article http://blogs.technet.com/b/configurationmgr/archive/2011/08/17/known-issue-and-workaround-duplicate-records-when-you-use-unknown-computer-support-with-active-directory-delta-discovery.aspx  .

    Is this problem solved in SCCM 2012,if yes can you tell me how they have resolved this bug of sccm 2007r3??

    Many Thanks in advance,

    Friday, February 21, 2014 2:10 AM