none
AD LDS LDIFDE question

Answers

  • Hey Jedi,

    I wanted to verify that an entry in users.ldf has a valid DN that maps to an application partition in AD LDS. For example, if your entries have DNs that look like this: dn: CN=Jedi,OU=People,O=Contoso,C=US then you will need to make sure that you have an application partition for O=Contoso,C=US and an organizational unit object for OU=People.

    I don't think there's anything wrong with your ldifde command (assuming you meant -i [for import] and not -l).

    Cheers,

    Tom Houston, UK Identity Management Practice

    Friday, April 21, 2017 9:03 PM
  • Hey Jedi,

    Right, now we're getting somewhere. Try appending this to your ldifde command:

    -c "CN=Schema,CN=Configuration,DC=X" #schemaNamingContext

    Cheers,

    Tom Houston, UK Identity Management Practice

    Friday, April 21, 2017 9:13 PM

All replies

  • Hey Jedi,

    Can you post an entry from users.ldf?

    Cheers,

    Tom Houston, UK Identity Management Practice

    Friday, April 21, 2017 7:33 PM
  • how do I do that? I am not accustom to working with AD LDS at all
    Friday, April 21, 2017 8:26 PM
  • Hey Jedi,

    Open users.ldf in Notepad, highlight the first record, copy it and paste it here.

    Cheers,

    Tom Houston, UK Identity Management Practice

    Friday, April 21, 2017 8:31 PM
  • The file has sensitive information, I can not add it here.

    What command should work? I used the following:

    ldifde -I -f "users.ldf" -s servername

    That's what gave me the error, the command used any other way would not work for me.

    Friday, April 21, 2017 8:40 PM
  • Hey Jedi,

    I wanted to verify that an entry in users.ldf has a valid DN that maps to an application partition in AD LDS. For example, if your entries have DNs that look like this: dn: CN=Jedi,OU=People,O=Contoso,C=US then you will need to make sure that you have an application partition for O=Contoso,C=US and an organizational unit object for OU=People.

    I don't think there's anything wrong with your ldifde command (assuming you meant -i [for import] and not -l).

    Cheers,

    Tom Houston, UK Identity Management Practice

    Friday, April 21, 2017 9:03 PM
  • The DN has the following

    CN=Schema,CN=Configuration,DC=x

    the DC=x is a problem

    I will look at replacing it with the AD LDS instance I have setup

    is that the approach I should take?

    Friday, April 21, 2017 9:06 PM
  • Hey Jedi,

    Right, now we're getting somewhere. Try appending this to your ldifde command:

    -c "CN=Schema,CN=Configuration,DC=X" #schemaNamingContext

    Cheers,

    Tom Houston, UK Identity Management Practice

    Friday, April 21, 2017 9:13 PM
  • thanks
    Friday, April 21, 2017 9:14 PM