Installation

The first step in setting up User Workspace Management is to install Workspace Control version 2020.0 on the computer on which you want to manage User Workspaces. With the installation of Workspace Control version 2020.0, the Management Console and an Agent will be installed.

  • To install Workspace Control version 2020.0 on your computer, use the Workspace Control Installer (Ivanti Workspace Control Installer [version].exe).
    • The Workspace Control Installer is an installation package that contains the MSI files for the different components of Workspace Control, grouped in one executable making it easier to install all necessary Workspace Control components. When using the Workspace Control Installer, you can either Select and install components on the machine on which you are currently working or Extract all components for later use.
      Choosing the option Select and install components, allows you to select which component(s) should be installed on the machine. The installation wizard of the selected component(s) will then guide you through the actual installation. The Workspace Control Installer auto-detects whether the 64-bit or 32-bit version of the component(s) needs to be installed.
      You can install the following components:
      • Clients:
        Workspace Composer
        Management Console
      • Services:
        Relay Server
        Reporting Services
      • Extra:
        Desktop Sampler
  • When extracting all components, individual MSI and EXE files will be saved in the specified location.
    Instead of installing Workspace Control fully, you can choose to perform:
    • an Agent-only installation, if you want to install Workspace Control without a Console (use Ivanti Workspace Control Agent [version].msi).
    • a Console-only installation, if you do not want to install a Workspace Control Agent on the computer on which you want to manage your environment (use Ivanti Workspace Control Console [version].msi).

Please note that it is not possible to install an Agent-only and a Console-only installation side by side on the same machine. To go from a partial installation to a full installation, first uninstall the Agent-only or Console-only installation, then install the full Workspace Control.

When installing Workspace Control, the Setup Wizard will guide you through the installation process.

  • After reading and accepting the End-User License Agreement and specifying the installation folder, you will be asked whether you want the Workspace Composer to launch the next time someone logs on to the computer. If you have not yet created a Datastore, select No, I will configure this later in the Management Console. This option is not available for installations on Terminal Servers and with Console-only installations.
  • After the installation of Workspace Control has completed, the Connection Wizard will start. This wizard helps you to connect the installed Agent to a Workspace Control environment.

Workspace Control is an End-User Workspace Management Product. Its brand purpose it to balance flexibility and control of the User workspace by means of Profile, Policy and Access Control management. The Workspace Control Agent has been designed and tested to operate on both Single and Multi-user platforms (See Maintained Platform Matrix) to secure, manage and customize the End User experience. We do not recommend running the Workspace Control Agent on Servers that operate Mission critical roles such as that of a Domain Controller. To deliver the aforementioned end-user experience, the Agent loads various drivers, hooks processes and intercepts system calls. Whilst these operations are all managed by means of configuration, they do have the potential to disrupt mission critical operations and therefore should not be in use on back-end operational servers.

  • Installing the Workspace Control Console, Datastore, and/or Relay Server on a domain controller is not recommended as this may cause performance issues and unexpected behavior.
  • Ivanti installation files are signed with certificates. Microsoft Windows tries to verify a certificate’s validity before installing software products. This process (Certificate Revocation List (CRL)) is run to check to see if a certificate was revoked because it was expired or compromised. This process is not unique to Ivanti and is something that happens for any product that contains a certificate and is run on Microsoft Windows (unless CRL is turned off which is not recommended by Microsoft). It is also possible under specific cases that a CRL check is done during process startup. An example of this is when the Workspace Control Agent Service is configured to connect to a Relay Server, it will perform a CRL validation on startup. A logon could potentially be delayed if the environment does not use a Corporate/Enterprise license and the user attempts to logon immediately after the restart of the computer or the service, before the CRL check has been done.
  • On computers without Internet access, the CRL validation may cause a delay of, for example, 20-30 seconds before an installation starts. This is by design of Microsoft Windows. To avoid this delay to occur, make sure machines can connect to the Internet. If this is not possible, implement a (manual/automatic) distribution system to keep the publisher's certificate revocation lists up to date.
  • For new installations of Workspace Control, the file capicom.dll will be installed if it is not yet present on the machine on which you install Workspace Control. Capicom.dll is a third-party component, supplied by Microsoft.
    The Capicom component version 2.1.0.2 (available at https://www.microsoft.com/en-us/download/details.aspx?id=3207) included in this Workspace Control release, is subject to the Microsoft Software License Terms, Microsoft Capicom, which solely govern End-User’s use of that component. By installing Workspace Control version 2020.0 on a machine on which capicom.dll is not yet present, the End-User assumes and accepts sole responsibility of the use of the Microsoft Capicom component and compliance with the applicable license terms.
Also see