Unassigned subnets - why manage them?

[adamgalbreath]

I was asked for Flexera's insight into why should Unassigned subnets be managed?   What could happen if there are Unassigned subnets?

The environment is FNMS-Cloud

Inventory Data Sources:

• SCCM
• FlexNet Agent on all servers (Physical / Virtual)
• Active Directory
• vCenters
• 6 Beacons (around the globe)
• IBM PVU scanning enabled
• Citrix XenApp
• O365

Tier 1 publisher licenses being managed:

• Microsoft
• IBM
• Oracle

[kclausen]

This view shows all of the Sites/Subnets that have been imported from Active Directory that are not assigned to a beacon.

This is only important if you have created specific Discovery Targets/Actions/Rules to be executed by a beacon (Remote Inventory, vCenter, Oracle VM, etc.)  The specific devices/IP Addresses in your defined Targets must be "managed" by assigning them to a beacon.

Based on the overview of your environment, the only Sites/Subnets that need to be "managed" by assigning them to a beacon needs to be your vCenter Servers defined in your Targets.

[adamgalbreath]

Thanks Kirk.

Would a best practice be to always managed Unassigned subnets so the Management Dashboard shows "0" ?  

[steven_donovan1]

Adam I would say yes, but if the customer is not using any remote targeting they can just ignore the message.