Hi I was wondering if anyone could help me here. I'm trying to use my own custom attributes (added to the computer class in AD) in SCCM. I added them to the AD Attributes Discovery and can see them being picked up by AD Discovery but for some reason SCCM doesn’t like them saying (adsysdis.log) - WARN: Type not supported for the follwoing optional attributes, MyNewAttribute. I tried various types (all sorts of string types and even integer) and I don’t seem to be able to get it working.. All those optional system attributes (like serialNumber, company etc..) are working fine it’s just those I created aren’t working. For sure I must be missing something there but have no clue what. Any help much appreciated. Thanks! Regards R

Hi, can you provide the information about the custom property that has been created under AD discovery. Also provide adsysdis.log information.Rakesh Kumar

Ok, maybe there’s something wrong with what I’m doing so I'll start from the beginning. I extended the AD schema (it’s W2K8) creating a new attribute (myNewAttribute) trying all sorts of types (Case Sensitive and Case Insensitive String, Print Case String, Unicode String), then I created a new auxiliary class called myNewComputerClass and added the attribute to the class then the myNewComputerClass has been added to the standard computer class thus extending it by the new attribute. I can see (and edit) my new attribute on AttributeEditor tab in Computer object properties (and in ADSI Edit) all is fine I so far. In SCCM I modify AD System Discovery adding myNewAttribute on AD Attribute tab as optional attribute to poll from the AD. After ADSD takes place I can see there’s no myNewAttribute in object properties in Discovery Data. I look for it in the adsysdis.log file and can see – (..) INFO: Processing search path: 'LDAP://OU=CLIENTS,OU=H,DC=HX,DC=COM'. INFO: Full synchronization requested INFO: DC DNS name = 'HDC.hx.com' INFO: search filter = '(&(objectClass=user)(objectCategory=computer))' INFO: ads path = 'LDAP://HDC.hx.com/OU=CLIENTS,OU=H,DC=HX,DC=COM' INFO: Bound to 'LDAP://HDC.hx.com/OU=CLIENTS,OU=H,DC=HX,DC=COM' INFO: discovered object with ADsPath = 'LDAP://HDC.hx.com/CN=PC1,OU=WSUS,OU=Clients,OU=H,DC=HX,DC=com' WARN: Could not get property (domain) for system (0x80005010) WARN: Type not supported for the follwoing optional attributes, myNewAttribute, (..) Last 3 lines are repeated for all discovered machines. What am I doing wrong?

This issue could be a AD issue, not SCCM issue. For your reference: Error in Active Directory System Discovery (0x80005010) http://social.technet.microsoft.com/Forums/en/configmgrgeneral/thread/a6be8c13-334d-4a93-9141-d55d6e5bf441 Hope it helps.

This issue could be a AD issue, not SCCM issue. For your reference: Error in Active Directory System Discovery (0x80005010) http://social.technet.microsoft.com/Forums/en/configmgrgeneral/thread/a6be8c13-334d-4a93-9141-d55d6e5bf441 Hope it helps. Hi the "Error in Active Directory System Discovery" - (0x80005010) relates to a property either because it's not set or doesn't exist. I don't think it has anything to do with my custom attibutes because - 1. Even if I remove my attibutes I get same error "coudn't get property (domain)" 2. When I specify any other system attibute from the computer class (serialNumber, company etc) it does work although it's still saying "couldn't get property (domain)" I don't think there's a property/attribute called "domain" in the computer class (I can't see it anyway)

Hi you can't modify the schema if you're not schema admin

are you able to find new attribute on all computer object. If no delete the attribute you have created and use below link for creating new attribute in schema- http://technet.microsoft.com/en-us/library/bb727064.aspx hope it will help you.Rakesh Kumar