Serena CM is well suited to highly controlled, audited, and process driven environments. It will allow strict segregation of duties, and change traceability. If implemented correctly it will help you quickly build trusts with your auditors. It is also well suited to environments that require constant branching and merging. Due to the complexity of the product and learning curve for your development and operations team it may be overkill in a small shop with loose rules
If your IT team isn't proficient in automation and scripting, Solarwinds NCM can fill that gap (assuming your company's security team signs off on approving SW in your environment given the hack.) Basic device configuration, pushing mass changes reliably and backups are NCM's strong suites. If you have a complex scenario where if/then cases are needed, NCM is a bit lack luster. Auto discovery isn't as easy either as certain parameters need to be met for that feature to work 100% of the time
Code Promotion: Dimensions CM allows supervisors to control changes to code, in that they delegate requests to developers, and act as a gatekeeper prior to promoting to the next environment. This functionality is configurable so you can set up a workflow that best fits the structure and requirements of your own company.
Code Repository for changes and versioning: Code can be checked out by item or by synchronizing folders. Code revisions can be compared against other revisions or work files. Item histories show which developers made which modifications, and which supervisor and operations personnel were involved in assigning the request and promoting the code to each environment. Additionally a pedigree will show a stream diagram which graphically displays branches and merges.
Deployment: Serena Change Management offers help automating deployment including integrations with SVN and Jenkins. Its newer versions also have a powerful graphical deployment automation tool (Serena Deployment Automation- SDA). It comes with a certain amount of licenses built-in. If you have a many nodes to deploy to there will be separate licensing costs for that.
The only major negative that I have encountered with Serena CM product is that the very power and flexibility of the tool means there is a risk that you will make a mess of things. In other words it gives you plenty of rope to tangle yourself with. I recommend careful, well thought out deployments implementing the built in roles and workflows that can be turned on and configured, using a consistent methodology.
My experience with the Serena help desk support has not been impressive. Though reasonably polite and diligent, the technicians were well trained, and often gave bad advise and terrible scripts. On several occasions I had to rewrite scripts they have me; if I had run them as provided they would have caused even more difficulties than the problem I was trying to solve. I speak of the support in the past tense because I conditioned myself not to call them, it was usually just easier to solve nay problems my self. They do have a good account management team though, and for any major issues you can go thru them.
For our use case, it does everything great and some of the features we underutilize but I would like to be able to set a configuration baseline when initially adding a node instead of after the configuration is pulled but it's not a particularly big deal to let it pull the configuration then set it as the baseline.
Medium complexity to set up in the beginning if using any non-standard devices or configurations, else fairly easy (e.g. Cisco Nexus or IOS-based devices). Reports are fairly straightforward to set up. Updates to the platform are fairly straightforward and don't take a major effort. Easy to add or remove devices.
The user interface is lacking. It is difficult to navigate at times and things can be done multiple ways. Quite often I am confused by how their notification structure works. It is not very intuitive. They do offer a free Academy. They also offer a community of other technical folks. I have enjoyed both.
To be fair, I have not had to involve Support in a number of years, but when I did, I was greeted with enthusiastic engineers who wanted to understand and solve the issue. It was a fairly complex scenario and I have discovered in my most recent implementation that engineering included that option as a standard now.
Solarwinds has actually produced new training since I last used it that is available on their site at any time. Their previous training was more than enough to get us started but now there is significantly more content. Since I'm comfortable with the Orion platform and the products we use I haven't checked the new training out yet but we have new staff go through portions of that training and they always come away with an understanding of the platform and ready to use it
it was a fairly easy implementation and everything was pretty straightforward. only challenge we had was getting all the snmp communities updated on the networking equipment
Serena CM is superior to Microsoft Team Foundation Server (TFS) in overall functionality, but does not have very good native integration with Microsoft. Therefore in a Microsoft centric shop with no audit needs ,TFS would be better. Otherwise I would choose Serena CM
Red Hat Ansible Automation Platform is a great tool and matches much of the functionality of SolarWinds Network Configuration Manager. Nothing about Ansible will likely be overwhelming to an engineer with a little time to spare, but that spare time combined with SolarWinds already being our monitoring tool made the decision easy. Time is at a premium in small teams and SolarWinds Network Configuration Manager is very easy to use right out of the box without all the tweaking required by powerful command line driven tools like Ansible.
Serena has facilitated our annual completion of various audit and technology control certifications. These certifications make a huge difference to our company's reputation and bottom line.
