The GUID (or SMSUID) definitively identifies a resource. If it exists in the DDR, it alone is used to match the DDR to a record in the database. Because the value of this property for a particular resource should not change from discovery to discovery, it is an artificial value that is generated by the client. The GUID property is always taken from the architecture definition in the database. As a result, if this flag is set for a property in a DDR, it is meaningful only if the architecture has not been created yet. For the System architecture, the GUID is the string property "SMS Unique Identifier".

Prior to SMS 2003 SP1, changes were allowed to records if a DDR arrived with a new GUID but with the same key properties. As of SMS 2003 SP1, this changed—a new GUID generates a new record even if the key properties remain the same.

Important
GUIDs are case insensitive; however, the case should never vary after the GUID has been submitted to the database. GUID processing issues will arise, if the GUID changes case.

Key properties are physical properties that individually can be used to uniquely identify a resource. Because they are physical properties, they might be subject to change. For this reason, in addition to the fact that not all discovery agents can discover a particular property, an architecture should have several key properties. The key property setting is taken from the DDR, not the architecture definition in the database. For the System architecture, the key properties are "MAC Addresses" and "NetBIOS Name".

A property can have either a single (scalar) value or multiple (array) values. The array flag in the DDR should match the architecture definition.

The meaning of this flag depends on whether the property is a scalar property or an array property. If it is a scalar value and this flag is set in the DDR, the DDR value should overwrite the database value only if the database value is null (not set). Usually, the value in the DDR overwrites the value in the database. If the property is an array property, the set of values in the DDR should fully replace the values in the database. Typically, the values in the DDR are added to the set of values in the database. This flag setting varies from discovery agent to discovery agent and is taken from the DDR. One example of this is the IP Addresses property reported by Network Discovery. Because Network Discovery might not be able to discover all the IP addresses for a computer, the Full Replace flag is not set in its DDR.

Each resource has an auto-generated name property called Name, which is generated by the Data Discovery Manager (DDM). This property is used as the display name of the resource and shows up as the name in the collection membership. If a Name property exists in the DDR, it is overwritten. The Name property is selected from the first non-null DDR property with the Name flag set. The properties are tried in the order according to the ordering flags. Each name candidate property should have both the Name flag and an ordering flag set. If a Name2 flag is set, it is taken as the description and appended to the Name property in parentheses: "<name> (<name2>)". The name flags are taken from the architecture definition but can be overwritten in the DDR. The DDR is rejected as corrupt if the Name property cannot be populated. The name properties for the System architecture in order of preference are "NetBIOS Name", "Resource Names", "IP Addresses", and "MAC Addresses".

The property type defines the data type of the property. Each property type can be either a scalar or an array property. Currently used and accepted ones are:

The property type in the architecture must match the type in the DDR.

The length setting is only applicable to string properties and represents the maximum length of the string. The value in the DDR permanently overrides the value in the architecture definition. Therefore, if this setting does not match, it permanently changes the architecture definition.

The property value should be represented in string format. Numbers should be represented in base 10 and contain no non-numeric characters. Dates should be formatted as "MM/DD/YY HH:MM:SS". If the property value is null, it should be set to the string "(null)". The value for a string should not exceed the maximum length.

This property is used by the DDM to determine when to generate a client configuration request (CCR) for push client installation. The property takes the format of "<operating system name> <operating system version>". The operating system name should be the common name of the operating system, not the name of the release ("Windows NT" instead of "Windows 2000" or "Windows XP"). The recognized operating system names for push installation are "Microsoft Windows NT Server" (servers products), "Microsoft Windows NT Workstation" (workstation products), and "Microsoft Windows NT Advanced Server".

Client type 1 is the System Center 2012 R2 Configuration Manager client type.