The initial setup has been made very easy over the last few years because all functions of the server become available on the solution's console upon installation. There is no longer a need to log in on the server side when performing routine tasks.

Deployment takes less than 30 minutes to run on a single machine if pre-requests, servers, databases, and ports are readied in advance. Errors or troubleshooting might add a bit of time to deployment. 

The initial setup for SolarWinds NPM was easy. I didn't do the configuration, but I watched our installer very closely, and he installed the tool quickly. For example: if you have a new module or a new product, you can do the installation very quickly.

The implementation process is pretty straightforward. They give you an MSI and once you have your servers and databases set up, it's just a couple of clicks and it's set up.

For overall importing of everything may have taken a couple of weeks to have things up and running due to how our organization is structured and how we can gather information to pull into SolarWinds and our implementation strategy. For example,  who set up servers and applications. We start getting with the appropriate aims to get whatever monitor or whatever polling method we need, whether it was S and NP strings or accounts for any server monitoring with administrative access or whatnot. Then we look at the network and do those automatic scans from there. Once we start pulling in that information, we start actually organizing all the nodes in there to properly alert and monitor. It takes maybe a month or so to get it to a baseline.

For deployment and maintenance, honestly, it's just me by myself doing it. It would be easier with a few more people.

The initial setup with Orion was somewhat complex. They do have templates in there that you can utilize, but most of those you are going to have to customize anyways. We found that it was easier just to go ahead and do our own.  

The way that I found it to be complex was that we had to do a lot of our own scripting to collect the data that we needed. Once you have got a template set up, you can pretty much populate that information to the Orion database, but I mean there is some pain to get started off. Overall we got involved in a year-long project where we were meeting on a weekly basis discussing all the issues. I think it took us a little over a year-and-a-half to actually declare success on the project.  

Only after that declaration of success were we able to get on to monitoring and dissemination of information to various users and get started with the monitoring. But our monitoring is a lot better than what it used to be. We were using Homegrown, Nagios, and Check_MK. People were not paying attention to alerts. I think the way we handle it now has really helped users mature in that way. We have still got a lot more work to do though.  

We started out with an implementation strategy, but there were some challenges when our directions got changed on us by senior leadership. We would have a plan and a direction and head down a path to implement those particular types of solutions. We would set up the alerting and monitoring and then three months later somebody would come up from an executive level and say, "Hey, we need to monitor this as well." So, we would have to make some changes just like any project. We had to learn to be flexible with it to meet people's needs, but having clearer goals from the outset would have made it easier and quicker in the long run.  

The initial setup is straightforward. It is easy to set up.

The initial configuration is simple. Because, they did not use a backend SQL database, their initial setup was extremely simple. 

As they grew, they began to use SQL, which made things a little more complicated. 

It was extremely simple at first.

It probably took me a week to get it all set up and running, and another month to get everything in it. 

The initial configuration to the point where it was up and running took me about a week.

We installed it in a central data center and then began implementing it. We had to manually discover devices, pull them in, and manually add them one at a time.

SolarWinds NPM's initial setup was straightforward. It took about a year to complete the full process of the implementation. The strategy we used was we worked on the setup of vCore and Microsoft Azure, and then for each of our sites, we did afterward.

The initial setup is straightforward. 

To install the SolarWinds for the first time, you need a virtual machine to install the demo or trial version of SolarWinds. You can then add some devices, monitor and try to use whatever dashboards or reports you think you will need. Installing NPM itself and adding the nodes took us three months.

The setup was pretty straightforward. We just went through a complete redeployment part of upgrading to the latest and greatest as we upgraded servers and databases and the whole nine yards. We just simply did a fresh install. It was pretty easy.

It probably took us about a couple of days. We had to go back in and once we re-added the location, we had to go back and tweak what we wanted to monitor, and that kind of stuff. We didn't simply just do a migration. It was a little bit of doing the network re-discovery and then going in and tweaking the individual locations. 

The one thing we did migrate over was the alerts. We didn't have to recreate alerts from scratch, however, it took us a while. We've got 400-plus devices that we monitor. It took a little while to get all of the devices back in the way they originally were.

The initial setup was pretty straightforward.

A third party helped with the initial setup, and they handled everything. I'm not sure how the deployment worked. 

The initial setup is simple.

The initial setup of SolarWinds NPM was not straightforward. We had some difficulty configuring some of the new features for the devices properly. However, this was because we were new to the solution. We had the documentation which was helpful.

The full implementation took approximately one month.

I rate the initial setup of SolarWinds NPM a three out of five.

The initial setup is very easy and quite straightforward. It's not overly difficult or complex. 

The implementation is fast and doesn't take more than a month or a month and a half. 

We only need one consultant to handle implementation. 

It was very straightforward, as you basically just have to start up a Windows Server, and click through the SolarWinds NPM installation wizard before you are ready to configure. You can configure most of the basic settings using the installation wizard (i.e. the database storage location).

I don’t recall any troubles during the initial setup. It was a long time ago. I was enamored by its mapping capabilities.

The setup and deployment are quite simple. 

It's straightforward, however, you need to have networking knowledge. If you have knowledge of the network, then it's straightforward. It's a great product.

On a medium-sized enterprise, for one of our clients, we deployed it in three hours.

Though I wasn't involved in the deployment process of SolarWinds NPM, I was involved in Fortinet FortiCloud's deployment. With the deployment part, my customers have deployed SolarWinds NPM and Fortinet FortiCloud on the same server.

The initial setup was complex as there was quite a bit of work that had to be done in terms of setting up databases and making sure the database was linked to the application.

The SolarWinds deployment was straightforward and took about two weeks. One support engineer can handle it. 

The initial setup for SolarWinds NPM is relatively easy, and anyone can do it.

As I deployed SolarWinds NPM in a huge environment, the deployment took almost six to eight hours for fifteen servers.

Deployment was straightforward and we had an expert of SolarWinds NPM who we employed. The process was completed within a couple of hours.

The server configuration for installation took about a week. And then another two to three weeks to get it installed across all of our servers. We're making modifications every day. We initially set it up ourselves and then about two years after the initial installation, we hired a consultant to redo the installation and make it more efficient because it wasn't initially configured optimally. It's the amount of detail you need that will determine how much time you spend setting something up.

Basic setup is a breeze for most folks!

The setup is straightforward almost to a fault. If you can follow directions, you can set this platform up in a day and start getting usable information.

The initial setup process requires specific knowledge of the product, and if the implementation manager has the appropriate knowledge, it will not be that difficult to set it up.

The deployment can take up to two weeks depending on the size and complexity of the network.

The initial setup was somewhere in middle.

This solution is maintained, deployed, and updated by a team of six people, and it is also automated for operating system upgrades. We have one or two server admins that are responsible for actual application upgrades.

Setting up SolarWinds NPM was relatively straightforward. There is always some complexity, but it's usually pretty straightforward. Two technicians were able to set it up.

Setting up SolarWinds is somewhat complex because the data is encrypted and banks require so many policies. The reporting and dashboards are also complex. 

The initial setup was straightforward, not complex.

The initial setup is very straightforward; you can have it running in about an hour.

The initial setup of SolarWinds NPM is easy.

The initial setup was quite complex and took a while. You need an engineer to install the solution and the database and configure everything. We have only two people accessing and maintaining SolarWinds.

The initial setup is very straightforward. It’s installed via a wizard and walks you through the steps, installing the extras it needs to function along the way. Then, it’s just a matter of activating your license and configuring the front end web page to look the way you want it. Most of the complexity of the initial setup and configuration is from custom modifications done by us on the back end. We had to modify the database to get NPM to hook into our in-house alert management system. But, for other companies' environments where this level of customization is not needed, NPM has an excellent amount of alerting methods that work right out of the box.

Deploying SolarWinds NPM is a straightforward process. The deployment steps include extracting the files, mounting them on the server, and deploying them. The documentation provided by SolarWinds is clear. 

The initial setup is not difficult or complex. It's quite simple and straightforward.

We have an internal team that can handle any maintenance we need.

The initial setup is as about as easy as they come. SolarWinds products are renown for being easy to install and configure, and for rapid time-to-value; but the devil is in the details.

As an experienced enterprise engineer, I often see inexperienced engineers jump into the product and start producing metrics that add value under the assumption that everything out-of-the-box adds value. This is not the case; and it is a weakness of the installation model. Customers can be lulled into a false sense of success by their rapid deployment and TTPP (time-to-pretty-pictures). Understanding the data is just as important, perhaps more important, than getting the data.

The initial installation is super simple. Pretty much you install SQL on one server, the app on another, and then you’re done.

In most cases, setting up SolarWinds is simple. However, when customers have some special requirements, the deployment can become highly complex.

It was easy to set up. It took less than a month.

The initial setup was pretty straightforward and simple. A company wouldn't have any issues with it. It's somewhat easy to deploy, however, I'm not the engineer. I was the business leader. I just know that I never received any complaints.

A moderate level of knowledge of the product's use is required for installation. 

The initial installation occurred a long time ago. While, for me, this process would not take long, somebody who is new and who has never used the solution may take a day or two to do installation and to become fully up to speed of what is being added, the reason for doing so and how the solution should be configured. 

Installation is not easy for a person who lacks the requisite experience. 

It is very easy to set up. We also deliver consultancy and I recommend to all our customers that they have us involved in the configuration of the software. It is easy to install but then when it is running, it has to be configured. We are good at that.  

The initial setup is pretty straightforward, as long as all of your devices are set up properly to talk to SolarWinds. However, it does get complex when you start configuring customizations for your environment. You have that with any product. The great thing is that SolarWinds ALLOWS you to customize.

The setup is simple and straightforward. It walks you through everything that needs to happen and is very clear and easy.

Initial setup of the application servers were very straightforward. It is possible to get started with one app server and the main SQL server then add more polling engine servers as your monitoring needs increase.

The initial setup can take time because it requires proper security access from the customer side. Setup and implementation took our customer one week. 

The initial setup wasn't complex, but not as easy as some systems either. It requires someone with experience with the network monitoring system. 

The installation takes about one day. However, it can take more than a couple of days to work with SolarWinds NPM or other products. The integration is part of the project.

The initial setup was straightforward. It was really smooth.

I personally did not handle the deployment part, however, the rest of the team who supported me had handled the process and it was my understanding that they didn't have any issues.

The initial setup was simple. I have also used Whatsup Gold and open-source Nagios; they were either too simplistic or too difficult to get actionable data.

This product is easy to install.

A single technical person can deploy it.

The initial setup was straightforward. We didn't have any issues at all. I don't recall how long deployment took. It does depend on what the company needs though. It can vary from company to company. Most installations don't take longer than six hours at a maximum.

Three people handled the implementation.

The set up was very easy. We didn't have any problems with the setup. The deployment took less than an hour.

The initial setup is not that straightforward and could be made easier. We have approximately 500 devices using this solution. We require only two team members for maintenance. 

The setup is straightforward and takes about a week.

The enterprise setup was complex because we have too many devices (about a 1000 routers). It is very challenging to tune all these devices.

Maybe the support team didn't train us well on how to use the product. We might need experts to train us.

Deployment took about six months.

I think the initial setup is pretty simple, the challenge is more about trying to generate all the dependencies, setting the rules and actually setting up internals, ENBB. Our deployment was staggered and took five to six months. We started with a pilot in a region with the most number of users and complexity in order to test and configure the rules we needed. We then went global, starting with the big operations and then moving to the smaller ones which would be easier and take less time. Implementation required a couple of consultants who were familiar with the application and a team that managed the whole operation. The deployment probably involved around 10 people.

It's easy and straightforward. There is no complication. 

We deployed it in one day. We had POC in one day, and we prepared the servers, virtual machine. We did the installation, database setup, and firewall setup in one day. It was easy.

The initial setup is straightforward. The implementation took about two weeks in a controlled environment. We had no problems with the installation and connecting to our devices.

The initial setup is very straightforward.

It's easy. A user can download the file, then they simply click the installer and it provides simple step-by-step click-through style instructions. It's been very intuitive for the most part. Before installation, it's important to consider space requirements, resources for the server, etc. before jumping in. Users will also need to consider (if they're running netflow) whether to save the data on the email server or not. It's possible to run out of space that way, however. There are various guidelines, however, at the end of the day, the installation process isn't complex in and of itself. 

As far as I know, SolarWinds was really the only option at the time.

Quite easy, the "next, next, next" GUI installation with the addition of a standard SQL database usage made installation quite seamless and easy.

It's a little complex for enterprise level installation.

The initial setup is straightforward. We have to just go to NetPath and just connect to the database. Once the connection is established to the database, then we will be up on both devices. There are a lot of options for onboarding the devices. It is easy. Anyone can do it.

There's an admin guide. There's a very helpful guide that SolarWinds has provided on their customer portal. There are training options too. You are well prepared.

The deployment took two to three hours to install the product and five to six hours for the entire deployment. It’s pretty fast if you have a good strategy.

While one person is enough to deploy or manage the solution, it would depend on how many devices you are dealing with.

If you are going to monitor 2,000 devices, one person is enough. If you're going to monitor a large number of devices, you might need two managers for all devices.

The initial setup was pretty straightforward. We had to do some customizations, which was great to provide better visibility of our entire network.

I’m doing initial setups all the time. As a consultant, I go from client to client on a regular basis. The setup is by far the easiest setup of any software that I know. Not only monitoring software, but any software. Even installing Microsoft Office is more complex than SolarWinds. It is really, really easy and straightforward. The wizard provides many guides and notes. The deployment is so well tested and structured that I literally click through the wizard.

Out-of-the-box, it works beautifully. But when it comes to the logic and company workflow, that's when I need to add a bit of a creativity.

The installation of it is simple. Getting the best of the product is where my consultant-level knowledge comes in. The average Joe tends to go as far as getting it installed and working, and then says, “Get lost.” Well, “Get lost” to get the extra bits and pieces to make it a little bit more flexible.

It's easy to get it in and install.

The implementation process is quite simple and straightforward. In fact, it's easier than a lot of other solutions. I wouldn't describe the process as difficult. 

The deployment is fast. It likely didn't take more than ten minutes or so. 

We have a technical team of about five or six people that are able to handle deployment and maintenance tasks. Two of those team embers are managers. 

The initial setup varies but can be quite complex.

The initial setup was pretty straightforward.

The SolarWinds setup is wizard based and walks you through each step. It will identify shortcomings with your system resources, but it could use a little more work. It would be helpful if the system would identify and configure based on a solution type, such as large (with pollers), medium (different buildings), or small campus.

You can quite literally download the installer, run through it, discover your network to add devices, and be “live monitoring” within one hour. Obviously, there are other factors in a complex environment to consider, such as scalability; but the installation of all SolarWinds core modules is extremely straightforward.

It's very simple. Anyone can install and configure SolarWinds with a step-by-step guide, even if that person is a layman when it comes to IT.

The initial set up was very straight forward. I think complication comes with differences in environment.

It is straightforward.

Installation is very straightforward; however, upgrades are a bit tedious (though not complex). It is complex only when you have a large platform of monitoring systems. For a small implementation, it is extremely simple.

I was involved in the installation. After discovery, you select what you want to monitor.

Pretty straight forward if you know your environment.

I did not originally deploy this software, but I haven't had any issues with upgrading to newer versions or installing new features.

Initial installation is straightforward. However, upgrading can be quite complex if you have multiple polling servers, as you need to carefully follow the same steps and upgrade path on each server.

The initial setup for this solution is pretty straightforward.

It took about a week to set up everything. First, we started with all of the networking devices and then we moved on to the workstations and servers.

The initial setup for this solution is very straightforward.

The time required for deployment depends on the number of devices that you want to monitor. For example, if you want to monitor a hundred devices then I think that it will take three or four days.

In our environment, we are monitoring more than four hundred servers and approximately two hundred network devices. Our deployment took about three weeks to complete.

Two or three staff are suitable for deployment.

I was involved in the initial setup when we re-purchased it. It was very straightforward.

The solution is easy to install and it takes a couple of hours.

The initial setup worked fine. This depends on the system and scale you are trying to implement.

General advice is to build the monitoring as a layered approach.

Add devices/systems by categories, starting with basic monitoring ICMP and SNMP, and then add specific metrics to the system.

Setup has always been very intuitive & simple.

Setup is straightforward and smooth just need to follow the installation wizard.

The initial setup is straightforward.

It's very straightforward and super easy to deploy, 15 minutes tops. It's documented well what you need, or there's an option you can do if you're on a limited budget. Also, the support engineers are always there to help with specific questions.

Installation needs reasonable understanding of Windows Servers, SQL Servers, Services and Group Policies (in enterprise). Customization might need good knowledge of SQL programming.

The initial setup of SolarWinds NPM is complex in my view. There are many knobs, dials and buttons to push, and it can take several days to get familiar with the product and it's functionality. 

The setup was straightforward.

Setup is very straightforward and easy to install.

The initial setup was straightforward. We deployed the solution from new and completed the upgrades. 

Initial setup was simple. Run an evaluation & win the team over, then procure the hardware/VMs/licences & follow the books.

I wasn’t part of initial setup/deployment of product itself.

The initial setup is quite straightforward. It was easy for us to install and the deployment took about one month to complete. In the first week, we gathered the software that we wanted to install. From there, it took us another week to do the different installations. After that, we deployed the agent and the tools for working with it.

We use BigFix to deploy, so it's easy for us. 

The product is updated regularly.

Straightforward, no training needed.

The setup is straightforward if you follow the OEM administrative guides and the server specifications and deployment.

Initial setup was straightforward, but this is s big system, ans we've spent years customising and tailoring the software to work the way we like it. 

It was fairly easy, but you just need to make sure that you have a SQL server on a different box or otherwise you would run into problems later on after your database grows.

Initial setup was a simple process.

The initial setup was straightforward. We had it up and running pretty quickly. The actual deployment takes a bit of time, but the initial configuration to import a few devices was about a day.

It was straightforward. You just install the application.

The setup is a little bit complex and it took me about a week to deploy. It took time to configure everything.

It's simple. I installed it. You just look at documentation, install a database, install the server and add the NTA. They have some recommendations, a separate database, but we didn't follow them. We just set up with the same server. Yes, it's easy. It's only the upgrade from the older version to the newer version where things start to get complicated.

It was easy to set up.

Straightforward.

The setup took approximately two to three hours. You need about two hours for tuning. If you use only two or three modules like network performance monitors or network traffic analyzers, you need two or three hours, not more.

The setup required two staff members. One network administrator who needs to pre-configure the network infrastructure and one administrator. You need only two administrators.

The solution’s initial setup is easy.