PMC will use HTTPS TCP port 443 to communicate with PMC managed devices
PMC managed devices will send "heartbeat" connections approximately every 30 seconds
Heartbeats allow PMC to keep track of devices which are online
- Each heartbeat is approximately 300 bytes sent \ 500 bytes received
In response to heartbeats PMC sends devices requests to execute management tasks such as retrieve FW updates or configuration changes
Related Articles
PMC 3.0, Start Guide
Overview This document is an extraction from the release notes of PMC 3.1.2. It covers everything you need to know, in-depth, regarding installation and deployment of PMC. It is always recommended that you use the current release notes of every PMC ...
Why am I getting 'Unsupported format of update package" message when I upload new firmware to PMC?
For PMC version 2.0.1 and earlier versions, there is a bug when you try to upload a new RX-series firmware image to PMC, PMC may display the following message: An easy work-around is to reboot the PMC appliance (no need to reboot the whole hypervisor ...
Where to get PMC Downloads
Where do I get PMC Software Downloads PMC software is provided as a virtual appliance compatible with VMWare ESXi, Citrix XenServer or Microsoft Hyper-V. PMC is also listed in Azure Marketplace. To obtain the latest PMC software virtual appliances ...
What is PMC?
OverviewNComputing PMC is an endpoint management system designed and developed to remotely manage NComputing access devices including LEAF OS devices (PCs/Laptops), RX420(RDP), RX-RDP+, RX-RDP and RX-300 thin clients. PMC is provided as a virtual ...
Log4J security patch update for PMC 2.7.0 and PMC 2.9.0 deployments
A new security flaw, known as ‘Log4Shell’, poses a critical vulnerability to millions of applications and devices across the globe. Log4Shell is a software vulnerability in Apache Log4j, a popular Java library for logging error messages in ...