import bulk failure

[Guest]

Im having a issue with doing bulk import. I'm unable to get consistency in importing names into their respective OU. Consistency that either it doesn't work at all or it works sometimes but other times it doesn't work.

They will go into user/domainusers fine but not respective OU.

I exported AD then modified names in Excel trying to eliminate any issues. With no luck.

Any suggestions?

 

[Cary Shultz [A.D. MVP]]

Mike,

Have you looked into ldifde? This might be a way. However, if you have an
Excel spreadsheet you might want to stick with csvde.

BTW, you have not mentioned which way you are trying to do this. Simply be
mentioning the Excel spreadsheet we are going to assume that you are using
csvde. However, that might not be accurate. Also, can you give us an
example of what your file looks like.

What do you mean by your last sentence?

HTH,

Cary

Im having a issue with doing bulk import. I'm unable to get consistency in

importing names into their respective OU. Consistency that either it
doesn't work at all or it works sometimes but other times it doesn't work.

 

[Cary Shultz [A.D. MVP]]

Mike,

As far as I can remember you can not make changes with csvde. You would
have to use either ldifde or ADModify ( or possibly the ds* tools ).

Should that not be correct, are you using graham.local.com as your domain
name, or are you using either graham.local or graham.com?

HTH,

Cary

I tried Ldifde and had the same problem, so I decided to try using CSVDE.
I'm using excel spreadsheet. What I meant by my last statement," I

exported AD then modified names in Excel trying to eliminate any issues.
With no luck. " was that I exported my AD file to have correct format.

 

[Guest]

The problem is not that I can't import the names that I can do, the problem is that the names are imported only into user/domain user only. The OU that they are suppose to go into they are not imported into that OU consistently.

This issue is happening with both importing tools, ldifde and csvde.
I am trying to find out why this is happening and what I should do to correct it.

 

[Cary Shultz [A.D. MVP]]

Mike,

I have used ldifde a gazillion times and never had a problem - unless the
syntax was incorrect!

Let's take a look at an example. Say that you have an OU structure of the
following:

Departments

Accounting

Finance

Sales

Marketing

Customer Service

IT


So, the DN of any user would look something like the following:

DN: CN=Cary Shultz,OU=IT,OU=Departments,DC=yourdomain,DC=local
DN: CN=Mike Garrett,OU=Sales,OU=Departments,DC=yourdomain,DC=local
DN: CN=Halle Berry,OU=Finance,OU=Departments,DC=yourdomain,DC=local
DN: CN=Salma Hayek,OU=Accounting,OU=Departments,DC=yourdomain,DC=local
DN: CN=Angelina Jolie,OU=Marketing,OU=Departments,DC=yourdomain,DC=local

If you are creating a user account in a domain by importing an .ldf file
then you need certain attributes with values to be included for every entry
in that particular .ldf file.

Here is an example of an .ldf file that would work:

DN: CN=Cary Shultz,OU=IT,OU=Departments,DC=yourdomain,DC=local
changeType: add
objectClass: user
userAccountControl: 512
sAMAccountName: cshultz
displayName: Cary Shultz
cn: Cary Shultz
givenName: Cary
sn: Shultz
company: NKD Solutions, Inc.
streetAddress: 12345 Main Street
l: Roanoke
st: VA
postalCode: 24014
c: US
co: United States
countryCode: 840
department: IT
physicalDeliveryOfficeName: Roanoke
telephoneNumber: 540.555.1212

For this to work, you need to make sure that the OU structure is already in
place.

What error messages are you getting when you try ldifde? From where are you
getting the .ldf file? Have you manually created it?

ldifde is going to put the user accounts where it is told to put them,
assuming that the structure already exists. By default, WIN2000 wants to
create user account objects in the USERS container. The above entry would
look like this if I were simply creating the user account object in the
default location:

DN: CN=Cary Shultz,CN=Users,DC=yourdomain,DC=local
changeType: add
objectClass: user
userAccountControl: 512
sAMAccountName: cshultz
displayName: Cary Shultz
cn: Cary Shultz
givenName: Cary
sn: Shultz
company: NKD Solutions, Inc.
streetAddress: 12345 Main Street
l: Roanoke
st: VA
postalCode: 24014
c: US
co: United States
countryCode: 840
department: IT
physicalDeliveryOfficeName: Roanoke
telephoneNumber: 540.555.1212

Notice that the only difference is in the first line....

Can you post an example of a user account object that was successfully
created and one that was failed?

HTH,

Cary

The problem is not that I can't import the names that I can do, the

problem is that the names are imported only into user/domain user only. The
OU that they are suppose to go into they are not imported into that OU
consistently.

 

[Guest]

Here is how i am doing it. Like I have mentioned this will work sometimes and others it will not. When it does not work it will import it into users/ domainusers but not into the OU.

dn: cn=steve glass, ou=students1,ou=students,dc=mydomain,dc=com
changetype: add
objectclass: person
objectclass: organizationalperson
objectclass: user
cn: steve glass
sn: glass
givenname: steve
distinguishedname: cn=steve glass, ou=students1, ou=students, dc=mydomain, dc=com
displayname: steve glass
samaccountname: sglass

Hopefully I've correctly typed this out as is being used for my import.

Again, the question is this why it will sometimes import into names into students1 and users/domainusers and then sometimes it will not import into students1 but will import into users/domainusers.

2) if i'm importing names from a database should i still import into ldifde or csvde? Should I use excel or something else if for ldifde ?

thanks
mike