Known Issue: Subnets may not be imported from Active Directory if multiple domains have sites with the same name (IOJ-2250453)
Known Issue: Subnets may not be imported from Active Directory if multiple domains have sites with the same name (IOJ-2250453)
Summary
If details from multiple Active Directory domains are imported and those domains have sites with exactly the same name, then some of the subnets configured in the domains associated with those sites may not be imported.
Details
This issue occurs because the site name is used as a unique identifier when processing data from Active Directory Sites & Services. Consequently, subnet details from sites with the same name from separate domains may overwrite each other.
The exact subset of IP addresses that appear may change over time in a way that is difficult to predict. It will be based on which domain data has been imported from most recently, and what changes have occurred in the domain's Sites & Services configuration since the last import.
Workaround
Add missing subnets manually to subnets configured in FlexNet Manager Suite / Flexera One ITAM.
Fix status
This issue is still open but not currently scheduled to be addressed.
Other information
Affected components: Integration: Active Directory
Tip: If you have been impacted by this issue, please click the KUDOS button above. This helps to track the relative significance and importance of issues. Clicking on an option against "Was this article helpful?" also helps assess and improve the usefulness of content.
