Deployment models

NVivo 10 Windows

NVivo can be deployed in a number of ways. Choose the deployment model that best suits your organization.

Deployment Model Description
Standard installation

This is a guided installation from either the NVivo DVD or the installation file if you downloaded the software.

For more information, refer to Standard installation.

Unattended command line installation

You can use the Microsoft Windows Installer (MSI) engine to perform an unattended installation of NVivo. An unattended installation is undertaken entirely from the command line and requires no user interaction.

For more information, refer to Unattended command line installation.

Microsoft System Center Configuration Manager (SCCM)

Microsoft SCCM uses packages to distribute software to client machines. A package represents a software application to be installed on a client computer.

For more information, refer to Microsoft SCCM deployment.

Citrix XenApp

Citrix XenApp is an on-demand application delivery solution that allows NVivo to be virtualized, centralized, and managed centrally. NVivo can be instantly delivered as a service to users anywhere on any device.

For more information, refer to Citrix XenApp deployment.

Microsoft Application Virtualization (App-V)

Microsoft App-V is an on-demand application delivery solution that allows NVivo to be virtualized, centralized, and managed centrally. NVivo can be instantly delivered as a service to users anywhere.

For more information, refer to Microsoft App-V deployment.

IMPORTANT  This deployment method is only suitable for sites using NVivo Server where:

  • All NVivo projects will be hosted on the server and there is no requirement to create projects on the client machines

  • The client machines are running Windows 7 (32-bit or 64-bit)

For more information about supported environments contact the Support team at QSR International.

Disk image

If your organization has an NVivo enterprise license, you may choose to deploy NVivo to multiple workstations by installing it once and copying the disk image to the individual workstations. This can be scripted—refer to Unattended command line installation for more information.

If this technique is used, the NVivo software must not be activated in the image. You must activate NVivo on each individual workstation that it is deployed to.

Top of Page