EVPM [0x8004011D]
- 5 years ago
This is interesting. The SynchInMigration value was already set to "1", but when re-enabling users (on a different server than originally) they were still getting a new blank archive instead of re-connecting them to their original archive.
Going further down the rabbit hole I started comparing the legacyexchangedn value I was zapping to the value in ADSI editor. I found that the values I was pulling from the EV database for the zap were different than the value in ADSI. This article was what I was following to zap, but I was getting the wrong value. https://www.veritas.com/content/support/en_US/article.100016639.html
This article is essentially what I was trying to accomplish: https://www.veritas.com/support/en_US/article.100019496 but was failing because 1. i couldn't get a good "zap" and 2. there were two entries for each user in the EnterpriseVaultDirectory database table. As long as I wasn't removing both database entries reconnecting the user to the archive, or running a next-next-next enable operation wasn't working.
Here's the process I had to take to fix the issue:
1. Identify which archive is blank and delete it
2. Get the correct legacyexchangedn value from ADSI editor and zap it
3. Delete both entries for the user in the EnterpriseVaultDirectory database
4. Run the provisioning task
5. Run the enable user wizard and select the original archive for the user
Now that I have the existing users sorted out, I have to figure out why this is happening so I can prevent it with future re-onboarded employees. Thanks for your help everyone.