If your Meridian server uses the Indexing Service instead of Windows Search, then for the content index update task to succeed, it is critical that the user account used to run AMFTFilter.exe have access to all folders in the vault. If not, documents that reside in folders that AMFTFilter.exe cannot access will not be indexed and users will not be able to search on content in these folders. The user account must also have full access to the file system on the computer where AMFTFilter.exe runs. The program will copy the document content (stream) files to the local disk before it filters the files.
For these reasons, we recommend that you configure the task to run under the local SYSTEM account (no password required), which will filter all documents in the vault regardless of the vault security. If this is not permissible under your organization's security policy, choose an account that:
-
Is a member of the local Administrators group
-
Has read access to the vaults' stream folders located at C:\BC-Meridian Vaults\<VaultName>
-
Full access to the file system on the computer where the AMFTFilter.exe is run.
We recommend that you specify a user account with a password that never expires. If the user account is removed, or the password either expires or is changed, the scheduled content index update task will fail, content index files will begin to age, and text searches will fail unexpectedly.
The AMFTFilter console window that is open when the program is running and that shows the filtering progress will not be visible if you are logged on to the computer with one account but AMFTFilter is running as a different account name. The only way to see that AMFTFilter is running in this situation is to open Task Manager, enable Show processes from all users on the Processes tab, and monitor the AMFTFilter process.
