Is there a way to replicate or archive the incoming SNOW Agent Inventory files on the SNOW Inventory Server? as this will help to understand we have received the agent inventory output files and use it for analysis & troubleshooting.
one thing that pops up to my mind (without being tested, anyway, just an idea), would be to add one or more drop locations. A drop location represents an additional location for delivery of the scan result. It can be network folder, an HTTP endpoint, or an UNC file path. If several one drop locations have been defined, the scan result will be sent to all of them.
The question is: as the snowpack files are encrypted and with a "random" name, not linked to the actual computer name, would it be really useful?
Just a thought.
Ester MemoliCustomer Success Manager EMEASnow Software srl - Milano - ItaliaAre you a SLM user and are willing to answer to a short survey about it? SLM Survey extended! Deadline is now 31st July!
we did set up a separate incoming folder where the .snowpack files are dropped and then by a scheduled task which runs each hour we copy the .snowpack files to the processing folders on our PRD, ACC and TST environments. The last action is not a copy but a move so the incoming folder is emptied again. That way those three environments have the same agent data input. You can arrange this in the Inventory snowserver.config file. E.g.:
<Server> <SiteName>yoursitename</SiteName> <IncomingFolder>X:\Program Files\Snow Software\Snow Inventory\Server\SnowDuplication\Source</IncomingFolder> <BaseAddress>https://yourbaseaddress.xxx.com:443</BaseAddress></Server><DataProcessor> <IncomingFolder>X:\Program Files\Snow Software\Snow Inventory\Server\Incoming</IncomingFolder> </DataProcessor>
You could use this mechanism to archive the .snowpack files but Ester's question is still valid: does it make sense to archive the .snowpack files for analysis & troubleshooting since they are encrypted?!
Retrieving data ...