Installing Meridian Enterprise on a server computer is a complex procedure that involves the installation and configuration of many different components and configuring the security of those components so that they can communicate with one another.
The following table is a checklist for confirming that the critical related tasks of installing a Meridian Enterprise application server have been performed. The table indicates those tasks that should be performed when:
-
Installing a Meridian Enterprise server for the first time
-
Migrating Meridian Enterprise from an existing server to a new server
-
Upgrading Meridian Enterprise on an existing server
The tasks are listed in the order in which they should be performed. Use the hyperlinks in the checklist to find the installation information for each task. Track your installation progress by printing this checklist and placing a checkmark in the box in the applicable column as you finish each task.
| First | Migration | Upgrade | Task | Topic References |
|---|---|---|---|---|
| o | o | o | Confirm all system requirements have been met | |
|
o |
o |
o |
Prepare for installation | Prepare For Installation |
| o | o | o | Create an account with Administrator rights on the server computer to perform the installation (if necessary) | See the Windows product documentation. |
| o | o | If multiple domains or multiple servers will be used, create a domain account to run the Meridian services (EDM Server, Task Server, License Server) | Grant Domain Privileges With a Service Account | |
| o | o | Create an account to use as a rescue account | Create a Rescue Account For Security Administration | |
| o | o | Disable DCOM remote connections to the server to prevent users from opening existing vaults until the installation is complete | Enable DCOM | |
| o | o | If vaults will be stored in Oracle, install the Oracle client software on the Meridian server | See the Oracle product documentation. | |
| o | o | If vaults will be stored in Oracle, create the Meridian service account with the required privileges | ||
| o | o | If vaults will be stored in SQL Server, create the required vault database folders (if absent) | Integrate With a Separate SQL Server Computer | |
| o | o |
If vaults will be stored in SQL Server, create the Meridian service account with the required privileges |
Configure the Windows Account Used By Meridian |
|
| o | o | Confirm that all vault users have adequate privileges on the server | Meridian Server Privileges | |
| o | o | o | Install any other software on the server that is required for content indexing (IFilters), default 64-bit external table support (SQL Server Compact Edition), AutoVue Client/Server viewing, optional Meridian modules, and so on. | See corresponding chapters in this document and appropriate chapters in the module's Administrator's Guide. |
| o | o | o | Install Meridian server components (latest service pack, if applicable) and necessary updates | |
| o | o | If multiple domains or multiple servers will be used, configure the Meridian services (EDM Server, Task Server, License Server) to use the domain account created above | Grant Domain Privileges With a Service Account | |
| o | o | o |
Obtain and register license keys for all products that will be installed |
|
| o | o | Create local Active Directory and/or Meridian Enterprise user groups | Meridian User Administration | |
| o | Restore existing vaults on the new server from backups made on the old server | Restore Backups | ||
| o |
Copy the existing BC-Meridian Extensions share to the new server, if necessary |
Move the BC-Meridian Extensions Folder | ||
| o | Copy any customized registry keys from the old server to the new server | HKEY_LOCAL_MACHINE | ||
| o | If the operating system on the new server is different from the old server, run the icosnlsver.exe vault upgrade tool described in the Meridian Enterprise knowledge base, if required. | Change Operating System Versions | ||
| o | o | Upgrade vaults with Meridian Enterprise Administrator | Upgrade Meridian Vaults | |
| o | Correct the security roles assigned in the vaults to refer to the new server name. This can be done by either deleting all role assignments and recreating them or with the ACL Rename tool described in the Meridian Enterprise knowledge base. | |||
| o | o | o | Configure the server to automatically deploy client upgrades (Optional) | |
| o | o | Configure PowerWeb (Optional) | ||
| o | o | Create scheduled tasks for vault backups and recovery logs | ||
| o | o | Configure content indexing (Optional) | Content Indexing | |
| o | o | Configure reserved licenses (Optional) | ||
| o | o | o | Create the subscriptions and audit log databases (FDA Module only). (Optional) | See corresponding chapters in this document and appropriate chapters in the module's Administrator's Guide. |
| o | o | Remove unused data in vaults (Optional) | ||
| o | o | Run Vault Consistency Toolkit tools | Vault Consistency Toolkit | |
| o | o | Configure any planned vault modifications (Optional) | ||
| o | Create Accruent users and groups and configure vault security. | Meridian User Administration | ||
| o | o | Enable DCOM remote connections to the server to allow users to open the upgraded vaults | Enable DCOM | |
| o | o | o | Perform user acceptance testing |
This checklist is not necessarily complete for every deployment scenario. Additional tasks may be required depending on your requirements and system configuration.
