Return
-
Title
Import of hosts NIS maps creating device type objects. -
Description
When running the RFC 2307 NIS Map Import wizard, it is creating entries from the NIS hosts map as "device" objects in AD. These device objects include an ipHostNumber attribute, which in AD is not an associated attribute of the "device" class object.. Which AD object class should the NIS Map Import Wizard be creating for the hosts NIS Map? -
Resolution
The IpHost is an auxiliary class to Device. IpHost object cannot be made however you can make a Device with the attributes from iphost. Please see below data from our lab:$ sv -u host/ search -b cn=schema,cn=configuration,dc=cpr1,dc=vas -s one "(cn=device)" auxiliaryClassdn: CN=Device,CN=Schema,CN=Configuration,DC=cpr1,DC=vasauxiliaryClass: ipHostauxiliaryClass: ieee802DeviceauxiliaryClass: bootableDevice$ printf "dn: cn=host3,CN=Computers,DC=cpr1,DC=vas\nchangetype: add\nobjectClass: ipHost\nIpHostNumber: 192.168.1.1\n\n" | /opt/quest/bin/ldapmodify -v -u administrator@cpr1.vas -w Test123 -c -H DC://cpr-ad.cpr1.vas@cpr1.vasadd objectClass:ipHostadd IpHostNumber:192.168.1.1adding new entry "cn=host3,CN=Computers,DC=cpr1,DC=vas"modify completeldapmodify: 00002099: NameErr: DSID-03050EB2, problem 2005 (NAMING_VIOLATION), data 0, best match of:'CN=Computers,DC=cpr1,DC=vas'$ printf "dn: cn=host3,CN=Computers,DC=cpr1,DC=vas\nchangetype: add\nobjectClass: Device\nIpHostNumber: 192.168.1.1\n\n" | /opt/quest/bin/ldapmodify -v -u administrator@cpr1.vas -w Test123 -c -H DC://cpr-ad.cpr1.vas@cpr1.vasadd objectClass:Deviceadd IpHostNumber:192.168.1.1adding new entry "cn=host3,CN=Computers,DC=cpr1,DC=vas"modify completeFor reference:https://msdn.microsoft.com/en-us/library/ms677964%28v=VS.85%29.aspx