From time to time it may be necessary to replace items from a customer staging area through ingestion into Exchange 2007/2010/2013/2016. This article will outline the exact steps needed in order to perform this operation in a lab environment for the purposes of reproducing the error that a customer has encountered.
There are a number of steps which are needed in order to successfully ingest the items from the customers staging area in place of your own items.
1. Create a new user.
2. Provision the user in Enterprise Vault, and enable the user for archiving.
3. Ensure that the mailbox for the user contains the number of items to match the quantity of items obtained from the customer.
4. Ensure the Exchange Import Module is disabled.
5. Archive the items, and verify the archive contains the correct number of items.
6. Create a new container mapping for this user, and proceed into Stage 1.
Data will now be extracted to the staging area on your lab environment.
7. Replace the items on disk with the items from the customer.
For example if you have an item on disk which is called:
And the customer has sent an item which is called:
Have two Windows Explorer windows open side by side.
Highlight the name of your item, and then start the rename operation and copy the filename to the clipboard using Control – C.
Cancel the rename (pressing escape is easiest)
Delete the item from your staging area
Drag and drop the item from the customers environment on to your staging area.
Click on the item, and then start the rename operation, and paste the filename from the clipboard using Control – V.
Repeat the above process for each item.
8. Turn off hash checking in the Archive Shuttle Directory Database.
UPDATE SettingDefinition SET DefaultValueNumeric = 0 WHERE Name = ‘Import Check Item Hash’
9. Ensure TRACE logging is enabled on the Exchange Import module, and it is restarted if necessary.
10. Enable the Exchange Import Module
11. Observe the Exchange Import Module log file over the next few minutes to confirm what is happening and that it is the same errors that the customer is seeing.
The logs, and items can then be used in discussion with development regarding what might be possible to do in order to fix the issue.