Back in 2007, when we got the initial nGenius system, we did have NETSCOUT pro service come over and give me some pointers on specific configurations on InfiniStreams and some service building. Then, it did taper off for a while because NETSCOUT didn't offer it, and I pretty much learned a lot of it on my own.

Our experience with their consultant was very good. He was very helpful and definitely would give his input. He would explain certain things, "This is what this is for. This is what you should do to create a better view."

I worked directly with the NETSCOUT SE. The deployment takes one SE from NETSCOUT and three engineers from our side.

We had Professional Services help us with it and it was a breeze. It was easy to set up. Their Professional Services were the only ones needed.

We did it ourselves.

When we started with the customer, NETSCOUT directly supported us with the implementation. And after that, we were all on our own. 

It took us six months to deploy the product.

It was deployed long before I got into my job, but the people that I've been working with were the original deployers. I'm pretty sure they worked with somebody.

It took us three to four hours to deploy the tool. We needed only one engineer to deploy it.

We used NETSCOUT directly for the deployment.

We have made on and off use of the NETSCOUT team. 

The solution was deployed in-house.

We did not use any outside resources for the deployment, but we do have onsite people from NETSCOUT.

For both cloud and on-prem deployments, we typically start by setting up the environment. We receive the devices, connect them, and then install the initial software and perform the initial configuration. However, the more complex and advanced configuration tasks are typically handled by NETSCOUT's cloud professional services team.

Typically, one or two people per site are sufficient for deployment. It's a bit of a snowball effect. The first site may take a couple of weeks to deploy, while subsequent sites may only take a couple of days.

It's fairly standard maintenance. It may involve changing power supplies or cards, but nothing fancy or complicated.

We did it ourselves.

We used a reseller for the deployment. They were very good. We have a good working relationship with them.

We worked closely with NETSCOUT for the deployment. 

We have our own IT department who channels the server, infrastructure, and networking. I'm on the engineering side, and we work directly side-by-side with NETSCOUT. 

We don't use a third party vendor.

For some customers, we need to work with them to receive many parts, such as some applications, which we will need to speak to the applications team. Additionally, there could be some services we need to monitor in the database, and in this case, we have to contact their database team.

We require more than two people for the deployment and maintenance of the solution.

We have worked directly with a NETSCOUT consultant. We have a reseller, but direct contact with NETSCOUT is very important for me.

On my team, we are doing the implementation. Other teams within the company are using third-parties to do the deployment. But on my side, it's all internal people.

A lot of it was internal or direct with NETSCOUT.

We've always gone straight through NETSCOUT in terms of the support and the hardware. We have never gone through a reseller.

The sales engineer helped me, and I got a lot of help from the website itself.

For complex implementations, we rely on the vendor for more support.

We used NETSCOUT Professional Services years ago. 

If the single pane of glass can be effectively implemented, it is very powerful. However, if you're not working with NETSCOUT closely, this is a little difficult. Overall, it is a very good pane of glass to provide customers.

If you are going to do a deployment of this product, you should use NETSCOUT Professional Services or have an expert.

We deployed the solution in-house.

We worked directly with NETSCOUT for the deployment.

We worked directly with NETSCOUT.

I used consultants for deployment.

We used a partner.

We deployed in-house.