I still don't quite understand why you don't just use the TCL Expect language in your product for doing config updates and device templates. You could choose to not implement "spawn", but using an existing Expect language means all programming docs and tutorials are already covered on the internet AND you could use modifications of existing RANCID scripts in Cirrus. Just expose the database variables and we could automate anything. Adding a tool like AutoIT to automate HTTP interfaces would complete the toolset for web-only interfaces.
CatTools had this phobia as well, requiring script changes to be compiled and encrypted by the Kiwi folks.
The ability to create compliance rules from the web browser would be great.
Also, being able to deploy config snipets to specific devices that are found to be compliant/not compliant from the compliance manager view in the web site.
For instance when you get the warning state of the device you can currently drill down into that device for more information. It would be nice to either have an option to deploy a configuration from that site or to right click on the warning indication.
Hi Chris - I can't give you dates because of our public company rules (such a drag), but I can speak in vague terms - so vaguely - I can say - in the next months. We're already doing customer walk-throughs of some of the features, so it's moving right along.
Will NCM be able to support user groups?
This question was previously asked and we were told "this is on our roadmap for our next major version release"
I still can not deploy NCM to local "field" engineers because there is no capability to limit device views to specific groups of AD authenticated users.
SolarWinds solutions are rooted in our deep connection to our user base in the THWACK® online community. More than 150,000 members are here to solve problems, share technology and best practices, and directly contribute to our product development process. Learn more today by joining now.