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.