Group Policy Object (GPO) template

URL for Remote Desktop Server includes *.admx and *.adml administrative template files. These template files allow to configure the product via Local GPO and/or Domain-Based GPO. Please refer to Microsoft MSDN article on managing ADMX files.

GPO Editor

The archive file containing administrative template can be found in the installation directory: 

%ProgramFiles%\FabulaTech\URL for Remote Desktop (Server)\policies.zip

Additionally, the administrative template files are deployed to a local GPO during product installation and can be found here: 

%WINDIR%\PolicyDefinitions\Fabulatech.admx
%WINDIR%\PolicyDefinitions\fturlrdpsrv.admx
%WINDIR%\PolicyDefinitions\en-US\Fabulatech.adml
%WINDIR%\PolicyDefinitions\en-US\fturlrdpsrv.adml

It's recommended to use the GPO template files provided with the latest product version of URL for Remote Desktop Server.

The GPO template can be used to configure the following settings:

Setting Description
Licensing

This policy setting is used for licensing management. The following licensing modes are used:

License key
use the specified license key for each product server;
License server
use a license server for centralized management of licensing;

For "License key" type of licensing you must specify a string of the key in the corresponding field.

For "License server" type of licensing you must specify a license server name in the name_or_ip:port format, where the port is an optional parameter.

If this policy setting is enabled, the licensing mode will be overridden by this policy setting. It means using GPO License key instead key that determined via the settings interface.

If this policy setting is disabled or not configured, the licensing mode is determined via the settings interface.

Log file rotation

This policy setting controls advanced log file rotation behavior. The product may create multiple logs for each user, depending on factors such as Session ID, Process ID (PID), and FabulaTech product module. Each log is stored on disk as a set of log file parts, which are created as the log is rotated. When the active log file part reaches the configured size limit, it is rotated: the current file part is renamed, and a new empty file part is created for the same log. If any of the configured limits are exceeded, the oldest log file parts are automatically removed according to the configured rules.

Maximum log file part size (per file), MB
Range: 50-1000
Specifies the maximum size, in megabytes, of a single log file part. When a log file part exceeds this value, the file is rotated and a new file part is created for the same log.
Maximum log file parts (per log)
Range: 1-99
Specifies the maximum number of log file parts allowed for each individual log. If this limit is exceeded, the oldest file part belonging to that log is removed. If set to 1, only a single log file part is kept. When the maximum file size is reached, the file part is overwritten.
Maximum log file parts (global)
Specifies the maximum total number of log file parts stored on disk across all logs and all users. If this limit is exceeded, the oldest log file parts are removed, regardless of which log they belong to. If 0, no global limit is applied; an unlimited number of log file parts is allowed.

If this policy is disabled or not configured, log file rotation behavior is controlled by the application’s internal log rotation settings.

Log level
Log Level
Range: 0–10
This policy setting configures the log level, which determines which events are written to the log files. This setting is intended for troubleshooting purposes and is typically enabled at the request of the FabulaTech technical support team.

The following values are supported:

  • 0 - Error
  • 1 - Warning
  • 2 - Information
  • 3 - Debug
  • 4 - Dump
  • 5–10 - Reserved

If this policy is disabled or not configured, the log level is controlled by the application’s internal logging settings.
Open custom protocols on the Workstation side

This policy setting specifies a list of custom protocol URLs (typically associated with Windows applications) that must always be opened on the local Workstation using their associated applications.

Example: 

msteams
zoommtg
zoomus

If this policy setting is used for the computer, it overrides the policy setting for all users of this computer.

Open files on the Workstation side (by extension)

This policy setting specifies the list of file extensions that, when launched, will always be opened on the local (Workstation) side.

Each file extension must be entered on a new line.

Example: 

DOC
DOCX
XLS
XLSX
PDF

If this policy setting is used for the computer, it overrides the policy setting for all users of this computer.

Open HTTP and HTTPS URLs on the Workstation side

This policy controls URL redirection based on URL masks. You can choose to redirect all URLs, only those matching specified patterns, or exclude certain patterns from redirection.

URL Matching Mode
This setting defines how URL masks control redirection:
  • Disabled – Redirects all URLs.
  • Whitelist – Redirects only URLs matching the patterns in the URL Mask List.
  • Blacklist – Prevents redirection of URLs matching the patterns in the URL Mask List; all other URLs are redirected.
URL Mask List
The list contains patterns (URL fragments) that determine which URLs are matched. Use the * character as a wildcard to represent any number of characters. Empty entries are not supported.

Examples:

www.example.* – Matches any URL containing www.example. Examples: www.example.com, www.example.domain.net

*.domain.com – Matches any subdomain of domain.com Examples: www.domain.com, api.domain.com Does not match: domain.com

site.internal/db/ – Matches URLs under the /db/ path. Example: www.site.internal/db/page.html Does not match: www.site.internal/page.html

https://www.company.com – Matches only the HTTPS version of the URL. Example: https://www.company.com Does not match: http://www.company.com

URL for Remote Desktop Server User Manual