Viewpoint Installation#

Introduction#

This document enumerates the steps to install the Viewpoint Application Suite into an environment for the first time. It is assumed that the individuals who will be using this document are familiar with IT terminology, IT best practices, and are comfortable working with Microsoft SQL Server and Active Directory.

To complete the installation process, you will need a copy of the Viewpoint File Store Security Guide, the Viewpoint Database Security Guide and the Viewpoint Config.txt Creation Guide.

Active Directory#

Viewpoint leverages Active Directory. Viewpoint databases and Workers must be deployed in an Active Directory environment.

1. Create two Active Directory groups:
   1. VP_Internal
   2. VP_External
2. Create an Active Directory user named VPWorker. Make this user a member of the VP_Internal Active Directory group.

File Store#

1. Identify your File Store server. The File Store must be accessible by UNC path from all potential machines running a Viewpoint application component (Review, Processing, Worker or QC).
2. If the File Store is running on a Windows server, be sure that Windows Indexing is turned off – it does not benefit Viewpoint and will unnecessarily consume extra space.

Note: If you are using Windows 2012 for your file store, we recommend using NTFS instead of ReFS due to the large block size required be ReFS, which results in a larger expansion rate (you will run out of space sooner).

1. Identify or create a folder on the File Store which will be the root folder for Viewpoint. This is the Viewpoint root folder.
2. Grant the VP_Interal Active Directory group full control over the Viewpoint root folder.
3. Acquire the Viewpoint File Store Security Guide. Follow the steps in the guide to apply the appropriate level of file system security to the File Store.

Database Setup#

Preparation#

1. Identify your Processing SQL Server. It should be a dedicated MSSQL 2008 R2 – 2016 server instance.
2. Identify your Review SQL Server. It should be a dedicated MSSQL 2008 R2 – 2016 server instance. The Review SQL Server must be a different instance than the Processing instance.
3. Identify the MSSQL Groups / Logins which you will be granting access to the databases. The Viewpoint Database Security Guide contains a listing of the types of Logins which will be required.
4. Make a backup of the model database on the Processing and Review MSSQL servers, as this database is going to be overwritten during this installation.
5. Each database server will need to have the Admin$ share enabled during the installation process – it can be turned off once the installation is complete.

Installing the Viewpoint Databases#

1. Launch the Viewpoint Installation program (LateralData.Tools.Installer.exe).
2. Click the “Install” button.
3. Follow the prompts of the Installation wizard. Use the default options whenever possible. You will be prompted for the names of the Processing and Review server and the root folder of the File Store. You will also be prompted for passwords for the Workflow Login and the Server Link Login – for more details on these logins (dedicated Viewpoint logins created during the installation process) see the Viewpoint Database Security Guide.
4. When the wizard completes your initial database setup will be complete. Your logins will have been associated with the Viewpoint database role (VP_USER), your server links have been created and some configuration values will have been populated in the Processing and Review configuration tables.

NSRL#

Viewpoint can utilize the NSRL’s (National Software Reference Library) Reference Data Set (RDS) to assist in filtering out files known to be safely excludable (for example, Operating System files). The installation process involves the acquisition of the NSRL RDS, loading it into a database and configuring Viewpoint to use the NSRL RDS database.

1. Locate the Viewpoint NSRL Loader application (“LateralData.Tools.NSRLLoader.exe”).
2. Locate the NSRL database (by default it will be located on the Processing MSSQL instance).
3. Locate and download the latest NSRL RDS files:
   1. Determine which PC you will be using to perform the download, extraction and assemblage of the database. This PC must have at least 20 gigabytes of free space available – this process is space intensive.
   2. Open a web browser and navigate to the NSRL DRS download site. (https://www.nist.gov/itl/ssd/software-quality-group/nsrl-download/current-rds-hash-sets at the time of this document’s publication).
   3. Locate the minimal hash set (as opposed to the unique hash set). As of October 2019, the latest version is RDS 2.66, the minimal hash set contains 56,058,194 file hashes. Download the file – do not unzip the file.
4. Launch the NSRL Installation Tool.
5. Click Next. Fill in the database credentials. Use the “Test Connection” button to verify your credentials.
6. Click “Add Files…” and select the ZIP file that you downloaded.
7. In the NSRL File Version box enter the version number of your NSRL files.
8. Click Next. The data will be extracted from the NSRL file and loaded into the NSRL database. The entire process will take several minutes.

Database Maintenance Plans – Index Maintenance#

Viewpoint is a database intensive application and as such requires regular index maintenance. Lateral Data best practice is to perform index rebuilds three times a week and index reorganizations on the other days of the week. Failure to execute index maintenance on a regular schedule will result in degraded performance, ultimately leading to timeouts. The following steps outline the creation of two maintenance plans – one for rebuilding indexes (to be run weekly) and one to reorganize indexes (to be run nightly). Perform these steps on both the Processing and Review MSSQL Server instances.

1. Connect to an MSSQL instance using Microsoft SQL Server Management Studio.
2. In the main tree, locate “Management”. Under this folder locate “Maintenance Plans”. Right-click “Maintenance Plans” and select “New Maintenance Plan…” You will be prompted for a name – enter “Rebuild Indexes” and click OK.
3. A new window opens for the new plan and the Toolbox appears with Maintenance Plan Tasks.

1. Locate the “Schedule” column. The first row will contain text indicating that no schedule has been defined. Locate the calendar icon at the far right of this column.

1. Click the calendar icon. The Job Schedule Properties dialog will appear.

1. Configure a schedule that runs three times a week during off-hours; for example, Monday, Wednesday, and Friday. Click OK to commit the schedule.
2. In the Toolbox, which contains Maintenance Plan Tasks, locate “Rebuild Index Task”. Click and drag this Task into the large yellow area. A “Rebuild Index Task” box will appear in with an arrow pointing downward on its bottom edge.

1. Right-click the Rebuild Index Task and select “Edit”. A dialog will appear with the properties of this task.
2. Open the “Databases” drop down and select the “All user databases” radio button. Click OK.
3. From the Main Menu select File | Save Selected Items.
4. From the Main Menu select File | Close.
5. Right click the “Rebuild Indexes” Maintenance Plan and select “Execute”. This will execute the plan. Verify that it runs to completion without error.
6. Right click “Maintenance Plans” and select “New Maintenance Plan…” You will be prompted for a name – enter “Reorganize Indexes” and click OK.
7. Locate the “Schedule” column. The first row will contain text indicating that no schedule has been defined. Locate and click the calendar icon at the far right of this column – the Job Schedule Properties dialog will appear.
8. Configure a schedule which runs for the days of the week that the Rebuild Indexes job does not run. The job should run during off-hours. Click OK to commit the schedule.
9. In the Toolbox, locate the Maintenance Plan Task named “Reorganize Index Task”. Click and drag the task into the yellow area.
10. In the Toolbox, locate “Update Statistics Task”. Click and drag the task into the yellow area, below the “Reorganize Index” task.
11. Click on the “Reorganize Index” task. Note the arrow pointing downward on the bottom edge. Click and drag the arrowhead so that it points into the body of the “Update Statistics” task. Release the mouse and the arrow from the top task will “stick” to the bottom task.

1. Right-click the “Reorganize Index” task and select “Edit”. In the “Databases” drop-down select “All user database”. Click OK. Click OK on the dialog to save the changes to the Task.
2. Right-click the “Update Statistics” task and select “Edit”. In the “Databases” drop-down select “All user database”. Click OK. Click OK on the dialog to save the changes to the Task.
3. From the Main Menu select File | Save Selected Items.
4. From the Main Menu select File | Close
5. Right click the “Reorganize Indexes” Maintenance Plan and select “Execute”. This will execute the plan. Verify that it runs to completion without error.
6. In the main tree locate “SQL Server Agent”. Open this item and locate “Jobs”. Locate the two new jobs (“Rebuild Indexes” and “Reorganize Indexes”).
7. Right-click each job and confirm that “Enable” is grayed-out and “Disable” not. This indicates that the Job is awaiting its next scheduled run. If this is not the case, click “Enable”.

Database Maintenance Plans – Backups#

At this point in the installation process it is prudent to set up your backup plans according to your enterprise standards and execute a test restoration. Viewpoint does not impose any particular requirements upon this, nor does Viewpoint come with its own database backup plans. Any reasonable backup scheme would consist of at least a daily full backup and more frequent transaction log backups. Database files grow as they are used – a maintenance plan for reclaiming unused space (“Shrink”) is also prudent.

Note that more databases will be added in the normal course of Viewpoint usage (each new project creates a new database) so be sure to create maintenance plans which anticipate the regular addition of new databases.

Consider your enterprise’s best practices regarding the monitoring of maintenance plan errors. A production Viewpoint environment should never be run without regular, known-recoverable backups.

Click-Once Deployment Server (IIS) Setup#

1. Identify a server which will act as your Click-Once Deployment Server. This server’s job is to hold the deployment packages for the various Viewpoint applications and to serve them to users (via IIS). Often customers use their File Store for this duty. Be sure that whatever server you select it is a server that it is highly reliable and backed up as an outage of this server will prevent users from being able to launch Viewpoint. It must be accessible by HTTP (or HTTPS) from all of the machines which will be running Viewpoint directly.
2. You may wish to disable User Account Control (UAC) temporarily during the setup of IIS. This is not a required step.
   1. Type “UAC” into the Start Menu.
   2. Move the slider all the way to the “Never notify” setting.
   3. Click “OK”.
3. Install IIS on this server if it is not already installed. Use default installation parameters.
4. Locate the Viewpoint ‘Click Once’ Deployment Packages. They are:
   1. PMC
   2. Review
   3. Worker
   4. QC
5. The Processing and Review Deployment Packages, received from Lateral Data, will come pre-packaged with your company’s license files.
6. Log into the server.
7. Create folder C:\Inetpub\wwwroot\Viewpoint\
8. Under this folder create four other folders:
   PMC
   Worker
   Review
   QC
9. Open the IIS Management Console. To do this, open the Start Menu and execute inetmgr.
10. Navigate to the Default Web Site node.
11. On Windows 2008 R2 or newer, perform the following steps:
    1. Right-click the Default Web Site node and select “Add Virtual Directory…” The Add Virtual Directory dialog appears.
    2. In the Alias box enter “PMC”. In the Physical path enter the path C:\inetpub\wwwroot\Viewpoint\PMC
    3. Click OK.
    4. Select the Virtual Folder. In the center pane, under the IIS group, locate and double-click “Request Filtering”.

• 1. Select tab “Hidden Segments”. If “bin” appears in this list, right-click “bin”, select “Remove” and confirm removal.
  2. Repeat these steps for the other three folders – Worker, Review and QC.

1. Copy the contents of the Processing Deployment Package to the PMC folder on your server. Locate file “LateralData.Applications.PMCEx.application”. Open this file with a text editor. Locate element “deploymentProvider”. Change the value of this element to be the fully qualified URL of this self-same file. For example “http://myCompany.com/Viewpoint/PMC/ LateralData.Applications.PMCEx.application”.
2. To test this install, bring up Internet Explorer and browse to the URL of the publish.htm file. You should be shown an installation page:

1. Repeat the same procedure for the Worker, QC and Review Deployment Packages. The name of the “application” file will be different for each of these applications. The Terminal Server setup follows a different procedure, outlined elsewhere in this installation guide
2. ‘Smoke Test’ the installations. Open Internet Explorer and navigate to the publish.htm page for each application – for example the deployment page for Viewpoint Processing will have a URL like “http://<server name>/PMC/publish.htm”.
3. Click the “Launch” button – this will initiate the deployment process. Once the application login box appears you may close the application. Repeat this process for all applications (Processing, Worker, Review and QC).
4. If you disabled User Account Control (UAC) previously you should turn it back on:
   1. Type “UAC” into the Start Menu.
   2. Move the slider to a setting appropriate for your enterprise policy.
   3. Click OK.

Worker Installation#

1. Identify your Worker PCs. These PCs should conform to the requirements of Worker PCs.
2. Identify the user account that the Workers will run as – this user must be an Active Directory user, and a member of the Active Directory Group which has been granted the VP_USER role on the Processing MSSQL Instance. This user will need Full Control access to the File Store(s) and be a local administrator. It is not necessary (nor recommended, for security reasons) to use Domain Administrators as your Worker users.
3. Ensure that Microsoft .NET Framework 3.5 SP1 and 4.0 (Full Extended) are installed.
4. Download and install Microsoft .NET Framework 4 Reliability Update 2. For more information on this topic see Microsoft Knowledge Base article KB 2600217.
5. Download and install the following Microsoft Visual C++ Runtimes versions:
   1. C++ 2012 (x86) - https://www.microsoft.com/en-us/download/confirmation.aspx?id=30679
   2. C++ 2017 (x86) - https://aka.ms/vs/16/release/vc_redist.x86.exe
   3. C++ 2012 (64 bit) - https://www.microsoft.com/en-us/download/details.aspx?id=30679
   4. C++ 2013 (64-bit) - https://learn.microsoft.com/en-us/cpp/windows/latest-supported-vc-redist?view=msvc-170
   5. C++ 2015-2022 (64-bit) - https://learn.microsoft.com/en-us/cpp/windows/latest-supported-vc-redist?view=msvc-170#visual-studio-2015-2017-2019-and-2022
6. Ensure that the Worker PCs are up to date with the latest Windows Updates. Reboot the Worker after installing all updates.
7. Install anti-virus software if desired. Typically, real-time scanning is sufficient (as opposed to a scheduled scan).
8. Log in to the Worker PC as the user which you have identified as the Worker user. This is the user that you must use to install software as some third-party components require single-user installations. This user must be a domain account and a local (box) administrator. All software installations will be under the C:\Program Files folder, as opposed to the C:\Program Files(x86) folder unless specifically noted otherwise in this installation guide.

Install Microsoft Office. The following versions are supported:
2016, 2019, 2021 (64-bit)

• 1. Open Excel.
  2. Click the button at top left to open the main menu. From the main menu click the “Excel Options” button at bottom right. This opens the Excel Options Dialog.
  3. On the left bar click “Trust Center”. Click the “Trust Center Settings” button. The Trust Center Dialog appears.
  4. On the left sidebar click “Macro Settings”. Checkmark “Enable all Macros”. Checkmark “Trust access to the VBA project object model”. Click OK on this dialog. Click OK on the Excel Options dialog.

1. Install Microsoft Outlook. Start Microsoft Outlook to create a profile (no email account)
2. Acquire the installation package for Lotus Notes 8.5.1.

Note: If you do not anticipate the need to process Lotus Notes files this entire step may be skipped. It can be performed later in the future if a need emerges.

1. Lotus Notes 8.5.1 Installation:
   1. Start the installation program.

• 1. Enter user and organization name. Select “Only for me” and click Next.

• 1. There are no points which need to be configured on this page – click Next.

• 1. There are no points which need to be configured on this page – click Next.

• 1. Uncheck all three of the checkboxes. Click Install. Wait for the installation to complete.
  2. Once the installation has completed launch Lotus Notes from the shortcut that was added to your desktop.

• 1. Click Next.

• 1. Enter a name if you’d like, however it is not required. You must uncheck “I want to connect to a Domino server”. Click Next.

• 1. Uncheck “setup instant messaging”. Click Next.

• 1. At this screen click Finish. You will be prompted to make Lotus Notes your default email program. Click No. Close Lotus Notes.
  2. Open the Windows Registry Editor and navigate to key HKEY_LOCAL_MACHINE\SOFTWARE\Lotus\Notes. If is does not exist, look for the key in HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Lotus\Notes. If neither exists, created a Registry Key with the path HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Lotus\Notes
  3. Locate Value ‘Path’. If it does not exist create it – it is of type string.
  4. Set the value for ‘Path’ to hold the executable path to Lotus Notes.
     Note: the typical installation path for Lotus Notes is:
     C:\Program Files (x86)\IBM\Lotus\Notes\

1. Install Informatik Image Driver version 6.21 (64-bit). This is a Virtual Printer. Install the Virtual Printer. Once installed locate the Printer icon, right-click and select “Properties”. Perform the following actions:
   1. Make this printer the default printer
   2. Change the name to Informatik Image Driver 3.00 (UM)
   3. Printing Preferences: Advanced Options
      • Scaling 95%, Format B/W Group4.
   4. Paper Quality
      • Color: Gray scale.
   5. Print Output Settings
      • Check on box #3 Serialization (each page in the document get written to an individual tiff)
      • Serial Prefix “ld_” or the initial letter of the company name
      • Check on the box “hide this dialog”
2. Install a printer with HP Drivers (4 PCL or 6). You do not need the actual printer, just the drivers. This printer should not be the default printer.
3. Acquire Adobe Reader DC (PDF Reader). Install with default settings.
4. Install Irfanview (iview427_setup.exe):
   1. Install for all users
   2. Select all image file types
   3. Do not install Google tool bar
5. Install Tesseract OCR support files using the following process:
   1. Locate the folder “TessData” among the installation assets provided to you.
   2. Select a location to copy this folder to. You have two options:
      • On a network drive which all Workers and PMC instances can access. This is the preferred method as it allows for easier maintenance.
      • In the root folder of every Worker / PMC instance. If this is done every Worker / PMC instance must use the exact same path (for example, C:\TessData).
   3. Copy the entire TessData folder to the target location. Note the path, you will be using it later in this process. The path must be a UNC path.
   4. Using MS SQL Management Studio log on to the Viewpoint Processing MS SQL Server Instance
   5. Locate the database LDControl.
   6. Under the LDControl folder locate Tables | Configuration. Right-click the “Configuration” table and select “Edit Top 200 Rows”.
   7. Create a new record with the following values:
      • ConfigName : Tesseract3Data
      • ConfigValue : <the fully-qualified UNC path to the TessData folder, such as \\myserver\viewpoint\TessData>
      • SortOrder : 1
   8. Move to a new row in the table to commit the change.
6. Install the Viewpoint Worker application on each worker PC. To this end, open Internet Explorer. Navigate to the Worker installation page (publish.htm). Once on the installation page click the “Launch” button – this will install the Worker and create a desktop shortcut.
7. Register the new worker machine to the processing SQL by following the steps. This step must be performed for each worker individually. Simply restoring a virtual image of a worker is not enough – every worker that will participate in the same environment must register itself with the environment.
   1. Run the Worker application. A console will appear. After a few moments you will be prompted to enter the name of the Processing MS SQL instance.
   2. Type in the name of the Processing SQL Server instance. Press Enter. The Worker is now registered with the Processing MS SQL Server.
   3. Stop the Worker by typing Ctrl-C.
8. Open a command prompt and enter the following: (replace VPWorker with the name of the worker Active Directory user account username if it is different than VPWorker).

netsh http add urlacl url=http://+:8731/LateralData.Workflows.Services.WorkflowService.svc/ user=VPWorker

In addition, execute the following if you plan on using Lotus Notes: (replace “viewpoint\vpworker” with the domain and name of the worker Active Directory user account username if it is different than VPWorker).

netsh http add urlacl url=http://+:8731/Extractors/LotusNotes/Extractor.svc/ user=viewpoint\vpworker

1. Disable User Account Control (UAC):
   1. Type “UAC” into the Start Menu.
   2. Move the slider all the way to the “Never notify” setting.
   3. Click OK.
2. If the Worker will not have outbound Internet access, the following steps need to be performed to prevent Office 2013 (or newer) from performing poorly during TIFFing:
   1. On the Worker, open Windows Firewall if it is running. This can be done by launching “Windows Firewall with Advanced Security” from the Start Menu
   2. Select “Outbound Rules” in the panel on the left and click “New Rule…” in the panel on the right.

• 1. The New Outbound Rule Wizard appears. Select “Program” and click Next.
  2. Select “This program path”. Enter the path to WINWORD.EXE into the edit box (this is typically something like: %ProgramFiles% (x86)\Microsoft Office\Office14\WINWORD.EXE). Click Next.
  3. Select “Block the connection” and click Next.
  4. Domain, Private and Public will all be checked. Click Next.
  5. Enter a name for the rule – any name will do, it is recommended that you use “Viewpoint Worker Rule - MS Word”.
  6. Click Finish. The outbound firewall rule has been created. You will now be able to TIFF MS Word files with external links without suffering a performance penalty.

1. The Workers can be remotely restarted through the PMC application using psexec. Typically, customers wish to use this feature. To make use of this feature the Worker, and any machine running the PMC, will need to have ports 135 and 445 (TCP) open. Additionally, the Worker will need to have its Admin$ and IPC$ shares on (they are on by default). If these steps are not taken, then Workers will need to be restarted manually.
2. Reboot the Worker.
3. Optional Worker packages (OCR, etc.) are installed later in this process.

First Run#

Some aspects of configuration cannot be completed until you have started some of the Viewpoint applications. To perform this step, you will need to work with someone who has been trained in the operation of the Viewpoint Processing and Review components.

Viewpoint Processing#

1. Install Viewpoint Processing. To do so, open Internet Explorer. Navigate to the Viewpoint Processing installation page (publish.htm). Once on the installation page click the “Launch” button – this will install Viewpoint Processing and create a desktop shortcut. If instead of “Launch” you are presented with a screen stating that you lack prerequisites, then follow the steps indicated to acquire the pre-requisites.
2. Install the Informatik Image Driver on this PC using the same options that were used when installing on to the Worker. Unlike the Worker installation, this printer does not need to be the default printer.
3. Install anti-virus software if desired. Typically, real-time scanning is sufficient (as opposed to a scheduled scan).
4. Launch Viewpoint Processing. You will be shown the Login Dialog.
5. Type the name of the Processing SQL Server instance into the Server box. If Windows Authentication is turned on your user credentials will auto-populate. If this occurs, uncheck “Use Windows Account” as your user does not yet have a Viewpoint Processing login.
6. Enter the bootstrap user name and password and click OK. Username: Administrator Password: ld
7. Locate and click on the Security Management button in the toolbar. The Security Management Dialog appears.
8. Click the Companies toolbar item. Select the Company “Lateral Data”. In the grid on the right side of the application locate the “Name” row. Change this name to the name of your Company.
9. Create a Viewpoint User for the Worker to use. This user will be an Active Directory user – this is the same user that the Workers will run as, set up earlier in this process. Follow these steps to create the Viewpoint User:
   1. Click the Users tab.
   2. In the Users grid, right-click and select “New”. The New User Wizard appears.
   3. Select your Company. Click Next.
   4. Enter the Worker Active Directory User account name into "User Name" box and click “Look up in Active Directory”. The User’s credentials will populate the form. Click Next.
   5. Click Finish to create the Viewpoint User.
   6. Select the “Roles” tab.
   7. Locate and select the Administrator Role.
   8. In the Users grid right-click and select “New”. Select the newly created Viewpoint User and select Finish.
10. Change the password for the built-in administrator account. This step is extremely important – it is critical that the bootstrap user have its password changed as soon as possible. To do this perform the following steps:
    1. Click the Users tab
    2. Locate the User “Administrator”. Right-click and select Update. The Create or Modify User Dialog appears.
    3. Click Next at the first page.
    4. On the second page change the password. Change the First Name, Last Name and Email if the default values are not appropriate to your use. Click Next.
    5. Click Finish to save your changes.
11. Close Viewpoint Processing.
12. Log in (to the Processing SQL Server) as the user “Administrator” and the new password.
13. Create a new (Processing) Project. The details of the project are not important – the purpose of this project is to facilitate the configuration and smoke test of Viewpoint. This project should not be used for live data. You may choose to remove this project once your installation is known to be complete and fully smoke tested however there is no requirement to do so.
14. Create a corresponding Review Project for this Processing Project.

Workers#

1. While still in Viewpoint Processing click on the Workers tab.
2. Click the “Worker Selector” toolbar button. Verify that the number of Workers in the grid is the same as the number of Workers you have set up.
3. Locate the column “Max. Simulations Workflows”. Set this value to 50 for each worker.
4. Select a single Worker. Right-click and select “Start Workflow Host”.
5. Populate the User Name and Password boxes with the username/password of the Windows User which will run the Worker. The Worker runs under the context of this user. This user must have local administrator rights and be able to read/write/delete files on the File Store.
6. The Executable box will automatically populate to contain the path of psexec.exe (on the PC running Viewpoint Processing, not the worker PC). Generally, you will not have a need to change this.
7. Populate the Remote Internet Explorer box. This is usually C:\Program Files\Internet Explorer\iexplore.exe
8. Populate the Install URL box. This is the full URL to the LateralData.Consoles.WorkflowRuntimeHost.application file for the Worker installation package.
9. Click OK to start the worker. After a few moments right-click the Worker grid and select “Refresh”. The Worker’s row should now appear in light green.
10. Select all the other workers, right-click and select “Start Workflow Host”. The settings from your previous session will be retained – just click OK and the other Workers will start. After a few moments refresh the Worker grid and verify that all Worker rows are displaying in light green.
11. Working with a user which has been training in how to process data in Viewpoint, process a small amount of data – a few files. As part of this process select options to generate TIFFs, HTML, text, metadata, and to set the File Identity. Ensure that the job completes without error.

Viewpoint Review#

1. Install the Review application. To do so, open Internet Explorer. Navigate to the Review installation page (publish.htm). Once on the installation page click the “Launch” button – this will install the Review application and create a desktop shortcut. If instead of “Launch” you are presented with a screen stating that you lack prerequisites, then follow the steps indicated to acquire the pre-requisites.
2. Launch the Review application. You will be presented with the Login Dialog.
3. Type the name of the Review SQL Server instance into the Server box. If Windows Authentication is turned on your user credentials will auto-populate. If this occurs, uncheck “Use Windows Account” as your user does not yet have a Viewpoint Review login.
4. Enter the bootstrap user name and password and click OK. Username: Administrator Password: ld
5. Locate and click on the Security Management button in the toolbar. The Security Management Dialog appears.
6. Click the Companies toolbar item. Select the Company “Lateral Data”. In the grid on the right side of the application locate the “Name” row. Change this name to the name of your Company.
7. Click the Users tab. Locate the User “Administrator”. Right-click and select Update. The Create or Modify User Dialog appears.
8. Click Next at the first page. On the second page change the password. Change the First Name, Last Name and Email if the default values are not appropriate to your use. Click Next. Click Finish to save your changes.
9. Close Review.
10. Log in (to the Review SQL Server) as the user “Administrator” and the new password.
11. Click the “Review” button. The installation of two OCX components will occur.

Processing and Review Interaction#

1. Launch Viewpoint Processing. On the Index tab, locate the data you have processed and Index the data. Once complete right-click the Scope and select “Post”.
2. Open the Review application. Select the project and click the “View Manager” button. The View Manager screen will appear. Click the “Scopes” tab. The Scope(s) you posted will appear.
3. Create a View containing the documents from the Scope(s).
4. Close the View Manager.
5. Click the “Review” button. Review appears. Select the View you just created. Browse through a few of the documents. Right-click on some documents and select “View Native”. A copy of the Native File for the selected Document will appear.

QC#

1. Install the Viewpoint QC Application. To do so, open Internet Explorer. Navigate to the Viewpoint QC installation page (publish.htm). Once on the installation page click the “Launch” button – this will install the Viewpoint QC application and create a desktop shortcut. If instead of “Launch” you are presented with a screen stating that you lack prerequisites, then follow the steps indicated to acquire the pre-requisites.
2. Log in (to the Processing SQL Server).
3. View a few documents.

Sample Repository#

Viewpoint ships with a sample project. The purpose of this project is to allow customers to quickly assess the readiness of the installation. It is not required that this process be performed – Viewpoint will function without the sample repository – however it is recommended.

1. Acquire the Viewpoint Sample Repository package. The package contains the following items:
   1. Folder ‘Databases’. This folder contains two database backup (.bak) files
   2. Folder ‘Repository Files’. This folder contains the 7-Zip archive “Processed Files.7z”
   3. Folder ‘SQL Scripts’ – This folder contains four SQL scripts
2. If you have not already performed the steps in the “First Run” section of this Install Guide, do it now – you will need to already have at least one Project database in the Review and the Processing servers.
3. Unzip the 7-Zip archive “Processed Files.7z” to your Viewpoint File Store’s root folder. When the process is complete you should have a new folder “T00001” in your Viewpoint File Repository. Note the file path of this folder – it will look like “\\ServerName\ViewpointRootFolder\T00001” … you will be using this value later in this process.
4. Open MS SQL Management Studio. Log in to the Processing Server Instance. Locate the LDControl database. Locate query “Add Processing Project.sql” from Sample Repository folder “SQL Scripts”. Execute this script on the LDControl database.
5. Locate the Processing Database backup file in the Sample Repository “Databases” folder and restore the database, naming it “T00001_Processing”.
6. Once the restoration is complete, browse to Security | Logins and locate the MSSQL Logins which you wish to give access to the sample repository database. Grant connect rights to each of these Logins and assign them the VP_USER role. To do this right-click a Login and select Properties. Select User Mapping from the panel at top-left. Locate the database in the grid on the right and checkmark the “Map” column. Then locate and checkmark the role “VP_USER” in the grid at bottom right. Click OK. Perform this step for each Login you wish to have permission to connect to the Sample Repository Database.
7. Right-click the database and select “New Query”. Locate the SQL script “Update Processing Paths.sql” in the Sample Repository “SQL Scripts” folder and copy its contents to the new query panel.
8. Locate the line:

set @NewPath = '\\NewServer\NewShare\T00001'

…and replace this value with the path to the T00001 folder on the Viewpoint File Store. Execute the query.

1. Log in to the Review Server Instance. Locate the LDControl database. Locate query “Add Review Project.sql” from Sample Repository folder “SQL Scripts”. Execute this script on the LDControl database.
2. Locate the Review Database backup file in the Sample Repository “Databases” folder and restore the database, naming it “T00001_Review”.
3. Once the restoration is complete, browse to Security | Logins and locate the MSSQL Logins which you wish to give access to the sample repository database. Grant connect rights to each of these Logins and assign them the VP_USER role. To do this right-click a Login and select Properties. Select User Mapping from the panel at top-left. Locate the database in the grid on the right and checkmark the “Map” column. Then locate and checkmark the role “VP_USER” in the grid at bottom right. Click OK. Perform this step for each Login you wish to have permission to connect to the Sample Repository Database.
4. Right-click the database and select “New Query”. Locate the SQL script “Update Review Paths.sql” in the Sample Repository “SQL Scripts” folder and copy its contents to the new query panel.
5. Locate the line:

set @NewPath = '\\NewServer\NewShare\T00001'

…and replace this value with the path to the T00001 folder on the Viewpoint File Store. Execute the query.

Close MS SQL Management Studio.

1. Open Viewpoint Review and select the Sample Repository project. Click ‘Review’ and select any document to verify that the database and file system have been properly configured. Close Viewpoint Review.
2. Open Viewpoint Processing and select the Sample Repository project. Click the Process tab. Select any group of documents and use the “Browse To…” menu to browse to the Native file. Close Viewpoint Processing.

Optional Worker Installations#

Viewpoint Workers can be augmented with additional capabilities by installing additional packages. Some packages require additional 3^rd party licenses – be sure to stay in compliance with all 3^rd party licenses.

When installing components on the Workers please be certain that you are performing the installation as the Worker user. Some 3^rd party components are single-user installations.

ExperVision (OCR)#

Viewpoint facilitates OCR capabilities through ExperVision. Each Worker will need to be installed and configured individually due to licensing requirements.

1. Locate the Viewpoint ExperVision Registration Package. Place a copy of this package on all Workers which will have ExperVision installed on them. Create a folder for the package (example: C:\ExperVision Registration Package).
2. Log into the Worker as an administrator.
3. Each worker will need to have its own key information – this is part of licensing ExperVision. The following steps outline this process:
   1. Open the folder containing the ExperVision Registration Package.
   2. Locate and run LateralData.Tools.ExperVisionInit.exe. Click the “Call Init ExperVision” button. The Registration Dialog will appear.

• 1. Copy the contents of the Site Code and MID boxes from the dialog. Click Cancel.
  2. Send the Site Code and MID information to viewpointsupport@lateraldata.com for the key specific to this Worker. Each Worker will have its own key. The process of key generation can take time – you may choose to continue with other facets of the Viewpoint installation process while waiting for the key.

1. Once the key has arrived, open the Viewpoint ExperVision Registration Package.
2. Locate and run LateralData.Tools.ExperVisionInit.exe
3. Click the “Call Init ExperVision” button. The Registration Dialog appears.
4. Type the license activation code into the box.
5. Click Continue and the dialog box will disappear.
6. Do not remove the copy of the Viewpoint ExperVision Registration Package from the Worker – you may need it in the future if your ExperVision key expires or is transferred to another Worker.
7. Open the Viewpoint Processing application. Select the Workflow tab. Locate the Worker. Enter WebserviceOCR into the column “Supported Features”.
8. Using MS SQL Management Studio log on to the Viewpoint Processing MS SQL Server Instance
9. Locate the database LDControl.
10. Under the LDControl folder locate Tables | Configuration. Right-click the “Configuration” table and select “Edit Top 200 Rows”.
11. Locate or create a new record with the following values:
    1. ConfigName : WebServiceOCRType
    2. ConfigValue : ExperVision
    3. SortOrder : 1
12. Move to a new row in the table to commit the change.

Mount Image Pro#

This package allows for the extraction of EnCase images. Generally this is only installed on a few workers.

1. Acquire a copy of Mount Image Pro and any secure any required licensing.
2. Must be installed into Program Files\GetData\Mount Image Pro v3\MIP3.exe - if your install does not place the executable here, or the executable has a different name, your executable will need to be moved / renamed.
3. Open Viewpoint Processing. Select the Workflow tab. Locate the Worker(s). Enter MountImagePro into the column “Supported Features”.
4. Once installed verify the File Identify for E01 points to this extractor.

StuffIt#

This package allows for the extraction of StuffIt archives (Mac OS). Generally, this is only installed on a few workers.

1. Acquire and install a licensed version of StuffIt 2010 v14.0.0.18.
2. Once installed verify the file identities for SIT point to this extractor.

DWGSee#

This package facilitates the TIFFing of AutoCad drawings.

1. Acquire and install a licensed version of DWGSee Pro v4.01.
2. Install the program under Program Files, not Program Files (x86).

Microsoft Project#

This package facilitates the TIFFing of Microsoft Project files.

1. Acquire and install a licensed version of Microsoft Project.

Microsoft Publisher#

This package facilitates the TIFFing of Microsoft Publisher files.

1. Acquire and install a licensed version of Microsoft Publisher.

Microsoft Access Snapshot Viewer#

This package facilitates the TIFFing of Microsoft Access Snapshot files.

1. Acquire and install a licensed version of Microsoft Access Snapshot Viewer.

Terminal Server Setup#

Often it is advantageous to make use of Terminal Server or similar product to serve the Viewpoint Review application to external users. Do not install Viewpoint Processing or Viewpoint QC on Terminal Server.

It is beyond the scope of this Installation Guide to outline the set of compatible products and the details of how to install these products. What follows is best-practice guidance on what to configure and what to be aware of when deploying in this scenario.

1. Identify the servers which will host your terminal server environment. Install the Terminal Server (or other) products. Ensure that the servers can:
   1. Access the File Store
   2. Access the Review and Processing SQL Server instances
2. Install the Adobe PDF Reader plug-in for Internet Explorer if it is not already installed. The free version is sufficient.
3. Install Microsoft Office 2016 or newer. Microsoft licensing requirements apply.
4. Download and install the following Microsoft Visual C++ Runtimes versions:
   1. C++ 2012 (64 bit) - https://www.microsoft.com/en-us/download/details.aspx?id=30679
   2. C++ 2013 (64-bit) - https://learn.microsoft.com/en-us/cpp/windows/latest-supported-vc-redist?view=msvc-170
   3. C++ 2015-2022 (64-bit) - https://learn.microsoft.com/en-us/cpp/windows/latest-supported-vc-redist?view=msvc-170#visual-studio-2015-2017-2019-and-2022
5. Install .NET Framework 4.72 if not already installed. Reboot after installation.
6. Viewpoint can view native documents both within the Viewpoint application and by launching the native file in its native application. Supporting the latter feature requires that native viewer applications be installed on Terminal Server. Licensing requirements may apply.
7. If the users are not domain users with access to the MSSQL Review instance you will need to construct a Config.txt / Config.INI file. See the Viewpoint Config.txt Creation Guide for instructions on how to set up one of these files.
8. Disable User Account Control (UAC):
   1. Type “UAC” into the Start Menu.
   2. Move the slider all the way to the “Never notify” setting.
   3. Click “OK”.
9. Reboot the server – this step is required so that Windows security configuration changes.
10. Create the root folder for the installation package. By convention this folder is named “INS”.
11. Under the “INS” folder create child folder “Viewpoint”. Under the “Viewpoint” folder create a child folder with the name of the version of the application you are running (7.0.0, etc.). In this folder place the Viewpoint Review installation file (SETUP.EXE).
12. Run the SETUP.EXE application. Complete the installation package – use all defaults.
13. Now that Viewpoint Review has been installed, navigate to the program files which by default are located at C:\Program Files\LateralData\Viewpoint\
14. If you have generated a Config.INI file, place it into this folder.
15. Configure Terminal Server to run the Viewpoint Review application executable. It is named LateralData.Applications.Dashboard.exe.
16. While still logged into the Terminal Server, as a box administrator, open the Viewpoint Review application. Click the ‘Review’ button at top-left; this will open the Review screen. Ensure that the Review screen opens without error. Close Viewpoint Review when done.
17. Log into a user PC and access Viewpoint Review through your server.
18. Click the “Review” button. Navigate to a document. Open a Viewer to ensure that the viewer is working properly through your hosting application. On the Viewer select the Native, HTML, Text and TIFF viewer types. These steps will exercise basic functionality for launching other programs from within Viewpoint Review, as well as surface any potential file store access / permission issues.
19. Configure printing – often hosting applications such as Terminal Server require a few additional steps to facilitate printing from a hosted application (Viewpoint Review) to the user’s local printer. If you are using Terminal Services try using the “Terminal Services Easy Print” driver as this is usually successful.
20. Click the “Review” button. Locate any Document. Right-click on the Document and select “Print” – ensure that documents are printed to the expected printer.
21. With a Document selected right-click and select “Save” and save a copy of any Document locally. This will further exercise file store access.

Optional Terminal Server Components#

You may choose to install additional software packages on Terminal Server to facilitate viewing documents in their native application. The following are recommended:

• VLC Media Player – to natively review audio and video files. Installation is a standard setup executable.
• RealLegal E-Transcript Bundle Viewer – To natively review LiveNote transcript files. Installation is a standard setup executable.

Viewpoint Installer Maintenance Options#

The Viewpoint installer package also includes a maintenance section that is used to perform various tasks post-installation. Each of the options is covered in detail, as follows:

Add Files#

This is used to aid in adding licenses, logos, and configuration files to the install location of the applications. Click the ellipsis on the right side and browse to the install location of the application where the files will be added to. After clicking Next, click the add icon and then click the ellipsis on the new box to browse to the file that will be added to the install location. To add multiple files, click the add icon again to create additional boxes. Click Next when all the files are ready to be added. The last screen verifies which file(s) will be copied to which location. Click Copy to finish.

NSRL Update#

The user will be required to login to the SQL Server instance containing the NSRL database. If Windows Authentication is used as the authentication type, the User Name and Password fields remain blank and the user can click Next. If SQL Server authentication is used as the authentication type, a user name and password will need to be typed in before moving on. Please ensure that whichever authentication type is used, the account has administrative rights in SQL to complete this task.

If the user has already downloaded the current hashset, click the ellipsis on the Location field to browse to the .zip file containing the hashset. Update the Version field to reflect the version number of the new hashset, and then click Next. Then click Update to begin the process of extracting and installing the new hashset.

Alternatively, checking the box to Attempt to download the RDS from http://www.nsrl.nist.gov, and clicking Next will attempt to download and install a legacy version of the hashset.

Review Settings#

Selecting Review Settings will bring up a window to log in to a Review SQL database. Successfully logging in will open the Settings window.

Configuration Settings#

This section is primarily intended to assist support personnel in troubleshooting specific issues without needing direct SQL Server access. It is recommended to only make changes to these settings when advised to do so by Viewpoint Support. These settings control many features within the Review application function.

Stock Fields#

The Stock Fields Editor allows users to manage which fields are available to use in the Review application. The Available, Global, and Word Wrap checkboxes are editable. The Available field controls whether the field is available to add to a Form. The Global field controls whether the field is included in the Global Form. The Word Wrap field controls whether the field will word wrap and adjust to the column width when it is displayed in the document grid.

When a View is loaded in the Review application, all the available fields are queried. That way when a new field is added to the grid from the Fields Selector, the application doesn’t have to send a new query to populate the added field. The Stock Fields Editor can be used to control the number of fields that get queried when a View is opened. By removing unnecessary fields, loading times of larger Views can be sped up.

There are some fields that are tracked in the database but are not considered stock. Occasionally, there is a need to make these fields available in the Review interface. New custom stock fields can be added by right-clicking in the list and selecting, New.

Field Text is how the name will appear in the application. A description can be entered, if desired. Table Name is selected from the dropdown box. The Field Name drop down box will list all of the fields in the table selected previously. This is where the user will find the field they wish to add to the stock fields list. A Format Type, such as Date/Time and Numeric, may need to be selected to display the field value as the correct data type. Format String is used to change how certain format types are formatted. For example, if a Format Type of Date/Time is used, a Format String of MM/dd/yyyy HH:mm can be used to display the field as 11/29/2017 12:27. Formula and Data Source are used for advanced customization of the new field. Using these two options, custom queries can be used to further customize the new custom stock field. The Grids field is a dropdown box where the user can select what parts of the application the new field will be available to be used.

String Resources#

String Resources is designed to give users the ability to update the values of string resources within the Review application. This means that many buttons, labels, settings, and dialog boxes can be updated with new text. This is especially useful for non-English users who would like the application to display application resources in their own language. Changes can be made on a global level or limited down to a single project.

To update values, select a language from the Language dropdown box. From the Project dropdown box, select whether the changes will be applied globally, or a single project. Then, find the Key or Value to be updated. Finally, click on the Value of the Key and type in, or copy/paste the new Value. Values that have been changed from default will now appear bolded in the list.

For users to see the changes reflected in the application, click the About button in the Review application. At the bottom of the About box there is a Language dropdown box. Select the desired language that was edited in the String Resource Editor. If changes were only made on a project level, select the project from the project list in the dashboard of the Review application, and then click the About button at the top of the screen and select the language from the dropdown box.

Processing Settings#

The Processing Settings will display the current settings for the system. It is not recommended to change these values without first speaking with Viewpoint Support.

Data Management Tool#

The Data Management Tool is designed to give users the ability to easily move Viewpoint project data and simplify the process of moving Viewpoint project database files.

The Data Management Tool (DMT) is accessed from the Viewpoint Installer application.

Within the application, click the Maintenance option on the left side and then click the Data Management Tool option. A login window will open where the user can enter the SQL Server name of the Viewpoint processing SQL database. Click OK to log in.

Note: Only user accounts with sys admin privileges to the SQL Server database will be able to log in successfully. Alternatively, users can uncheck the “Use Windows Account” option and use a set of SQL Server credentials that have sys admin privileges.

If successful, users should see a window like the screenshot below. There are two radio button options, Manage Data Store and Move Entire Project. These will be covered in detail below. The Projects list displays all the Viewpoint projects stored in the database. Additional fields can be added to the list, such as Database Version and File Server, by right-clicking in the panel, selecting Fields Selector and then double-clicking on or dragging the desired field into the panel.

Manage Data Store#

When a user selects Manage Data Store and clicks Next on the main page, a window opens like the screenshot below. This feature allows users to move specific project data to a new location based on selected Medias, Views, Dedupe Set, File Category, or Ignored Files, and then automatically updates the path information in the project database to reflect the new location within the application.

To use this feature, type in the UNC file path of the location where the files will be moved to. This will be the root path where the selected file type folders will be moved to. Alternatively, click the ellipsis to browse to the new root folder. After a destination has been chosen, the Destination Server Root Path field will be populated on the right side of the window. Individual paths can also be used for Index, Text, HTML, and Tiff. To change a path, either click on the Destination Server Root Path field and type in a new path or click the ellipsis on the right side of the field to browse out to a new location.

Note: The credentials used to log in to the Data Management Tool will need full file permissions in the current file location and the new file location for the data to successfully move. Also, check to make sure there is sufficient free space available in the new location.

Also, please do not attempt to move files if they are already in their target location.

Next, check the boxes of the file types that are to be moved from the current location to the new location.

Finally, select whether to move files based on Media or Filter Options. The filter options gives the user the option to move files based on View(s), duplicate files as defined by a Dedupe Set, file category, or files marked as Ignored.

Media#

If the Media option was selected, the next window will display the list of Medias in the project. Check the boxes of the Medias that need to be moved. If all Medias need to be selected, right-click in the panel and select Check All.

Users can see where the different file types are currently stored by right-clicking in the panel using the Fields Selector option to add in the root path fields.

When the user is ready to move forward, click Next.

Filter Options#

If Filter Options was selected instead of Medias, the next window will display four filter options. Selecting the Move docs in View(s) option and clicking Next will display a new window where the user will select one or more Views to move. Selecting the Move Duplicate DeDuped Files option will enable the dropdown box to select one or more Dedupe Sets from the project. Selecting the Move Files by File Category will enable the dropdown box to select one or more file categories, such as compressed archives or system files. Finally, selecting Move Ignored Files will move all files in the project that are marked as Ignored

Ready to Process#

After the user is done making selections, there is a confirmation window that is displayed before executing any change. Please verify that all the information displayed here is correct before clicking Finish.

When the process is complete, a box will pop-up to notify the user that the process is completed successfully.

Move Entire Project#

This option provides an easier way to migrate whole projects (databases and/or project data) to a new location.

The Move Data Store option is essentially performing the same function as the Manage Data Store option discussed above. However, this will move the entirety of the project data without needing to select which file types and Medias to include. Either type in or paste the new root UNC file path in the field provided or click the ellipsis to browse to the new location. Once the migration has been executed and the files have been moved, the new file paths will be updated in the project database and reflected in the application.

Note: The user account used to log in to the Data Management Tool needs full file permissions in the old file location as well as the new location for the data migration to complete successfully. Also, check to make sure there is sufficient free space available in the new location.

Moving the project database(s) is done by checking either the Move Processing Database box and/or Move Review Database box. Then, if the database being moved will need to communicate with a different LDControl database, check the box labeled, Move to a Different Processing (or Review) LDControl.

Each of the four sections has identically labeled fields to enter in the pertinent information of each checked option. The Server field will be the new SQL Server instance the database will be moving to (ex. NewViewpointSQL\Processing.) The Database field will be the database name in the new location. This name may need to be changed if a project with the same name already exists in the new location. The Authentication field gives the option to use either Windows Authentication or SQL Server Authentication. If Windows Authentication is used, the User Name and Password fields will be disabled. If SQL Server Authentication is used, use a set of credentials that has sys admin rights to the server entered in the Server field. Use the Test Connection button to check the credentials and database name against the new server.

After the necessary selections have been made and the connection tests complete successfully, click Next. If moving LDControl databases, a window will pop up requiring the user to select a Company from the new LDControl database to associate to the project being moved.

There is a confirmation window that is displayed before executing the move. The text box summarizes the selections that were made previously and give important information on how to proceed after the process finishes. Please read this and verify that all the information is correct before clicking Finish.

Note: This tool does not completely automate the migration of a project from one SQL Server to another. This tool will make the necessary changes in the project database and LDControl databases to make it easier to move. Once the process is complete, the database files will need to be manually moved to the new location and then attached to the new SQL Server.

The grid on the bottom portion of the window is displays the processes in SQL Server currently accessing the selected project. There is a separate tab for the Processing and Review databases. From here, users still accessing the project can be seen. Please make sure that all users are out of the project before moving the project databases and/or project files.

Clicking Finish will do a final check and prompt the user if there are still open processes accessing the project database.

The process may take some time to complete depending on the size of the database and files being moved.