vladimirsp asked a question.
Hi, What could the problem is windows agent 6.7.0 starts working (scanning and sending data) after we open snowagent.exe as administrator ?
We are using Snow agent 6.7.0 for windows machines. Deploying them using Active Directory.
Agents deploys successfuly, but it only starts scanning computer and sending data to inventory server if we open snowagent.exe (c:/program files/snow software/invnetory/agent) as Administrator. After that agent starts to work properly and send data.
If we do not do that, agent is not working.
What could cause this problem ?
Best regards,
Vladimirs
Hi Vladimirs,
in general, after installation of the agent using the MSI, it does not send data instantly. There is a randomized delay of 90 minutes (default) that seems to allpy after installation as well.
When we deploy agents using software deployment packages, I usually advice the administrators to execute a "snowagent.exe scan" and a "scnowagent.exe send" directly after the installation.
If we do not execute these commands, the computer appears in snow invventory greyed out with the status "no inventory send yet".
So, it basically depends on what you mean by "Deploy them using Active Directory".
Kind regards,
Axel
Hi,
I mean that we create GPO, add .msi package, chooses devices where the agent will be installed. After deployment we can see that agent is installed on those computers.
We waited for a month just to receive those devices in inventory but they did not report at all. Those computers are turning on and off every day so the snowagent service should start by itself and start scanning computers.
After 1 month we ran snowagent.exe as administrator and the next day it started to work.
The thing is that we have to deploy those agent to 1000+ devices and it is not a solution to connect to every computer and run snowagent.exe as administrator for it to work.
I just want to understand where could be the problem - in agent itself or GPO settings...
hi - in my experience this tends to be a proxy/networking issue... The admin will have rights to send to the internet, the agent local service account may not... check the firewall to see if you can see the traffic hitting the firewall/proxy and not being allowed through....
I would check start by checking the log file on such a client, default under C:\Program Files\Snow Software\Inventory\Agent\Data named snowagent.log. Agent is started as a service and that should run in local system context. Is it running? What is your schedule entry set in the snowagent.config file. Default is like this
Our log file look like this when it is working (we have info as log level, default is just warning which is not useful when you need to figure out what is going on)