Showing results for 
Show  only  | Search instead for 
Did you mean: 
Engaged Sweeper
We are using the lspush utility to gather information from a number of segregated networks and importing it into the one database.
The problem we have is that some of these networks have machines with the same hostname (but different IP address). When we import the lspush result, it will overwrite the existing machine with the new one.
Is there a simple way to avoid this and mark them as 2 unique machines?
Also is there a report which I could run (or write if I knew where to look) which shows when this has happened?
Over time we will correct the machine names so that they are unique as the networks will eventually be joined.
Lansweeper Alumni
Yes, you could probably detect the overwrite through the history tables. You could look for changes in tblComputerSystemProducthist for instance.
This wouldn't help in terms of separating the machines however. A lot of tables do not have a counterpart with historical records. The only way to really solve the problem is by renaming the machines.

Report listing computers that underwent changes to the Win32_ComputerSystemProduct WMI class:

Select tblComputers.Computername, tblComputers.ComputerUnique,
tblComputers.Domain, tblComputerSystemProducthist.IdentifyingNumber,
tblComputerSystemProducthist.Name, tblComputerSystemProducthist.UUID,
tblComputerSystemProducthist.Vendor, tblComputerSystemProducthist.Version,
tblComputerSystemProducthist.Lastchanged, tblComputerSystemProducthist.Action
From tblComputers Inner Join
tblComputerSystemProducthist On tblComputers.Computername =
Order By tblComputers.ComputerUnique
Engaged Sweeper III
I am still very new to Lansweeper but I have a thought on detecting this issue. Would something show up in history each time one machine scan overwrites something from the other machine with the same name? You could then probably create a report looking for machines with more than x number of history records added over the past day or week.
Lansweeper Alumni
The only way to fix the issue is by renaming the machines unfortunately, and assigning them a unique name.