bshopp

Might want to open a ticket with support to look into

Yes, you make complete sense and yes we do plan to make this more seamless and usable. Right now what you can do is on one of the subnets delete out the duplicate IP's. If you have large subnets and this is a pain, let me know

Have you seen these advanced SQL alerts we published? See here and here and here

Don, check this out. This should help you out

Can you elaborate? We pull the list of thin AP's directly from the controller we are managing. If you remove that thin AP from the controller, it should remove itself from NPM as well. In Advanced Alert Manager we ship with an alert out of the box to alert when a thin AP goes down. If you log into the Orion server and…

For sure want to open a support ticket here on this one

What version are you running on?

We don't have a resource right now to do this out of the box. One thing you might try is to create a report writer report, then add a report writer resource to the web console and select this new report.

Do you or did you have the Netflow module installed? It looks like the error is around that.

You have NTA as well correct? If so, please apply NTA 3.5 SP1 and I believe the issue should go away. If not, please report back or open a support ticket

Correct, it is still on our list of enhancement to add to the product, but adding IPv6 support is not a trivial effort.

Still on the list of things for the future. Are ya'll rolling out IPv6 and are you doing pure v6 or dual stack?

Elaborate on reporting? I assume IIS to it can handle scale/volume/response time better?

We are looking to address in an upcoming SP

If you have the MIB that needs to be added to the MIB DB, just submit a ticket to support.

Will log this as an enhancement request.

Good Morning. We actually have a release in progress right now with engineering, but I would love to chat with you further and get input from you on what additional use cases and functionality you would like to see in the product. Please let me know if you are open to this discussion.

This is a known issue and is addresses in the next release.

Yes please with diagnostics

Hard to tell, I would recommend a support ticket.

This is high on our list, but not something that I can commit to for the next release at this point in time.

That is next on the list. Our strategy was instead of doing one huge release that takes awhile, try and trickle the module support out as quickly as we can. IPAM & UDT have been around the longest and SEUM is new, so I put it lower priority than these two.

Why not use the Orion Web Configuration Backup utility?

Are you running SP1? You can restart the Netperfmon service in the meantime, that should pick up the change.

1. You can reset the admin password to blank by going to the Accounts table in the database and deleting the encrypted Password for that account. 2. We leave that out to reduce the download size. You can download it separately directly from Microsoft. We do ship a simple database tool that you can find on the Start menu…

It should work fine with Orion NPM 9.5, except for Report Scheduler.There’s a workaround: set up two IIS websites pointing to the same \Inetpub\SolarWinds directory. One for localhost only that does not require client certificates for use by Report Scheduler running locally, and a second website bound to the server’s…

You can see the latest updates here - https://status.solarwindsmsp.com/category/solarwinds-take-control/

Too many things going on at the same time, this is 100% my fault and I apologize for not getting it posted and out. As you indicated, it is GA now and the team is already hard at work on the next update and I will get the "what we are working on" post updated shortly.

We have a release in progress currently, but I would love to hear what else you would like to see in the product. Feel free to ping me at brandon.shopp@solarwinds.com to discuss.

Right now the engineering team is focusing on another service release where we are looking to squash down more defects and other items. We are about 2/3 the way through this service release, but happy to discuss or answer any questions for folks.