CSVDE is Your Friend

As I only wanted to update users objects generated by the migration wizard – in this case migrating from GroupWise – I used the following command line to generate the source .CSV: (I have replaced the company specific info with ACME for security reasons.) Lets look at what this command line means:

csvde -f %1.csv -d "ou=budapest,dc=hu,dc=ACME,dc=com" -r "(&(objectCategory=user) (proxyAddresses=gwise:*) )"

“csvde -f %1.csv “

-d "ou=budapest,dc=hu,dc=ACME,dc=com"

The lowest level is the domain, shown as “acme.com” – Our path to this is “dc=ACME,dc=com”. Note how we refer to different objects in the domain as we move along. Domain names will always be referenced using the “DC=” prefix. The problem with this is that our users don’t live in the root of a domain, they need to live in a container, so lets look at the rest of the LDAP path. The users that needed updating were in a child domain, that makes their root address “dc=hu,dc=ACME,dc=com". Now that we have the domain address we need to know one more thing, how do we refer to the container housing our users?

I created an OU called Budapest just off the root of the domain, and choose that as the root OU for the remote office. This means that any users created in this OU or in nested OU’s created within the Budapest OU will be included in the result set created by the csvde.exe utility. Note : If we refer to the users container, then our reference changes from OU=Budapest to CM=users. Note that the “system generated folders” look different from OU’s, which have a distinctive folder icon. For the purpose of simplicity, this is the easiest way of noting the differences in order to construct an LDAP search path.

-r "(&(objectCategory=user) (proxyAddresses=gwise:*) )

-r specified our LDAP search filter and defaults to (objectClass=*). In this case were not interested in extracting anything but users. The thing that made my migration users unique was the fact that they had a groupwise address. This meant that only the users created as a result of being migrated would appear in the search result. This could be further customised based on the groupwise address space or any other attribute that makes your users unique, i.e. (sn=a*) – all surnames starting with an “a”.