A SQL Server database is configured to use the FQDN (Fully Qualified Domain Name).
In the Agent Status Properties (ASP) of the database agent is the following:
monICHostName=HOSTNAME
monHost=myhost.subdomain.domain
In the agent log file was printed
INFO [DBSS-myhost.subdomain.domain.-INTB1W-highPriorityPool-1] com.quest.qsi.fason.sqlserver.agent.SqlServerAgentData - Physical host name changed from null to HOSTNAME
Since the user does not want to use the short hostname, the parameter was disabled.
If the osUsePhysicalHostName=0 , the SQL Server agent will use the SQL Server Host (monHost=myhost.subdomain.domain) as the hostname for the OS connection, otherwise else it will use the short hostname which comes from database from this query:
Select ServerProperty ( 'ComputerNamePhysicalNetBIOS' ) as host_name
Users can find the FQDN name in the OS collection log.
INFO [DBSS-myhost.subdomain.domain-lowPriorityPool-1-[DBSS_Maintenance][]] com.quest.glue.core.services.AgentEstablishedConnectionStore - Established a PoolableWMINativeConnectionImpl connection to myhost.subdomain.domain [root/cimv2]
The SQL Server agent will also use the short hostname "HOSTNAME" which come from the database to create the Infrastructure (IC) agent
WORKAROUND
Contact Support for hotfix HFIX-502 for this issue.
STATUS
Enhancement ID FOG-9787 was logged to create Windows agents using the FQDN (Fully Qualified Domain Name). This will be included in an upcoming release of the SQL Server agent.
Note: The resolve of the physical hostname to FQDN will work only if the FglAM machine is configured with the organization’s DNS server
© 2025 Quest Software Inc. ALL RIGHTS RESERVED. Termini di utilizzo Privacy Cookie Preference Center