It is recommended to discuss such an issue with the OS vendor (for example, Microsoft Support). If that is currently not possible, the workaround outlined below is available.
WORKAROUND:
1. Stop the FglAM instance that is hosting these agents (fglam01.domain.com)
2. Open the "baseline.jvmargs.config" file (fglam\state\default\config)
3. Set the following:
vmparameter.0 = "-Dquest.host.name=fglam01";
4. Save the changes
5. Restart the FglAM