Release Notes

Welcome to the July 12, 2019 release of the Cloud Access Connector for Google Cloud, AWS and On-Premises. This release includes the following updates:

AD groupName is no longer case sensitive 

The groupName defined in the Active Directory query was case sensitive. It would treat the value as a Distinguished Name or Group Name based on the string "DC=domain,DC=local".
If the value is provided with the incorrect case, then queries to the Active Directory may fail, and logging into the Management Interface on the Cloud Access Connector may fail.

This is no longer the case. If this error occurs, then download the latest Cloud Access Connector and try installing again.

PCoIP Agent state can be provided to clients

The list of resources (PCoIP Agents) a user can connect to after they have authenticated
using a PCoIP Client, can be sorted or display information on the state of the PCoIP Agent.
This feature is disabled by default on the Cloud Access Connector.
Users with a large number of resources assigned to them may experience a delay in the listing of the resources in their clients. If retrieval of the state of any resource takes too long, then the list will return and the state will be described as unknown.

To enable the determination of the state, when installing the Cloud Access Connector provide:

• --retrieve-agent-state for Cloud Access Connector v2

and provide the value true.

The Cloud Access Connector can be configured to send the state description of the resource in the name of the resource by passing the parameter:

• --show-agent-state for Cloud Access Connector v2

and pass in the value true.
This parameter only updates the name with the state if the Retrieve Agent State parameter is also set to true.

For more information see the administration guide for your version of the Cloud Access Connector.

Explicitly specify domain controllers during install or upgrade

Users can optionally specify one or more domain controllers to use with the Cloud Access Connector by providing the --domain-controller option with the install or update commands.

For example (other required options elided):
 

sudo ./cloud-access-connector install --domain-controller dc1.domain.com [--domain-controller dc2.domain.com]

Multiple domain controllers can be specified by providing multiple --domain-controller options. If domain controllers are explicitly provided like this, the Cloud Access Connector will only use these domain controllers when authenticating users or syncing user and computer information to CAM Service, regardless of whether other domain controllers are available.

Important: If provided, the domain controller must be specified as an FQDN (fully-qualified domain name), not an IP address.

DNS error during interactive installation resolved

During an interactive installation of the Cloud Access Connector the following error occurred:
[2019-07-10T20:17:30Z] DEBUG lookupDC: lookup _ldap._tcp. on 127.0.0.53:53: no such host
[2019-07-10T20:17:30Z] ERROR A DNS error occurred. Please verify the DNS configuration on your connector.

If this issue occurs, download the latest Cloud Access Connector and try installing again.

Configurable user and computer Active Directory DNs

The configuration settings on the Cloud Access Connector for configuring specific DNs when querying Active Directory for users and computers when running the install command.
This permits existing deployments to be updated with new DNs without requiring a fresh install.

The options are:

• --users-dn The base DN to search for users within AD. This option may be specified multiple times to provide multiple DNs.
• --computers-dn The base DN to search for computers within AD. This option may be specified multiple times to provide multiple DNs.
• --sync-interval The interval (in minutes) for how often to sync AD users and computers with CAM Service. Must be at least 5 minutes.

These options may be provided to the install command.

Note, this configuration is applied to the entire deployment. All connectors in a deployment will get this configuration, and the last connector to set this command will set the setting for the entire deployment.

Certificates can be replaced during a connector update

The certificate on the Cloud Access Connector can now be replaced when the connector is being updated.
sudo ./cloud-access-connector update --ssl-key key.pem --ssl-cert cert.pem

Alternatively, during an update, the self-signed certificate can now be recreated.
{{ sudo ./cloud-access-connector update --self-signed}}