Why do you even have a CAS? Robert
"Spinelli, Robert J" <[email protected]> wrote: >Another team member found the info below, stating that new resources >are created by the CAS and then sent back down to the primary. > >I also spoke to MS, who also confirmed. I don't like that fact that a >CAS needs to be online for new records to be created, but it is what it >is. > >http://technet.microsoft.com/en-us/library/gg712308.aspx > >About Discovery Data Records<javascript:void(0)> >________________________________ >Discovery data records (DDRs) are files created by a discovery method >that contain information about a resource you can manage in >Configuration Manager. DDRs contain information about computers, users >and in some cases, network infrastructure. They are processed at >primary sites or at central administration sites. After the resource >information in the DDR is entered into the database, the DDR is deleted >and the information replicates as global data to all sites in the >hierarchy. >The site at which a DDR is processed depends on the information it >contains: >* 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. >* DDRs for previously discovered objects are processed at >primary sites. Child primary sites do not transfer DDRs to the central >administration site when the DDR contains information about a resource >that is already in the database. >* Secondary site do not process discovery data records and >always transfer them by file-based replication to their parent primary >site. >DDR files are identified by the .ddr extension, and have a typical size >of about 1 KB. >Thank you. > >Robert Spinelli | CTS | GTI | 575 Washington Boulevard, Jersey City, >NJ, 07310, United States| T: +1.201.595.6820 | C: +1.917.538.6192 | >[email protected]<mailto:[email protected]> > >From: Spinelli, Robert J >Sent: Friday, August 9, 2013 1:50 PM >To: '[email protected]' >Subject: RE: SCCM 2012 - CAS - New Records > >Resend... one more time. > >Thank you. > >Robert Spinelli | CTS | GTI | 575 Washington Boulevard, Jersey City, >NJ, 07310, United States| T: +1.201.595.6820 | C: +1.917.538.6192 | >[email protected]<mailto:[email protected]> > >From: Spinelli, Robert J >Sent: Wednesday, August 7, 2013 5:56 PM >To: '[email protected]' >Subject: SCCM 2012 - CAS - New Records > >Can anyone confirm what I'm seeing is correct? > >In looking over the ddm.log on W01 (Tier 2 Primary) after AD Group >discovery finds a machine that was just added to the group; I see the >info below: > >>> The site will not process newly found System from Agent >SMS_AD_SECURITY_GROUP_DISCOVERY_AGENT >[cid:[email protected]] > >We have a CAS, and the discovery is occurring at the Tier 2 primary >called WDR. > >If a new record comes in from a primary (ex: AD Group Discovery, AD >User discovery, client registration for new client) does that new >record 1st need to be forwarded up to the CAS to create the record (I'm >assuming this is how the resource ID for the object is the same on all >SCCM servers) and then sent back down for the primary to process? > >This would mean that if the CAS is down any new records that are >created (new client installed, new groups created, new users added) >won't be processed for my entire environment until the CAS is back >online? That seems like a pretty big single point of failure, as if >the CAS is down I won't be able to do anything with new objects. Our >thinking was if the CAS went down worse came to worse we could always >scope down to each primary and create advert/deployment if need be. It >sounds that wouldn't work for new objects. > >We have over 300k clients, so we need a CAS. > >Thank you. > >Robert Spinelli | CTS | GTI | 575 Washington Boulevard, Jersey City, >NJ, 07310, United States| T: +1.201.595.6820 | C: +1.917.538.6192 | >[email protected]<mailto:[email protected]> > > >This communication is for informational purposes only. It is not >intended as an offer or solicitation for the purchase or sale of any >financial instrument or as an official confirmation of any transaction. >All market prices, data and other information are not warranted as to >completeness or accuracy and are subject to change without notice. Any >comments or statements made herein do not necessarily reflect those of >JPMorgan Chase & Co., its subsidiaries and affiliates. > >This transmission may contain information that is proprietary, >privileged, confidential and/or exempt from disclosure under applicable >law. If you are not the intended recipient, you are hereby notified >that any disclosure, copying, distribution, or use of the information >contained herein (including any reliance thereon) is STRICTLY >PROHIBITED. Although this transmission and any attachments are believed >to be free of any virus or other defect that might affect any computer >system into which it is received and opened, it is the responsibility >of the recipient to ensure that it is virus free and no responsibility >is accepted by JPMorgan Chase & Co., its subsidiaries and affiliates, >as applicable, for any loss or damage arising in any way from its use. >If you received this transmission in error, please immediately contact >the sender and destroy the material in its entirety, whether in >electronic or hard copy format. Thank you. > >Please refer to http://www.jpmorgan.com/pages/disclosures for >disclosures relating to European legal entities.
