Microsoft System Center deployment

NVivo 12 (Windows)

This topic explains how to use Microsoft System Center Configuration Manager (SCCM) to install NVivo 12 (Windows) to client machines. Microsoft System Center uses ‘packages’ to distribute software to client machines and then sequences the running of these.

NVivo 12 (Windows) can be installed with SCCM versions 2012 SP2 and 2012 R2 SP1.

Click below for instructions to deploy NVivo’s supplementary add-ons:

Step 1 - Determine which packages you need

You need to create a package to install NVivo 12 (Windows) and another package to activate the software. You also need to create a package for each prerequisite that you need to install. The prerequisites will vary, depending on the operating systems of the client machines, software currently installed, and whether you are installing the 32-bit or 64-bit version of NVivo.

Use the table below to determine which packages you need to create:

Packages NVivo (x86) on
Windows (x86)
NVivo (x86) on
Windows (x64)
NVivo (x64) on
Windows (x64)
Microsoft .NET Framework 4.6.2
Microsoft SQL Server 2014 SP3 Express LocalDB (x86) _____ _____
Microsoft SQL Server 2014 SP3 Express LocalDB (x64) _____
Microsoft Visual C++ 2010 SP1 Redistributable Package (x86) _____
Microsoft Visual C++ 2010 SP1 Redistributable Package (x64) _____ _____
Microsoft Visual C++ 2012 Update 4 Redistributable Package (x86) _____
Microsoft Visual C++ 2012 Update 4 Redistributable Package (x64) _____ _____
NVivo 12 (x86) _____
NVivo 12 (x64) _____ _____
NVivo 12 Activation

Step 2 - Prepare the source files

Before creating the packages, save all required source files in a source directory accessible to the Configuration Manager and client machines (e.g. \\FileServer\SourceDirectory) .

The following table describes the source files needed for each package:

Packages Source files Steps to create source files
Microsoft .NET Framework 4.6.2 NDP462-KB3151800-x86-x64-AllOS-ENU.exe Download suitable versions from QSR International—refer to Software download locations.
Microsoft SQL Server 2014 SP3 Express LocalDB (x86) SqlLocalDB_SP3_x86.msi
Microsoft SQL Server 2014 SP3 Express LocalDB (x64) SqlLocalDB_SP3_x64.msi
Microsoft Visual C++ 2010 SP1 Redistributable Package (x86) vcredist_2010_x86.exe
Microsoft Visual C++ 2010 SP1 Redistributable Package (x64) vcredist_2010_x64.exe
Microsoft Visual C++ 2012 Update 4 Redistributable Package (x86) vcredist_2012_u4_x86.exe
Microsoft Visual C++ 2012 Update 4 Redistributable Package (x64) vcredist_2012_u4_x64.exe
NVivo 12 (x86 or x64) All the files extracted from the NVivo 12 32-bit or 64-bit Windows Installer package. Download the 32-bit or 64-bit NVivo 12 Windows Installer package from the QSR website. Extract the contents of the package using the relevant command:
  • For 32-bit, use: NVivo12.x86.exe /a
  • For 64-bit, use: NVivo12.x64.exe /a
NVivo 12 Activation activation.xml
activation.bat
  1. Create the XML file manually or download and edit, see Activation_XML_file.
  2. Download and edit the batch file, see Activation_batch_file.

Step 3 - Create the packages and programs

Now create a package for each source file you need to install. Each package has an associated program to define system requirements, command line parameters and other run options.

  1. To launch the Configuration Manager Console, click Start, point to All Programs,  Microsoft System Center and then click ConfigMgr Console.

  2. In the Configuration Manager console, navigate to Software library / Overview / Application management.

  3. Right-click Packages, click Create package. The Create Package and Program Wizard opens.

  1. Enter the name of the software, its version, manufacturer, language and a descriptive comment, and then click Next.

  2. Select This package contains source files.

  3. Click Browse and enter the UNC path of the source directory you created in the previous step.

  4. Click OK and then click Next.

  5. On the Program Type page, select Standard Program, and then click Next.

  6. On the Standard Program page, in the Name field enter a descriptive name for the program.

  7. In the Command line, type the command line that will be used to execute the program (or click Browse to select a batch file). In many cases, you will use the batch files you downloaded in Step 2 – Prepare the source files.

See the following table for more information.

Package Command line Comment
Microsoft .NET Framework 4.6.2 NDP462-KB3151800-x86-x64-AllOS-ENU.exe /showrmui /passive /norestart
Microsoft SQL Server 2014 SP3 Express LocalDB (x86) SqlLocalDB_SP3_x86.msi IACCEPTSQLLOCALDBLICENSETERMS=YES /q
Microsoft SQL Server 2014 SP3 Express LocalDB (x64) SqlLocalDB_SP3_x64.msi IACCEPTSQLLOCALDBLICENSETERMS=YES /q
Microsoft Visual C++ 2010 SP1 Redistributable Package (x86) vcredist_2010_x86.exe /passive
Microsoft Visual C++ 2010 SP1 Redistributable Package (x64) vcredist_2010_x64.exe /passive
Microsoft Visual C++ 2012 Update 4 Redistributable Package (x86) vcredist_2012_u4_x86.exe /passive
Microsoft Visual C++ 2012 Update 4 Redistributable Package (x64) vcredist_2012_u4_x64.exe /passive
NVivo 12 (x86 or x64) msiexec /Option [Optional Parameter] Refer to Installation options and parameters for detailed information about the options you can specify when you install NVivo.
If you exceed the length of the command line, you will need to create a batch file to execute your command line statements.
NVivo 12 Activation activation.bat This batch file provides the license key plus information from the activation.xml file.
See Activation_XML_file and Activation_batch_file.
  1. From the Run list, select Normal, Minimized, Maximized or Hidden to determine how the program runs on the client machine.
  2. Under Program can run, choose when this program can run. No user interaction is required to install NVivo and its prerequisites, however the computer may be restarted as part of the task sequence, so you should select whichever option suits your organization.
  3. Under Run mode, select Run with administrative rights.
  4. Under Drive mode, select Runs with UNC name. Then click Next.
  5. On the Requirements page, enter information about the system requirements that apply to this program. Use these options to determine how much disk space should be available for the setup, the maximum amount of time to let the program run, and the operating systems supported by this program. Then click Next.
  6. View the summary and then click Close to create the package and program.
  7.  After creating the package, click on the created package to select it.
  8. Open the Programs tab at the bottom of the screen to see the program inside the package.
  9. Right-click on the program and select Properties.
  10. On the Advanced tab, check Allow this program to be installed from the Install Package task sequence without being deployed.
  11. Click OK to save your changes and close the Properties windows of the program.

Repeat this procedure for each package and program that you need to create.

Step 4 - Create a task sequence

Now that you have created the packages and programs, create a task sequence to execute the packages in order.

NOTE If you need to install Microsoft .NET Framework 4.6.2 we recommend that you create a separate task sequence for this to run first, as you may need to restart the client machines after installing it.

First, create the new task sequence:

  1. In the Configuration Manager console, navigate to Software library / Overview / Operating systems.

  2. Right-click the Task Sequences folder and then click Create Task Sequence. The Create Task Sequence Wizard opens.

  3. On the Create New Task Sequence page, click Create a new custom task sequence, and then click Next.

  1. On the Task Sequence Information page, enter a descriptive name for the task sequence, and then click Next.

  2. On the Summary page, check the name for the task sequence, and then click Next. A new (empty) task sequence is created.

  3. Click Close to exit the wizard.

Next, add the required packages to the sequence:

  1. In the Configuration Manager console, navigate to Software library / Overview / Operating Systems / Task Sequences.

  2. Right-click on the new task sequence, and then click Edit.

  3. Click Add, then click Software, then click Install Package, and then click Browse to add the required packages to the task sequence:

  4. Repeat Step 3 for all packages below:

  • Microsoft SQL Server 2014 SP3 Express LocalDB (x86 or x64)

  • Microsoft Visual C++ 2010 SP1 Redistributable Package (x86 or x64)

  • Microsoft Visual C++ 2012 Update 4 Redistributable Package (x86 or x64)

  • NVivo 12 (32-bit or 64-bit)

  • NVivo 12 Activation

  1. Click OK to close the task sequence.

Step 5 - Deploy the task sequence

Now everything is set up, you need to create a deployment for the task sequence to be sent to the client machines.

  1. In the Configuration Manager console, navigate to Software library / Overview / Operating Systems / Task Sequences.

  2. Right-click on the task sequence, and then click Deploy. The Deploy Software Wizard opens.

  1. On the General page in the Collection field, select the client machines you want to deploy the task sequence to. For example, a collection of Windows 10 machines. Click Next.

  2. On the Deployment Settings page, make sure Action is set to Install and change Purpose to Required. Click Next.

  3. On the Scheduling page, set the date and time that you want the task sequence to run.

  4. On the Distribution Points page, set Deployment options to Download content locally when needed by running task sequence. This ensures that setup files (which include license keys) are not cached on client machines.

  5. Optionally, check When no local distribution point is available, use a remote distribution point and Allow clients to use a fallback source location for content. This gives clients flexibility to use any available source for deployment packages, ensuring they are not blocked by distribution point configurations.

  6. Continue through the wizard selecting your preferred options, and then click Finish to create the deployment.

At the scheduled time and date, Microsoft System Center sends the task schedule to the client machines. When these machines recognize that the schedule is available, the installation process begins. If a package fails to install on a machine, the task sequence stops on that machine.

Software download locations

The NVivo 12 (32-bit and 64-bit) installer packages are available for download from the QSR website. Later releases of these components may become available, however we recommend that you use the versions listed below, as these have been tested with NVivo 12.

www.qsrinternational.com/support/downloads

Windows Installer Packages for NVivo 12’s prerequisites are available for download using the following links:

Activation XML file

Copy the text below into Notepad, set the values within the tags, and then save as an .xml file with UTF-8 encoding.

Alternatively, download a copy of the file with the link below, then edit.

Name the file “activation.xml”

 

 

  

    John

    Sysadmin

    admin@yourorg.com

    +1-555-555-5555

    +1-555-555-5555

    Your Job Title

    Your Sector

    Your Industry

    Your Role

    Your Department

    Your Organization

    Boston

    USA

    Massachusetts

  

 

You can also download a zip file containing the sample activation file. Extract the file and then open it in your text editor.

NOTE  You must observe the following rules, or the activation will fail:

  • Fields in bold are mandatory.

  • State is a mandatory field if you set the country field to USA, Canada or Australia.

  • You must use a valid email address.

  • You must use abbreviations for the following countries:

  • For United States of America, use USA

  • For United Kingdom, use UK

  • For all other countries, capitalize the first letter of each word—for example, ‘Mexico’ or ‘New Zealand’. Refer to the list of accepted country names for the specific format and spelling for your country name.

Activation batch file

Download the activation batch file from https://download.qsrinternational.com/Document/NVivo12/SCCM/v12/NVivo12-SCCM-Script.zip

This ZIP file contains:

  • activation.bat

Edit the BAT file to add your site’s license key and the directory where you saved the source files (to provide the file path to the activation XML file).