|
|
|
|
|
BlueCielo TeamWork 2012 Administrator's Guide | BlueCielo ECM Solutions |
Installing TeamWork 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 should serve as a checklist for confirming that the critical related tasks of installing a TeamWork application server have been performed. The table indicates those tasks that should be performed when installing a TeamWork server for the first time, migrating TeamWork from an existing server to a new server, and upgrading TeamWork 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 | Preparing 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 TeamWork services (EDM Server, License Server) | Granting domain privileges with a service account | |
| o | o | Create an account to use as a rescue account | Creating 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 | Enabling DCOM | |
| o | o | Confirm that all vault users have adequate privileges on the server | Understanding the TeamWork server privileges | |
| o | o | o | Install any other software on the server that is required for briefcases (for example, WinZip), content indexing (for example, IFilters), default 64-bit external table support (SQL Server Compact Edition) and so on | See corresponding chapters in this document and appropriate chapters in the module's Administrator's Guide. |
| o | o | o | Install TeamWork server components (latest service pack, if applicable) and necessary hotfixes |
Starting TeamWork installation |
| o | o | If multiple domains or multiple servers will be used, configure the TeamWork services (EDM Server, License Server) to use the domain account created above | Granting domain privileges with a service account | |
| o | o | o |
Register license keys for all products that will be installed Note TeamWork 2010 and earlier licenses must be deleted before later version licenses are added. For more information, see the TeamWork knowledge base. |
|
| o | o | Create local Active Directory and/or TeamWork user groups | About user administration | |
| o | Restore existing vaults on the new server from backups made on the old server | Restoring backups | ||
| o |
Copy the existing BC-TeamWork extensions share to the new server, if necessary |
Moving the BC-TeamWork 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 TeamWork knowledge base, if required. | Changing operating system versions | ||
| o | o | Upgrade vaults with TeamWork Administrator | Upgrading TeamWork 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 TeamWork knowledge base. | Update security settings to point to new server or domain controller | ||
| o | o | o | Configure the server to automatically deploy client upgrades (Optional) | |
| o | o | Configure Web Access (Optional) | ||
| o | o | Create scheduled tasks for vault backups and recovery logs | ||
| o | o | Configure content indexing (Optional) | About content indexing | |
| o | o | Configure reserved licenses (Optional) | ||
| o | o | Remove unused data in vaults (Optional) | ||
| o | o | Run Vault Consistency Toolkit tools | About the Vault Consistency Toolkit | |
| o | o | Configure any planned vault modifications (Optional) | ||
| o | o | Enable DCOM remote connections to the server to allow users to open the upgraded vaults | Enabling DCOM | |
| o | o | o | Perform user acceptance testing |
Note This checklist is not necessarily complete. Additional tasks may be required depending on your system configuration.
|
Copyright © 2000-2012 BlueCielo ECM Solutions |