NVivo Server must be installed on a dedicated server (physical or virtual)—the server cannot have any other installation of SQL Server or any other SQL Server database instance. Only one version of NVivo Server may be installed on a physical or virtual server.
The process for installing NVivo Server is:
Add server roles and services before you install NVivo Server.
Consider administrator accounts—what accounts will you use to install and administer NVivo Server?
Before installing NVivo Server, you need to add server roles and services. The actions you need to take depend on your operating system.
On Windows Server 2008 or 2008 R2, you should add the Application Server role using the Add Roles Wizard as follows:
On Windows Server 2012 or 2012 R2, you should add the Application Server role using the Add Roles and Features Wizard as follows:
NOTE If you want to install NVivo Server 10 on Windows Server 2003 SP2 or 2003 R2, use these instructions for adding server roles and services. NVivo Server 10 R2 cannot be installed on Windows Server 2003.
Before installing NVivo Server, you should consider the administrator accounts you will use to install the software and the account you will nominate as the default NVivo Server administrator account.
The account you use to run the NVivo Server installer must have administrator privileges on the server.
During installation, you need to specify a default NVivo Server administrator account. This is the account you use to monitor the server in NVivo Server Manager and it may or may not be the same as the account used to run the installer.
The following considerations apply when choosing which accounts to use:
Account used to install NVivo Server—this may be a local account on the server, or a domain account on a domain to which the server belongs.
Default NVivo Server administrator account—this may be a local account on the server, or a domain account on a domain to which the server belongs. You may want to create a dedicated Windows group (for example, ‘NVivo Administrators’) and add user accounts to this group, as required. This account becomes the default Project Owner for the NVivo sample project.
IMPORTANT On Windows Server 2008 or later, you may need to disable the ‘User Account Control: Run all administrators in Admin Approval Mode’ security policy. If you are using an account that is a member of the server’s administrators group and the account is not the local administrator account ‘BUILTIN\Administrator’, then you may need to disable this security policy, if you want to:
Open or create NVivo projects using the NVivo client
Uninstall NVivo Server
Log on to the server using an account with administrator privileges.
Mount the disk image (the .iso file) that is provided on the NVivo Server USB flash drive.
Open the root folder of the mounted drive, and then double-click setup.exe.
Click Install, and then follow the prompts to:
Install any prerequisite components. You may be asked to restart your machine—on restart the installation will continue automatically. You may also be prompted to configure roles and services.
Accept the license agreement and enter your license key.
Choose the Complete set up option, and then select other options as required.
NOTE When choosing the Windows account or group to be given server administrator permissions for NVivo Server—enter the server location (machine or domain name) and the Windows user name or group. This defaults to the local Administrators group on the server.
Firewalls can block communication channels. There are some ports and applications that must not be blocked by a firewall for NVivo Server to function correctly.
CAUTION To prevent unauthorized access to your network, configure the firewall so that these ports and applications are exposed to the required network(s) only.
Port exceptions include:
TCP Port 8733 for the NVivo Service
TCP Port 1433 for the SQL Service
UDP Port 1434 for the SQL Service
TCP Port 80 for https (only required when activating NVivo Server or adding license keys)
Application exceptions include:
C:\Program Files\Microsoft SQL Server\MSSQL11.QSRNVIVO9\MSSQL\Binn\sqlservr.exe
If you are using a firewall that does not support application exceptions, you must manually configure the firewall to open the port allocated to the SQL service. To identify the port allocated to the SQL service:
Launch SQL Server Configuration Manager.
In the console tree, expand SQL Server Network Configuration, and then select Protocols for QSRNVIVO9.
On the right, under Protocol Name, double-click TCP/IP.
In the TCP/IP Properties dialog box, click the IP Addresses tab.
Under IPAll, locate TCP Dynamic Ports. The port number allocated to the SQL service is shown on the right.