LDIF Conversion Program/Script

  • Thread starter Thread starter David
  • Start date Start date
D

David

Does anyone have a program or script that will convert a
normal ldif file to the format that Microsoft uses for AD?

Thanks, David.
 
I'm guessing that by "normal" you mean you have an ldif file containing the
export of another directory and you want to use it to import those objects
into AD. In order to answer that we'd need to know what directory you
exported the information from. An example would help.

Jason
 
Rereading this I found my tone cold. Please excuse that. Really there's
just not much I can do without more information on the format. I don't have
a script but can start pointing you in the direction of information that has
what you'll need to set.

J

--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
 
No problem. We currently have a Critical Path directory
and are trying to export the schema to ADAM. We tried to
get ldifde to export the schema, but had no luck - it
would return all the user objects, but not the schema.
Here is how the output looks for one of the utilities.

attributeTypes: ( 0.3.2080.6030532.4.7 NAME 'Specialty'
EQUALITY caseIgnoreMat
ch ORDERING caseIgnoreOrderingMatch SUBSTR
caseIgnoreSubstringsMatch SYNTAX
1.3.6.1.4.1.1466.115.121.1.15{32767} USAGE
directoryOperation )

objectClasses: ( 1.0.12073.6.4
NAME 'eDISecuritySubprofile' SUP top AUXILIARY MAY (
eDISecuredObject $ eDISecurityMechanisms ) )

Ldifde likes things a little different. If you have any
ideas or sources that would be great - it's been a pretty
frustrating process so far.

Thanks, David.
 
This isn't a difference in how ldifde works, but in how ADAM and AD works
for schema updates. That output format is a standard way to publish a
directories schema. You can query the schema from AD in that format (get
the DN from the subschemaSubentry attribute from the rootDSE, authenticate,
and query that DN specifying objectclasses and attributeTypes) but it
doesn't accept updates in that format.

Just so you know, I personally don't have much hands-on experience with
AD/AM - just AD. Here's the documentation I found from MSDN on updating
AD/AM's schema:
http://msdn.microsoft.com/library/en-us/netdir/adam/extending_the_adam_schema.asp?frame=true

So what you have is an output format for the schema, likely per RFC 2252 (
http://www.ietf.org/rfc/rfc2252.txt ). You're most likely interested in
sections 4.2 and 4.4 describing the strings for objectclasses and attribute
types. AD's schema is stored as a collection of objects in the Schema
naming contexts. So instead of adding lines to the attributeTypes or
objectClasses attribute of a subschema object you'll add an object for each
attribute and objectclass you're creating. If making a LDIF file for this
is too much work I'm told AD/AM has a GUI schema manager similar to AD's
schema manager but I don't have an AD/AM instance installed to verify this
with.

Sorry, I don't have a script that will parse the subschemasubentry output.

Jason
 
Back
Top