You are here:
< Back

This technical document explains the steps to follow to deploy NetSupport Manager or NetSupport School using Windows Server 2019.

The following files are required to perform an Active Directory installation (they need to be placed in the package):

NetSupport Manager

    • NetSupport Manager.msi.
    • NSM.lic (licence file).
    • NSM.ini (the component file which tells the installer which components to install, i.e. Control, Client).
      This file is located in the following directory:
      C:\Program Files (x86)\NetSupport\NetSupport Manager\Deploy
      Note: The machine needs to have NetSupport Manager with the Remote Deployment Utility installed.
    • Client32.ini and Client32u.ini (this is the pre-configured Client configuration file).

NetSupport School

    • NetSupport School.msi.
    • NSM.lic (licence file).
    • NSS.ini (the component file which tells the installer which component to install, i.e. Tutor, Tech Console, Student).
      This file is located in the following directory:
      C:\Program Files (x86)\NetSupport\NetSupport School\Deploy
      Note: The machine needs to have NetSupport School with the Remote Deployment Utility installed.
    • Client32.ini and Client32u.ini (this is the pre-configured Client configuration file).

Once you have the files, place these in the Package folder. This location must be accessible by all Client machines you wish to deploy to, and they must also have read access for these files. We recommend you use a UNC path and not a mapped drive as the Client machines mapped drives may differ from machine to machine, i.e. \\server\share\NetSupport_Manager.msi

  1. Open Group Policy Management.
  2. Right click Group Policy Objects and select New. Enter a name so it is clear what package you will be distributing, i.e. NetSupport School Tutor.
  3. Right click the Group Policy Object you have created and select Edit. The Group Policy Object Editor will open.
  4. In the Group Policy window, you are given two possible installation types/levels for the NetSupport Manager/School package: “Computer Configuration” and “User Configuration”.

If you use “Computer Configuration”, the package will be installed before the user is prompted to log in. The installation will use the System Service Account to install the package.

If you use “User Configuration”, the package will be installed when a user logs on. Please note that the user will require administrator rights to install the software at this level.

We recommend installing the package under “Computer Configuration” to prevent the possibility of any issues installing at “User” level.

  1. Select the type of configuration you require and go to Policies > Software Settings > Software Installation.
  2. Right click Software installation and select New > Package.
  3. You will be prompted for the location of the package (NetSupport Manager/School.msi). Ensure when selecting the package, you enter the full UNC path, i.e. \\server\share\NetSupport_School.msi
  4. When prompted for the deployment method, select Assigned.
  5. The package will be displayed (there may be a brief delay). If you selected the “User configuration”, right click the package and select Properties. In the Deployment tab, select the Install this application at logon option.
  6. Close the Group Policy Editor.
  7. This policy can be linked to the desired OUs by right clicking the OU and selecting Link an Existing GPO. You can then select the policy that was created and click OK.

If you have deployed at the “Computer Configuration” level, the Client machines will need to be restarted for the software package to be installed. If the package is set at the “User Configuration” level, it will require the user to log off and back on again.

When creating the package, you will only see the installer file (NetSupport Manager/School.msi), but as long as the additional files (NSS/NSM.ini, NSM.lic) are located in the same UNC path, it will read the files during the deployment. If you do not have the licence file (NSM.lic) in the package folder, the installer will install the software using the default EVAL licence.

Was this article helpful?
5 out of 5 stars
5 Stars 100%
4 Stars 0%
3 Stars 0%
2 Stars 0%
1 Stars 0%
How can we improve this article?
Need help?