Skip to main content

Export users or groups from active directory by LDIFDE Export

 Introduction to LDIFDE Export

The purpose of this page is to show you how to export user accounts from Active Directory. The killer advantage of LDIFDE over CSVDE is that you can modify existing objects with LDIFDE (but not with CSVDE). The disadvantage of LDIFDE is that it will not sit nicely in my spreadsheet, whereas CSVDE data is made for a table.
In term of learning, the tricky LDIFDE switches, it is much easier to begin with the export commands before moving on to import.
Here are scenarios to use LDIFDE:
 Adding a bulk lot of new users to Active Directory, complete with passwords.
 Modifying existing users or groups in Window Server 2003 or Windows 2003.
 Exporting Active Directory information. You may want to modify attributes then import again.
 Changing schema information, for example adding email attributes.

Let us pause for a minute to think of what the acronym LDIFDE means. The L stands for LDAP. LDAP is the Active Directory language, protocol, method of finding objects. In this context, DIF means Data Interchange Format, whilst DE means Data Exchange. Put it altogether and you have LDIFDE - the name of the executable that you can use to manipulate user accounts and other objects in Active Directory.


It is no surprise that you need Active Directory installed before you can use LDIFDE. However, once Active Directory is installed you can execute LDIFDE from the command prompt. ˚


LDIFDE Export Examples
1. Getting started
The situation is, you want to extract user accounts from Active Directory. Perhaps you are doing this with a view to making changes, then importing them back into Active Directory. Alternatively, you may just want to practice the export to gain experience because LDIFDE -f filename, is harmless compared with the import command. Note that export is the default so you do not need a -i switch, all you need is the -f switch and a filename.
ldifde -f export.ldf -s BigServer (Where BigServer is your domain controller and export.ldf is the filename)

In theory you can export user accounts by just giving the filename, but I find you need the -s switch to connect to the server. (-s BigServer)

Type your ldifde commands in notepad, then save as a .bat file then execute your .bat file from DOS.
2. Adding filters with -r
Use the -r switch to filter your data, for example: the command to export only computer objects on a server called BigServer is:
ldifde -f ExportComputer.ldf -s BigServer -r "(objectclass=computer)"


Gradually add to your basic ldifde file, pay attention to the syntax e.g. "speech marks", commas
Exporting only the LDIFDE fields you want with -l (lower case L)
ldifde -f ExportUser.ldf -s BigServer -r "(objectclass=user)" -l "dn, cn, givenName, sn, department"
You can see that ldifde uses LDAP attributes so it worth learning the basics of the names and what they are used for. See more in my ebook.
Summary of LDIFDE Export
It is best to begin your research into LDIFDE with the Export commands. Not only are the export switches easier, but also there is no chance of damaging your Active Directory accounts.

Comments

Popular posts from this blog

Integration with vCloud Director failing after NSXT upgrade to 4.1.2.0 certificate expired

  Issue Clarification: after upgrade from 3.1.3 to 4.1.2.0 observed certificate to be expired related to various internal services.   Issue Verification: after Upgrade from 3.1.3 to 4.1.2.0 observed certificate to be expired related to various internal services.   Root Cause Identification: >>we confirmed the issue to be related to the below KB NSX alarms indicating certificates have expired or are expiring (94898)   Root Cause Justification:   There are two main factors that can contribute to this behaviour: NSX Managers have many certificates for internal services. In version NSX 3.2.1, Cluster Boot Manager (CBM) service certificates were incorrectly given a validity period of 825 days instead of 100 years. This was corrected to 100 years in NSX 3.2.3. However any environment originally installed on NSX 3.2.1 will have the internal CBM Corfu certs expire after 825 regardless of upgrade to the fixed version or not. On NSX-T 3.2.x interna...

Calculate how much data can be transferred in 24 hours based on link speed in data center

  In case you are planning for migration via DIA or IPVPN link and as example you have 200Mb stable speed so you could calculate using the below formula. (( 200Mb /8)x60x60x24) /1024/1024 = 2TB /per day In case you have different speed you could replace the 200Mb by any rate to calculate as example below. (( 5 00Mb /8)x60x60x24) /1024/1024 =  5.15TB  /per day So approximate each 100Mb would allow around 1TB per day.

Device expanded/shrank messages are reported in the VMkernel log for VMFS-5

    Symptoms A VMFS-5 datastore is no longer visible in vSphere 5 datastores view. A VMFS-5 datastore is no longer mounted in the vSphere 5 datastores view. In the  /var/log/vmkernel.log  file, you see an entry similar to: .. cpu1:44722)WARNING: LVM: 2884: [naa.6006048c7bc7febbf4db26ae0c3263cb:1] Device shrank (actual size 18424453 blocks, stored size 18424507 blocks) A VMFS-5 datastore is mounted in the vSphere 5 datastores view, but in the  /var/log/vmkernel.log  file you see an entry similar to: .. cpu0:44828)LVM: 2891: [naa.6006048c7bc7febbf4db26ae0c3263cb:1] Device expanded (actual size 18424506 blocks, stored size 18422953 blocks)   Purpose This article provides steps to correct the VMFS-5 partition table entry using  partedUtil . For more information see  Using the partedUtil command line utility on ESX and ESXi (1036609) .   Cause The device size discrepancy is caused by an incorrect ending sector for the VMFS-5 partition on the ...