In Enterprise Vault 11.0 significant changes have been made to the search application (EVS). Apart from multiple browser support and a new UI there are few other features which are introduced at the server side. In the Vault Admin Console (VAC), a new node “Client Access” has been added to help EV administrators in deploying Enterprise Vault Search (EVS) and Internet Mail Archives. In this article I will explain all that you should know about the server side setting for deploying Enterprise Vault Search. Below mentioned terms have been introduced in EV11.0
Search Provisioning Group:
Under Client Access node you can create and configure a Search Provisioning group. Any provisioning group will always have a search policy assigned to control the availability of features within EVS. There are two types of provisioning groups, Default and Custom. Below is the brief description about the groups.
Default Provisioning Group: This group is created when you perform a fresh install of EV11.0 or if you upgrade from EV10.0.X to EV11.0 and upgrade the Search too*(Read how to upgrade EV search). Default Search Policy is assigned to the Default provisioning group and it contains all the users from the domain. There can be only 1 default provisioning group per site. You can neither edit nor delete the Default Provisioning Group.
Custom Provisioning Group: As the name suggests EV administrator can create a custom provisioning group and add users as per requirement. There are two types of custom groups, Active Directory and Domino Provisioning Group. There is no restriction on the number of custom groups and these groups can be edited & deleted too. In case of multiple custom provisioning groups administrator can also decide on the ranking\order of the provisioning group to be executed.
Active Directory Provisioning Group: In this group you can add one or more Windows User, Windows Group, LDAP Query, Organizational Unit and Distribution Groups.
Domino Provisioning Group: One or more Domino Directory Group, Mailbox, Organizational Unit and Corporate Hierarchy can be added to this Provisioning Group.
Default Search Policy:
Irrespective of an upgrade or fresh install the Default Search Policy will always be available under the Policies node. Through search policy an administrator can decide on the features to be made available within EVS for the end user. Default Search Policy cannot be deleted.
Every search policy has below options.
1) Allow Reading Pane to be shown: With this option enabled user can view HTML preview of items in the reading pane. By default this option is enabled when you create a search policy
2) Export To...
ZIP: Files from the archive can be exported to a ZIP file. By default this is enabled.
PST: User can export any Exchange Item to PST including files (any file type) which are archived in the Exchange mailbox.
NSF: Only Lotus Notes items can be exported to NSF file.
Note: Export to NSF will always create an .nsf file of 25MB. So if you export a 5MB item to NSF the size of the output file will be ~30MB.
Allow Copy Operations: This option allows user to copy item from Archive to the Original location (Content Source). For eg: an item from Exchange archive can be copied to the Exchange mailbox. Similarly an FSA item can be copied to the original File Share. This operation is like copy and paste. By default this option is enabled when you create a search policy.
Allow Move Operations: Move operation allows user to move item from Archive to the Original location (Content Source). This operation deletes the item from the archive and moves it to the source. Move operation is like cut and paste. In the search policy Move option has a dependency on the Delete & Copy operation. So an administrator can enable Move option only if Delete & Copy options are enabled.
4) Delete: Allows end user to delete items from the archive.
Note: An item can be deleted from an archive only if Delete is enabled in the…
Custom Search Policy:
Only difference between Default and Custom search policy is that the custom search policy can be deleted.
Client Access Provisioning Task.
Similar to Exchange Provisioning Task there is a Client Access Provisioning Task (CAPT) for the Search and Internet Mail archives feature. There can be only one CAPT per site. CAPT is automatically created when you create the 1st custom search provisioning group. To manually create a CAPT navigate to any EV server within VAC, right click on Task -> New -> Client Access Provisioning Task and then follow the wizard. Linking of the search policy and search provisioning group is done by the Client Access Provisioning Task. The report related to the CAPT is located in the Reports folder within the EV installation directory.
Scenario#1 You have upgraded from EV10.0.X to EV11.0.0
When you upgrade from EV10.0.X to EV11.0.0 by default the search is NOT upgraded and hence there is no default provisioning group under Search node. Without default provisioning group users will be directed to old search applications (Archive Explorer, Search.asp and Browser Search). There are two ways to make new search application available to the users. Either upgrade the search*(Read how to upgrade EV search) which will create a default provisioning group containing all the user or create a Custom Search Provisioning group and add specific users for whom you want to make the new search application available. Default Search Policy will always be available irrespective of a fresh install or an upgrade scenario. Without upgrading the search when you try to create the 1st Custom Search Provisioning Group* EV will prompt to add a domain for which you want to enable EVS. (Read how to create 1st custom search provisioning group)
Sceanrio#2 You have performed a fresh install of EV11.0.0
When you perform a fresh install EV11.0 all the users from the domain are provisioned for the new search (EVS).There will be a default provisioning group under the Search node and a default policy will be assigned to the group. You can create custom provisioning group and custom search policies as per your requirement.