The Snow Inventory Server can be configured to do a network discovery using SNMP, SSH, WMI or DNS lookup. It will discover IP phones but will not necessarily report all of these as such.
This information will only be visible in the Snow Inventory Admin Console in the Devices views.
Also you can have a completely separate source of data that scans or get data from a file or a DB and then format it to be imported into Snow using the "Web Configurator" tool that comes with SLM.
I had a view on it for a customer, to get an compliance overview based on Telekom hardware I think.
At the end, there was no real benefit from implementing it into Snow. The customer was fine knowing where to get the data from and embedded a process to reviewed it regularly.
Let's see:
IP-Phones are not working on their own with no configuration - you need an infrastructure to run this. Find the management server and get some sort of report from it.
Also, they need traditional network infrastructure - any IP scanner run by your networking team can do it.
If they need Active Directory, you could use that as a data source.
Some IP-Phones come with some sort of companion software, which would be installed on the individuals computer. If so, that could be inventoried by the Snow Inventory Agents, and if there is a registry Value, Environment variable, you could transport that detail towards the snow servers.
Concluding: Define your needs and why you need that data, to find the easiest way to get it.
The Snow Inventory Server can be configured to do a network discovery using SNMP, SSH, WMI or DNS lookup. It will discover IP phones but will not necessarily report all of these as such.
This information will only be visible in the Snow Inventory Admin Console in the Devices views.
Also you can have a completely separate source of data that scans or get data from a file or a DB and then format it to be imported into Snow using the "Web Configurator" tool that comes with SLM.
Hi @David Baird​ , as @Axel Lamparth​ and @Samuel Baughan​ already mentioned, there is no direct and easy approach.
I had a view on it for a customer, to get an compliance overview based on Telekom hardware I think.
At the end, there was no real benefit from implementing it into Snow. The customer was fine knowing where to get the data from and embedded a process to reviewed it regularly.
Let's see:
Concluding: Define your needs and why you need that data, to find the easiest way to get it.
Cheers Oliver