The initial setup was relatively easy. I would rate it seven out of ten.

Setting up a solution involves configuring a server and a web console, which is straightforward. Network team coordination is necessary when applying it to devices. This involves creating device connection profiles and ensuring SNMP is enabled. Initially, there were challenges involved in this process, but once the setup was complete, operations proceeded smoothly.

All network devices are automatically added to NPM during auto-discovery in SolarWinds Network Performance Monitor, including Network Configuration Manager features. Once configuration profile credentials are established in NCM, they are automatically deployed to all network devices.

The solution is easy to use and deploy, although initial setup may require coordination and overcoming challenges.

The initial setup process for the SolarWinds Network Configuration Manager was somewhat complex, particularly due to the need to ensure that the devices being managed had the necessary base configuration, such as SSH, in place. However, once the devices were registered with NCM, we found it easier to navigate and use.

For the most recent deployment of SolarWinds Network Configuration Manager, a team of five engineers was involved. One engineer was responsible for managing the dashboard, while the other four were distributed to the site to ensure that the base configuration was properly set up on the devices to allow them to be registered with SolarWinds Network Configuration Manager. This project we recently worked on it took approximately six weeks to deploy. It was a large network.

The first step in deploying the SolarWinds Network Configuration Manager was to ensure that the network was properly set up and that all the devices had the necessary base configuration in place to allow them to communicate with the solution. This included preparing the desktop where SolarWinds Network Configuration Manager would be installed and ensuring that it had connectivity with all the other devices on the network.

After setting up the network and preparing the devices for communication with SolarWinds Network Configuration Manager, the next step was to prepare a database for the solution to use to store the configuration data. Once the database was set up, the next step was to configure SolarWinds Network Configuration Manager to connect to the database before proceeding with registering the other network equipment with the solution.

Lastly, we provide training for the network administrator who is going to take charge.

I rate the initial setup of SolarWinds Network Configuration Manager a nine out of ten.

The documents for setting up SolarWinds Network Configuration Manager are straightforward, but configuring the monitored device is a challenge because our support team lacks the necessary knowledge. It's crucial to assess the impact of these configuration changes on the integration with the NCM module, such as high resource utilization or other potential issues. It's essential to evaluate the effects of these changes on both sides.

The deployment tool one to two days because we had to verify the setup and configure the devices. We have to add the devices through the SSMP We are not only doing one device, we are doing more than 20. The more devices added to the solution will add more time. 

The initial setup is straightforward. It begins with a scan to populate the database with asset information. Once the scanning process is complete and the database is filled, you can easily manipulate and customize the view of these assets. Once you grasp the necessary steps, the process becomes simple and manageable.

The initial setup is simple. I deployed the solution on-prem and have used the on-premises version for over ten years.

It typically takes under an hour, with us assisting our clients throughout the process.

The initial setup is easy. The deployment process is very fast. I did that in the past. SolarWinds has a good graphical interface that allows users to save the credentials if they enable the SNMP credential or community strings. The software provides instructions for the configuration and all the needed features. Also, users can test their credentials before finalizing their configuration. So it's very simple. It's good.

The solution's initial setup process is moderately complex. Before starting the deployment, the network engineer must take specific training for the tool.

The initial setup was pretty straightforward. The initial setup did not take very long. I think the base platform was set up in a day's time. But I think configuration compliance policies, which is actually more of writing the policies rather than anything to do with SolarWinds, are slightly more time-consuming. The creation of policy is time-consuming. That has more to do with the organization policy, i.e., do I need Telnet enabled, do I need Telnet disabled, etc.

I've been using SolarWinds for a long time. I'm using NBM, NTA, and other models also. For me, it was not a tough task to set up the solution. That said, I only am familiar with the ORM platform and its features. 

If someone does not have any knowledge of ORM or SolarWinds and they just start with the NCM, then they may face issues and may consider it difficult to deploy. 

Therefore, while deployment is easy, whenever someone is new, they may face some issues running the jobs, and figuring out the jobs and configurations and it all works. For me, it was easy since I already have certain experience and certifications.

NCM deployment takes the usual amount of time as compared to other modules. I deployed on two to three instances and along with other modules. It doesn't take much time. I would not say it's unresponsive. It just takes time.

The setup of SolarWinds NCM can be difficult in a large environment. However, if you have a small environment with a few nodes, the process is easier and faster.

The deployment typically takes two days.

The initial setup was straightforward. I use a team to deploy and maintain this solution.

The initial setup was very easy. There were no issues at all.

I was an integrator and would help to deploy the solution for some of the companies.

We have a team of three to manage and maintain the solution.

The installation is straightforward.

The initial setup is easy. If it is already done with existing network infrastructure, deployment takes only two to three hours.

It was straightforward for monitoring a small environment.

The implementation process is very user-friendly. Deployment takes about three hours with customization. You only need a few people to handle the deployment; it doesn't take too many. You might need one on the server-side and one for the application.