ddambra asked a question.
Is it possible to install Snow Extender alongside Snow Inventory Server ?
I’ve got a scenario where the client will be running Snow License Manager on‑premise alongside Snow Atlas for a period of time.
I was considering enabling the File History module in Snow Inventory Server to move processed Snowpacks into a folder that the Snow Extender could pick up and forward to Atlas.
In theory this would allow processing of inventory both on-premise and in the cloud.
Hi Dan,
Yes - you could do something like that.
There are a number of ways to get Snowpacks into both systems for a transition period
This usually requires running at least one of them on a different port/DNS name during transition.
1) As you suggested you can use the FileHistory option on the Inventory Server. The files created by this module can be forwarded (maybe using a SIM File forwarder) to an Extender
2) The Extender has a built-in Data forwarder, which can be used to send a copy of each snowpack to the on-prem system.
Once you have completed your transition - you would need to ensure that the forwarding is turned off and that the Extender
The timing of how you do this is key.
Tom
Hi @Tom Lineen (Flexera Software)​
Thanks for the detailed feedback... appreciate it.
I was hoping you might also know whether it’s possible to use a single Snow Extender for multiple sites.
We currently have a shared platform setup with six tenants reporting inventory through the same Inventory Servers, and the destination is determined by the sitename.
Does Snow Atlas also interpret the sitename in the SnowAgent configuration to decide which tenant the inventory should flow to?
Or is it strictly a 1:1 relationship between each Snow Extender and an Atlas tenant?
Hi Dan,
re: I was hoping you might also know whether it’s possible to use a single Snow Extender for multiple sites.
That will not work as each Extender is uniquely bound to a specific Snow Atlas tenant.
re: Does Snow Atlas also interpret the sitename in the SnowAgent configuration to decide which tenant the inventory should flow to?
The Extender does not interrogate the sitename - so you cannot use this. (sorry)
The only option I can think of would be to use a the Droplocation as mentioned by Liam.
You would need to update the agents of each of your 6 sites and add a unique http droplocation for these.
Note: There are two things you should be aware of when using Droplocation.
This is quite a complex scenario and would need to be thoroughly tested for feasability.
Tom
Tom
Very interesting that you mention the Webmetering rules as i had a ticket open for 5 months around ours not updating and not once did someone mention that it was due to us using a drop location.
Would it be possible for us to have a conversation around this?
You can amend the config file of the agent to add an additional drop location.
<DropLocation>
<Endpoint>
<Address>****/</Address>
</Endpoint>
</DropLocation>
</Configuration>
As mentioned above you will need to use a different port to your current address.
Hope that helps