Deployment Guide

Deployment Guide
 Veriato Recon / 360
Deployment Guide
Deployment Guide Contents
Before You Begin .......................................................................................................... 1 How the System Works ............................................................................................................................. 1 Requirements and Planning ...................................................................................................................... 5 How to Disable Antivirus Scanning ......................................................................................................... 11 Setting up SQL Server 2016 ................................................................................................................... 13 Installing the Veriato Server ....................................................................................... 18 Quick Install with SQL Server Express ................................................................................................... 18 Install for Use with Full SQL Instance ..................................................................................................... 22 Install Management Console Only .......................................................................................................... 30 Install the Database Separately .............................................................................................................. 34 Creating the Master Login Account ......................................................................................................... 39 Logging in ................................................................................................................................................ 42 Activating Veriato Recon/360 .................................................................................................................. 42 Configuring a New Install ........................................................................................................................ 44 Deploying the Recorder .............................................................................................. 45 Adding a Test Recorder .......................................................................................................................... 45 Supplying Device Credentials ................................................................................................................. 50 Using Active Directory to Add More Recorders ...................................................................................... 52 Using Active Directory to Add Users ....................................................................................................... 57 Deploying to Android ............................................................................................................................... 61 Deploying in a Windows Workgroup ....................................................................................................... 66 Deploying to a Session Host ................................................................................................................... 68 Deploying with SCCM ............................................................................................................................. 70 Troubleshooting .......................................................................................................... 83 Exclude the Server from Scanning ......................................................................................................... 83 Exclude the Recorder from Scanning ..................................................................................................... 90 Recorder Errors ........................................................................................................... 95 Check antivirus settings .......................................................................................................................... 95 Administrative Share Access .................................................................................................................. 96 Disk Space or System Requirements ..................................................................................................... 98 Enable File and Printer Sharing .............................................................................................................. 99 Insufficient Permission .......................................................................................................................... 100 Invalid credentials ................................................................................................................................. 101 The Recorder Was Not Installed ........................................................................................................... 102 The Recorder Version Is Not Supported ............................................................................................... 104 ii Deployment Guide Remote registry cannot be enabled ...................................................................................................... 105 Windows UAC Prevented installation ................................................................................................... 106 WMI Firewall Blocking Communication ................................................................................................. 107 Unable to discover... ............................................................................................................................. 108 Too Many to List .................................................................................................................................... 109 Contact & Copyright ................................................................................................. 111 Contact Us............................................................................................................................................. 111 Copyrights and Trademarks .................................................................................................................. 111 Index...................................................................................................................................................... 115 Deployment Guide iii Before You Begin How the System Works
To capture data, Veriato Recon/360 relies on endpoint Recorders, load balancing (if enabled), application server(s), and a database. The Management Console accesses the database through the server to provide status and views of the data. When you install using the Veriato Setup program, you install a Veriato Database, the "primary" Veriato Application Server, and a Management Console. Deployment Guide 1 How the System Works NOTE: Contact Veriato Technical Support for assistance in setting up multiple Application Servers.
Installing all components on one server
You have several options when you first install. The default is to install all server components, including a Management Console, on a single computer ‐ the computer you are installing on. The "Quick Install" and "Install with Options" provide a single‐server installation with SQL Server Express (limited database size). Use "Install with Options" to select an existing SQL Server (2016 Standard edition) to provide your database. When you use and existing SQL Server, you will need to (1) create a database instance before you begin, (2) provide the SA SQL account and the name of the SQL instance during the installation. NOTE: Screenshot and Attachment files (File Storage) can take up a great deal of disk space. The
default location is on the same, single server. You can direct this storage area to a separate hard
drive during "Install with Options," if you wish.
Installing the database on its own server
For a large number of clients generating a lot of data, you may want to install SQL Server and the Veriato database on a separate computer. After installing SQL Server 2016 (or setting up access to a web‐hosted SQL Server), create a new, empty SQL Server instance. You will install the Veriato database first, on the SQL Server computer, using the "Install Database Only" option. When the Veriato database is set up, install the Veriato Server at its computer using "Install with Options." 2 Deployment Guide How the System Works IMPORTANT: If you plan to connect to a SQL Server Standard database, create an empty database
instance first (even if you are upgrading).
Using a separate file server
To insure that many screenshots will not interfere with performance, set up a separate file server. NOTE: The file storage location needs a direct connection to the application server. Contact Veriato
Technical Support for assistance.
Deployment Guide 3 How the System Works Veriato Database
The database instance when hosted on SQL Server Standard (or another "full" edition) provides a 30 GB admin database and a 50 GB Reporting database, with growth by 15% as needed, and no maximum size. The database when installed with SQL Server Express has a maximum size and is limited to a single, 9 GB maximum size for admin and reporting databases. We recommend this convenient, automatic database setup for evaluating the product and small companies. Veriato Application Server
Add Application Servers to speed up performance and contribute to efficient load balancing. One or more servers relay data uploaded by the Recorder to the database. A "load balancer" can intercepts Recorder data and passes it to an application server, which in turn routes it to the database. The entire process, even for hundreds of thousands of endpoints, takes a few seconds. Only one database is necessary, even for the largest installations. Veriato Endpoint Recorder
The Recorder can be deployed en masse to endpoint computers from the Management Console or by creating a manual setup file to execute at each device by other means (such as SCCM). A license is required for each device recorded. Use a manual setup file to install a Recorder app on Android mobile devices. The Recorder captures the activity of every user who logs into the device and stores activity by user. Veriato Recon sends back user metadata for analysis. Veriato Recon sends back complete, detailed user activity data and screenshots. Management Console
The Management Console provides dashboards, data views, configuration, and access to all components, as permitted by each user's login account. Install as many Management Consoles as you need. 4 Deployment Guide Requirements and Planning Requirements and Planning
Plan your installation
The system requirements for installing all components on one machine (all‐on‐one) or separately are listed below. Refer to the Upgrade Guide for requirements and recommendations on upgrading. NOTE: Do NOT install Veriato server components on a machine that is also hosting a Domain
Server or an Exchange Server.
Quick install with SQL Server Express (all-on-one)
A Quick Install Installs MS SQL Express 2016 and configures a database instance in addition to the Veriato Server and Management Console and provides capacity for maintaining about 6 months of recorded user data. Installing with SQL Server Express is recommended for evaluations and small installations. If a system restart is pending due to OS updates, you are prompted to exit and restart the computer before installing. Requirement
Quick Install (with SQL Express)
Operating System
Windows 8.1
64-bit OS
Windows 10 or
Windows Server 2012
Windows Server 2016
If a system restart is pending due to OS updates, you are prompted to exit
and restart the computer before installing.
Business-class Desktop
Hardware
Quad Core 17
8 GB RAM
Disk space
(see also Data Storage below)
40 GB free disk space minimum to evaluate
100 GB for on-going monitoring
Prerequisites
.NET 4.6.1 (install requires restart)
(Installed if not found)
Visual C++ runtime
Microsoft Message Queueing (MSMQ)
Microsoft SQL Server Express 2016
If SQL Express is already installed, the setup creates a new instance
named VERIATO360

The SQL Server Express instance is limited to a single, 9 GB maximum database (admin and reporting databases) with 0 file growth. Deployment Guide 5 Requirements and Planning 
You can manage ongoing data size by using Management Console reporting and export features, while trimming older data from the database with automatic Data Retention settings. Install with existing full SQL Server (all-on-one)
Recommended for customers with up to 1,000 endpoint clients. An alternative to installing SQL Server on a local machine is subscribing to a hosted, cloud‐based SQL Server. If a system restart is pending due to OS updates, you are prompted to exit and restart the computer before installing. Requirement
up to 500 Endpoints
up to 1000 Endpoints
Operating System
Windows 8.1
Windows Server 2012
64-bit OS
Windows 10
Windows Server 2012
Windows Server 2016
Windows Server 2016
Hardware
Server-class System
Quad Core Xeon
Enterprise-class System
Dual Quad Core Xeon
16 GB RAM)
32 GB RAM)
Free disk space
100+ GB
250+ GB
Prerequisites
.NET 4.6.1 (install requires restart)
.NET 4.6.1 (install requires restart)
(included)
Visual C++ runtime
Visual C++ runtime
Microsoft Message Queueing
(MSMQ)
Microsoft Message Queueing (MSMQ)
To connect to and configure a full SQL Server database instance, select Install with Options and "Use an existing SQL Server": 
MS SQL Server 2016 (Standard or enterprise edition) must be pre‐installed. 
You must have created a new, empty SQL Server instance to receive Veriato configuration. 
When installing the Veriato Server, provide the location and name of the SQL instance and the SQL Server SA password. Standalone Management Console
Install the light‐weight Management for each manager or administrator on separate network computers. If a system restart is pending due to OS updates, you are prompted to exit and restart the computer before installing. 6 Deployment Guide Requirements and Planning Requirement
Operating System
Windows 7 SP1, 8, 10
64-bit OS
Windows Server 2008 R2, Server 2012, Server 2016
Prerequisites (included)
.NET 4.6.1 (install requires restart)
Visual C++ runtime
Microsoft Message Queueing (MSMQ)
Disk space
200 MB
Standalone components (Enterprise)
A separate database server is recommended for a large number of endpoint clients. The full SQL Server instance configures a 30 GB admin database and a 50 GB Reporting database, with growth by 15% as needed, and no maximum size. If you plan on monitoring 3,000+ endpoints, you can distribute components across the network, provide load balancing, and add application servers to ensure disk space and optimal performance. Requirement
Database (without
SQL)
Primary Server +
Management Console
Secondary
Application Server
Windows Operating
Windows Server 2012
Windows Server 2008 R2,
Windows Server 2008
System, 64-bit OS
Windows Server 2016
Server 2012, Server 2016
R2, Server 2012,
Server 2016
Disk space
100 GB
120 MB (server)
120 MB
See Data Storage below
200 MB (Management
Console)
Processing
RAM
Speed
RAM
Speed
RAM
Speed
Prerequisites
.NET 4.6.1*
.NET 4.6.1*
.NET 4.6.1*
Visual C++ Runtime
Visual C++ Runtime
MSMQ
Visual C++ Runtime
MSMQ
TCP port 1434 for default
443
443
instance
Check the error log for
the port number
57409
57409
Run the VeriatoSetup
Run the VeriatoSetup with
Contact Veriato
with "Install Database
Only"
"Install with Options." Point
to your pre-installed
Technical Support
Ports used
Method of installing
database instance.
*Installing the prerequisite requires computer restart. Deployment Guide 7 Requirements and Planning Read How the System Works for an overview. General steps will be: 1.
Install SQL Server on a server grade machine. Create a new, empty SQL Server instance to receive Veriato configuration. 2.
Run the setup on the SQL Server machine. Use Install Database Only to configure the Veriato database instance. 3.
Run the setup on the Veriato "Primary" Server machine. Use Install with Options to install the Server and Management Console, point to the installed database instance, and select data and file storage locations. 4.
Install additional application servers after the primary server is fully set up. Contact Veriato Technical Support for customized assistance with your setup. Data storage requirements
Veriato Recon/360 uses a single Data Storage location and Backup Location, where data is copied during backups. By default, all data, files and backups are stored on one machine. Use "Install with Options" to direct files and backups to different drives. Install with options lets you direct data storage to local hard drives The table below show daily and monthly totals for data and backups, without totalling them. Size estimates are based on 3 MB per user per day. Actual daily size may be much larger, depending on level of user activity and the Recording Policy settings. As you can see, if stored on a single server, a great deal of disk space might be needed! Make sure the drives where you direct data, files, and their backups have enough disk space to handle the amount of data you expect to record. 8 Deployment Guide Requirements and Planning Requirement
Drive location
Data Files
Automatic Database Backups *
Local to database computer
SQL Server and Veriato Service can access
to backup location
Recorders
Est. Daily
Monthly
Daily**
Monthly***
1 - 15
45 MB
1.35 GB
50 MB
2.6 GB
15 - 100
300 MB
9 GB
350 MB
18.2 GB
100 - 500
1.5 GB
45 GB
1.55 GB
80.8 GB
500 - 3000
9 GB
270 GB
9+ GB
470 GB
3000 - 10,000
30 GB
900 GB
30+ GB
1.56 TB
10,000+
100 GB
3 TB
100+ GB
5.2 TB
* No trimming ** One differential backup (data + 50 MB) *** Entire month of backups: (Diff * 6 + Full) * 4, where Full = (Diff * 6) + Diff. 
Data files ‐ Recorded data stored in the Veriato database. 
Automatic Backups ‐ Backups of the Veriato database. Differential backups performed nightly include new data, starting from the last backup. Full backups performed weekly include a complete snapshot of the current data. Monthly (4‐week) rough estimates are based on a weekly accumulation of ((Differential * 6) + Full) * 4. IMPORTANT: Keep in mind that SQL Server Express has a 9 GB maximum size for single Admin
and Reporting databases. The SQL Server Express Reporting database is FULL and the system
stops operating when data reaches just over 4 GB.
File storage requirements
The Veriato Server directs files associated with recorded data to a single file storage location. Files are backed up along with database backups, if you choose. By default, all data, files and backups are stored on one machine. Use "Install with Options" to direct files and backups to different drives. Size estimates for screenshots associated with recorded data are based on the default Recording Policy of one grayscale screenshot every 30 seconds, each user with one monitor working a light day. The average daily disk cost might be about 8 MB per user. The table below omits capture of email file attachments (sizing would based on number and file size of attachments). Deployment Guide 9 Requirements and Planning File Requirement
File Storage*
File Backups**
Drive location
Local to server installation
Veriato Service can access the
backup location
Recorders
Daily
Monthly
Daily
Monthly
1 - 15
120 MB
3.6 GB
120 MB
3.6 GB
15 - 100
800 MB
25 GB
800 MB
25 GB
100 - 500
4 GB
120 GB
4 GB
120 GB
500 - 3000
24 GB
720 GB
24 GB
720 GB
3000 - 10,000
80 GB
2.4 TB
80 GB
2.4 TB
100 GB
3 TB
100 GB
3 TB
10,000+ * Files include ONLY screenshots, attachments are NOT captured ** No trimming You can prepare for disk space usage by selecting "Install with Options" and by installing the database separately. As a matter of best practice, you should enable settings to automatically delete older backups. Find all necessary settings under System Management in the Management Console: 
Data Retention ‐ Enable automatic removal of old/extra backup sets, screenshot and attachment files, and log files. Also provides the ability to "trim" active data. 
Server Settings ‐ View current data and file storage locations and change backup locations. 
Backup & Restore ‐ View backups, as well as backup on demand and restore backups. Recorder at Windows client
Veriato Recon/360 version 9.0 communicates only with Recorder Version 9.0+. Updated Recorder software is supplied on activation. Requirement
Operating System
64-bit or 32-bit
Windows 7, 8, 10
Windows Server 2008, 2012, 2016
Prerequisites (included)
.NET 4+ (installed if not found)
Administrator-user credentials to install the software
File and Printer Sharing enabled (for remote install)
Disk space
1.5 GB free disk space
10 Deployment Guide How to Disable Antivirus Scanning Recorder at Android client
Manage Recorder installation, updates, and uninstallation at the device itself. See Deploying to Android. Requirement
Android mobile phone
Android OS 5.0+
or tablet
Prerequisites
Enable “Allow app installs from Unknown Sources”
Install the provided "Chromium" app
Free space
145MB - Required Chromium app
24MB - Veriato Recorder
How to Disable Antivirus Scanning
Some antivirus and anti‐spyware programs scan for and attempt to remove Veriato files on a computer. Files may be removed during or after Veriato Recon/360installation. Before you install the Veriato Server, temporarily disabling scanning during the installation and exclude the installed Veriato Recon/360 files from ongoing detection by your antivirus software. Before deploying Recorders, exclude the Veriato Recorder files. Temporarily disable scanning at the server
1.
Find the antivirus icon. At the computer where you will run the Veriato Setup program, look in the windows notification area in the lower right corner of your desktop. Active antivirus programs usually display an icon directly on the task bar or when you click an up‐arrow in the notification area. 2.
Right‐click the antivirus icon and select "Disable <Program>." If a "disable" option is not available, open or modify the program and find the control to temporarily disable it. (If the install program needs to restart the computer due to prerequisites installation, you may need to turn it off again.) Example of an active antivirus icon in the taskbar Deployment Guide 11 How to Disable Antivirus Scanning 3.
Exclude the Veriato Server files. Before re‐enabling scanning, exclude the Veriato installed files by adding them to an "whitelist." This is only necessary at the Veriato Server computer. This ensures the antivirus software will bypass these files in subsequent scans and not remove or quarantine them. Refer to Excluding the Server from Scanning for folder/file names. 4.
Re‐enable antivirus scanning. When Veriato files are excluded, re‐enable antivirus scant. IMPORTANT: Especially when AVG Anti-Virus or a similar product is used, be sure to disable
scanning BEFORE downloading and installing. For this product, make sure you open the control
panel and turn OFF Resident Shield scanning.
Exclude Veriato Recorder files across the network
Before you deploy Recorders: 1.
If you use an enterprise antivirus solution, such as McAfee or Symantec, open the management application and exclude the Veriato Recorder files for all Windows devices (and VMs) on your network you plan to manage. Build this step into your network‐wide endpoint policy and virtual machine setup. If you do NOT use an enterprise solution, go to each endpoint Windows computer and exclude the Veriato Recorder files within the antivirus control panel. 2.
If you do not depend on additional local applications, such as Windows Defender, you could disable the program as part of group policy to avoid any future problems. Refer to Excluding the Recorder from Scanning for the folder/file names. 12 Deployment Guide Setting up SQL Server 2016 Setting up SQL Server 2016
If you plan to use Veriato Recon/360 with SQL Server Standard, you'll need to install (or connect to a cloud version of) SQL Server and create a database instance BEFORE running the Veriato Setup. For complete SQL Server installation information, consult the Microsoft website. If you're upgrading Veriato Recon/360 with SQL Server Standard installation, you still need to create a new database instance. NOTE: If you plan to use Veriato Recon/360 with SQL Server EXPRESS and are aware the
limitations, you can skip this step.
1.
Download a SQL Standard 2016 package from Microsoft. If you have an existing SQL Server installation, make sure it has been upgraded to 2016. 2.
Run the SQL Installer elevated as Administrator. 3.
Click Installation in the left navigation. Select "New SQL Server stand‐alone installation or add features to an existing installation." 4.
Enter your SQL Server product key. At the Product Key panel, enter your SQL Server product key and click Next. 5.
Accept the license Agreement. Click Next. 6.
At the Product Updates panel click Next. Deployment Guide 13 Setting up SQL Server 2016 7.
At the Feature Selection pane: Be sure to check the following: Database Engine Services Client Tools Connectivity Client Tools Backwards Compatibility Leave the default instance root directory, or change it if you wish. You'll need the instance root directory during Veriato Setup. Click Next. 8.
At the Instance Configuration panel, set up the new instance. Select Named Instance and give your Veriato Database instance a name. Any name will do, but it's best to specify something that is NOT the SQL default. We use VERIATO360 in documentation examples and as the default for SQL Server Express installations. The instance ID is automatically supplied. You'll need the instance name during Veriato Setup. 14 Deployment Guide Setting up SQL Server 2016 Click Next. 9.
Note the SQL Service accounts. On the Server Configuration panel the SQL service accounts are defined. Accept the default settings by clicking Next. 10.
On Database Engine Configuration select Mixed Mode. Type a secure SQL Server System Administrator (SA) password and confirm the password. This SA password is required during the Veriato Setup. For emergency use, assign a local Windows Administrator‐user the same SA access rights: Use the current login account ‐ Add Current User, or someone else ‐ Add. Specify credentials Deployment Guide 15 Setting up SQL Server 2016 as prompted. Click Next. 11.
Select the "Data Directories" tab and note the default directories. You can change them to another location on the local machine, if you wish. You'll need the System database directory during Veriato Setup. 12.
For advanced setup, select TempDB. If you are configuring an advanced, performance setup, select the "TempDB" tab and specify 16 Deployment Guide Setting up SQL Server 2016 the log file configuration. 13.
Press Next and then press Install. Deployment Guide 17 Quick Install with SQL Server Express Installing the Veriato Server Quick Install with SQL Server Express
A Quick Install is the fastest way to get up and running with Veriato Recon/360. It installs all components on one computer, providing SQL Server Express 2016 for the database. This installation is recommended for evaluating the product and for customers with fewer than 100 client endpoints to monitor. Steps
1.
Start the setup ‐ Following purchase, go to www.veriato.com/support, enter your product key, and download the setup package. Extract the package, open the extracted folder, and open the Installer folder. Double‐click the VeriatoSetup file to start the installation. 2.
Welcome ‐ At the Welcome panel, click Next. 18 Deployment Guide Quick Install with SQL Server Express 3.
End user license agreement ‐ Read the license agreement, press Agree, and Next. 4.
Disable antivirus and set exclusions ‐ Because antivirus can interfere with this installation, we recommend "excluding" Veriato files and disabling scanning during the Veriato installation. Press the blue buttons to learn more and get a list of files to exclude. Press Next. Deployment Guide 19 Quick Install with SQL Server Express 5.
Options for installing ‐ Leave this set to "Quick Install." Press Next. 6.
Create the master login account ‐ You are creating the primary, full‐access login account for this Veriato Recon/360 installation. For complete details, see The Master Login Account. 
Email Address ‐ Enter your email address. You can use your email address to log in to the Management Console. Uncheck the "Use email as login name" box to enter a unique SQL user name. 20 Deployment Guide Quick Install with SQL Server Express 
Password ‐ Enter a password for the account that meets the displayed criteria. Type the password again to verify. 
How to send alert emails ‐ The Veriato Server sends automatic email alerts and reports to "operators." Your above email address will be the first "operator." Read more about email service options. Press Next. to begin installing
7.
Wait for the installation to complete, then press Finish. 8.
If the login prompt does not appear, use Windows to find and start the Veriato Management Console. Log in using the account you just created. 9.
Complete your setup: Activate using your product key and then Add Recorders to begin monitoring users. Deployment Guide 21 Install for Use with Full SQL Instance Install for Use with Full SQL Instance
To use an existing, full MS SQL Server instance, you must select Install with Options during the setup. This option allows you to: 
Use an existing, full MS SQL Server installation 
Change installation folders (on the current machine) 
Specify non‐default locations for database files and screenshot and attachment file storage 
Set up the primary server and Management Console for a Veriato 9.0 database you already installed. If SQL Server and the Veriato database instance are located on a separate computer,
use the Install Database Only setup option on that machine first.
IMPORTANT
Before you begin

Log in to Windows using the appropriate domain account. If you're going to reference any non‐local locations (for SQL Server, database, files, backups, etc.), log in using a Windows network account that has full access to those locations. Run the setup as elevated user ‐ "As Administrator." If all components will be installed to drives local to this computer, you can log in as a local administrator. 
If using full SQL Server, it must be "ready to go." If you are using SQL Server Standard, Enterprise, hosted or pre‐installed, make sure you have a working system administrator (SA) account, and a SQL Server instance ready for the database installation that is accessible on the network from your current computer. See Setting up SQL Server. 
Install the database first, if not on the same machine. If your plan is to use an existing SQL Server on a different machine, install the Veriato Database FIRST, before performing this "server" setup. Make sure you have the correct SQL Server location and Veriato database instance name. Follow instructions for (1) Setting up SQL Server (2) Installing the Database Separately Then return to this page. 
If the database or file storage will be remote, be prepared to enter credentials. The Veriato Service is normally assigned "local" service credentials. If remote directories are 22 Deployment Guide Install for Use with Full SQL Instance specified in this setup, you will be prompted to provide network account credentials with privileges to read and write at the specified locations. Start the setup
1.
Start the setup. Following purchase, go to www.veriato.com/support, enter your product key, and download and double‐click the VeriatoSetup file. 2.
Welcome ‐ click Next. Deployment Guide 23 Install for Use with Full SQL Instance 3.
Accept the end user license agreement. Read the license agreement, press Agree, and Next. 4.
Disable antivirus and set exclusions. Because antivirus can interfere with this installation, we recommend using your antivirus solution to "exclude" Veriato files. Press the blue buttons to learn more and get a list of files to exclude. See Exclude the Server from Scanning. Press Next. 24 Deployment Guide Install for Use with Full SQL Instance 5.
Options for installing. Select "Install with Options." This panel sets up your Veriato installation. 
Use an existing SQL Server installation ‐ Check to use a full MS SQL Server (recommended) pre‐installed on this or at another location. If not checked, MS SQL Server Express and a size‐limited storage database will be installed. 
Services Port ‐ The default communication port for Recorder to Server communication is 443 at the Server computer. Change this only if there is a conflict on your network. 
Services Installation Path ‐ The Veriato Service will be installed in this folder, on this machine. The default location is C:\Program Files\Veriato. If you wish, click Change and browse to a different folder or drive (preferably on this machine). 
Management Console Installation Path ‐The Management Console installed WITH the Veriato Server will be installed at this location. If you wish, click Change and browse to a different folder or drive on this machine. 
SQL Server Data Path ‐ The directory where the Veriato SQL Server instance is set to store data. If you have already installed the database on ANOTHER machine, be sure to use the complete network path to the location you specified before (e.g., \\MACHINE02\Program Files\Microsoft SQL Server\MSSQL13.VERIATO360\MSSQL\DATA). If you are installing the database on THIS machine, you can leave the field blank to use the System database Deployment Guide 25 Install for Use with Full SQL Instance directory already set in SQL Server, or you can select Change and navigate to another folder or drive local to the SQL Server computer. 
Screenshots and Attachments Path ‐ Indicates where captured Screen Snapshot and Email Attachment files are stored (the File Storage folder).Otherwise, the default location is set to C:\VeriatoData. Select Change and navigate to any folder local to the Veriato Server where you want files stored. 6.
Connect to SQL Server. If you selected the option to use an existing SQL Server installation, a second Options panel appears. If you did NOT choose the option, this panel does not appear. 
SQL Instance Name ‐ The name of the SQL Server database instance you have created for Veriato installation purposes, or the name of Veriato database instance that has already been installed (using "Install Database Only"). 
SQL Username ‐ The root login account to the SQL Server installation you will be using, usually SA. The Veriato setup needs full access to SQL Server to continue. 
SQL Password ‐ The password for the SA username you provided. 
SQL Server Address ‐ Specify a fully qualified device name (computer.domain) to locate the SQL Server installation you want to use on your network. 26 Deployment Guide Install for Use with Full SQL Instance 
SQL Server IP Port ‐ Normally SQL Server communicates at TCP/IP port 1433, but will dynamically select available ports for its named instances. If SQL server will communicate on a fixed port for your Veriato instance, enter the port here. Do NOT enter a value here unless you are fully aware of your network infrastructure. Click Next. If the setup is able to find and log in to SQL Server, it begins installing
the database instance, and then continues on to the remaining installation.
If the SQL username/password is incorrect, or SQL Server cannot be found at the location specified,
an error message appears: "Unable to log in to existing SQL Server." Click OK, review your entries
on this panel, and try again.
7.
Set up the Master Account. The Account panel is where you set up the primary, full‐access login account for this Veriato Recon/360 installation. The account applies only to your Veriato database instance. For complete details, see The Master Login Account. 
Email Address ‐ Enter your email address. You can use your email address to log in to the Management Console. Uncheck the "Use email as login name" box to enter a unique SQL user name. Deployment Guide 27 Install for Use with Full SQL Instance 
Password ‐ Enter a password for the account that meets the displayed criteria. Type the password again to verify. 
How to send alert emails ‐ The Veriato Server sends automatic email alerts and reports to "operators." Your above email address will be the first "operator." Read more about email service options. Press Next. to begin installing.
8.
Wait for the installation to complete. Wait as the product is installed and configured. Then, press Finish.
28 Deployment Guide Install for Use with Full SQL Instance Next steps
If the login prompt does not appear, use Windows to find and start the Veriato Management Console. 1. Log in using the account you just created. 2. Activate using your product key 3. Add Recorders to begin monitoring users. Deployment Guide 29 Install Management Console Only Install Management Console Only
Install a standalone Management Console AFTER you have installed the Veriato Server components. 1.
Welcome ‐ At the Welcome panel, click Next. 2.
End user license agreement ‐ Read the license agreement, press Agree, and Next. 30 Deployment Guide Install Management Console Only 3.
Disable antivirus and set exclusions ‐ Because antivirus can interfere with this installation, we recommend "excluding" Veriato files and disabling scanning during the Veriato installation. Press the blue buttons to learn more and get a list of files to exclude. Press Next. 4.
Options for installing ‐ Select "Install Management Console Only." Deployment Guide 31 Install Management Console Only 
Management Console Installation Path ‐ The folder where the application will be installed. Change the installation folder, if you wish, by clicking Change and browsing to a different folder or drive on this machine. 
Veriato Server address ‐ Enter the fully qualified domain name (FQDN) or an IP address (IPV4 or IPv6) of the device where your Veriato Server is located. An error appears if the device cannot be found. Examples of appropriate entries are: MYMACHINE.mydomain.local
192.162.0.55 
Veriato Server Port ‐ The Veriato Server communication port, by default 443. If the Veriato Server uses a custom port, change this entry to match. Press Next.
An error appears if the server address could not be found. Check your entry
and try again.
When the server is found, you see "Checking Space Requirements" as the
setup checks this computer for Management Console requirements.
5.
Wait for the installation to complete and click Finish. You exit the setup, and the Management Console login prompt appears. 6.
Log in to test the installation. 32 Deployment Guide Install Management Console Only You don't have to select the Veriato Server, since you just entered it. But if the
server can't be found when you're logging in, click the drop-down to select or type in
the server name.
Deployment Guide 33 Install the Database Separately Install the Database Separately
A Veriato installation serving many Recorder endpoints will need the ability to store rapidly accumulating data. Install the Veriato Database separately on a dedicated machine to be assured that data and data backups can be reasonably managed without the worry of running out of disk space due to other reasons. Before you begin

Create a SQL Server instance ‐ MS SQL Server Standard or Enterprise must be pre‐installed with an instance ready to receive the Veriato installation. This installation configures your SQL Server instance as a Veriato 9.0 database instance. 
Install the Veriato database first ‐ The database instance must be installed BEFORE installing the Veriato Server or Management Console components. 
Data is stored locally ‐ Veriato data and data backups are written to and read from the local database machine. Consider using multiple local hard drives to receive the data and store current data backups. Use your Windows/network tools to move backups, and enable Veriato Space Management to control disk space consumed by backups. 
Upgrades ‐ You can start with this procedure when upgrading a distributed Veriato installation, but it does NOT upgrade your existing database. Instead, create a NEW instance with a new name and then run the setup using "Install Database Only." After you have installed the Veriato Server, configured to communicate with this new instance, you will restore your latest 8.5 database backup to your new database instance. See Upgrading from 8.5 to 9.0. 
Install on hardware that meets requirements ‐ The database requires Windows 64‐bit, OS 8+ or higher, and we highly recommend server‐grade hardware and OS for enterprise installations. See Requirements for hardware, estimated disk space needs, and other prerequisites. A message appears if the system does not meet requirements. NOTE: Do NOT install Veriato server components on a machine that is also hosting a Domain
Server or an Exchange Server.
Start a database-only setup
1.
Start the setup at the SQL Server machine. Following purchase, go to www.veriato.com/support, enter your product key, and download and double‐click the VeriatoSetup file to start a database installation. 34 Deployment Guide Install the Database Separately 2.
Welcome At the Welcome panel, click Next. 3.
End user license agreement Read the license agreement, press Agree, and Next. 4.
Disable antivirus and set exclusions ‐ Because antivirus can interfere with this installation, we recommend using your antivirus solution to "exclude" Veriato files. Press the blue buttons to Deployment Guide 35 Install the Database Separately learn more and get a list of files to exclude. See Antivirus Exclusions Press Next. 5.
Options for installing ‐ Select "Install Database Only" to view the database install options. Options for Installing (database only)
The Options panel is where you connect to SQL Server and direct the setup how to configure the database instance. 
SQL Server Data Path ‐ Directory where SQL Server instance will store data. For example, C:\Program Files\Microsoft SQL Server\MSSQL13.VERIATO360\MSSQL\DATA (where VERIATO360 is the instance name). If you wish, select Change and navigate to a location on the current computer you want to use for Veriato data. 
SQL Instance Name ‐ Enter the name of the SQL Server instance you have created for Veriato (it may or may not be VERIATO360). The Management Console will connect to this SQL instance to access data. 36 Deployment Guide Install the Database Separately 
SQL Username ‐ The setup needs privileged access to configure the Veriato instance. Provide your "root" SQL Server username, usually "SA" (System Administrator). 
SQL Password ‐ Enter the password for the SQL Server account you named above. If the username/password is incorrect, an error appears when you click Next. 
SQL Server IP Port ‐ Normally SQL Server communicates at TCP/IP port 1433, but will dynamically select available ports for its named instances. If SQL Server will communicate on a fixed port for your Veriato instance, enter the port here. Do NOT enter a value here unless you are fully aware of your network infrastructure. Press Next to continue. Messages that follow may include: 
Database Files Found ‐ Are you sure you wish to continue and overwrite these files? There are existing files in the selected SQL Server Data Path. Click Yes to overwrite the files or No to choose a different Data Path. Be careful not to overwrite existing data unless you are ready to! 
Verifying SQL credentials... An error appears if credentials are incorrect or SQL Server cannot be accessed. Check the SQL Username, Password and Port you entered. Deployment Guide 37 Install the Database Separately 
Checking space requirements... A message appears if there is not enough free space for database configuration or data files. 
Checking Screenshots and Attachments path access... A message appears if there is not enough free space for file storage.. Wait for the installation to complete
Wait for the installation to begin and complete.Then, press Finish. Setup the Veriato Server
Install the Veriato Server and Management Console at another machine using Install with Options. You will point to this SQL Server machine and specify the configured Veriato SQL instance you just created. 38 Deployment Guide Creating the Master Login Account Creating the Master Login Account
The Master Login Account is the first account created for your Veriato database instance, and has full access and permissions to Veriato features, devices, and users. This will be the login you use the first time you open the Veriato Management Console. Email address
The email address identifies a point of contact for Veriato, can stand as the Master Login user name, and provides an initial email operator address to receive Recon, 360 Event, or System Health email alerts. If this is an evaluation, just provide your own email address. Use email as login name
Check this option if you prefer to use the email address to log in. Deselect this option to enter a unique SQL user name, separate from the email address. Remember the username and password you choose: you need them to login the first time! Password
Type a password for the new Master Login account. Verify the password by typing it again. The password must be at least 6 characters long and include THREE of the following criteria: Deployment Guide 39 Creating the Master Login Account 
An uppercase letter 
A lowercase letter 
A number 
A non‐alphabetic character, such as # ^ _ ‐ 
Do NOT use the characters: / | ' " [ ] { } ( ) , ; ? * ! @ $ \ or <space> Type the password again to verify it and continue. NOTE: Make sure this password meets any system security requirements for your own network.
Use Veriato secure email service
When installation is complete and you have installed Veriato Recorders, you'll want to begin receiving alert email immediately. The default choice is an email service provided by Veriato. This option requires no setup and guarantees you will receive the first email the Veriato Server sends. Email is simply relayed through the Veriato service to the target email address. Nothing is retained at the mail server, and no one at Veriato can see your email. Read the End User License Agreement for more information. It's easy to switch from this service to another SMTP service following installation. Simply open the Management Console, select Global Options on the top bar, and change the email service. Global Options NOTE: The email address you specify during installation is automatically added as an email operator
and is assigned to receive System Health notifications. Following installation, you can edit or delete
this operator and change assignment.
Use another SMTP email service
If you are familiar with mail servers and know which one you want to use, select "Use another SMTP email service." You will need to provide the host name and a valid account to access the service. A test option allows you to check your settings, and if successful, sends the Veriato Welcome Email to the address you provided.. 40 Deployment Guide Creating the Master Login Account 
Outgoing Server ‐ Name of the email server host you would like to use. 
Mail Login Account ‐ A valid user login to the email server host. 
Password ‐ The login account's password. 
Use SSL ‐ Use security, check only if the host uses SSL for SMTP outbound email. 
Port ‐ Change if this host does not use port 25 for outgoing email. 
Send Timeout (sec) ‐ Period of time to try sending email before timing out. 
Test ‐ Sends a test email to the email address you provided on the main Account panel using these settings. If the email is successfully delivered you see: It's easy to change the email delivery details following installation. Simply open the Management Console, select Global Options on the top bar and click Configure Alert Email Delivery. The Management Console form provides a few more options for refining mail delivery. Deployment Guide 41 Logging in Logging in
To access the login panel, find start Veriato Management Console in your Windows apps. If you just installed, the Management Console may automatically open. Use the account created on installation. 1.
Login in as ‐ Enter your Master Account name or email address. Your login account is set up either with a unique login name or your email address. 2.
Password ‐ Type the password for this account. 3.
Press Login. The Management Console opens. Activating Veriato Recon/360
After installing or upgrading Veriato Recon/360, you must activate it for use. You cannot deploy Recorders or receive data from deployed Recorders until you activate! 42 Deployment Guide Activating Veriato Recon/360 1. Find your Product Key in the purchase confirmation email from Veriato. 2. If this prompt is not displayed, select Configurations | Licenses and click the Activate Product button. 3. Copy the Product Key from your receipt email and paste it into the first field. 4. Click Activate Now. Wait as the product activates. What happens on activation
When you activate, your Veriato Recon/360installation contacts the Veriato licensing service, retrieves the licenses you have purchased, and downloads new Recorder versions. 
Licenses available appear in Configurations | Licenses. 
Recover versions appear in Configurations | Recorder Versions and become available for updates from Recorders. Activation may take several minutes. If a message appears because it's taking too long, wait a little longer activation may still be successful. If an error message appears, close all dialog boxes and try the activate link again. Contact Veriato if you continue to see errors. Deployment Guide 43 Configuring a New Install Configuring a New Install
The system works automatically for the most part. Some adjustments you should make following installation are: 
Antivirus exceptions. Some antivirus and malware scanning products detect and quarantine Veriato files. Not only does this prevent successful installation and disable network recording, it compromises stealth at your endpoints. Avoid the problem by setting "exclusions" in the antivirus for Veriato files before you deploy the Recorder. See Exclude the Recorder from Scanning. 
Data storage and space management. Database backups occur nightly, and full system backups are run every Sunday night. Automatic backups are stored on the database computer. To make sure backups don't use too much disk space, following installation, use System Management Data Retention in the Management Console to set up automatic management of backups and file storage. Always keep at least 2 system backup sets at a separate location, just in case. 
Enable alert operators. During the setup, you chose either Veriato Relay Mail Service or another SMTP Relay service to deliver alert email. The email address you entered on installation is automatically added as an email operator. Make sure someone who can respond receives the system health alert notification by providing that person's email address in System Management | Server Settings). You'll want to enable Recon and 360 Event alerts on user activity as soon as possible, too. 
Check ports. Make sure that the communication port between server and client (HTTPS 443) is not blocked or already used. 44 Deployment Guide Deploying the Recorder Adding a Test Recorder
If you have just installed the Veriato Server, your Management Console data views and lists are pretty empty. You'll need to Add Recorders to begin capturing and view user activity. It's with a few "test" devices to see how it works. NOTE: You won't add Android devices using this method. Instead, you will create a Manual Setup
file and install the Veriato Recorder app on each device.
1.
Select Recorders | Ungrouped. At first, the only Recorder group is "Ungrouped," which is always present and includes devices that don't belong to another group. If you have other groups, they are listed here. 2.
Select Deployment | Add Recorder from the top bar. The window flips around and the Add Devices wizard begins attempting to discover network devices. (You can flip back to the main group list by clicking the X in the upper left corner. ) If discovery isn't working or there are "Too many devices to list," try one of add options offered on the "Select" panel. a. For your test Recorder, select Add One. Deployment Guide 45 Adding a Test Recorder b. Type the name of the device in the first field. If you are on a domain, you'll have the most success entering a fully qualified domain name, such as: machine422.mydomain.local c. Enter the username and password for a network account. The account should be an administrator‐user on the device. If you are installing on your own device, this can be your own administrator‐user account. d. Press Add. If the account credentials can't be verified, an error appears. Press Try Again and
type the information again, or, if you wish try another Add option.
If the device and credentials could be verified, the device is added to the "Select
devices" list, and it is selected.
46 Deployment Guide Adding a Test Recorder If the device is listed as "Verified," there should be no problem with the Recorder
installation. If the device is off the network, or the if credentials aren't valid for this
device, "Unverified" appears. (You can still continue.) As gray the message states,
the same credentials will be used for any other devices you add now, so if different
credentials are needed for a second device, finish the wizard, and then select Add
Recorder again.
When one device in the list is selected, you can click Next at the bottom-right of the
panel.
3.
On the Prepare panel, schedule Recorder installation. The note reminds you that you've already supplied Administrator‐user credentials. If you were not using Add One, you'd have to supply credentials here. Click Next at the bottom‐right of the panel to continue. You can set the installation time for "Now" (as soon as possible) or schedule Deployment Guide 47 Adding a Test Recorder it for the future. The installation will restart the computer. 3. On the License panel, assign a license to the device. Only the license types you have purchased will appear. You can assign a Veriato 360 and a Veriato Recon to a device for both detailed recording and behavioral analysis. Click Next at the bottom‐right of the panel to continue. 48 Deployment Guide Adding a Test Recorder 4.
On the Summary panel, click Install. This panel shows your previous choices and allows you to go back and make corrections. Wait a few seconds as the deployment is prepared and sent. 5.
You then return to the "Ungrouped" Recorders list. Your test Recorder is listed as "Installing..." Notice that if you rollover the row, a dropdown button appears. Press the button at any time to display details about the device 6.
When the Recorder displays Install Complete, you know the Recorder was successfully installed. If there are errors, open the device details and follow instructions to make corrections or try installing again. Consult the Veriato Recon/360 Help for further explanations of Recorder Install errors.
Deployment Guide 49 Supplying Device Credentials Supplying Device Credentials
Computer Only. To deploy Recorder software installations from the Management Console, you need Administrator user permissions on the target devices. You don't have to be logged in as this account, but you do need to enter these credentials when you: 
Add One ‐ These credentials are verified for the target device. You cannot proceed in the Add Recorder wizard without valid credentials, and you won't be entering them in the Prepare step (the verified credentials will be used). 
Prepare ‐ Entered on the Prepare panel (when Add One was not used), credentials are accepted for use in installing the entire list of devices without verification at target devices. 
Update Recorder (Push) ‐ Credentials used to "push" a Recorder reinstallation are accepted without verification at the target device. NOTE: To learn about Active Directory credentials, see Active Directory.
Local vs. Domain credentials
If your network is not managed as a Windows domain, use local credentials. If you are on a domain, specify the target computer's domain with the user account. 
Local credentials ‐ Your Management Console computer must have Windows Network Discovery and File and Printer Sharing enabled. Enter just the user name, for example: jsmith, and the password. 
Domain credentials ‐ Your Management Console computer must be connected to the network with access to the target domain. Enter the fully qualified network user name, for example: MYDOMAIN\jsmith jsmith.mydomain.local Which account to use

Your own ‐ If you're testing or evaluating and want to install one or two Recorders on devices you manage, your own Administrator‐user account should work. 
Common administrator ‐ If your devices are networked (sharing some device or service) but not on a domain, you can add a user to the Administrator group at each computer, using exactly the same username and password. 
Domain administrator ‐ If you are on a domain network, you may be able to use an existing account with privileges the domain. 50 Deployment Guide Supplying Device Credentials 
Windows service account ‐ Some customers create a unique, network‐wide account that is a member of each computer's Administrators group and handled as a service account with a strong password. Verified vs. unverified
You won't be able to Add One without verifying. To verify, the server actually checks the credentials at the device you are entering. However, when credentials are simply accepted without verification (Prepare, Update Recorder), go ahead and schedule, assign licenses, and deploy the Recorder. Any devices not covered by the one set of credentials you provided will appear in the Recorders group list with a red status icon and Install Error: Invalid Credentials, or Insufficient Permission. Open the Recorder Details for the device, and you'll have the opportunity to type in credentials and try the installation again. NOTE: If you choose to "Remove" a device where a Recorder has never been successfully installed,
the license will be released. Once the Recorder is installed, only a floating license can be released.
Do I have to enter credentials each time?
The Management Console does not save privileged credentials ‐ for your security. You do have to enter credentials each time you deploy Recorder software. Deployment Guide 51 Using Active Directory to Add More Recorders Using Active Directory to Add More Recorders
A connection to Active Directory makes it easy to manage recording on your network. Use the Active Directory tools to browse the network, adding only devices you need to record. Base your selections on License Type. All devices in your Add Recorder selection list will be assigned the same license(s). Add recorders in separate batches to install Veriato Recon only, or Veriato 360 only. Accessing Active Directory
1.
Select Recorders and "Ungrouped" (or the group you wish to add to). 2.
From the top bar, select Deployment | Add Recorder. 3.
On the Select panel, click the Active Directory button. The Active Directory panel opens. If "Access Active Directory" is the only active tab, you must enter credentials. Most users with a network account on the domain should be able to view Active Directory, but your access depends on configuration at your site. If you have trouble, ask an IT administrator responsible for networks and domains about your access. 52 Deployment Guide Using Active Directory to Add More Recorders 4.
Type the name of domain to access. Type name of a domain network managed by AD. 5.
Enter Account Name. Type the user name for an account on the domain you entered that can access AD. 6.
Password ‐ Type the password for the account. 7.
Click Submit. If the account is verified, the other tabs are activated. If the account is not verified, you can try again. The previous credentials (if any) remain in place until a new credentials are verified. Discovery with verified credentials
Once credentials are verified, you can click the upper right X to exit the Active Directory panel. If there have been no selections, discovery begins. This time, all unrecorded network devices or users begin to appear in the list. If there are too many to list, a message appears, and you can click Active Directory again to browse for OUs or specific devices or users. Select devices from Active Directory
The first tab on the Active Directory panel allows you to select individual devices or users from AD organizational units. Deployment Guide 53 Using Active Directory to Add More Recorders NOTE: You can select more than 1,000 items, as many as you like, from the Active Directory
structure. However, for better organization, add items to different groups. If a group has more than
2,000 items, you will view it as Summary rather than a List, and it will be harder to get an individual's
status.
1.
Locate the AD area you are interested in. In the left "tree" view, expand organizational units by clicking the +. 2.
Find and click on devices/users you want to add. If you select a folder (OU), you automatically select all items within the folder. Selections are checked and highlighted, and a count is tracked on the right side of the panel. Click a selection again to clear it. 3.
Select [n] devices. You have two choices for adding selected devices or users. The first option simply adds items to the current Recorder or User Group when the wizard is finished. You can organize later, if necessary. 4.
Select [n] devices and add to group. The second option adds the devices or users to the group you select. Open the group drop‐
down list and select a group. All selected devices will be added to this group. 5.
If you wish, create a new group. Select New Group, and type a group name in the entry field, and press Enter. Once the group is 54 Deployment Guide Using Active Directory to Add More Recorders added, you can manage the members as you wish. 6.
Click Add Devices. The Active Directory pane closes, and the Select panel appears with all devices listed. If you selected a group, the group appears in the "Group" column. Any device that was already in a Recorders list will not appear. NOTE: When the wizard is finished, be sure to look for the added items within the appropriate
sidebar group!
Select Organizational Units
The second tab in the Active Directory pane lets you browse the current AD structure and select entire Organizational Units (OUs) to import. All selected OUs will be imported as Veriato Recorder Groups. If an OU has the same name as a Recorder Group, it will not be duplicated, but any new devices in the selection will be added to the group. Deployment Guide 55 Using Active Directory to Add More Recorders 1.
Locate the AD area you are interested in. In the left "tree" view, click the + to view OUs within OUs. In this view, individual devices or users are not shown. The number of items in an OU is shown in parentheses. 2.
Find and select the OUs where you want to add Recorders. Select a higher‐level OU to automatically select all of its sub‐ OUs and their devices or users. Selections are checked and highlighted. Numbers are tracked in options on the right side of the panel. Click a selections again to deselect. 3.
Select [n] organizational units ([n] devices) The right side of the panel offers one choice: to add the selected OUs and devices within them. 4.
Click Add Devices. The Active Directory pane closes, and the Select panel appears with all devices listed. The OU name appears in the "Group" column. NOTE: When wizard is finished, look for the added items within the appropriate sidebar group!
Imported OUs are NOT synced to Active Directory. You will have to add and remove devices or
users manually to keep the group the same as the Active Directory OU.
Check to select items and continue
Your Active Directory selections come in to the Select list as pre‐selected. Check the box next to "Devices" or "Users" at the top of the list to select ALL items or to deselect ALL items. You can return to the Active Directory panel as you like to add more items before pressing Next (for devices) or Add (for users). If you are adding devices, keep in mind that all devices added will receive the same license assignment. If you want Veriato Recon on some devices and Veriato 360 on others, you should add them in separate batches. 1.
On the Prepare panel, schedule Recorder installation and enter credentials to install the Recorder. 2.
On the License panel, assign a license to these devices. 3.
On the Summary panel, review your choices and click Install at the bottom of the panel. 4.
You return to the Recorders list, where devices show "Installing" or "Waiting to Install" status. If you imported devices into groups, look for the devices in their assigned sidebar groups. 56 Deployment Guide Using Active Directory to Add Users Using Active Directory to Add Users
A connection to Active Directory makes it easy to manage recording on your network. Use the Active Directory tools to browse the network, adding the users you need to monitor. Add users into groups that mirror Active Directory or suit your purposes for Veriato Recon/360 management. Accessing Active Directory
1.
Select Users and "Ungrouped" (or the group you wish to add to). 2.
From the top bar, select Deployment | Add Recorder. 3.
On the Select panel, click the Active Directory button. The Active Directory panel opens. If "Access Active Directory" is the only active tab, you must enter credentials. Most users with a network account on the domain should be able to view Active Directory, but your access depends on configuration at your site. If you have trouble, ask an IT administrator responsible for networks and domains about your access. Deployment Guide 57 Using Active Directory to Add Users 4.
Type the name of domain to access. Type name of a domain network managed by AD. 5.
Enter Account Name. Type the user name for an account on the domain you entered that can access AD. 6.
Password ‐ Type the password for the account. 7.
Click Submit. If the account is verified, the other tabs are activated. If the account is not verified, you can try again. The previous credentials (if any) remain in place until a new credentials are verified. Select users from Active Directory
The first tab on the Active Directory panel allows you to select individual users from AD organizational units. NOTE: For best organization, add no more than 1,000 users to a group.
1.
Locate the AD area you are interested in. In the left "tree" view, expand organizational units by clicking the +. 2.
Find and click on users you want to add. If you select a folder (OU), you automatically select all items within the folder. Selections are checked and highlighted, and a count is tracked on the right side of the panel. Click a selection again to clear it. 3.
Select users or Select users and add to group. You have two choices for adding selected users. The first option simply adds items to the current Recorder or User Group when the wizard is finished. You can organize later, if necessary. The second option adds the devices or users to the group you select. Open the group drop‐
down list and select a group. All selected users will be added to this group. 4. If you wish, create a new group. Select New Group to create a new group for these users. Type a group name in the entry field and press Enter. The New Name appears as the selected group, and will appear under Recorders in the sidebar as a group. Once the group is added, you can manage the members as you wish. Click Add Users. The Active Directory pane closes, and the Select panel appears with all users listed. If you selected 58 Deployment Guide Using Active Directory to Add Users a group, the group appears in the "Group" column. Any user that was already in a Recorders list will not appear. NOTE: When the wizard is finished, be sure to look for the added items within the appropriate
sidebar group!
Select Organizational Units
The second tab in the Active Directory pane lets you browse the current AD structure and select entire Organizational Units (OUs) to import. All selected OUs will be imported as Veriato Recorder Groups. If an OU has the same name as a Recorder Group, it will not be duplicated, but any new users in the selection will be added to the group. 1.
Locate the AD area you are interested in. In the left "tree" view, click the + to view OUs within OUs. In this view, individual users are not shown. The number of items in an OU is shown in parentheses. 2.
Find and select the OUs where you want to add Recorders. Select a higher‐level OU to automatically select all of its sub‐ OUs and their users. Selections are checked and highlighted. Numbers are tracked in options on the right side of the panel. Click a selections again to deselect. Deployment Guide 59 Using Active Directory to Add Users 3.
Select [n] organizational units ([n] devices/users) The right side of the panel offers one choice: to add the selected OUs and users within them. 4.
Click Add Users. The Active Directory pane closes, and the Select panel appears with all users listed. The OU name appears in the "Group" column. NOTE: When wizard is finished, look for the added items within the appropriate sidebar group!
Imported OUs are NOT synced to Active Directory. You will have to add and remove users manually
to keep the group the same as the Active Directory OU.
Check to select items and continue
Your Active Directory selections come in to the Select list as pre‐selected. Check the box next to "Users" at the top of the list to select ALL items or to deselect ALL items. You can return to the Active Directory panel as you like to add more items before pressing Add. When you press Add, you return to the Users list where you should see added user names. If you imported users into groups, look for them in their assigned sidebar groups. 60 Deployment Guide Deploying to Android Deploying to Android
Deploy the Veriato Android Recorder by installing an app directly on the mobile device. In addition to a Recorder, you will install Chromium to provide a mobile web browser that allows Veriato monitoring. The basic steps are: Create a manual setup file
Start at your computer. 1.
In the Veriato Management Console, go to Recorders and open a group, such as Ungrouped. 2.
From the top bar, select Deployment | Create Manual Setup. 3.
In the Create a Setup File panel, select Android and the Veriato 360 license type. 4.
Select the group you want the Android devices to appear in. (You will be able to move devices to other groups once they appear in the group list.) 5.
If you want to change the Recording Policy or Recorder Version, select Change Android Configuration. 6.
Otherwise, click Create File. 7.
Save the VeriatoAndroid setup package to your computer. Set the device to allow apps from unknown sources
Now prepare the device. You will see an "Install blocked" message when you attempt to install the Recorder if you don't complete this step. 1.
Navigate to the phone's Settings area and find Security. Look for it under a section called "Device Administration." 2.
Enable installation from Unknown sources. Choose to trust both trusted and unknown sources. 3.
Connect the device to your computer via USB. The device should appear in the computer's file management. Deployment Guide 61 Deploying to Android Copy setup files to the device
Use your computer for these steps. 1.
Unzip (extract) the VeriatoAndroid setup folder where you saved it. Copy the 3 unzipped files. 2.
Navigate to the mobile device's Download directory. Paste (or drag) the files to the directory. Install the Veriato Recorder
Use the mobile device to install apps. 1.
From the device, navigate to the Download directory and tap the Veriato.apk file. The installation process begins. Accept all prompts along the way. 62 Deployment Guide Deploying to Android 2.
When prompted to "activate device administrator," tap ACTIVATE. Deployment Guide 63 Deploying to Android Install Chromium
1.
Tap the Chromium.apk file. Accept all prompts along the way. 64 Deployment Guide Deploying to Android 2.
The Chrome browser opens at the end of the installation. 3.
The Android device is now fully set up. In a few minutes, the device appears in the Recorders group that you selected for this manual setup. Uninstall the Veriato Recorder
1.
Navigate to the phone's Settings. 2.
Find the Security area within the settings application. 3.
Locate the Device Administrators area. This is sometimes found under "Other security settings." 4.
Disable the Veriato Administrator. 5.
Return to the settings home page and navigate to the Applications area. 1. Locate the Veriato application and enter its settings. 2. Select Uninstall and Confirm. Deployment Guide 65 Deploying in a Windows Workgroup Deploying in a Windows Workgroup
Veriato Recon/360 supports workgroup networks
You can configure a Windows Workgroup for Veriato Recon/360management. Make sure every computer you wish to monitor is on the same Workgroup as the Veriato Recon/360server. 
Define common Administrator credentials. To properly manage workgroup devices, you need access to a Local Administrator account. You can add the SAME Administrator User Account (same user name, same password) to each computer you want to record. Be sure to check each device's network and local security policy settings, as described below. 
Use the common Administrator credentials as needed. You may need the credentials for workgroup computers to Update/Reinstall or for troubleshooting at the device. 
Install the Recorder manually. If you don't have success deploying from the Management Console, build a manual setup file and run it at each device. NOTE: It does NOT matter which user is logged on to the network computer as long as the account
as described above exists in the local Administrators group on the computer.
Set up a common Local Administrator account
At each computer: 1.
From the computer's Control Panel go to Local Users and Groups. 2.
Create a New User. Refer to Windows help on creating administrator users. 3.
Carefully note the user name and password. You will create the exact, same account on other computers. 4.
Give the account Administrator Group membership. 5.
Save the account. 66 Deployment Guide Deploying in a Windows Workgroup Make sure each computer belongs to the workgroup
1.
While at each computer, use Windows Control Panel | System to view the current workgroup settings. If necessary, change settings so that each computer is a member of the same workgroup. 2.
If necessary, change the computer's local security policy to allow user authentication. This may or may not be a problem. The steps may be: Control Panel |Administrative Tools | Local Security Policy | Local Policies | Security
Options | Network access: Sharing and security for local accounts. Enable this setting for local security: “Classic – local users authenticate as themselves” 3.
Make sure File and Printer Sharing is enabled. 4.
Make sure C$ Administrative Share is enabled. Install the Recorder manually
If you are unable to deploy from the Management Console, create an executable Manual Setup file and launch the file at each computer. Follow instructions in Installing Manually. When the computer restarts, it becomes visible in the Management Console Recorders | Ungrouped list. Once the Recorder is installed, you can change the Recon/360 license capability, the Recording Policy and otherwise manage it from the Management Console. Deployment Guide 67 Deploying to a Session Host Deploying to a Session Host
Record the server
To record users who log into sessions hosted by Citrix or Microsoft Terminal Services, you must install a Recorder client on the Citrix or Terminal server. Special "shared" licensing will be required (see SHD Licensing). All recorded activity will be stored by user. In addition, Veriato Recon/360provides several recording options that ensure each user logging into the host server is monitored as expected. As long as users log onto the server using their own accounts, Veriato Recon/360records as usual, capturing and displaying activity by user. However, if users log in using a common account, you will not be able to manage recording or view data in the Management Console by user, as expected. Make sure login accounts are properly assigned and used. Record workstations, if necessary
If users also launch browsers or applications installed locally on their workstations (not hosted), you will need a Recorder installed on each workstation, too, for complete coverage. For example, web surfing from the local Internet Explorer will not be captured by a Recorder on the server. Depending on your network, use the Management Console to deploy to all computers remotely, or create a Manual Setup file to execute at each computer. Recorded workstations use regular licenses and behave as any other Veriato Recon/360client (you will NOT use Manage Users). NOTE: A Recorder installed on the Citrix or Terminal server is NOT able to record applications
installed and running on the local workstation.
Records full desktop and published apps
A Recorder will capture sessions directly from a Terminal Server (Microsoft Remote Desktop) or Citrix server where either “Full Desktop” or "Published Applications" are used. No special options are needed to capture activity when Full Desktop is used. When published applications are used: 
The Client Options setting “Alternative Shell” is required. 
The advanced “Session Linger Timeout” setting may capture data at the close of a session that would otherwise be lost. NOTE: If you use Citrix VDI or another virtual desktop environment, see Recording Virtual Machines.
68 Deployment Guide Deploying to a Session Host Steps for installing
Because Recorder installation restarts the device, be sure to deploy the Recorder when users are not logged in. 1.
Create a Recording policy with the settings required to capture and retain activity if published applications are used. 2.
Use either the Add Recorder wizard from the Veriato Recon/360or a Manual Setup file to install the Recorder on the server. 3.
When you are prompted to select a license, assign the Recorder one or both license types, depending on your purchase. 4.
The Recorder detects the target device as a session host and warns that an SHD license is required. If the appropriate license is purchased and assigned, click OK to continue. If you need to purchase a license, contact Veriato. 5.
The Recorder installation completes, and the hosting server restarts. 6.
The Recorder begins capturing activity of any user who logs in to a published application or desktop. View and manage recorded data
All recorded data is stored by user name in the Database. Use the Management Console to view data. 
The Recorder records each activity under the login name of the user who performed the activity. This means the Recorder will capture email, web sites visited, keystrokes, and all other activities for DOMAIN\SALLY, DOMAIN\PETER and DOMAIN\JIM as they use the terminal services, even when activity occurs simultaneously. 
The data recorded and stored is accessible for viewing by user and by other Management Console criteria. 
Keep an eye on performance and usage. The more users who connect and are recorded, the more difficult it becomes for the Recorder to take Screen Snapshots for each user every 30 seconds. Use Recorder Profile settings to reduce frequency of (or disable) Screen Snapshots, or consider disabling other activity recording. Deployment Guide 69 Deploying with SCCM Deploying with SCCM
Create a manual setup file
Veriato 360 allows you to create an executable Recorder install file that can be deployed to any number of computers with the same OS platform. The file includes the recording profile and version you select, but does NOT include a license assignment. 1.
Create a Manual Setup File (.exe) in the Veriato Management Console . 2.
Copy the Manual Setup File (for example, 360Manual.exe) to a network shared folder accessible by both the deployment server and the client devices. IMPORTANT: As you prepare to deploy, be careful to select the intended group, as it is possible to
deploy to your entire network. Schedule a time when users are not likely to be at their computer.
Add the client to SCCM for deployment
An experienced administrator can deploy a Veriato Recon/360Manual Setup executable file from SCCM as a custom application package using the following settings within SCCM. 1.
Open the Configuration Manager Console. 2.
On the lower left, navigate to Software Library. 3.
Under Software Library, expand Application Management | Select Applications. 4.
Select Create Application in the upper left corner. The Create Application Wizard opens. 5.
On the General panel, select "Manually specify the application information" and click Next. 70 Deployment Guide Deploying with SCCM 6.
General Information: Type in a unique Name, the Publisher, the Software Version, and the Date published. No other fields are required. Click Next. Deployment Guide 71 Deploying with SCCM 7.
Application Catalog: Enter a unique Localized application name, such as "360 Client," and click Next. 8.
Deployment Types: Select Add. This opens the Create Deployment Type Wizard. 72 Deployment Guide Deploying with SCCM 9.
In the Deployment Type Wizard's General panel, open the Type list and select Script Installer. Select "Manually specify the deployment type information" and click Next. 10.
Enter a unique Name for the new deployment, such as "360 Installation." Click Next. 11.
On the Content panel: Deployment Guide 73 Deploying with SCCM 
Next to Content Location, enter the Network Shared folder path to the manual setup file. 
Select "Allow Client to share content with other client on the same subnet." 
Next Installation program, use Browse to navigate to and select the manual setup file you wish to deploy. Click Next. 12.
The Detection Rule dialog box opens. 
For Setting Type, select File System. 
For Type, select File. 
For Path, enter the path for the Recorder's installation folder. The default location is "C:\Windows\Winipbin." 
For File or folder name, enter the name of a file or folder that will reside in the installation ("Wzodlg.dll" is an example). 
Select the "The file system must exist on the target system to indicate presence of this application" radio button. 
74 Click OK and Select Next. Deployment Guide Deploying with SCCM 13.
Detection Method: Click the Add Clause button and add the presence indicator created in the above steps. Click Next. 14.
User Experience: 
For Installation Behavior, select Install for System from the dropdown menu. Deployment Guide 75 Deploying with SCCM 
For Logon Requirement, select Only when a user is logged on from the dropdown menu. 
For Installation program visibility, select Normal from the dropdown menu. 
Select the "Allow users to interact with the program installation" checkbox. 
For Maximum allowed run time (minutes), select 120 minutes. 
For Estimated installation time (minutes), select 0 minutes. Select Next. 15.
Requirements: Nothing to enter here. Click Next. 16.
Dependencies: Nothing to enter here. Click Next. 76 Deployment Guide Deploying with SCCM 17.
Summary: Verify all settings and click Next. 18.
Completion: The Deployment Type wizard is complete. Click Close. 19.
You return to the Create Application Wizard, where your 360 installation is listed. There are no further settings to add. Click Next. Deployment Guide 77 Deploying with SCCM 20.
Summary: Check your settings and click Next. 21.
Completeion: Click Close. Schedule and deploy via SCCM
1.
Navigate to Assets and Compliance in the Lower left corner and to Device Collections in the tree hierarchy on the left. 2.
Right‐click the device group you wish to deploy to and select, Deploy | Application. The Deploy Software Wizard opens. 78 Deployment Guide Deploying with SCCM 3.
General: Next to Software, use the Browse button and find and select your Manual Setup (for this example, "360 Client" as in step 6 above). Click Next. 4.
Content: Specify the content destination by clicking the Add drop‐down and selecting Distribution Point. In the Add Distribution Points pop‐up window that appears, select your SCCM deployment server and click OK. It appears in the list. Click Next. Deployment Guide 79 Deploying with SCCM 5.
Deployment Settings: Use the drop‐down menus to set Action to Install and Purpose to Required. Click Next. 6.
Scheduling: Configure a time for the client Recorder to be deployed. Check "Schedule the application the be available at" and select a date and time. 80 Deployment Guide Deploying with SCCM For the installation deadline, select "As soon as possible after the available time." 7.
User Experience: For User notifications, select "Hide in Software Center and all notifications." Check "Software Installation" and "System Restart (If required to complete the installation)." Select Next. Deployment Guide 81 Deploying with SCCM 8.
Alerts: Nothing is required. Click Next. 9.
Summary: Verify all settings and click Next. 10.
Completion: The installation is ready to go at the scheduled time. Click Close. 82 Deployment Guide Troubleshooting Exclude the Server from Scanning
Veriato server exclusions
Exclude the server files at the computer BEFORE installing server components. If you wish, you can disable antivirus before installing, and then exclude Veriato files before re‐enabling antivirus scanning. Set server exclusions in antivirus software
Open the antivirus or anti‐spyware control panel and look for an option that allows you to exclude specific files from scanning. If the antivirus solution allows excluding entire folders, we recommend excluding the entire *\Veriato\* folder from scans. However, this may not be possible, and you may need to exclude each installed file. 
If you can, exclude entire folders from scans. 
If you can, simply copy and paste the file paths below into your antivirus software's exception or exclusion list. You will have to adjust the paths for your particular system folder and Veriato Recon/360program location. 
Computers where a standalone Management Console is installed should not be affected. 
See Antivirus Help for articles on excluding Veriato Recon/360from antivirus scans in McAfee, Symantec, and other popular programs. IMPORTANT: If you are upgrading from version 8.5, all files below must be added as exceptions. If
you are not uninstalling version 8.5, keep your old exceptions.
MS SQL Server
The folder below shows the default path for an instance set up as "VERIATO360" (default instance created when installing with SQL Server Express). Your instance may have a different name and location. The files will be the same with the instance name replacing "VERIATO360" below. C:\Program Files\Microsoft SQL Server\MSSQL13.VERIATO360\MSSQL\DATA FileManipDriver.exe
FileManipCommon.dll
DataExporter.dll
Deployment Guide 83 Exclude the Server from Scanning Veriato360.Database.Logging.dll
Veriato360.Database.SqlAgentInterface.dll
Veriato360.Database.SQLCLR.dll
Veriato360.Database.WinService.dll
Veriato\Deployment Manager
C:\Program Files\Veriato\Deployment Manager Veriato360.Communication.dll
Veriato360.Composition.SimpleInjector.dll
Veriato360.Configuration.dll
Veriato360.Configuration.Models.dll
Veriato360.Configuration.Repository.dll
Veriato360.Cryptography.dll
Veriato360.Deployment.dll
Veriato360.Deployment.Manager.exe
Veriato360.Deployment.Models.dll
Veriato360.Deployment.Repository.dll
Veriato360.dll
Veriato360.Inventory.dll
Veriato\Deployment
C:\Program Files\Veriato\Deployment Veriato360.Communication.dll
Veriato360.Communication.Repository.dll
Veriato360.Composition.dll
Veriato360.Composition.Serialization.dll
Veriato360.Composition.SimpleInjector.dll
Veriato360.Configuration.dll
Veriato360.Configuration.Models.dll
Veriato360.Configuration.Repository.dll
Veriato360.Cryptography.dll
Veriato360.Deployment.Dispatcher.exe
Veriato360.Deployment.Dispatcher.exe.config
Veriato360.Deployment.dll
Veriato360.Deployment.Mac.dll
Veriato360.Deployment.Models.dll
Veriato360.Deployment.Uninstall.dll
Veriato360.Deployment.Upgrade.dll
Veriato360.Deployment.Windows.dll
Veriato360.dll
Veriato360.Inventory.dll
84 Deployment Guide Exclude the Server from Scanning Veriato360.Inventory.Models.dll
Veriato360.Inventory.Repository.dll
Veriato\ExchangeRecorder
Files for future functionality. C:\Program Files\Veriato\ExchangeRecorder ExchangeRecorder.Configuration.dll
ExchangeRecorder.exe
ExchangeRecorder.exe.config
ExchangeRecorder.Interfaces.dll
ExchangeRecorder.Models.dll
ExchangeRecorder.Repository.dll
ExchangeRecorder.Session.dll
ExchangeRecorder.Utility.dll
Veriato\Notification Services
C:\Program Files\Veriato\Notification Services Veriato360.Communication.dll
Veriato360.Composition.dll
Veriato360.Composition.SimpleInjector.dll
Veriato360.Configuration.dll
Veriato360.dll
Veriato360.Inventory.dll
Veriato360.Notification.Services.exe
Veriato360.Notification.Services.exe.config
Veriato\Scheduler
C:\Program Files\Veriato\Scheduler SpectorSoft.Spector360.Data.dll
SpectorSoft.Spector360.Logging.dll
SpectorSoft.Spector360.Report.dll
Deployment Guide 85 Exclude the Server from Scanning SpectorSoft.Spector360.Types.dll
Veriato360.Communication.dll
Veriato360.Composition.dll
Veriato360.Composition.Serialization.dll
Veriato360.Configuration.dll
Veriato360.dll
Veriato360.Licensing.Models.dll
Veriato360.Scheduling.SchedulerService.exe
Veriato360.Scheduling.SchedulerService.exe.config
Veriato360.VPNProvider.dll
Veriato360.Web.Controllers.dll
VeriatoVPNDataCollector.exe
VeriatoVPNDataCollector.exe.config
AlertProcessor.dll
ReportGenerator.exe
ReportGenerator.exe.config
EmailHandler.dll
Veriato\Service
C:\Program Files\Veriato\Service Veriato360.Alerting.dll
Veriato360.Alerting.Managers.dll
Veriato360.Alerting.Models.dll
Veriato360.Alerting.Repository.dll
Veriato360.Communication.dll
Veriato360.Communication.Models.dll
Veriato360.Communication.Repository.dll
service.log
Veriato\SignalR
C:\Program Files\Veriato\SignalR 86 Deployment Guide Exclude the Server from Scanning application.log
AuthenticationManager.dll
Logger.dll
Veriato\Tools\ImportUtility
C:\Program Files\Veriato\Tools\ImportUtility Migration.exe
Restore.exe
Veriato360.Communication.dll
Veriato360.Configuration
Veriato360
Veriato360.ImportUtility
Veriato\WebUIDataService
C:\Program Files\Veriato\WebUIDataService 360DataServiceGenerator.exe
ADProvider.dll
Communication.dll
DataAccess.dll
DatabaseSettingsRepository.dll
DataContract.dll
DBBase.dll
DeviceDataMediator.dll
DomainEntities.dll
LoginAccountRepository.dll
ParallelExtensionsExtras.dll
Veriato360.Alerting.dll
Veriato360.Alerting.Models.dll
Veriato360.Communication.dll
Veriato360.Communication.Models.dll
Deployment Guide 87 Exclude the Server from Scanning Veriato360.Composition.dll
Veriato360.Composition.Serialization.dll
Veriato360.Composition.SimpleInjector.dll
Veriato360.Configuration.dll
Veriato360.Configuration.Models.dll
Veriato360.Cryptography.dll
Veriato360.Deployment.dll
Veriato360.Deployment.Models.dll
Veriato360.dll
Veriato360.Inventory.dll
Veriato360.Inventory.Models.dll
Veriato360.Inventory.Windows.dll
Veriato360.Licensing.Models.dll
WebUIDataService.BusinessLogic.dll
WebUIDataService.dll
webuidataservice.log
WebUIDataServiceHost.exe
WebUIDataServiceHost.exe.config
WebUIInterfaces.dll
Veriato\Management Console
C:\Program Files (x86)\Veriato\Management Console 360Admin.chm
Auditing.dll
AxInterop.SHDocVw.dll
AxInterop.SnapshotCtlLib.dll
BehaviorAnalysisInterfaces.dll
BESData.dll
CEAdminExt.dll
CEClientSettings.dll
CNECommDLL.dll
CommonSettings.dll
Communication.dll
88 Deployment Guide Exclude the Server from Scanning Configuration.dll
ControlCenter.WindowsResources.dll
ControlCenterAppLog.xml
CWrap.dll
DatabaseSettingsRepository.dll
DataContract.dll
DataMediator.dll
debug.log
FileManipCommon.dll
home.html
icudtl.dat
Interop.SHDocVw.dll
Interop.SnapshotCtlLib.dll
LoginAccountManager.dll
LoginAccountRepository.dll
ManagementConsole.exe
ManagementConsole.exe.config
ManagementConsole.ico
ManagementConsole.XmlSerializers.dll
ProfileData.dll
Read360.htm
ReportGenerator.exe
SnapshotCtl.dll
snapshot_blob.bin
Spector.Crypto.dll
Spector360DataObjects.dll
SpectorDashboard.exe
SpectorLogging.dll
SpectorMarker.dll
SpectorSoft.ActiveDirectory.WebService.DTO.dll
SpectorSoft.BehaviorGroup.WebService.DTO.dll
SpectorSoft.Enterprise.Diagnostics.dll
SpectorSoft.NetUtil.dll
SpectorSoft.Policy.WebService.DTO.dll
SpectorSoft.Spector360.CommonForms.dll
Deployment Guide 89 Exclude the Recorder from Scanning SpectorSoft.Spector360.ControlCenter.Bridge.dll
SpectorSoft.Spector360.ControlCenter.DataAccess.dll
SpectorSoft.Spector360.ControlCenter.Settings.dll
SpectorSoft.Spector360.ControlCenterControls.dll
SpectorSoft.Spector360.CustomControls.dll
SpectorSoft.Spector360.Data.dll
SpectorSoft.Spector360.Logging.dll
SpectorSoft.Spector360.Notifications.dll
SpectorSoft.Spector360.Report.dll
SpectorSoft.Spector360.SQLBase.dll
SpectorSoft.Spector360.Types.dll
Spectorsoft.WebServices.CommonBase.dll
Spectorsoft.WebServices.DataTransfer.dll
SpectorSoft.WmiUtil.dll
SpectorWebServiceProxy.dll
SpectorWorkflowServiceInterfaces.dll
TaskScheduler.dll
Veriato360.Communication.dll
Veriato360.Composition.dll
Veriato360.Composition.Serialization.dll
Veriato360.Composition.SimpleInjector.dll
Veriato360.Configuration.dll
Veriato360.Configuration.Models.dll
Veriato360.Cryptography.dll
Veriato360.dll
Veriato360.Inventory.dll
Veriato360.Inventory.Models.dll
Veriato360.Licensing.Models.dll
WebService.Device.DTO.dll
WelcomePage
widevinecdmadapter.dll
Exclude the Recorder from Scanning
90 Deployment Guide Exclude the Recorder from Scanning Veriato recorder exclusions
Antivirus and anti‐spyware software can cause problems for the Recorder at Windows clients. To be sure the antivirus software will not quarantine or display warnings, set file and folder exclusions within the antivirus software BEFORE deploying the Recorder to Windows clients. If you use an endpoint antivirus solution, set the exclusions to apply across the network. NOTE: For a list of the Veriato Recon/360Server files to exclude, click here. For instructions on
setting exceptions in McAfee, Symantec, and other popular antivirus programs, refer to Antivirus
Help.
Check policies for custom settings
Normally, the Recorder software (for Windows OS) is installed in a single folder using fixed filenames. The files are hidden in a folder named winipbin. However, for greater security, the name of this folder can be changed (prior to Recorder installation) in the Recorder Policy. Look for these settings in General Options | Client Options of a Windows Recording Policy. 
Use Fixed Filenames If this option is checked (default), use the exclusion list as shown below. If you have unchecked this option and are NOT using fixed filenames, exclude the entire winipbin folder. 
Use Custom Binary Subdirectory The default folder is winipbin. If you are not using a custom folder, enter the exclusion list as shown below. If you have checked "Custom Binary Subdirectory" and specified another name in any policy, repeat the winipbin file paths below, replacing "winipbin" with your folder name. NOTE: Be sure to exclude the *.1 files as directed.
Wildcards or browsing to files

Use wildcards in the exclusion path or filename ‐ Files listed below containing ????? (question marks) listed below indicate the Recorder version number. Use the ? (question mark) or * (asterisk) wildcard if possible, since the version will change in the future. 
Users\*\ folder ‐ The Users\"user"\ folder will be the domain account assigned as installation credentials. On a manual install, it may be the user's admin account (e.g., Users\Bill\AppData\). If wildcards are accepted in antivirus exclusions, you can enter Users\*\ for the user folder, as shown below. Deployment Guide 91 Exclude the Recorder from Scanning 
If wildcards are not allowed ‐ If your antivirus software does not accept wildcards in exclusions, temporarily exclude the entire folder (e.g., C:\Windows\TEMP) or specify the version number as indicated in the Management Console (e.g., spsetup30679.exe). 
If you must browse to files ‐ If the antivirus software requires you to browse to and select each file (such as Windows Defender), the temporary installation files will NOT be available. You'll need to completely disable antivirus scanning during Recorder installation. Following installation, select and exclude the installed files BEFORE re‐enabling antivirus scanning. Manual installation
If you are using a Manual Setup file to install the Recorder, add an exclusion for the location from which you run the file and the name of the executable file that you have created (such as, spsetupMAN_*.exe or MyInstallFile.exe). Note: The file path to the system folder (shown as C:\Windows below) varies, depending on the
computer.
Temporary setup files
Temporary files and folders are created as the Recorder is installed. These are removed after the computer has restarted and the Recorder is fully installed. To prevent antivirus warnings and quarantines during deployment and upgrades, specify exclusions for these files BEFORE installing the Recorder. 
Use wildcards for Recorder versions ‐ Files with appended version numbers are shown with ????? (question marks) below. The filenames will change. 
Users\*\ folder ‐ The asterisk here replaces a user account name (e.g., Users\jsmith\AppData\Local. When the Recorder is deployed from the Management Console, the "user account" will be the account credentials used in the Add Wizard. When the Recorder is deployed by Manual Setup file, the user will probably be the local, active administrator account. If wildcards are accepted in antivirus exclusions, enter Users\*\ for the user folder, as shown below. 
If wildcards are not allowed ‐ If your antivirus software does not accept wildcards in exclusions, temporarily exclude the entire folder (e.g., C:\Windows\TEMP) or specify the version number as indicated in the Control Center (e.g., spsetup30679.exe). 
If you must browse to files ‐ If the antivirus software requires you to browse to and select each file (such as Windows Defender), the temporary installation files will NOT be available. You'll 92 Deployment Guide Exclude the Recorder from Scanning need to completely disable antivirus scanning during Recorder installation. Following installation, select and exclude the installed files BEFORE re‐enabling antivirus scanning. Exclude temporary files with wildcards Below are the temporary files during installation: C:\Users\*\AppData\Local\Notifier.exe
C:\Windows\admin.exe
C:\Windows\InstallerService.exe
C:\Windows\Preinstaller.exe
C:\Windows\spsetup.exe
C:\Windows\spsetup64.exe
Installed Recorder files
C:\Windows\SysWOW64\winipdat\ kyqdhy.db
queue.db
sessions.db
winipdat.log
C:\Windows\winipbin bissimo.dll
cmproxfr.dll
eanipw.dll
mossimo.dll
mrstch.exe
msnwcfg.ini
mxcrsc32.exe
ntbsvr.dll
quasima.dll
quasimo.dll
rcxaemap.dll
svrltmgr.dll
Deployment Guide 93 Exclude the Recorder from Scanning svrltmgr64.dll
svrltwp.dll
svrltwp64.dll
vdorctrl.dll
vdorctrl.sys
wzodlg32.dll
The files below are the same as the above with ".1" appended. These are temporary files marked for deletion during an upgrade. C:\Windows\winipbin: bissimo.dll.1
cmproxfr.dll.1
eanipw.dll.1
mossimo.dll.1
mrstch.exe.1
mxcrsc32.exe.1
ntbsvr.dll.1
quasima.dll.1
quasimo.dll.1
rcxaemap.dll.1
svrltmgr.dll.1
svrltmgr64.dll.1
svrltwp.dll.1
svrltwp64.dll.1
vdorctrl.dll.1
vdorctrl.sys.1
wzodlg32.dll.1
94 Deployment Guide Check antivirus settings Recorder Errors Check antivirus settings
Antivirus software may be interfering with the Recorder installation and operation. Verify that all files for the current Recorder are excluded in the antivirus software. Explanation
Some antivirus and anti‐spyware programs will look for and attempt to remove Veriato files on a computer. Files may be removed during or after Veriato Recon/360installation. To keep all components running properly, exclude Veriato Recon/360server files from scanning. If you use enterprise or endpoint antivirus software, make exclusions at the antivirus server to apply across the network. If antivirus programs are installed locally, make exclusions the server computer. Exclude files
If possible, set exceptions for the Veriato Recon/360server folders or files. Open the antivirus or anti‐
spyware control panel, and look for the option that allows you to exclude specific files from scanning. Exclude Client Recorder files before deploying to Windows computers Option - Re-install after excluding the files
Once exclusions are in place, antivirus should no longer be a problem. When you are ready, schedule installation right from the device error message. If the problem was fixed, deployment should be successful. Option – Remove the device
If you couldn't solve the problem or if the device was improperly specified, remove the device. This cancels or removes the Recorder installation, and you may be able to "Add" the device again later. Deployment Guide 95 Administrative Share Access Administrative Share Access
It appears that administrative share access has been disabled in the Windows OS settings at this device. Remote installation requires that your install credentials have C$ or “C” drive share privileges at the computer. Explanation
To install the Recorder from the Management Console, the credentials you supply during Add Recorders wizard must have access to the administrative share. You may need to enable sharing at the target Windows computer. If the target computer has C$ or Admin$ share disabled, or if you don't use proper credentials, the device will deny Recorder installation. Note that for Windows 10 machines, credentials must be able to bypass User Account Control (UAC), which would restrict access to the administrative share. If you get this message, you can check the device, attempt to enable adminstrative share access, and then re‐schedule installation. Test for access
1.
Select Start | Run or Select Start | Search programs or files 2.
In the Run or Search programs and files entry box, type: \\computername\C$ where computername is the name of the computer not detected.
3.
Press OK or Enter. 4.
A message appears: An error message, such as "Network Path Not Found," or "Windows cannot access \\computername\C$," means he computer name may be incorrect, the computer is off, the computer is not connected to the network, or the computer is not on a domain that you can access. Check the network status of the device. If the device comes back online, you can simply re‐schedule installation from this message. A security message, such as an "Enter network credentials" prompt or an "Access Denied" message, means the credentials you supplied during the Add Recorder wizard do not have administrator privileges at this computer. Using different credentials to add the Recorder may 96 Deployment Guide Administrative Share Access solve the problem, or you can enable adminstrative share at the device and re‐schedule installation from this message. Option - Enable administrative share
The procedure to configure administrative C$ share or its equivalent varies, depending on the Windows OS version. 1.
Open the file explorer, navigate to the top level This Computer or This PC view. 2.
Right‐click the C drive and select Properties. 3.
In the Properties box, first select the Security tab, select the Administrators user group, and verify that Administrators have "full control" of the computer. 4.
Then, in the Properties box, select the Sharing tab and click Advanced Sharing. 5.
In the Advanced Sharing dialog, select "Share this folder," provide a share name, and give access to the account you are using to Add Recorders. Option - Install the Recorder manually at the computer
You can create a Manual Setup file to deliver to and run at the computer. You will still need Administrator‐user access to run the setup, but sharing is not required. See Manual Setup. Option - Remove device
Select this option to cancel the installation request and remove the device from the Recorders group. If a Recorder was NEVER installed on this device, the assigned license will be released. You can always use Add Recorder to add it later. Deployment Guide 97 Disk Space or System Requirements Disk Space or System Requirements
The device does not have a supported operating system or does not have enough free disk space to install the Recorder. Requirements for Windows client

Windows 7, 8, 10, Windows Server 2008+ 
1.5 GB free disk space 
Administrator‐user access to install the software 
File and Printer Sharing Enabled 
9.0.* Recorder Version software Option - Correct the problem and schedule installation
Update the device OS, free up disk space, replace the main hard drive with a larger one, or take this device off the network and replace it. The replacement device must have exactly the same network name (device.domain). You can then re‐schedule installation from the status message in the Recorders list. Option - Remove device
Select this option to cancel the installation request and remove the device from the Recorders group. If a Recorder was NEVER installed on this device, the assigned license will be released. You can always use Add Recorder to add it later. 98 Deployment Guide Enable File and Printer Sharing Enable File and Printer Sharing
File and printer sharing is not enabled at the device. Explanation
Remote deployment on Windows relies on File and Printer Sharing to remotely manage computers. File and Printer Sharing is a software component installed and enabled for each network connection on your network devices. It allows other computers on your network (the Veriato Server) to access the resources of the network computer (the endpoint). File and Printer Sharing must be enabled at the endpoint for the Management Console to retrieve status information and deliver remote Recorder installations to the network computers. Option - Enable file and printer sharing at the device
This procedure varies depending on the Windows operating system. 1.
Open Windows Explorer and select Network. 2.
Click on Network and Sharing Center. 3.
Select Change Advanced Sharing Settings. 4.
Make sure Turn on file and printer sharing is selected. 5.
After enabling sharing, return to the Management Console. When you are ready, schedule Recorder installation right from the device error message and click Apply. If the problem was resolved, the error status will be replaced by normal recording status Option - Install manually at the device
If changing OS settings at the device is not possible, you can deliver a Manual Setup file to the device instead. Option - Remove device
Select this option to cancel the installation request and remove the device from the Recorders group. If a Recorder was NEVER installed on this device, the assigned license will be released. You can always use Add Recorder to add it later. Deployment Guide 99 Insufficient Permission Insufficient Permission
The credentials used for installation do not have local administrator user privileges at this device. When you enter credentials for installation from the Management Console, be sure to use a‐user account name and password that belongs to the Administrator users on the local device.. Explanation
This message appears if the credentials you entered in the "Prepare" step of adding Recorders are not valid on a computer. To deliver and install the Recorder on remote computers, the Veriato server requires administrator user permissions on each endpoint. Some customers use Domain Administrator accounts and others create special accounts that have administrator user privileges on each computer. Option – Set credentials and schedule installation
If you know credentials with administrator access on this device, enter them in the error message. When they are verified, you can re‐schedule installation. 100 Deployment Guide Invalid credentials Option - Remove device
Select this option to cancel the installation request and remove the device from the Recorders group. If a Recorder was NEVER installed on this device, the assigned license will be released. You can always use Add Recorder to add it later. Invalid credentials
The account credentials you entered in the Add Recorders "Prepare" panel do not have administrator user privileges at this device. Enter a valid adiminstrator‐user account name and password. Explanation
To access a remote computer and deliver and install software, you need to supply administrator credentials (username and password). The account credentials must be present in the administrator users group on the local computer. A domain administrator fits this description, or "service" account present on all computers you plan to monitor. See Device Credentials. TIP: If you are evaluating Veriato Recon/360, try deploying to a computer where you yourself are
administrator. Just enter your own credentials in the Add Computers "Prepare" panel.
Option - Set credentials and reinstall
To try the installation again, enter credentials for a valid administrator‐user at the device. See Device Credentials. 1.
Type the username for the account. 2.
Enter the password for the account. 3.
Press Submit. 4.
If credentials are valid, schedule reinstallation: 
Now ‐ Installs the Recorder as soon as possible. 
At scheduled time ‐ Installs the Recorder at the date and time you select. Type in a date and time, or use the buttons to select from a calendar and adjust a clock. Deployment Guide 101 The Recorder Was Not Installed Date and time selection 5.
Click Apply. The device status changes to installing or "Waiting to install." Option - Remove device
Select this option to cancel the installation request and remove the device from the Recorders group. If a Recorder was NEVER installed on this device, the assigned license will be released. You can always use Add Recorder to add it later. The Recorder Was Not Installed
The Recorder installation did not complete due to errors. Veriato was unable to determine exactly what caused the problem, but the installation could not be verified as being received by or started at the device. Explanation
Likely one of the following is causing the problem: 
The device is offline. Other network tools and vacation/ travel schedules should tell you what the story is with this device. When the device comes back online, re‐schedule installation from this message in the Recorders list. 
Antivirus scanning is detecting and interfering with the installation. Make sure you have excluded the Veriato Recorder folder or files in your antivirus management system. Be aware that different antivirus/anti‐spyware programs, other than your Enterprise solution, may be running at various devices and causing this problem. If this is the case, you'll need to either remove the programs or exclude the Veriato files in each program. See Check Antivirus Settings. 102 Deployment Guide The Recorder Was Not Installed 
A firewall or network configuration is preventing communication. Your network tools will tell you if a device is outside the firewall protecting the Veriato server. Open firewall holes or plan to install a client manually at the device. 
There's a system or hardware problem at the device. The device itself may be compromised and unable to receive the Recorder installation. 
The device wasn't found (try FQDN). It may be that the device name was entered incorrectly, or that a fully qualified domain name (FQDN) was required; for example, machinex.mydomain. This is especially likely when the domain is not the same one the server is on. To try again, remove the device. Use Deployment | Add Recorder and add the device again using the FQDN. Option - Do nothing
If you expect the device to come back online or are waiting for the problem to be resolved, dismiss the message without using "Apply." The device with its error will remain in the Recorders list until you are ready to try again. Option - Correct the problem and re-install
After updating the antivirus exclusions or addressing a firewall issue, re‐schedule installation from the Recorder status message. Option - Remove device
Select this option to cancel the installation request and remove the device from the Recorders group. If a Recorder was NEVER installed on this device, the assigned license will be released. You can always use Add Recorder to add it later. Deployment Guide 103 The Recorder Version Is Not Supported The Recorder Version Is Not Supported
The Recorder will not operate until you update ("push") a supported version. When the update is complete, the Recorder will begin working again, and no data will be lost. Explanation
The Recorder software installed is no longer supported. Update the version to begin receiving data. If you have just upgraded Veriato Recon/360, this message appears next to Recorders in communication with the server. The message disappears when you upgrade the software to a 9.* version. Option - Set credentials and schedule installation
Because replacing an obsolete Recorder Version is a complete software re‐installation, you must supply administrator‐user credentials when installing from the error message. See Device Credentials. 1.
Type the username for the account. 2.
Enter the password for the account. 3.
Press Submit. 4.
If credentials are valid, schedule the update. Keep in mind that installation will restart the device. 
Now ‐ Installs the Recorder as soon as possible. 
At scheduled time ‐ Installs the Recorder at the date and time you select. Type in a date and time, or use the buttons to select from a calendar and adjust a clock. 6. Click Apply. The device status changes to installing or "Waiting to install." Instead of responding to the error message, you could select devices in the list and then choose Deployment | Update Recorder from the top bar. Click the option to "Reinstall (push) the software, enter valid administrator credentials, and click Submit. 104 Deployment Guide Remote registry cannot be enabled Remote registry cannot be enabled
Contact with the Windows Remote Registry service is required to access the endpoint for
installation and display the computer's status. If a computer is displayed as Not Detected and
you are sure it is on and connected to the network, most likely Remote Registry service
capabilities are not enabled for that computer, or you do not have Administrator user privileges
to access it.
When you deploy the Veriato Recorder, Remote Registry Services on the endpoint is enabled, if
possible. If Remote Registry services cannot be enabled, try the instructions below.
Test Remote Registry Services
1.
Select Start. 2.
In the Search programs and files or Run entry box, type: regedit 3.
Press OK or Enter. 4.
Select File | Connect Network Registry. 5.
For an object type of Computer, type the name of the computer you are not detecting and press OK. If you do not receive a list of Registry folders for the computers, enable Remote Registry
Services at the computer.
Option - Enable Remote Registry Services and try again
The procedure varies, depending on your operating system.
1.
At the computer you wish to record, open the Windows Control Panel. Select Administrative Tools and Services. 2.
Find the Remote Registry Service. 3.
Verify that it runs on System Startup. Deployment Guide 105 Windows UAC Prevented installation Option - Install manually at the device
If changing OS settings at the device is not possible, you can deliver a Manual Setup file to the device instead. Option - Remove device
Select this option to cancel the installation request and remove the device from the Recorders group. If a Recorder was NEVER installed on this device, the assigned license will be released. You can always use Add Recorder to add it later. Windows UAC Prevented installation
User Account Control (UAC) on a Windows device prevented Recorder installation. Explanation
A local, non‐network account would not have access privileges to install remotely to a Windows device with User Access Control enabled. UAC causes a credentials prompt to appear when software is about to be installed. Option - Correct the problem and install
If you have domain‐level credentials that will not elicit the prompt, remove the device (see below), then add it again using those credentials. If you wish, disable UAC at the device and re‐schedule installation from the error message. Option - Use a manual setup file at the device
Create a Manual Setup file and run it directly at the device. When the UAC message appears, you can respond by entering administrator credentials. 
Cancel installation and remove the device. Option - Remove device
Select this option to cancel the installation request and remove the device from the Recorders group. If a Recorder was NEVER installed on this device, the assigned license will be released. You can always use Add Recorder to add it later. 106 Deployment Guide WMI Firewall Blocking Communication WMI Firewall Blocking Communication
It appears that Windows Management Instrumentation (WMI) is being denied access to this device. Enable firewall exclusions for all WMI entries in the Windows Firewall panel for the device. Explanation
WMI needs access to the device to deliver Recorder installation. If you get this message, enable Group Policy rules to allow WMI on the domain. If you are not on a domain, you can change firewall settings at each computer. Options
1. Use Windows search for "Firewall" to bring up the Windows Firewall security panel. 2. Go to Advanced Settings and select Inbound Rules. 3. Find and select "Windows Management Instrumentation" entries. 4. Select Enable Rule. The rule is enabled for ALL domains in the following example, and the message will not appear. Deployment Guide 107 Unable to discover... Add Messages Unable to discover...
If the Add wizard is unable to retrieve devices or users, this message is displayed. You are prompted to log into Active Directory or use another method of listing available devices or users. Explanation
Possible reasons for this message are: 
Your computer is not connected to the network. 
Network discovery is turned off. 
Computers are not properly networked together. 
The wizard doesn't have credentials to access Active Directory. 
The Active Directory credentials are OK, but no "unused" devices or users were found. Option - Check your computer
Check your computer network and network discovery settings. Option - Provide Active Directory credentials
If you know you have Active Directory services: 1.
Click the Active Directory button. 2.
Under the "Access Active Directory" tab, enter account credentials for the domain you want to access. These might be your credentials, or they might be credentials for a more privileged account. Once set, the credentials stay in place until you change them. 3.
You can then click the X in the upper right corner of the panel to exit, and Active Directory discovery will commence. 4.
Instead of using discovery, if you prefer, choose another tab on the Active Directory
panel to select individual items or OU groups. When you are ready, click the Add
Devices/Add Users button on the Active Directory panel. The panel closes, and the
items are added to the list and selected.
108 Deployment Guide Too Many to List Option - Use another method

Importing a CSV file does not require discovery capability. 
Add One allows you to enter the name and credentials for a device that you know about. No unused devices (or users) were found
in discovery, only the domain\device or domain\user names not already in your groups are listed. You can't bring in duplicates! If everyone is already accounted for, nothing will be found. Too Many to List
If the Add wizard has successfully discovered more than 1,000 devices or users, it doesn't list them, but rather displays this message. You are prompted to use Search, Active Directory, Import or Add One to obtain your list of devices or users. Explanation
It's better to add batches of less than 1,000. Performance improves, and its easier to manage the credentials and licensing required in the Add Devices wizard. Options

Search ‐ If your Virtual Machine naming convention is DEPT‐VM‐MACHINE, you could enter *‐
VM‐* and, if the results are fewer than 1,000, any matching names in the discovery will appear in the list (DEPT1‐VM‐MACHINE1, DEPT1‐VM‐MACHINE2, and so on). For users, you could enter *Smith* to find and add a particular "Smith." 
Active Directory ‐ Click the Active Directory button and browse for specific Organizational Units or individuals to select. Click the Add Devices/Add Users button on the Active Directory panel to bring the selections in to your list. 
Import CSV ‐ Create or cut down your CSV file to less than 1,000 devices or users. Use Import Devices, or Import Users, to bring them into your list. 
Add One ‐ If you know which devices or usesr you want to add, you can use Add ONe to add items one at a time. Deployment Guide 109 Contact & Copyright Contact Us
When sending email, please include your company name, city, and state to ensure your request
is handled as promptly as possible.
General Contact
Veriato, Inc. 4440 PGA Boulevard Suite 500 Palm Beach Gardens, FL 33410 www.veriato.com Toll Free +1 888‐598‐2788 Phone +1 772 770 5670 Fax +1 772 770 3442 Monday through Friday, 7:00 AM to 7:00 PM Eastern Time [email protected] Technical Support
Use the telephone number above or contact Veriato Technical Support. Copyrights and Trademarks
Copyright Notice
Copyright © 2017 Veriato, Inc., 4440 PGA Boulevard, Suite 500, Palm Beach Gardens, FL 33410. Veriato, Veriato Recon/360, and Veriato Recon are Registered Trademarks of Veriato, Inc.. Your use of Veriato Help Files constitutes your acknowledgment and acceptance of the Veriato terms of use. If you do not agree with these terms of use, please do not use these Help Files. All materials appearing anywhere within this guide are protected by worldwide copyright laws and treaty provisions. The copyright on such materials is held by Veriato or its subsidiaries (collectively, Deployment Guide 111 Copyrights and Trademarks "Veriato"), or by the original creator of the materials. None of the materials may be copied (other than for personal use), reproduced (other than for personal use), displayed, modified, published, uploaded, posted, transmitted, or distributed in any form or by any means without prior written permission from Veriato. All rights not expressly granted herein are reserved. Any unauthorized use of the materials appearing on Veriato Help Files may violate copyright, trademark, and other applicable laws and could result in criminal or civil penalties. Third-party software

Microsoft ‐ Veriato software includes code under license from Microsoft Corporation. © 1995‐
2017 Microsoft Corporation. All rights reserved. 
Microsoft SQL Server ‐ Microsoft SQL Server Express is delivered with a Veriato "Quick Install" and is licensed by Microsoft, under the terms of the Microsoft license agreement with Veriato. All end users are bound to the terms of the Veriato End User License Agreement. These additional terms apply to the Microsoft SQL Server 2014 Express software.
1. Restrictions. You may not:
• unbundle the Microsoft SQL Server 2014 Express from the Veriato Software;
or
• disclose the results of any benchmark tests of the software to any third party
without Microsoft’s prior written approval.
2. Third Party Notices. The software may include third party code, that Microsoft, not
the third party, licenses to you under the terms set forth in this agreement. Notices, if
any, for any third party code are included for your information only. Additionally, any
third party scripts, linked to, called or referenced from this software, are licensed to
you by the third parties that own such code, not by Microsoft, see ASP.NET Ajax CDN
Terms of Use: <http://www.asp.net/ajaxlibrary/CDN.ashx>.
3. SQL Server Reporting Services Map Report Item. Power View and SQL Reporting
Services Map Item both include use of Bing Maps. You may only use the content
provided through Bing Maps, including geocodes, within Power View or SQL Reporting
Services Map Item. Your use of Bing Maps is also governed by the Bing Maps End User
Terms of Use available at: http://go.microsoft.com/?linkid=9710837 and the Bing Maps
Privacy Statement available at: http://go.microsoft.com/fwlink/?LinkID=248686.
112 Deployment Guide Copyrights and Trademarks 4. No support or warranty. The software is provided “As-Is” with no support of any
kind from Microsoft. You bear the risk of using it. Microsoft gives no express
warranties, guarantees, or conditions.

miniz ‐ Used for Mac client installs. Provided by Google Code and completely free: Public domain in jurisdictions that recognize copyright laws, with a license patterned after the public domain SQLite project, see unlicense.org. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL
THE AUTHORS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN
AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN
CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.

ActiveMQ ‐ Copyright © 2016 Veriato, Inc. Licensed under the Apache License, Version 2.0 (the "License"). You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE‐2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. 
Newtonsoft.Json ‐ The MIT License (MIT), Copyright © 2007 James Newton‐King. Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or
substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY
KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE
WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR
PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM,
DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF
CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN
Deployment Guide 113 Copyrights and Trademarks CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
DEALINGS IN THE SOFTWARE.
Trademarks for other companies

Microsoft Windows, MSN and other Microsoft products referenced herein are either registered trademarks or trademarks of Microsoft Corporation in the U.S. and / or other countries. 
Macintosh and Mac, Mac OS X, and Leopard are trademarks of Apple Computer, Inc., registered in the U.S. and other countries. 
Citrix is a registered trademarks or trademarks of Citrix Systems, Inc. These Help Files may contain other names and phrases (marks) that may or may not be trademarks of other organizations. All other trademarks and service marks are the property of their respective owners. 114 Deployment Guide Index
A Database server 5 Activation 68 Deploy Active Directory 82 Accessing with account 82 to Android 94 Deploying Importing OUs from 82 Selecting devices from 82 with SCCM 113 Device credentials 79 Add a test Recorder 73 E Add recorder Error status Too many to list 167 File and printer sharing 153 Unable to discover 168 Insufficient permission 154 Unable to verify one 170 Invalid credentials 156 Adding users 89 Recorder not installed 158 Administrative C$ share 149 Recorder version not supported 160 Administrator user account 108 Remote registry cannot be enabled 162 Administrator‐user credentials 79 Windows UAC preventing installation 164 Alert emails 63 WMI denied access 165 Alternate activation 68 F Alternative shell 110 File and printer sharing 153 Android 94 File server 5 Deployment 94 Antivirus interferes with installation 147 I Install Database Separately 56 Antivirus/Disabling 22 Application server 5 Install Database Only 56 C Install full SQL Server 40 Chromium 94 Install Management Console Only 51 Citrix 110 Install SQL Server Express 33 Connect to Veriato Server 67 Install with Options 40 Contact us 173 Installation configurations 5 Copyright 174 Insufficient permission 154 D Invalid credentials 156 Data Path 56 L Data retention 70 Logging in 67 Deployment Guide 115 SQL server 11, 24 M Management Console 51 Install with Options 40 Master login account 63 Installing 24 Multi‐user networks 110 SQL Server IP port 40 P System diagram 5 Password requirements 63 System requirements 11 Ports 70 T Primary application server 5 Technical support 173 Product key 68 Terminal server support 110 Q U Quick install 33 Use email as login 63 R Users 89 Recorder installation 73 Troubleshooting 147 V Recorder version not supported 160 Veriato email relay 63 Remote registry 162 Veriato Server Port 51 Requirements 11 W S Windows 11 SCCM 113 Services required for Recorder 11 Screenshots 56 Systems supported 11 Session host 110 Terminal Services 110 SMTP email relay 63 Windows Management Instrumentation 165 Space management 70 Windows UAC prevented installation 164 SQL instance 24 Workgroup deployment 108 Deployment Guide Deployment Guide 116 
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertisement