Supported virtual machine environments:
Supported NComputing access devices:
NComputing PMC is a device management system designed and developed to remotely manage NComputing access devices. PMC Device Management provides simple and powerful device management for RX300, RX-RDP, RX420(RDP) and LEAF OS thin clients. PMC does NOT support RX-HDX nor RX420(HDX) (Citrix) thin clients.
Number of available PMC licenses depends on managed device model and associated AMP (Annual Maintenance Program) status:
Following are the important points to consider before and during PMC installation:
Below is some general information about how PMC works:
- Each device managed by PMC must belong to a Subnet. Subnets will be identified by Subnet IP address, Subnet Mask and device’s Visible IP Address. Subnets exist in Subnet Groups. When a device from a not yet known Subnet connects to PMC, then PMC creates the Subnet automatically and puts it into the ‘Auto-created Subnets’ Subnet Group.
- Subnet Groups can be created manually and the Subnets can be moved between Subnet Groups.
- Subnets can be created manually too, even before the first device from the Subnet will connect to PMC.
- A Visible IP Address and Visible IP Address Mask can be specified when creating a Subnet. The Visible IP Address can be used to differentiate NAT-ed Subnets using the same local IP addressing.
- PMC allows assigning device profiles at several different levels: Organization, Subnet Groups, Subnets, Name Scopes, Asset Tag-based Groups, Manual Groups.
- Profiles for different device families/models and different configuration versions of the same model can be assigned at all levels.
- Profiles do not need to contain all device settings. Only the necessary subset of settings can be defined in each profile.
- When a device model using particular configuration version connects to PMC, PMC merges settings from all profiles matching the configuration version used by the device, to create the effective configuration. Effective configuration will be sent to the device.
- Settings merging (to create the effective configuration) happens in the above mentioned order: first the settings from appropriate (matching device's family/model/version) Organization's profile will be taken, then from the Subnet Group (which reflects a site or geographical location) the device belongs to, then from the Subnet, and so on. Settings from profiles assigned at Organization level are the most global (as all connected devices belong to Organization group), thus things like branding (desktop wallpaper) or CA certificates (for 802.1x network connections) should be contained there.
- If same settings are defined in profiles assigned at different levels, then the settings from profiles assigned at more specific (lower) level overwrite settings from more general (higher) level, e.g. settings defined in a profile assigned to a Subnet Group overwrite settings from profile assigned at Organization level (if same settings but with different values exist in both profiles). Settings from a profile assigned to Subnet overwrite settings from profiles assigned to Subnet Group and Organization, and so on, up to Manual Groups.
- PMC assigns devices to Name Scopes (inside Subnet) by parsing device name and matching it with device name pattern defined for the Name Scope.
- PMC assigns device to Asset Tag-based Groups by checking the value of the Asset Tag reported by the device.
- Devices (inside Subnet) can be manually assigned to Manual Groups.
- Name Scopes, Asset Tag-based Groups, and Manual Groups can be used when some specific settings need to be provided to a specific groups of devices (e.g. belonging to organization's department, building floor, room, etc.).
- Device saves locally the configuration received from PMC. This configuration will remain active even if the device will lose PMC connectivity.
- If devices belonging the same department in Organization's structure exist in different locations (Subnet Groups) then the same profiles with department-specific settings can be assigned to Name Scopes, Asset Tag-based, or Manual Groups created under different Subnets.
Please follow the below procedure to update an older PMC version to version 2.5.0:
- Automatic profiles upgrades after uploading schema files with definitions of new device configuration versions.
When multiple upgrade paths exist, e.g. in case when existing profiles for multiple older configuration versions can be upgraded, the administrator will be able to select which profiles and to which configuration version should be upgraded. The upgraded profiles can be automatically assigned to the same device groups, where the original (old) profiles were assigned.
- Manual profiles upgrades after uploading schema files.
The upgrades can be performed with the Upgrade task of the Device Profiles list.
- Automatic profiles upgrades when restoring a backup containing profiles created for older configuration versions.
In this case the profiles will be automatically upgraded to the latest available configuration version only. The upgraded profiles can be optionally assigned to the same device groups where the original profiles were assigned.
- Automatic upgrades of configuration edited directly on specific devices.
When the device configuration was edited in the past directly on a device when the device was using some older configuration version, then PMC will automatically upgrade the edited configuration to device’s current configuration version when the device will report a newer configuration version during check-in.
Workaround: The below steps must be followed to update the RX300 3.1.3 firmware to a newer version:
systemctl stop firewalld
After this change PMC will create the firmware download URLs using the modified Base URL. This will allow the devices running the 3.1.3 firmware to successfully download and update the firmware.
To revert the changes after completing firmware updates on all devices do the following:
systemctl start firewalld
Note: This issue was specific to RX300 device with firmware version 3.2.7 or older. Newer RX300 firmware versions correct this issue automatically during firmware update. NComputing strongly recommends updating all devices to latest available firmware version before starting to manage them from PMC.
Note: This is a problem on the Management Portal side which will be fixed there.
Workaround: For the time being please use other browsers for accessing PMC, like Google Chrome or Mozilla Firefox.