Deploying the ActivClient Setup

This section explains how to deploy ActivClient once you have customized the HID ActivClient setup.

Warning!

Configuring WDAC or AppLocker to use PowerShell Constrained Language Mode may prevent the PowerShell scripts included in the ActivClient MSI installer from running. As a result, you may be unable to install a new version of ActivClient or uninstall or update an existing installation.

Until a solution is available, temporarily disable this mode before installing, updating, or uninstalling ActivClient. We are working on an installer update that will support this security mechanism.

The standard HID ActivClient deployment method consists in running the ActivClient .MSI installer.

The ActivClient setup uses MSI, the current standard in Windows. Most Enterprise Management products support MSI technology. Therefore, if you are using or planning to use a product that is MSI compatible (such as Tivoli or Novadigm), this product will likely work with ActivClient.

Note: Once the ActivClient MSI is deployed, you can deploy ActivClient policies, as described in Configuring ActivClient Using Policies. ActivClient uses administrative templates, also supported by most enterprise management products.
Important: Before deploying the ActivClient MSI and ActivClient policies on your production network, it is strongly recommended that you perform a test with ActivClient in a separate test environment.

As an administrator, you can remotely install ActivClient for a set of users or computers using Microsoft System Center Configuration Manager (SCCM).

This reduces the total cost of ownership of ActivClient because administrators are not required to perform installation in person at every workstation. Also, users do not require instructions on how to install the product, thereby eliminating on-site installation support and associated help desk calls.

Note: For complete details on SCCM installation, configuration and usage, see the Microsoft documentation.

As an administrator you can remotely install ActivClient to a set of users or computers using the automated software push capabilities in Microsoft Windows Server Active Directory.

This reduces the total cost of ownership of ActivClient because administrators are not required to perform installation in person at every workstation. Also, users do not require instructions on how to install the product, thereby eliminating on-site installation support and associated help desk calls.

Note: The following procedure is illustrated using Microsoft Windows Server 2008. The steps and interface might vary with newer versions of Microsoft Windows Server. Refer to the Microsoft documentation for further information.

The following table lists the tasks associated with distributing ActivClient in the order they are to be performed and where to find information about each task:

Task Task Description See

1

Create a shared network folder as a distribution point.

Create a Distribution Point

2

Limit deployment to a predefined user population and distribute the package containing ActivClient to computers.

Assign the Package

3

Test the package.

Test the Package

4

Redeploy a package.

Redeploy the Package

  1. Log on to the server computer as an administrator.

  1. Create a shared network folder in which to place an ActivClient .msi installer for each ActivClient edition to be deployed.

  2. Set permissions on the shared network folder to allow access to the distribution point.

  3. Copy the ActivClient .msi installer to the distribution point.

The package to be deployed must be assigned to a group of computers (an Active Directory Organizational Unit, or OU) on which the package is to be installed.

For deployment, follow these steps:

  1. On the domain controller, start the Server Manager, and expand the Features node.

  1. In the Group Policy Management node, expand Forest and Domains and then select the domain containing the organizational unit(s) to which you want to deploy ActivClient.

  2. Depending on the scope of the deployment, right-click on the domain or OU and select Create a GPO in this domain and Link it here (or edit an existing GPO).

  3. In the Group Policy Management Editor, expand Computer Configuration, then Policies and then Software Settings.

    Group Policy Management Editor

  1. Right-click on Software Installation point to New, and select Package.

  2. In the Open dialog box, in the File name field, enter the full Universal Naming Convention (UNC) path to the shared folder that contains the MSI package you want to deploy.

Important:

  • Do not browse to the location. Make sure that you use the UNC path to the shared folder.

  • It is mandatory that the package is assigned to a computer, as opposed to assigning it to a user.

  1. Select the package and click Open.

    Deploy Software dialog box.

  1. Select Assigned and click OK.

    Group Policy Management Editor

    The package is listed in the right pane of the Software installation window.

  1. Close the console window.

    When the client computer starts, the managed software package is automatically installed.

To validate the package, you can force package installation on a computer from the target Organizational Unit (OU) and verify that the installation has completed successfully. To do so:

  1. Log on to a computer that is part of the target OU.

  1. From the Start menu, point to Settings, and select Control Panel.

  2. Double-click Programs and Features, and then click Install a Program from the Network.

  3. Select the ActivClient edition that you published, then click Add.

    The package is validated as ActivClient is installed.

  1. Click OK, and then click Close.

    Note:

    If error 1274 (Group Policy installation failed) occurs, enable the following policy:

    Computer Configuration > Administrative Templates > System > Logon > Always wait for the network at computer startup and logon

    This ensures that the Group Policy is applied correctly during startup.

In some cases, you might want to redeploy a package. For example, you can use the redeploy function to upgrade to a more recent version.

Use the following procedure to redeploy a package:

  1. In the Group Policy Management Editor, return to the Software installation container that you created above.

  1. Right--click the package, point to All Tasks, and select Redeploy application.

  2. When prompted to accept that the application will be installed everywhere it is already installed, click Yes.

  3. Close the console window.