Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 865
  • Last Modified:

Need help with removing data from an LDIFde export of users

Hi everyone,
Ok so I've exported a group of users from a server to be imported on another new server. When I export the users all their information is exported fine, however at the end of each entry I get a few additional lines of data starting with dsCorePropagationData
example:
dsCorePropagationData:2498416498464

After working on the import of the users that kept failing I realized that it was these lines of data that were causing the import to fail. After removing the lines the user entry would import without a problem.

Here is the command I'm using to export  the users.

Ldifde f dndousers.ldf s nstd-admin d "OU=dndousers, dc=initech,dc=org" -p subtree -r
"(&(objectCategory=person)(objectClass=User)(givenname=*))" -o "badPasswordTime,badPwdCount,lastLogoff,lastLogon,logonCount,
memberOf,objectGUID,objectSid,primaryGroupID,pwdLastSet,sAMAccountType"

How do I get this to export these users without including this dsCorePropagationData?

Let me know if you know or if you have any further questions.
0
nstd-sts
Asked:
nstd-sts
  • 6
  • 3
1 Solution
 
Netman66Commented:
I'm not sure all of those attributes can be migrated in this manner.  That attribute (dsCorePropagationData) seems to be a System flag for data that needs to replicate to a Global Catalog.  I would imagine some of the attributes you are attempting to capture are in that set.  

Have you attempted to move some users with ADMT?  I think this would be a cleaner method.


0
 
nstd-stsAuthor Commented:
ADMT doesn't work for what we are doing, we aren't moving users we are just copying them and to totally different networks that are not connected in anyway.

All the specific attributes in that ldifde command are the ones being ignored and not exported, I've done this same method with new user accounts for testing and that extra information isn't included in the export so I'm guessing it is something thats added due to all the extra information thats attached to these user accounts, I just don't know which one.
0
 
nstd-stsAuthor Commented:
Here is an example of what I'm getting, I understand now that the problem is being caused because I have three entries that are the same, I just need to know how to either stop them from being exported or a good way of removing them from my output. It was fine when I had to move 16 users, now I'm up against copying 250 and I can't manually go through and remove the entries.

> dSCorePropagationData: 20040917192502.0Z
> dSCorePropagationData: 20040917192502.0Z
> dSCorePropagationData: 20040917192502.0Z
> dSCorePropagationData: 16010108151056.0Z
0
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
Netman66Commented:
I would think it's the password information (not the password itself) - like last set, bad password count, etc.

Since those are somewhat urgent replication attributes they would likely cause the dsCorePropogationData to be set.

Try only the user account first to see if that is successful.
0
 
nstd-stsAuthor Commented:
Those attributes are ignored in the command with the -o
0
 
Netman66Commented:
Funny, I looked at that a number of times and only realized after your last post that the command was for Export...  wow...I sure need some glasses.


Try exporting using -l with specific attributes (like "cn,givenName,objectclass,samAccountName") instead of the -o switch to omit.

0
 
nstd-stsAuthor Commented:
Ldifde f dndousers.ldf s bolton01 d "OU=dndousers, dc=initech,dc=org" -p subtree -r
"(&(objectCategory=person)(objectClass=User)(givenname=*))" -o "badPasswordTime,badPwdCount,lastLogoff,lastLogon,logonCount,
memberOf,objectGUID,objectSid,primaryGroupID,pwdLastSet,sAMAccountType"

There is the command I use to export, if you think I can use a -l one better then write me up the correct command and if it works you win! lol

Thanks for you help.
0
 
nstd-stsAuthor Commented:
finished
0
 
nstd-stsAuthor Commented:
Basically I'm just going to use a fine and replace to take out all the data that is causing the problems.
0

Featured Post

[Webinar] Database Backup and Recovery

Does your company store data on premises, off site, in the cloud, or a combination of these? If you answered “yes”, you need a data backup recovery plan that fits each and every platform. Watch now as as Percona teaches us how to build agile data backup recovery plan.

  • 6
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now