How to use ‘Subnet Tags’ to assign devices to groups in PMC
Increasingly, the endpoint deployments happen outside of corporate networks. PMC Endpoint Management supports the concept of ‘Subnet tags’ to further differentiate device groups when managing devices across public Internet (i.e., not within corporate network).
Basic devices-to-subnets assignment (with empty ‘Subnet Tag’
values):
In the typical corporate deployment, where all endpoint devices are within the corporate network, the ‘Subnet Tags’ can be left empty. The basic devices-to-subnets assignment relays on the Ethernet or Wi-Fi and Visible IP addresses and network masks.
Use network addressing when assigning devices with a Subnet
tag value:
Ideal for deployments in remote offices, each with multiple endpoints connecting to PMC across the Internet.
This option should be selected when managing devices located in networks which are distinct, but use the same addressing schemas. Customers should select this option to be able to differentiate with the ‘Subnet Tags’ the deployment networks using the same network addressing, like 192.168.0.0/24.
Only use device Subnet tag value when assigning devices
to groups:
Ideal for deployments with working-from-home initiative. This option only uses the ‘Subnet Tag’ when assigning devices to groups (i.e. network addressing schema will be ignored).
This option should be selected when the ‘Subnet Tag’ (when specified) should be the only factor determining the Subnet affiliation of the device. E.g., customers with work-from-home users should select this option to have devices connecting from different home networks grouped together based on the Subnet Tag value.
In the above example, the Office users, whose devices do not have any ‘Subnet Tag’ values configured, will be grouped based on the Ethernet or Wi-Fi and Visible IP addresses and network masks only.
Related Articles
PMC Version 4, Start Guide
Overview This document based on the release notes of PMC 4.1.1. 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 version that ...How to Use Device Groups in the Management Portal
Introduction The Device Groups feature in the NComputing Management Portal simplifies device organization, license allocation, and deployment workflows. This article explains how to create and manage Device Groups and outlines the benefits of using ...Zero-Touch Onboarding with Device Groups in the Management Portal
Introduction Zero-touch onboarding enables brand-new NComputing thin clients to automatically connect to a designated PMC instance upon first boot — with no manual setup required. When combined with Device Groups in the Management Portal, this ...How to Create and Deploy the PMC Virtual Appliance
Overview NComputing 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. It is offered as a ...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 ...