How to overwrite Hostnames?

[Alex Kodnar]

Hey.

I´m currently testing Jira, Insight and Discovery for our Company, because we want to implement a CMDB. 

One use case I couldn´t handle with Discovery is the following:

If the hostname of a Client changes, Insight imports this host as a new (second) host, although the Serial-Number, MAC-Adress and many more attributes are identical.

So I tried to set the attribute Serial-Number for Hosts unique. When the next Discovery import was ready, Insight indeed recognized that the Serial Number is already in use, but didn´t overwrite the name of the Host but rather just declined it with an error.

Do you have any hint how to solve this?

Thanks a lot.

[Christian_Solle]

Hi,

in that case the Host in the import result will be ignored.

You can do the following:

The Discovery-Tool has a file called ObjectHashSettings.xml

edit this file and change the following from

<HostInfo_Hostname>true</HostInfo_Hostname>

<HostInfo_FQDN>true</HostInfo_FQDN>

to

<HostInfo_Hostname>false</HostInfo_Hostname>

<HostInfo_FQDN>false</HostInfo_FQDN>

Now the Hostname (and FQDN) will be not used when the Hash of the HostObject is build.

Also don't forget to revert your attribute change in Insight.

PS: Why is the Hostname changing? It shouldn't change.

// Christian

[Alex Kodnar]

Hey Christian!

Thanks for the fast answer.

I edited the file and reverted the attribute change.

Now, I have the same host in my Insight twice again, just with different hostnames. 

But I want Insight/Discovery to recognize that this host already exists, only with another hostname and overwrite the name. 

And to answer your question: Sometimes PCs switch departments and in that case we also adapt the hostname.

[Christian_Solle]

I am sorry I forgot to say,

that if you change the HashSetting and you will get "new" Hashes

this will result in "new" Objects. You need to delete the old ones.

Also when you updating the discovery-tool the updater asks you if you want to overwrite the ObjectHashSettings.xml file.

You need to choose "No" be aware any changes to that file will result in "new" Objects.

// Christian

[Alex Kodnar]

Alright, thanks a lot. I´ll apply a new object-schema and try again :)

[Alex Kodnar]

It worked now. Thanks a lot Christian!