Open for Voting
over 2 years ago

Test/Development Licenses

Disclaimer: I know that there are other threads on this but I wanted to update it in this new Idea space.

I would really like to have Test/Development licenses for SolarWinds products, at least for the products that we have purchased.  These licenses could be restricted to just a few nodes (like 10ish).

The reasons for this would be having the ability to do the following things in a non-production environment...

  • Testing upgrades
  • Testing different configurations
  • Learning the SolarWinds products for SCP (SolarWinds Certified Professionals)
    • In the case of SCP's I think they should get access to test licenses for all of the SW products to keep current
  • Creating a small training environment
  • Creating a demo environment

I am sure there are other reasons that I have not already thought of, please share if you have them and vote on this idea if you like it!

Parents
  • At my company, we are not allowed to do an upgrade or implement a new application monitor until we test in dev.  That means that we have to load all the modules as an eval, copy the DB, do the upgrades, etc. etc.  Now we have to clean all that up to test the new upgrade since the 30 days have past.

    My company ended up buying NPM and SAM at lower levels to accomodate this.  But upper management could not understand why there is no "development" or test license that we can buy or why maintenance is so high on a dev system.  We did not have the budget to duplicate NTA, IPAM, IPSLA, UDT, Failover or NCM, so we 'wing it' with those.  But we have to find a solution to those soon....

    This is needed for true enterprise customers.  I understand the risk of loss revenue due to people abusing the license, but I think there are ways around it since the prod and dev would both be on the same network.

    We would love to see this happen, my management would be "stuck" on Solarwinds!


Comment
  • At my company, we are not allowed to do an upgrade or implement a new application monitor until we test in dev.  That means that we have to load all the modules as an eval, copy the DB, do the upgrades, etc. etc.  Now we have to clean all that up to test the new upgrade since the 30 days have past.

    My company ended up buying NPM and SAM at lower levels to accomodate this.  But upper management could not understand why there is no "development" or test license that we can buy or why maintenance is so high on a dev system.  We did not have the budget to duplicate NTA, IPAM, IPSLA, UDT, Failover or NCM, so we 'wing it' with those.  But we have to find a solution to those soon....

    This is needed for true enterprise customers.  I understand the risk of loss revenue due to people abusing the license, but I think there are ways around it since the prod and dev would both be on the same network.

    We would love to see this happen, my management would be "stuck" on Solarwinds!


Children
  • I strongly agree with this idea.  We have some very recent experience with an upgrade that brought our system to it's knees and took Orion developers over a month to resolve.  I would have much rather have discovered the issue on small development system than have inflicted pain on the production universe.  I don't even mind paying for it but obviously it should be at a much more reduced rate than a full system even less than the minimal production licenses.  Something that will handle about 10 devices and no more