No history yet

Enterprise Vault Veritas Technologies LLC Version: 15.1.0.1163 add a exchange 2016 server svr-ex2016-mk created provisioniong tasks make sure emails are archived and indexed

Welcome! I can certainly help you get your Exchange 2016 server, svr-ex2016-mk, fully configured for archiving and indexing in Veritas Enterprise Vault 15.1.

Before we dive into adding the server and creating the provisioning tasks, we need to make sure the underlying credentials and permissions are ready.

To get started, could you confirm if you have already set up the permissions in your Exchange environment, or would you like to start with those preparation steps?

Yes, the Vault Service Account is configured.

Great! With the Vault Service Account ready to roll, we can dive into the actual setup. Since Enterprise Vault organizes its targets hierarchically, we must first tell EV about the domain where your target Exchange server lives.

Step 1: Adding the Exchange Domain

Before we can target your specific Exchange server, svr-ex2016-mk, Enterprise Vault needs to register the entire in which that server resides.
To add the domain, open your Administration Console and perform the following actions:
  1. Locate and expand the Targets node.
  2. Right-click on Exchange and select New, then click Active Directory Domain.
  3. Enter the fully qualified domain name (FQDN) for your environment and click through the wizard to complete the association.
Once the domain is added, we can officially add svr-ex2016-mk as an Exchange Server target underneath it.

How do I add svr-ex2016-mk specifically?

Now that your Active Directory domain is registered, adding your specific Exchange Server, svr-ex2016-mk, is a direct and logical next step.

Step 2: Adding the Exchange Server Target

By targeting the individual server, Enterprise Vault learns exactly where to find the database stores and mailboxes we want to process. We will do this from the same where we added the domain.
To add your Exchange Server target, follow these steps:
  1. In the left-hand pane of the console, expand Targets and then expand Exchange.
  2. Right-click on your newly added Active Directory Domain.
  3. Click New, and then select Exchange Server.
  4. In the wizard, enter the fully qualified domain name (FQDN) or IP address of your server: svr-ex2016-mk.
  5. Select Exchange Mailbox Task to associate with this server, and choose the designated you configured for EV operations.
  6. Finish the wizard to register the server.
Once the server is added as a target, we need to create the Exchange Mailbox Archiving Task specifically for it so EV can actually log in and process the emails.

Continue to creating the Exchange Mailbox Archiving Task

Now that our domain and target server are registered, we need to create the actual engine that will do the heavy lifting: the Exchange Mailbox Archiving Task.

Step 3: Creating the Mailbox Archiving Task

The archiving task is the background service responsible for crawling, processing, and indexing the mailboxes on your target Exchange server. In Enterprise Vault, you typically run one Mailbox Archiving Task per target Exchange server to keep performance snappy and isolated.
To set this up on svr-ex2016-mk, follow these steps in your :
  1. In the left-hand pane, navigate down to System, then expand Tasks.
  2. Right-click Tasks, select New, and then click Exchange Mailbox Task.
  3. The creation wizard will launch. Click Next.
  4. Name the task (e.g., Exchange Mailbox Archiving Task - svr-ex2016-mk).
  5. Select your target Exchange server: svr-ex2016-mk.
  6. Choose the Enterprise Vault server that will run this task (by default, your local EV server).
  7. Click Next to run through the default service configurations and click Finish.
Now, the task is created but is in a stopped state. Before we start it up, we need to establish how EV identifies which mailboxes on that server to archive. We do this by creating a Provisioning Group.

Continue to creating an Exchange Provisioning Group

With the Exchange Mailbox Archiving Task standing by, we are ready to set up the targeting rules. Enterprise Vault uses to define which mailboxes on svr-ex2016-mk get archived and which archiving policies apply to them.

Step 4: Create the Exchange Provisioning Group

To set up the group, head back to your Vault Admin Console and follow these steps:
  1. Expand Targets, right-click Exchange, and select New -> Provisioning Group.
  2. In the wizard, name your group (e.g., Provisioning Group - svr-ex2016-mk).
  3. Choose how you want to target users. You can add them by Active Directory Organizational Unit (OU), Windows Groups, or individual users.
  4. Select your archiving policies: the Mailbox Policy (which controls which items are archived) and the Desktop Policy (which controls what options users see in Outlook).
  5. Pick the Retention Category to apply, which dictates how long archived emails must be kept (such as a 7-year corporate policy).
  6. Choose the Vault Store where the archived physical data will actually be written.
  7. Check the box to Automatically enable mailboxes if you want new mailboxes added to this target scope to be set up automatically.
Once the group is configured, the rules are in place, but Enterprise Vault hasn't actually applied them to the mailboxes yet. To make that happen, we must run the Provisioning Task.

Continue to running the Exchange Provisioning Task

With your Provisioning Group rules written, we are ready to fire up the engine that connects those rules to actual Exchange mailboxes: the Exchange Provisioning Task.

Step 5: Running the Exchange Provisioning Task

In Enterprise Vault, configuring a Provisioning Group is like writing a policy draft; running the is what actually publishes and enforces it. This task queries your Active Directory domain, matches target users based on your group criteria, and creates the corresponding archive entries in Enterprise Vault.
To run this task manually and provision your mailboxes on svr-ex2016-mk, perform these steps in the Vault Admin Console:
  1. In the left-hand pane, navigate down to System -> Tasks.
  2. In the right-hand details pane, locate the Exchange Provisioning Task for your domain (e.g., Exchange Provisioning Task - yourdomain.local).
  3. Right-click the task and select Properties to confirm its schedule or targeting, or simply right-click and choose Run Now.
  4. In the dialog box that appears, select Run provisioning in normal mode to process all targets, and click OK.
You can monitor the progress by looking at the task's status in the console. Once it completes, the mailboxes defined in your Provisioning Group are officially registered and enabled for archiving. Next, we need to verify that your archiving tasks can successfully crawl these mailboxes and that the indexing engine is properly digesting the archived emails so they are searchable.

Continue to verifying indexing status

Now that our mailboxes are provisioned, we must ensure that the emails we archive are being correctly processed and that their search indexes are healthy.

Step 6: Verifying Indexing Status

In Enterprise Vault, archiving and indexing go hand in hand. While the Mailbox Archiving Task handles copying the physical emails into your Vault Stores, the is what parses the metadata and body content, making every single archived email instantly searchable for compliance or end-user discovery.

To verify that your newly archived mailboxes are being indexed correctly, follow these steps:

  1. In the Vault Admin Console, expand your root Enterprise Vault Directory node.
  2. Navigate to Search -> Search Provisioning Groups to confirm your search policies are active, or go directly to the Monitoring tab.
  3. Expand System -> Indexing, and then click on Manage Indexes.
  4. From the Manage Indexes tool, you can check the synchronization status, run reports on index volumes, and verify that your target archives on svr-ex2016-mk are showing a status of Healthy.

If you see any volumes marked as 'Failed' or 'Rebuild Required', you can initiate a repair task right from this console to bring them back in sync.

How do I troubleshoot an index volume that shows as Failed?

When an index volume shows as Failed, it usually means the indexing service lost track of the underlying data files, or the data has corrupted.

Troubleshooting Failed Index Volumes

To bring a failed index volume back online, you can use the built-in to verify, synchronize, or completely rebuild the index from the stored archived data without losing any user emails.

Here is how to run a repair using the built-in wizard:

  1. Right-click the Indexing container under System in the left-hand pane and choose Manage Indexes.
  2. In the wizard, select Rebuild (or Synchronize if you suspect it's just temporarily out of sync).
  3. Search for and select the specific archive or mailbox showing the failure on svr-ex2016-mk.
  4. Monitor the task in the Monitor Tasks node under your EV server to ensure it transitions back to Healthy.

This process reads the raw archived data straight out of your physical vault store and completely regenerates the indexes, restoring full search capabilities to your users.

How do I check EV event logs for indexing errors?

Checking the event logs on your Enterprise Vault server is the fastest way to get to the bottom of indexing failures. Windows Application logs capture every step of the indexing process, but we must filter them to isolate the noise from other services.

Locating Indexing Events in Event Viewer

To pull up the diagnostic logs, log on to your Enterprise Vault server with your admin credentials and open the Windows Event Viewer. Navigate to Applications and Services Logs, and then select the dedicated category.

Look specifically for events generated by the Enterprise Vault Indexing Service source. Common error events include:

  • Event ID 41315: Indicates that an indexing engine search or update request has failed.
  • Event ID 41293: Warns of bad or unparseable attachments within a processed email, which can stall the index pipeline.
  • Event ID 41352: Occurs when an index volume is marked as corrupt or inaccessible due to storage offline conditions.

Once you find the error, the event description usually points to the exact transaction ID or the specific physical storage path where the index file cannot be read.

It is more than 2 days since any archive-enabled mailboxes on Exchange Server 'SVR-EX2016-MK' were scanned for new archive eligible items.

Date of last scan: 17/07/2026 10:22

Mail is not being archived from the mailboxes. There is likely to be a build up of unarchived mail that will increase the mailbox sizes. The unarchived mail is not available to discovery applications.

The problem is most likely to be that Enterprise Vault cannot access Exchange Server.

That event alert is the smoking gun we needed. When you see that it's been more than two days since a scan occurred, Enterprise Vault is warning you that the communication channel between your EV server and svr-ex2016-mk has broken down, halting the processing pipeline completely.

Step 1: Verify Direct Network Connectivity

Since the error explicitly points to a connectivity failure, our first order of business is to make sure the EV server can actually talk to the Exchange Server over the network. We need to verify basic name resolution and port availability.

Log on to your Enterprise Vault server and open a PowerShell window to run a few quick tests against svr-ex2016-mk.

# 1. Test DNS name resolution
ping svr-ex2016-mk

# 2. Test RPC connectivity (Port 135) to the Exchange Server
Test-NetConnection -ComputerName svr-ex2016-mk -Port 135

If the ping fails, we have a DNS resolution issue. If the TCP connection to port 135 fails, a local or network firewall is blocking the traffic that Enterprise Vault relies on to initiate the archiving scan.

Let's run these tests first. What are the results of the connection check?