Hi David, I looked at objectGUID as well. It's also an octet-string and it works ok. But it's one of the default includeds. I tried manually populating the netbootGUID attribute with an octet-string, not sure if it is in the correct format though. This attribute is for diskless systems? Do you have the attribute populated by the system or did you try manually like me?
Andrew From: [email protected] [mailto:[email protected]] On Behalf Of David O'Brien Sent: 09 January 2014 00:21 To: [email protected] Subject: [mssms] RE: AD System Discovery and special attributes Hi Andrew, thanks for the feedback. Interesting that this obviously doesn't seem to work. David From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Andrew Craig Sent: Mittwoch, 8. Januar 2014 17:40 To: [email protected]<mailto:[email protected]> Subject: [mssms] RE: AD System Discovery and special attributes I tried it here in the lab and got exactly the same result. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of David O'Brien Sent: 08 January 2014 09:59 To: '[email protected]' Subject: [mssms] AD System Discovery and special attributes Hi all, has anyone ever added the Active Directory attribute "netbootGUID" to their AD System Discovery? I tried, but failed. WARN: Type not supported for the follwoing optional attributes, netbootGUID, SMS_AD_SYSTEM_DISCOVERY_AGENT 1/8/2014 9:07:39 AM 6888 (0x1AE8) INFO: DDR was written for system 'DO-LAP-0' - D:\Program Files\Microsoft System Center 2012 R2\Configuration Manager\inboxes\auth\ddm.box\adsjqh1u.DDR at 1/8/2014 9:7:39. SMS_AD_SYSTEM_DISCOVERY_AGENT 1/8/2014 9:07:39 AM 6888 (0x1AE8) So it does look like adding the attribute worked, but the type inside that attribute is not supported? I added that device / object via the GUI as managed computer, so it can't have anything to do with me screwing up the format. Anyone got luck with that? Thanks, David
