MgsADSiteMatch: Match to Active Directory Site

FlexNet Manager Suite 2021 R1 (On-Premises)

Prerequisites

• The target inventory device is running Windows 2000 or later
• The target inventory device must be joined to an Active Directory domain
• Active Directory Sites and Services must be correctly configured.

This algorithm is particularly useful when the failover list includes a large number of inventory beacons (perhaps all the inventory beacons in your enterprise), and you want to restrict transfers to those within the same site that contains the inventory device. MgsADSiteMatch takes the following steps:

1. Identifies the Active Directory site in which this inventory device is a member.
2. Collects the list of selected inventory beacons from the preference settings (normally in the machine hive of the registry).
   • If the algorithm is in use by the launcher component of the FlexNet inventory agent (for example, collecting updated device policy), it collects the inventory beacon list from the preference DownloadSettings
   • If the algorithm is in use by the upload component, it collects the inventory beacon list from the preference UploadSettings.
3. For each inventory beacon in the list, it looks up the Active Directory site in which the inventory beacon is a member. You can restrict the domain controller used for these inventory beacon site queries using the localSiteDCOnly parameter (see below).
4. If the inventory beacon’s site is the same as the site for the target inventory device, the algorithm assigns a high priority. Where there are multiple such inventory beacons, their relative priority is left unchanged.
5. If the inventory beacon is in a different site than the inventory device, the behavior depends on the discardForeign parameter (see below).

MgsADSiteMatch (int limit, boolean discardForeign, boolean localSiteDCOnly)

where:

• limit is an optional integer setting the maximum number of inventory beacons to which priorities will be assigned by this algorithm.
• discardForeign is an optional boolean represented by the case-insensitive strings true or false. The default is false.
  • If false or omitted, the algorithm assigns a low priority to inventory beacons that are not in the same Active Directory site as the target inventory device. Where there are multiple such inventory beacons, their relative priority is maintained.
  • If true, the algorithm sets the priorities of any inventory beacons that are not in the same Active Directory site as the target inventory device to the string literal invalid. The launcher component and the upload component will not use such inventory beacons for transfers.
• localSiteDCOnly is an optional boolean represented by the case-insensitive strings true or false. The default is false.
  • If false or omitted, the algorithm does not require the domain controller used for inventory beacon site queries to be in the same Active Directory site as the target inventory device.
  • If true, the algorithm restricts the inventory beacon site queries to a domain controller that is in the same Active Directory site as the target inventory device. If there is no domain controller in the same site as the inventory device, the algorithm treats all inventory beacons as being in a different Active Directory site than the target inventory device.

Example of MgsADSiteMatch algorithm results

For target inventory device in Active Directory site: boston

Location	AD site of inventory beacon	AutoPriority	discard-Foreign	Incoming priority	Resulting priority
A	melbourne	true	false true	1	2 invalid
B	boston	true	false true	3	1 1
C	boston	false	Don't care	4	4
D	frankfurt	true	false true	2	3 invalid

In the above example, the algorithm determines priorities in the following way:

• Location C has AutoPriority set to false, so that it is excluded from the calculation process and its priority value of 4 is carried through unchanged.
• When the algorithm parameter discardForeign is false or missing, Locations A and D will be given lower priorities (with their relative order maintained). However, when discardForeign is true, both Locations A and D will be marked invalid because they are not in the same site as the target inventory device.