none
Agent without fqdn RRS feed

  • Question

  • In our scom (1807) we have 1 windows agent that doesn't have a fqdn as displayname and networkname

    At 1st we focused on the DNS where reverse DNS was not ok. but after fixing that and reinstalling the agent it still returns without a domain in the name. I completely removed the agent, scom registry was gone and then installed the agent again.

    It is a domain joined server SQL server, and from the servers perspective all lookes fine.

    Does anyone know how scom determines what the displayname should be?


    Ronald

    Monday, November 18, 2019 12:27 PM

All replies

  • Its normally dependant on the default Windows Operating System Management pack, and using the class of Windows Computer Role uses the property for the network name.

    So you are seeing the server is being monitored but only showing a netbios name? Have you tried right clicking the view and adding some more properties to the view to see if you can see the FQDN?

    If your machine is joined to the domain with no issues, shouldnt really be anything to do with DNS


    Website: www.walshamsolutions.com Technical Blog: https://www.walshamsolutions.com/technical-blog Personal Blog: https://www.walshamsolutions.com/personal-blog Twitter: Dwalshampro

    Monday, November 18, 2019 12:34 PM
  • I don't think this issue depend on the OS managementpack. No it's not possible to fill attributes by hand luckally, neither do i want to, the system works fine for thousands of other agents so this is really an agent issue.

    In fact i already see a difference when i install the agent.

    In the install window i enter a fqdn and then in the results found i only see the hostname to install the agent on, so in that phase there is not even an agent on the server.

    I install this agent via a scom gatewayserver, from there resolving works fine.


    Ronald

    Monday, November 18, 2019 1:23 PM
  • So your not pushing them out through the discovery wizard? If you have thousands of agents that show the FQDN normally then sounds like it would be specific to that machine then.
    Do you get the same if you push the agent from the discovery wizard or are you only doing manual installs?

    Website: www.walshamsolutions.com Technical Blog: https://www.walshamsolutions.com/technical-blog Personal Blog: https://www.walshamsolutions.com/personal-blog Twitter: Dwalshampro

    Monday, November 18, 2019 1:33 PM
  • Yes i do use the discovery wizard, instead of selecting a scom managementserver i select a gatewayserver which belongs to the domain in which the agent is in. So in the discovery wizard i already see that something is wrong, since normally after discovery it will present an fqdn and now it presents only the hostname.

    Ronald

    Monday, November 18, 2019 1:45 PM
  • do you use certificate authentication with the gateway server and scom agents? Wonder if they are using just the hostname and not the FQDN on them could that be the issue?

    Website: www.walshamsolutions.com Technical Blog: https://www.walshamsolutions.com/technical-blog Personal Blog: https://www.walshamsolutions.com/personal-blog Twitter: Dwalshampro

    Monday, November 18, 2019 2:10 PM
  • The gateway is connected to scom via manually created certificates and between gateway and agent this is done automatically.

    I checked the local certificate store on the agent server and the gatewayserver but i dont see any leftover certificates of the scom agent.


    Ronald

    Monday, November 18, 2019 2:35 PM
  • the machine doesnt use anything like the hosts file or anything like that does it? The suffix is on the machine that applies to the domain?

    Website: www.walshamsolutions.com Technical Blog: https://www.walshamsolutions.com/technical-blog Personal Blog: https://www.walshamsolutions.com/personal-blog Twitter: Dwalshampro

    Monday, November 18, 2019 3:42 PM
  • Correct, hostfile is default and contains only localhost and dns suffix is set on the real domain.

    Ronald

    Tuesday, November 19, 2019 9:29 AM
  • quite strange. is there a computer account in AD? Have you tried dropping it out of the domain and re-joining back ?

    Website: www.walshamsolutions.com Technical Blog: https://www.walshamsolutions.com/technical-blog Personal Blog: https://www.walshamsolutions.com/personal-blog Twitter: Dwalshampro

    Tuesday, November 19, 2019 3:31 PM