.png)
Changing the dashboards settings
When the Remote Edit Dashboard is installed, a 7FiveFive engineer will configure the dashboard for your environment, install all the required components and set it up in a way that lets you get started quickly. If your environment has changed or you wish to reconfigure the system it’s possible to do this on the settings page. The sections below will take a look at what each option does:
AWS
The AWS (Amazon Web Services) settings controls which machines are detected in your environment, how cost is tracked and more.
General: Enabled
This option controls if the AWS integration is enabled.
General: Region
Currently, the Remote Edit Dashboard can only access one region at a time. This control selects the region where the AWS instances are located. This option is populated by querying AWS for the region list, so if the list is blank, try running all tasks to refresh the cache, and then refresh the page. See the tasks page for more.
Instance classes
Instances are classified as ‘workstations’ or ‘infrastructure’ based on an AWS tag. This section provides details of what to tag your instances as to have them correctly detected by the system.
Billing and cost traffic: Only track these tags
When gathering billing and cost data from AWS, the dashboard can filter this data based on which cost tag the resource has associated with it. Only one tag key can be selected, however, multiple values can be selected from that key. See here for more information https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/cost-alloc-tags.html.
Required permissions
This section provides the minimum AWS IAM permissions required for all Remote Edit Dashboard components to function.
VMWare
The Remote Edit Dashboard supports multiple VMware vCenters. There must be one common user with API access to all required vCenters. The folder structures for edit VM’s must also be identical across all vCenters.
Enabled
Controls if the VMware integration is enabled.
FQDN or IP address for VCenter
This field is where the FQDN (fully qualified domain name) or IP address for the VMware vCenter should be entered. Multiple vCenters should be separated by a comma (,).
vCenter username
This field is where the username for the vCenter user should go. If using multiple vCenters, the credentials must be the same on all of them.
vCenter password
This field is where the password for the vCenter user should go. If using multiple vCenters, the user must have API access to all vCenters.
Ignore invalid SSL certificate
Quite often vCenters have self-signed SSL certificates which prevent the Remote Edit Dashboard from connecting. This control permits the use of self-signed certificates. If your vCenter has a valid SSL certificate, it’s recommended to leave this option disabled.
Instance classes: Edit workstations
Use this control to select the vCenter folder that edit workstations are located. If using multiple vCenters, only folders that have identical structures on all vCenters will be shown here.
Instance classes: Edit infrastructure
Use this control to select the vCenter folder that edit workstations are located. If using multiple vCenters, only folders that have identical structures on all vCenters will be shown here. This should be a different folder from the one selected in the edit workstations control.
Scan
When should a workstation be marked as available
This control is used to decide when a workstation should be marked as available in the Remote Edit Dashboard. This setting does not affect if the workstation is actually available. The options for this are:
When PCoIP is ready- When the Remote Edit Dashboard detects the PCoIP service is listeningWhen broker agent is ready- When the Remote Edit Dashboard detects the Leostream Broker agent service is listeningWhen PCoIP and broker agent are ready- When the Remote Edit Dashboard detects the PCoIP service and the Leostream Broker agent service are listening
Broker
The Remote Edit Dashboard currently supports the Leostream Broker for collecting and controlling workstations. Leostream Broker v8 and v9 are supported.
Enabled
Controls if the broker integration is enabled.
FQDN or IP address
This field is where the FQDN (fully qualified domain name) or IP address for the broker should be entered.
Username
This field is where the username for the broker user should go. It’s recommended to make a new user for the API to use. Ensure that the user is allowed to access the XML-RPC functionality of the broker.
Password
This field is where the password for the broker user should go.
Number of desktop licences
Some Leostream Broker licences are limited to how many workstations it can manage/have in its inventory. Enter the maximum number of desktops that your licence allows for in this field. If your licence allows for unlimited workstations (hosts) then click the ∞ infinity button on the right of the field.
Broker pools
The Remote Edit Dashboard can collect information about any broker pools which have been set up. In addition to this, if a broker pool is named in a specific format, the Remote Edit Dashboard can allow this pool to be used within a deployment template, so new machines are automatically deployed to this pool (See the Deployment templates page for more). The broker pool needs to be configured to automatically add workstations with hostnames that begin with a three-letter code. An example of a pool name that could be used in this way is:
_7FF-7FiveFive’s pool
The _ indicates this pool has been created for the Remote Edit Dashboard. The 7FF is the pool code that will be added to the front of the workstation’s hostname when it’s deployed via an instance template with a pool selected. The - acts as a visual separator. Finally, the 7FiveFive’s pool is the display name that will be shown in the Remote Edit Dashboard.
When broker pools have been found via the broker integration, they will be populated in the Broker pools table. It is possible to hide pools from the Remote Edit Dashboard interface by clicking the Show in stats button, if the pool has been named as mentioned in the last paragraph, it is possible to prevent this pool from being available for selection in the Deployment Template settings.
PCoIP
Number of concurrent session licences
The PCoIP licensing system makes use of a floating licence model. The Remote Edit Dashboard can track the number of active PCoIP sessions and deduct these from the number of PCoIP licences you have, specified in this field. For PCoIP licence tracking to be accurate, only workstations monitored by the Remote Edit Dashboard should use the PCoIP licence source (either a single cloud licence instance or a single licence server). If you do not wish to track this usage or receive any alerts regarding PCoIP licensing then click the ∞ infinity button on the right of the field.
Authentication
Active Directory/LDAP settings
The Remote Edit Dashboard supports Active Directory or LDAP domain for user authentication. When users log in to the dashboard with their domain credentials they will be assigned a role based on what domain user groups they are part of. If they are part of multiple groups with multiple assigned roles, the role with the most access is selected. Currently, this integration is limited to a single domain.
Enabled
Controls if the Active Directory/LDAP integration is enabled.
Server FQDN or IP
This field is where the FQDN (fully qualified domain name) or IP address for the domain controller should be entered. This can also be the domain’s DNS name.
Domain base DN
This field is where the distinguished name for the domain should go.
User search base DN
This field is where the distinguished name for the user OU (organisation unit) should go. This OU and all objects within it will be searched when populating the user list. The bind user must be within this OU otherwise the bind will fail.
Group search base DN
This field is where the distinguished name for the group OU (organisation unit) should go. This OU and all objects within it will be searched when populating the group list.
Bind user
This field is where the username for the user that will be used for the bind to the domain should go.
Bind user DN
This field is where the distinguished name for the user that will be used for the bind to the domain should go.
Bind user password
This field is where the password for the binding user should go.
Use LDAPS
By default, LDAPS is not enabled, as many Active Directory environments have not been set up for LDAPS. If your Active Directory supports this, then LDAPS can be enabled with this toggle.
Role mapping
In the role mapping section, it is possible to assign particular permissions to your Active Directory/LDAP user groups. By default, all groups are set to ‘Deny’ which will prevent login. Changing a groups role can be done by selecting a new role from the group’s drop-down box
App
Logging: Log level
This option will change the current logging level the application is using. This option is usually only required by 7FiveFive.
Health check: Connection manager URL
The PCoIP connection manager URL is used by the Remote Edit Dashboard to perform speed testing in most environments. This option defines which URL and port to use to communicate with the speed test API.
Health check: Support email address
This option defines the email address which is used when remote editor users select the ‘I’m still having issues’ option on the remote editor status page.
Licensing
The Remote Edit Dashboard is offered by 7FiveFive on a subscription basis which is tied to the support of the remote edit system. Usually, a 7FiveFive engineer will apply the licence for you, however, if you are asked to modify the licensing then see the information below:
Licenced to
Enter the business name or customer name in this field.
Installation ID
7FiveFive will provide you with an installation ID when a new licence is provided, this should be entered here.
Hardware ID
The licence provided by 7FiveFive is tied to a particular instance or piece of hardware. 7FiveFive may require you to provide your hardware ID before a new licence can be issued.