locked
New clients not getting registered RRS feed

  • Question

  • I've got CAS and 3 Primary sites running SCCM 2012 SP1 CU2.  I've started to see following issue with new clients being installed, but not getting registered hence not receiving policies etc....

    checking DDM.log on each of my primary sites I started to see following entries that would run for hours (see log snippet below), while this process is running my inbox "G:\SCCM\inboxes\auth\ddm.box" would just queue message(s).  If I do stop/start of my sms_executive service, that message in the inbox would be processed and my client is registering just fine.  Initially I thought this has solved my problem but monitoring this now for last few days, it hasn't as I see this process running alsmost constantly for hours, when the SMS backup task kicks in that will do quick stop/start of the sms_executive service and would process some DDR files but in the end does not really solve anything.

    In our environment we are using IP Address ranges for the boundaries, as we couldn't leverage AD Sites/IP Subnets due to use for Supernets, and AD site not being 100% accurate.  We have about 6,000 boundaries and if I look at the logs below it takes almost 15seconds to process each boundary, this process in my opinion will never complete.  Our environment currently has 68,000 clients.

    Any advice suggestions to resolve this are appreciated.

    Log snippet

    Working on site A00           SMS_DISCOVERY_DATA_MANAGER 10/4/2013 1:32:30 AM 5820 (0x16BC)
    Adding assignments for Architecture System, Property IP Ranges, Value 131.190.37.0-131.190.37.63 SMS_DISCOVERY_DATA_MANAGER 10/4/2013 1:32:30 AM 5820 (0x16BC)
    Updating resident sites sql command insert System_SMS_Resident_ARR (ItemKey, SMS_Resident_Sites0) select distinct ac.ItemKey,'A00' FROM System_IP_Address_ARR AS ac INNER JOIN 
      System_DISC AS d ON ac.ItemKey = d.ItemKey  ~ AND dbo.fnGetNumericIPAddress(ac.IP_Addresses0) >= dbo.fnGetNumericIPAddress(N'131.190.37.0') AND
      dbo.fnGetNumericIPAddress(ac.IP_Addresses0) <= dbo.fnGetNumericIPAddress(N'131.190.37.63') and d.Decommissioned0=0  and NOT EXISTS
      (select s.ItemKey from System_SMS_Resident_ARR s where s.ItemKey =  ac.ItemKey and s.SMS_Resident_Sites0 = 'A00'). SMS_DISCOVERY_DATA_MANAGER 10/4/2013 1:32:32 AM 5820 (0x16BC)
    Adding assignments for Architecture System, Property IP Ranges, Value 131.190.193.16-131.190.193.31 SMS_DISCOVERY_DATA_MANAGER 10/4/2013 1:32:45 AM 5820 (0x16BC)
    ..

    Adding assignments for Architecture System, Property IP Ranges, Value 143.30.72.0-143.30.79.255  SMS_DISCOVERY_DATA_MANAGER 10/4/2013 9:46:38 AM 5820 (0x16BC)
    Waiting for 2 seconds for THREAD_ProcessNonUserDDRs to stop.      SMS_DISCOVERY_DATA_MANAGER 10/4/2013 9:46:38 AM 4484 (0x1184)
    Updating resident sites sql command insert System_SMS_Resident_ARR (ItemKey, SMS_Resident_Sites0) select distinct ac.ItemKey,'A00' FROM System_IP_Address_ARR AS ac INNER JOIN 
    System_DISC AS d ON ac.ItemKey = d.ItemKey  ~ AND dbo.fnGetNumericIPAddress(ac.IP_Addresses0) >= dbo.fnGetNumericIPAddress(N'143.30.72.0') AND
    dbo.fnGetNumericIPAddress(ac.IP_Addresses0) <= dbo.fnGetNumericIPAddress(N'143.30.79.255') and d.Decommissioned0=0  and NOT EXISTS
    (select s.ItemKey from System_SMS_Resident_ARR s where s.ItemKey =  ac.ItemKey and s.SMS_Resident_Sites0 = 'A00'). SMS_DISCOVERY_DATA_MANAGER 10/4/2013 9:46:39 AM 5820 (0x16BC)

    Friday, October 4, 2013 8:06 AM

All replies

  • Are each of your boundary groups set to be used for site assignment to the appropriate site?

    My Personal Blog: http://madluka.wordpress.com

    Friday, October 4, 2013 8:30 AM
  • What about MP_RegistrationManager.log (MP) and ClientIDManagerStartup.log (client)?

    Torsten Meringer | http://www.mssccmfaq.de

    Friday, October 4, 2013 8:36 AM
  • yes, each boundary is also configured for site assignment.  We're supporting global company with about 600 remote locations.  we cannot tell which subnet should be used for site assignment and other subnet for content retrieval.
    Friday, October 4, 2013 9:08 AM
  • when I check ClientIDManagerStartup.log the registration remains in pending state, trying every 60, 120, 240, ..... seconds.

    when I did see the messages in DDM.log, I did stop/start of sms_executive and that processed the DDR files, and the client got registered successful.  I can easily reproduce this.  I need to understand why that process to check for the network config or boundaries is taking up so much time and why it would stop the process of DDR's.  I've just checked my primary site in the US, it had same issue last night, "2 second message" around 10:04pm it stopped

    Synchronizing network config data (NCF) files with database. SMS_DISCOVERY_DATA_MANAGER 10/3/2013 10:04:23 PM 4928 (0x1340)
    Synchronization of network config data (NCF) files is complete. SMS_DISCOVERY_DATA_MANAGER 10/3/2013 10:04:44 PM 4928 (0x1340)
    Updated inbox def 15, Discovery Data Manager SMS_DISCOVERY_DATA_MANAGER 10/3/2013 10:04:44 PM 3976 (0x0F88)

    ...

    after that it started to process the backlog (about 56,000 records) that completed around 2:00am EST, and since then working just fine.  My 2 other primaries (Europe/Asia) are still experiencing the issue.

    checking the ddm.log (previous version) I can also see the issue is starting when it's processing .SCA files, file gets created for each site A00.sca; B00.sca; C00.sca  (Site codes for my primary site)

    log snippet

    Rule change detected.  Preparing to process rules...   SMS_DISCOVERY_DATA_MANAGER 10/4/2013 1:32:30 AM 5820 (0x16BC)
    Refreshing site settings.....      SMS_DISCOVERY_DATA_MANAGER 10/4/2013 1:32:30 AM 4132 (0x1024)
    Rule change detected.  Preparing to process rules...   SMS_DISCOVERY_DATA_MANAGER 10/4/2013 1:32:30 AM 1464 (0x05B8)
    Working on site A00       SMS_DISCOVERY_DATA_MANAGER 10/4/2013 1:32:30 AM 5820 (0x16BC)

    Friday, October 4, 2013 9:37 AM
  • yes, each boundary is also configured for site assignment.  We're supporting global company with about 600 remote locations.  we cannot tell which subnet should be used for site assignment and other subnet for content retrieval.

    All boundary groups should be configured for site assignment to their respective site - unless you also have one or more over-arching boundary groups that are used solely for site assignment that contains all boundaries?  I'm not a huge fan of the latter.

    Are your primaries discovery methods optimised for discovering resources only in their respective locations or are all configured the same?


    My Personal Blog: http://madluka.wordpress.com

    Friday, October 4, 2013 9:53 AM
  • our boundary groups are all configured for Site assignment, just like you stated.  My primary sites are configured to only discover resources for that region, we did optimize that already few months ago.

    Friday, October 4, 2013 9:57 AM