JoannaJankowska asked a question.
Hi all,
Does anyone know what is the difference in the amount of information transmitted by network discovery using different protocols? I know that the SNMP protocol gives the most information, but what is the difference in the others? Using which protocol gives the least amount of information when a device is detected on the network?
Kentaur77 asked a question.
Last week we had to do a reinstall on ALL our machins of the Snow Inventory Agent (we had an old version and the newest version on at the same time, it was a mess)
Now one of our software suppliers want to do an audit and the Snow Inventory agent has not started reporting in any data on the systems that we have done the reinstallation on.
Is there a way to force the software to report in faster?
Hi @Peter Månelin​
Sorry that the Snow Globe community wasn't able to answer your question. Did you manage to find the solution? If not you may want to contact the Support team for advice: https://community.flexera.com/s/support-hub
Best wishes
Karen
DavidH asked a question.
Hello,
I'm still investigating, but we're having trouble installing SIS 6.8.2, and getting a SQL error every time:
I just wondered if everybody else is having this same problem? I'm guessing I'll be logging a support ticket though...
David
I could install 6.8.2 successfully in one environment.
But this time it took around 30 minutes instead of less than 1 minute as usual
MWuendisch asked a question.
I've found a very helpful Snow documentation about " How to move databases ..." But what about the Snow Master Server Installation (or SLM Installation) if the underlaying Server will be changed! Do I have to reinstall the Snow Master Server (or SLM) ? What about the existing databases ? Are the Installer prepared for that purpose?
Best Answer
Hello,
If you are planning to migrate your Snow Inventory Server to another server, than its pretty simple solution. As you just need to take your license key for Snow Inventory and have connection to DB server, and you can do brand new installation of Snow Inventory on that server. You dont have to restore database, as Snow Inventory installation will recognize that you already have Snow Inventory DB on your SQL once you put SQL informations to installer GUI. So that part is pretty simple. Of course you need to ensure that everything is properly configured, but migration itself is pretty simple.
Regarding Snow License Manager, there you need to take backup of your Snow License Manage DB, than remove that database / rename if required. And you need to do brand new installation of SLM on new Windows server, that will create again Snow License Manager DB and after installation process finish, you need to restore new DB with backup that you have taken. it includes few more steps as you need to ensure that you first update your SLM to version which your previous SLM had to ensure you dont create any errors. But both migrations are pretty simple.
As Jordan says - I'd recommend going through Snow Professional Services or your Snow Partner if you have one to assist. It's unfortunately not as easy as just lifting and shifting, especially if you're migrating your databases as well.
There's a lot of things that can go wrong, and in some cases you actually need to install it on the new server, upgrade Inventory to the same version as your current one and THEN migrate the database over. You can't just migrate the database and install Snow Inventory 6, as the versions may be different and it'll have a version mismatch and stop working.
If you're also then going down the route of migrating Snow License Manager, that's an even bigger task and there's a few pre-reqs involved like getting a new license key since it's locked to your current 2016 Server HWID.
AshishP asked a question.
Hi Folks,
Network Discovery not working outside of the interface's subnet. Network discovery configured with IP address ranges outside of the interface's subnet. Where we can see log file if there is any error?
We are using Snow Inventory Server v6.6.3
It seems, you must open up at least the following ports:
"... discovery feature, uses multiple protocols, and they use the default address for those LDAP: TCP 389 SNMP v1: UDP 162 SSL: 443 WinRPC\WMI: TCP 135,445 + 1024-1034 dynamicly ICMP: TCP 7"
Citation is taken form one of the following posts which may help you in digging deeper on how to do/configure the network discovery and the headaches associated with it.
https://community.flexera.com/s/question/0D51r00008OrDNyCAN/network-port-diagrams
https://community.flexera.com/s/feed/0D51r00008PwuEvCAJ
Because we almost never managed to convince security to open up all those ports and because you _never_ know, if you really had access to all segments this way the value of the network discovery is very 'questionable'.
I personally prefer to match the list of devices with agents reporting into snow to Lists from CMDB, Antivirus, Firewall-logs, etc to narrow down the gap between 'Devices-with-Agents' versus 'Devices known but still need an agent deployed'.
suri asked a question.
Hello Community,
Can someone help me to understand the timeframe of the Not Reported devices in the inventory status. and do we need to delete this manually or can we configure this for auto-deletion.
Please refer to the below snippet, not reported devices are stuck for 4-5 months.
Hi,
the "not reported" computers, also listes in the devices kind of "greyed out", are computers that have the agend installed but did not send inventory data yet.
This happens, for example, install a new computer including the Snow Agent, then switch off the computer and ship it to a homeoffice user with no connection to the Snow Inventory Server.
After installation, the Snow Agent will send a heartbeat, but will scan and send within the next 90 minutes (by default).
These devices will not disappear but will also not show up in the SLM web ui.
So you should track these devices.
Another possible cause is, that the SnowAgnet is installed onto a computer and the computer is renamed, before the scan and send happens. In this case, the "not reporting" computer can be deleted, as it will report under its new name.
My recommendation always is, to run a "snowagent scan" and "snowagent send" instantly after installation.
Hope this helps,
Axel
PiotrBraun asked a question.
We have agents installed in the segregated area and we cannot send snowpacks directly through the Service Gateway to the Master inventory Server. We do it via Standalone Receiver - from where we manually transfer files to Master Inventory Server. Anyone have an idea how to automate this process without installing Service Gateway?
We could probably make a powershell script that would dump data from the Standalone Receiver directory to some shared directory, and then another script on the Master Inventory server would transfer files from the shared directory to the Master Inventory Server directory.
Are there other ways to automate that?
Is this other network segregated from the Master Server by lack of network routing of the Master servers port, as if file copying is still open and all it's associated ports the networks are not segregated.
In a truly segregated network it would be USB stick time from one server to another.
Also if file copying is open port wise - you could look to have the files dropped on the Standalone Receiver but also sent by the Agent to a file drop location on your actual master server.
You still need the standalone receiver as at this time the agent can't use the file drop functionality without some form of HTTP(s) response from an INV server of any type
SamuelBaughan asked a question.
In the Snow Inventory Server SMACC User Guide, there is this paragraph.
Anyone knows what this is for exactly? When would the Inventory Server process TXT and EXE files?
I'd be interested as well as one would expect only .snowpacks and .inv to be accepted. I am wondering what the use case would be to accept other file formats?
Hey Joanna,
please have a look here Discovery view (snowsoftware.com)