Batch file to extract user profile from OU

[yokoyoko]

Have you tried Ed Dyreen 's Code ?

Hi,

Sorry for the late reply. I have tried that as well, it did not capture the infiormation from the OUs, only print on the cmd.

[abc0502]

only print on the cmd.

what do you mean by that ?
does that mean the code show the correct result on the screen

[yokoyoko]

only print on the cmd.

what do you mean by that ?
does that mean the code show the correct result on the screen

Meaning it shows the code/texts created in myNamesIndex.TXT on the cmd. There is no information from the OUs.

Tks.

[abc0502]

myNamesIndex.TXT is supposed to be your full location to the OU file "single file", are you sure you set the correct location

[yokoyoko]

Hi All,

Managed to solve this issue using ldifde -f Exportuser.ldf -s Server1 -d "dc=Export,dc=com" -p subtree -r "(&(objectCategory=person)(objectClass=User)(givenname=*))" -l "cn,givenName,objectclass,samAccountName"

Thanks to DigitalSnow and the rest for help.

Have a good new year ahead!

[foxidrive]

I'm glad to hear you solved it. AD makes a horrible command line to do stuff.

[Squashman]

I'm glad to hear you solved it. AD makes a horrible command line to do stuff.

There are some better freeware tools to export AD information. I have always used Joeware's tools.
http://www.joeware.net/freetools/

But I think the big push is for Windows Server admins to use PowerShell. It has plenty of built-in cmdlets and 3rd party cmdlets to work with Active Directory and Exchange.

[foxidrive]

It's good to see there are better tools out there. I personally have nothing to do with AD or Exchange and will probably keep it that way.

I'm not in the IT market for server admin jobs so I'll pass on those types of queries.

[DigitalSnow]

Glad that you got ldifde to work.

No need to use 3rd party tools when there are native solutions. That is my focus when using batch anyway.

[Squashman]

Glad that you got ldifde to work.

No need to use 3rd party tools when there are native solutions. That is my focus when using batch anyway.

I agree with the native solutions. But some times the 3rd party works better as is the case with many of Joe's tools. Many of the tools he wrote were because Microsoft never provided a tool to do that specific job at the time he wrote it. If you read some of the stories behind some of his tools you will even see him get challenged by Microsoft saying it could not be done. Don't remember which tool that is but remember reading it many years ago.

[abc0502]

I suggest dostips.com create a compressed pack of 3rd party tools, that can do what batch file can't and this pack uncompressed to the system32 directory. by that they can be just like any other dos command and if the help file can be changed to add these tools that will be more that great .

Note:
To avoid any legal problems about distribution , i think free tools will be better.

[Squashman]

I suggest dostips.com create a compressed pack of 3rd party tools, that can do what batch file can't and this pack uncompressed to the system32 directory. by that they can be just like any other dos command and if the help file can be changed to add these tools that will be more that great .

Note:
To avoid any legal problems about distribution , i think free tools will be better.

But even then you should read the License that came with the Free Tool just to make sure it is OK to distribute the program by other means then the authors website. It always good to send a note to the author as well.

[abc0502]

Actually you have a point i remembered now a tool that is used to create multi-boot usb, it say free for personal use.

I guess then a topic that has a name or a link of the tools well be enough .. or just re invent the wheel