CSV import not working consistently and improvement suggesti
I'm trying to import a few users from a CSV file that was extracted from AD with the following command (which I believe is part of the W2K resource kit):
csvde.exe -r "objectClass=user" -f output.csv
I edited down the output file to hold only two lines, containing two test accounts I want to import in.
I mapped nearly every field to an input field, with the exception of the password and employee ID fields.
But the import is not working consistently. In my test case, I had only two lines, and I'd not get the first line. Once the 2nd one failed, but the first one had a partial entry already in the system due to a mail I sent from that account to the SD account.
Thinking that perhaps the 1st line is thrown out as a "header line", I put the first line in which generates the field names, but then I'd get NO records imported.
So I'm abandoning trying to import records, as a means to create user entries.
On top of that, there should be a saved "template" that one could select which has all the proper field mappings that you took the time to map out earlier. It was tedious to run tests and have to manually input each field location time and time again.
THEN you should display a sample input to be sure you're getting the fields you think you're trying to get.
Justin
csvde.exe -r "objectClass=user" -f output.csv
I edited down the output file to hold only two lines, containing two test accounts I want to import in.
I mapped nearly every field to an input field, with the exception of the password and employee ID fields.
But the import is not working consistently. In my test case, I had only two lines, and I'd not get the first line. Once the 2nd one failed, but the first one had a partial entry already in the system due to a mail I sent from that account to the SD account.
Thinking that perhaps the 1st line is thrown out as a "header line", I put the first line in which generates the field names, but then I'd get NO records imported.
So I'm abandoning trying to import records, as a means to create user entries.
On top of that, there should be a saved "template" that one could select which has all the proper field mappings that you took the time to map out earlier. It was tedious to run tests and have to manually input each field location time and time again.
THEN you should display a sample input to be sure you're getting the fields you think you're trying to get.
Justin
