The initial setup will go smoothly if the design of the solution was done correctly. 

NSX-T can be complex if the discovery phase was not granular enough.

We are just reselling the product. I've seen demos and things like that. It seems very straightforward. 

There could be some challenges around the implementation time, and you need to know what you're doing. There were some challenges from one of our customers. It had to do with the migration of VTT that wasn't made clear to him, so he complained about that, but it's not my experience. Some of the end-users in that space may have a feeling that they're not being informed sufficiently of product changes in a timely manner. 

Deploying NSX is difficult. VMware NSX has three components: management, controller, and database. You have to understand each of them and where to deploy them. There are lots of logs as well. The deployment varies whether you are deploying on a VM, public cloud, or standalone hardware. Each has its own prerequisites.

First, you have to enable features on your physical equipment, enabling you to install NSX. You have to deploy the dependencies and fix the board. The deployment time depends on the equipment, whether it's from Cisco, Jupiter, or another vendor. They have different approaches to enabling NSX.

Straightforward setup; best practices need to be adhered to.

The initial setup is complex.

When it comes to VMware, there are two primary options: NSX-V and NSX-T. NSX-V is known for its user-friendliness and effectiveness. Setting up SD-WAN connectivity with NSX-V is straightforward.

The solution's initial setup process was easy.

It's intermediate in terms of ease of setup. It is not so straightforward, and it's not also complex.

 It integrates with certain vendors like Palo Alto very well. That said, other vendors, like Fortinet or others, do not have the same level of integration.

I'd rate the process a there out of five in terms of ease of setup. 

The deployment took three weeks the first time we did it. The strategy is mainly segmenting between operational virtual machines which have, for example, the database and the application front end on the same VLAN. If I need to segment this traffic, it wouldn't be possible without NSX.

We have two people that can handle deployment and maintenance tasks. We need someone who understands the schema of the solution itself, the software itself, the front end and the database, and so on. Then, we also need one person from the security team.

The setup depends on the project scope. For example, CaixaBank's project had a very large scope that was divided into many different parts. Deployment took one year but the project is still ongoing. 

Good deployments depend on an assessment phase where you talk with different departments before defining objectives. Discussions should occur both with systems and security staff. With proper pre-assessment, the solution operates and integrates perfectly. 

The initial setup is relatively straightforward, but it takes a long time to implement this solution. You need hundreds of people to deploy and maintain this solution.

I'm not implementing. I am selling the solution. You can use it on-prem or in the cloud. If you are using SRM, including NSX in your workloads makes things easier. You can easily move everything, including the network security and several layers inside the appliance, to the cloud or any other site.

I didn't handle the initial installation. I can't speak to how easy or difficult it was to implement, or how long it took to deploy. I wasn't a part of the process.

The initial setup is straightforward but still takes time.

It takes longer to deploy than Cisco products. It takes between three and seven days to deploy,

We had a team of five for deployment. Two are from our company and three were from the vendor.

The initial setup was simple. We started probably in December of last year and did a lot of prep: A lot of VMware upgrades, licensing upgrades, etc. All this was done in advance with VMware's help. The project came in for install in June and it took about two weeks. It was great, and we did not have problems.

It is a little bit complex to set up. It depends upon deployment. Either it is greenfield or brownfield deployment. If it is greenfield, it is very easy. If it is a brownfield deployment, so you need to take care of multiple scenarios of your network, and you need to understand the network architecture, then the deployment of services. 

While deployment requires a complete team, maintenance only requires on VMware administrator. 

I was the previous architect for the NSX, not the implementer.

My understanding is the setup process is quite straightforward. 

Our deployment was quite big. Including the staging and all the stuff, we were able to deploy in a four-month timeframe. That is not only NSX, that is the complete deployment of the cloud. We had a few issues here and there, however, overall, it was fine. 

It's easy to maintain for the most part. The orchestration layer for it was a bit hectic work for us. That needed a dedicated VMware team. Apart from that, everything was quite smooth for NSX or vSphere, et cetera, and it is quite simple to manage it.

If you have experience with the setup of VMware NSX it is simple, but if you do not it could be difficult. I would advise new users to contact professional support from VMware.

The initial setup is straightforward. The implementation time ranges from days to weeks, depending on the business use cases per customer requirements. It involves the assessment of design, deploying, and verifying the same. I rate the process an eight out of ten.

The installation process for VMware NSX can be intricate. We obtained the executable file for the specific server we intended to install VMware NSX and then proceeded to configure it. This involved ensuring that the IP and ID matched the installation, as well as completing other necessary details such as setting up the gateways.

The initial setup offers an average level of complexity. It's neither too difficult or too hard. 

Regarding the initial setup, VMware products, including NSX, are generally straightforward to set up and deploy, so complexity hasn't been an issue.

The initial setup for VMware NSX is not that complex. It's in the middle, so I'd rate it as five out of ten.

I'm trying to remember how long the deployment of the solution took, but it didn't take up a lot of time.

The initial installation feels at first a little complex because there are a lot of components, but when you get the understanding after a short time, it is fine.

The initial setup is easy and takes between one and five days.

It was easy to set up. It hardly took a week.

The installation is straightforward, it took a couple of hours.

The initial setup of VMware NSX is not complex. If someone has an understanding of how networks work it will be easy. It can take some time to be completed. For example, to configure the solution with the correct commands.

The implementation time can vary depending on the clarity and complexity of the requirements.

When comparing VMware NSX to OpenStack, VMware NSX is simpler to implement.

I rate the initial setup of VMware NSX a six out of ten.

The solution's implementation is easy.

The tool's setup is complex. When I deployed it myself, it took less than one day.

The setup of VMware NSX is very easy.

I rate the setup of VMware NSX a four out of five.

The installation is straightforward and it took approximately two days.

The solution is difficult to deploy due to network complexity. The deployment took three months to complete. We had around five to seven resources involved in the product's deployment. They were mainly from the roles of network security and infrastructure. We created a plan and deployed the solution following it. 

The initial setup is not that straightforward. We used a consultant and even then deployment took a full week. It wasn't easy. 

The solution was easy to install but not easy to deploy. 

In the beginning, implementation was quite challenging. Once you know your way around it, it becomes a lot easier to navigate. Every master was once a disaster. The beginning stages are the most challenging but as you pass through the initial starting point, you begin to realize how easily it can be integrated with multiple devices. 

I have been in technology for 23 years and I see the constant evolution of not just the portable technology but also the management. I believe that adapting to the multiple levels of security inside of the business management is a challenge for different vendors.

Of all the cybersecurity vendors we have, the installation of VMware products is the most straightforward. The time needed to deploy depends on the purpose of the use case. Complex tasks between two data centers could take up to four days, whereas micro-segmentation would usually take only two days.

Our team is already trained, so the setup is straightforward.

The initial setup is very simple. It's not overly complex.

All the VMware platforms are really easy to implement. They require knowledge, of course. However, if you follow the procedure, the output is good.

The deployment itself doesn't take more than two or three days. 

That said, we have knowledgeable workers that have done NSX and the previous release (not the NSX-T). They have done deployments several times. That's why, each time, it's really easy to do. If you have to do that in a customer production environment, it will take say no more than one week including both the deployment in production and the training for the customer.

We have three people that can handle deployment and maintenance tasks. 

At first, it was a little complex, but it's more internal, just learning a new product and what it can do for you. But once you get all that set up, and done with the collaboration, and the other groups, it's really not that bad.

The initial setup is very straightforward. Our deployment took three months, end to end.

It was a complex setup.

The initial setup was straightforward.

VMware NSX is straightforward to install and configure, but for a user who's new to it, the product can be somewhat complex to understand, though not too complex.

The installation is very straightforward. The part that gets complex is how you do your routing, how you do your ESGs, how you set up the actual network itself within it. But once it's set up, you just create virtual switches and put any network you want on it. It becomes almost seamless.

The initial setup was straightforward. Deployment was very easy.

The initial setup was straightforward. It follows a certain structure and you won't miss a step. It's all on the same level, step by step.

NSX is one of the simplest network solutions that I've ever worked with.

I did a demo for our company's engineers about a year ago, and in 45 minutes, I stood up a cluster and had the VXLAN and some of the firewall policies, up and running in a 45-minute demo. It's really easy to use and everybody walked away from it knowing how to use NSX just from a 45-minute presentation.

The initial setup for VMware NSX was pretty straightforward. In terms of our implementation plan, mostly we have standard SOPs that we have laid down for our implementation teams and we stick to those. It would still depend on the environment where we're going to execute it, for example, it could be on-premises or on the cloud, and we'd also take into consideration which type of cloud they have and what other technologies they have in their environment, so based on all of those, the implementation plan and how we're going to approach the implementation changes.

How long the deployment of VMware NSX takes would depend on the client, the environment, and the requirements, but for the basic setup or initial setup where we would just get the box and the do configuration, the IP, etc., that doesn't take more than four to five days.

Our deployment model for VMware NSX used to be on-premises, but now the deployment is mostly on the public cloud.

The installation has been complex.

The initial setup was straightforward. You just have to click it and follow the manuals. Deploying the infrastructure code can be more complex.

It seems to be very straightforward. Usually a lot of it's handled by the installer. Yeah, very straightforward. As long as you read the design guide, it's easy.

It's a complex product so setup is essentially as easy as the person whose knowledge is being used to install it. There are various elements to it. It can be installed in modules - in a modular fashion. You don't have to install everything right away. And, unfortunately, with this particular product, when you read through all the marketing materials it sounds like it has to be installed completely when, in fact, you can start out with only the pieces you need and add what you need - the other pieces - later as needed.

I didn't actually handle the implementation. I'm working more on the design side, not on setup or configuration. Therefore, I can't speak to how easy or difficult the implementation process is for users. 

We have done three installations and we have not had any critical issues. The time it took for the installation was approximately two days. However, they should provide better documentation.

I would not say that the initial setup was straightforward. In terms of how easy it was to complete the deployment, I would rate the process a seven out of ten. 

The initial setup is straightforward.

The NSX setup is complex. That's one area where they could improve. Generally, it's too complicated to deploy. You can spend two or three days on it. And if you've never done it before, it might take a week. So it takes a relatively long time and lacks comprehensive end-to-end documentation. We had inadequate documentation when we implemented it, but I think it's better now. Total deployment for us took more than two weeks, but there were some breaks in that time where we stopped working on it. We weren't under any deadline. If we were pressed, we could have finished in four or five.

After the initial setup, NSX doesn't require a whole lot of maintenance. It's mostly troubleshooting, checking error codes, etc. There is no dedicated maintenance personnel specifically for NSX. Some guys in the IT department support this solution along with several other solutions. We have about four to five people handling that side of things, but there are six of us in the whole department responsible for infrastructure.

The setup was straightforward and it took a few weeks.

It was straightforward. Just a couple of install media and .ovf files and you're done. The interesting part comes after installation when you need to define your virtual network architecture and how you're going to deploy rules and connectivity for your VMs.

I found that it was easy to install. In fact, I installed it myself.

We had some complexities implementing into the other parts of a network. Otherwise, the NSX product was straightforward to setup.

The initial setup was a bit lengthy in the beginning. Now, it is a bit smoother. While I like it, it still takes time to setup. It is a bit slow, which is surprising.

We had some challenges during the installation and setup.

The setup is not easy, but it is doable.

Sometimes, deployment can take around four weeks. For the design and deployment, it can take eight weeks. We need more days, at times, for migration or for deploying security.

It is easy to implement it.

I was involved in the initial setup. It was straightforward. We did it with our government PFE.

We did face some challenges with the initial setup. 

I'm not a VMware expert and as a network engineer, I find the setup to be quite complex.

The implementation of VMware NSX is moderately complex. However, it depends on your data center environment complexity.

The first time setting it up was difficult. After a couple of installations, it should get easier.

I found the initial setup to be complex. 

The initial setup was straightforward.