What do you want to do?
Before users can access projects on NVivo Server, you need to add them to the appropriate server user groups. Users access the NVivo server using either of the following:
Their current Windows domain account (using integrated Windows authentication).
A nominated Windows account on the server or a domain to which the server belongs.
As server administrator, you control access to the server by assigning users to server user groups—these groups control what the group members can do on the server. You can assign the following roles:
Users—can connect to the server and access server projects.
Project Creators—can connect to the server and are allowed to create new server projects.
Administrators—have access to license allocation, user groups and other server management tools via the NVivo Server Manager.
The server administrator does not control access to specific projects—this is controlled by Project Owners, who can add users to project user groups from within the NVivo client—refer to the NVivo client Help for more information.
Before users can access server projects, you must assign user roles and permissions. When assigning users to server groups, consider the following:
You must add at least one user account or group to the Project Creators group.
The server administrator defined during install is automatically added to the Administrators group. This group must contain at least one user account or group.
User accounts must be either local Windows accounts on the server, or Active Directory user accounts in the same domain as NVivo Server.
To assign users to server user groups:
In NVivo Server Manager, click the Users tab.
On the left, click the Groups tab.
In the Groups box, select the group you want to add users to.
Click the Add button. The Select Users dialog box opens.
In the From this location box, enter the server or domain name of the user account or group.
Enter the user accounts or groups you want to add—separate multiple names with a semi colon.
Click the Check Names button to verify user account and group names.
Click OK.
NOTE
To remove users from an NVivo Server user group, select the names in the Members list and click the Remove button. If you remove a 'named' user, you should also remove their CAL allocation— refer to Allocate Client Access Licenses (CALs) for more information.
If you experience difficulty adding users to a server group, check the sever configuration:
Make sure Network Discovery is turned on.
If the server is configured to use a static IP, then check that NetBIOS over TCP/IP is enabled.
Make sure the Computer Browser service is started.
Depending on the terms of purchase, your NVivo Server license:
Entitles you to run NVivo Server on a server with a specific number of processor cores.
Entitles you to a number of Client Access Licenses (CALs) that allow users to access server projects.
You must purchase at least one processor license. NVivo Server processor licenses are based on quad-core processors and the number of licenses you require is determined by the number of cores allocated to the server. You should discuss your processor licensing needs with QSR International. If you upgrade your hardware, you may need to purchase additional processor licenses.
NOTE The processor licensing information above applies to NVivo Server 10 R2. If you are using NVivo Server 10, processor licenses are based on the number of CPUs allocated to the server.
NVivo Server supports multiple active license keys, as shown in the example below:
CALs can be distributed among:
Named users—specified user accounts (not groups) that have 1 CAL reserved for their specific use. These user accounts have a guaranteed server connection at all times.
Concurrent users—user accounts that do not have any CALs reserved for their use. These user accounts require 3 CALs each. Concurrent or 'floating' users connect to NVivo Server on a first-come, first-served basis. A concurrent user can only connect if there are available CALs.
For example, if your license includes 12 CALs, you could allocate 3 CALs to named users and allow 3 concurrent users to connect to the server:
Or you could leave all CALs unallocated and allow 4 concurrent users to connect at the same time:
When allocating CALs you may want to consider the following:
CALs are consumed when users open projects and are released when projects are closed.
Users cannot conserve CALs by logging on to multiple machines using the same 'named' user account—a named user consumes 1 CAL on the first machine and 3 CALs on any subsequent machine.
To maximize the use of your CALs, the number of licenses available for concurrent users should be a multiple of three (3, 6, 9,12 and so on).
To allocate a CAL to a named user or group:
In NVivo Server Manager, click the Licensing tab.
On the left, click the Allocation tab.
Click the Add button.
The Select Users dialog box is displayed.
In the From this location box, enter the server or domain name of the user account.
Enter the user accounts you want to add—separate multiple user account names with a semi colon. If you allocate a license to a user account that has not been added to the Users project group—it is automatically added.
Click the Check Names button to automatically verify the correct user account names.
Click OK.
NOTE To remove a named user, select it from the list and click the Remove button. Removing a named user merely removes the CAL allocation—it does not remove the user from server user groups—refer to Assign user roles and permissions for information about removing users from server user groups.
To see how many CALs are currently being consumed by NVivo users:
In NVivo Server Manager, click the Users tab.
On the left, click the Users tab.
The number of CALs currently in use is displayed at the bottom of the screen.
To see how many CALs are allocated to named users and how many are available for concurrent users:
In NVivo Server Manager, click the Licensing tab.
On the left, click on the Allocation tab. The distribution of CALs is displayed at the bottom of the window.
For named users it displays:
CALs The number of CALs currently in use by named users
CALs per user The number of CALs consumed by named users—a named user always consumes 1 CAL
Users The current number of named users that can access the server. The named users may not be currently connected but a CAL is reserved for each of them so they can connect at any time.
For concurrent users it displays:
CALs The number of CALs currently in use by concurrent users.
CALs per user The number of CALs consumed by each concurrent user—concurrent users always consume 3 CALs.
Users The maximum number of concurrent users that can connect to the server at any time.
Refer to Understand how licenses work for more information about how CALs are allocated.