Known Issue: Computer domain is blank by default and does not reflect output from hostname/domainname commands in inventory & usage data returned by installed agent on Unix-like operating systems (IOJ-1832862)

[#1]

Summary

The domain reported by installed FlexNet inventory agents from Unix-like operating systems is blank by default, even if a domain can be identified from system calls.

Details

The domain reported in files (such as inventory NDI files) generated by the inventory agent is controlled by the value of the ComputerDomain agent preference.

On Unix-like operating systems, the agent installer explicitly sets the ComputerDomain agent preference to a blank value in the agent’s /var/opt/managesoft/etc/config.ini file (unless a non-blank value is specified in the mgsft_rollout_response configuration file used to install the agent). As a consequence, no domain is identified for the device in inventory and other files generated by the inventory agent.

Note that the behavior of the inventory scanner (that is, not an installed agent) is different: this component will report a domain in inventory that is based on any domain identified in the output of the “domainname” or “hostname” comments.

Workaround

The internal agent preference OSComputerDomain contains the domain of the computer, as determined by various platform-specific systems calls. Setting the agent preference ComputerDomain to the value $(OSComputerDomain) will result in files generated by the agent reporting the system domain domains.

This can be achieved by including the following line in the /var/tmp/mgsft_rollout_response file used when the agent installed:

MGSFT_DOMAIN_NAME=$(OSComputerDomain)

Alternatively, execute commands like the following on a computer that already has the agent installed to change the current configuration:

cat <<EOF >tempconfig.ini
[ManageSoft\Common]
ComputerDomain=\$(OSComputerDomain)
EOF

/opt/managesoft/bin/mgsconfig -i tempconfig.ini

rm tempconfig.ini

Related information

See:

• Documentation for the ComputerDomain preference

Fix status

This issue has been fixed in the following FlexNet Manager Suite releases: 2022 R1.3 / Jul 2022 (Cloud), 2022 R2 (On Premises)

Other information

Affected components: Agent, Component installers

Master issue ID: IOJ-1832862

Also known as: FNML-75876

[anhpham1652]

Hello, thank you for the article. I have some questions

1) This solution is on mgsft_rollout_response so it is only available for machines where agent is not installed? Is there anyway for installed machine to automatically get the domain name?

2) What version of agent package will work? Is agent 17.0.1 (go with FNMS on-prem 2021R1) still ok? Will next-ver agent get this feature added or we have to use mgsft_rollout_response?

[ChrisG]

@anhpham1652 - the configuration described in this article through mgsft_rollout_response is for using at the time the agent is installed: the mgsft_rollout_response file is only used at installation time. If you want to change the configuration of an already installed agent, run the commands like what is described in the article above that use mgsconfig to update the current configuration.

This guidance in this article should work for all agent versions. See the "Fix status" section of this article for details about future plans - this information will be updated as any plans change.

[RayanKS]

Hi @ChrisG, I was informed by support that this fix would be available with agent version 19.X and it would be recommended to upgrade to both agent version 19 and FNMS 2022 R2.

[ChrisG]

@RayanKS - yes, that plan should get you to an agent version that contains the fix for this issue.

As per the details currently shown in the "Fix status" section of this article, the fix for this issue is first included in the following agent releases:

• For Flexera One ITAM (aka FlexNet Manager Suite Cloud): in the 2022 R1.3 agent release (which has a version number of 18.3.x), 
• For FlexNet Manager Suite (On premises): in the imminent 2022 R2 agent release (which will have a version number of 19.0.x).

[DiannaB]

What command(s) is the FNMS agent running to get the domain?  We added ComputerDomain=$(OSComputerDomain) to config.ini on a few Linux servers to test this, and it works on some and not on others.   Thanks!

[ChrisG]

@DiannaB - I believe the details come from system calls that are associated with the domainname(1) and hostname(1) commands. Check whether you see any domain details when running these commands.

[DiannaB]

@ChrisG Thanks for confirming the commands!