The solution's initial setup is very straightforward.

The setup is very easy. All the APs come from the manufacturer so you can start right away with configurations. The features make configurations and upgrades very easy. 

I rate setup a ten out of ten. 

The Aruba partner deployed the solution. I was partially involved, though. It wasn't that difficult, but it took a while because we have complex corporate standards. It was maybe three weeks plus testing in the lab. 

Setting up Aruba was straightforward. We did the initial deployment on our own. After we got the Aruba Central licenses, Aruba's team provisioned the first five APs and prepared documentation on how to do provisioning. My team was quickly able to do that. We completed everything in a day and had it running without any challenges.

Initial setup was complex. The vendors have to perform due diligence and heat mapping in the height of the pandemic. The project started last year in September and it was completed last February. Deployment took less than a year.

We had a software and hardware implementation plan. 

I would rate the initial setup an eight out of ten. While the implementation may not be instant, it is relatively simple.

The deployment time depends upon the organization. So, even if it's a big organization with multiple branches, their network, availability, and other factors can differ. However, if it's a single-site implementation, it will not take much time. The only thing that we need to ensure is that the prerequisites are ready, which may take a few days. That's it. Two to three people, including a project manager and one or two engineers, are required for deployment.

The initial setup is very easy because we change all the models. We have around 1,000 units and we changed all of them in one week.

The initial setup of Aruba Wireless is of a medium level of difficulty. However, it is not simple to configure. It took approximately one month to deploy.

We installed the devices everywhere on-premise and had the field engineer from Aruba Wireless first power up all the access points. We then tried to integrate it with the LDAP, but they found some problems. They had to change it with another system for it to work.

I rate the initial setup of Aruba Wireless a five out of ten.

The initial setup process for these access points tends to be time-consuming. While other products can start up in as little as ten to fifteen minutes, these access points take longer to get going. They are relatively stable once configured. We've noticed that they can remain stable for a year or even longer initially.

The initial setup was easy compared to other solutions. We have two staff members who maintain the solution. 

The solution is simple to set up.

The configuration and everything it is pretty straightforward. We are using Aruba’s central console to manage the wireless. There are no complications, actually.

On the initial level, it took two months to complete the complete projects and everything.

In terms of maintenance, we are paying our partner for an AMC annual maintenance contract. We are paying yearly, and they are just maintaining our network. They're managing everything. We have around 20 people working on their team to support us.

The standalone deployments are straightforward whereas the introduction of wireless controllers and security parameters can be complex. That depends on the architecture to which you are applying. Even though direct integration with any of the radio servers or any of the triple-A authentication servers like Mac is very straightforward, it could be complex depending upon the environment.

A standalone deployment would not take more than 15 minutes. It is quite simple. You might need some pre-planning before that. If you planned enough in advance, then it would take you 15 minutes or 20 minutes at a maximum to deploy. If there's a wireless controller deployment, it would take a maximum of two hours to three hours. Not more than that.

Maintenance as such is not required. It's just the regular maintenance that you do in terms of software upgrades or firmware upgrades, in terms of when vulnerabilities are found. 

I would say it is straightforward. It is just that it is a backward way of doing it. They had a fundamental shift in the way you deploy configurations in version 6 to version 8. So, basically, you would do one way in version 6, and then they completely reversed it in version 8. When you come into the product for the first time, it is easy and fairly straightforward. It is an easy adoption process. If you have got lots of experience with the previous version of code, such as version 6, and then you move to version 8, it is very confusing.

Deploying Aruba Wireless is pretty straightforward.

It took several days to complete the deployment because the office was enormous and the number of APs deployed was quite significant.

It took one to two months to pre-stage, install, and make Aruba Wireless stable.

The tool's deployment is easy. Its deployment depends on the network type and scope of work. Simple scenarios can be completed in a week. Complex networks take two to three months to complete. 

The initial setup is pretty easy, certainly not as complicated as Cisco. There aren't many upgrades or major bugs so it's more stable than Cisco. Deployment time depends on the size of the project. A small site will take about two weeks, a larger project might take three or four weeks. We have nine engineers supporting Aruba.

Deploying Aruba is somewhat complex. There are many layers. It's easy to make mistakes because the same setting will appear in different layers. Various parts of large buildings can have different settings.

The initial setup for Aruba Wireless is not easy. It's not straightforward. The setup for the solution is quite complicated, but this is not unusual, because it is an enterprise solution, and it is no different from the competition, in terms of the complexity of the setup.

If I would rate the setup of Aruba Wireless between one to five, with five being the highest, I'm rating the setup a two.

The initial setup is more complex than other solutions. You need to understand the technology, the way it's configured, and the way you have to set it up. The solution requires more knowledge and more commitment than others.

The initial setup is a bit complex and requires some basic networking and wireless networking concepts.

The initial setup of Aruba Wireless is a lot easier to do than on other solutions.

The implementation is easy. Anyone that has a platform from Aruba or knows about Aruba knows about configuring the product, which can be difficult. There are many deployment options for a natural configuration. You need to figure out what type of deployment you are doing (and there can be many) and do it according to your specific needs. If one has enough experience or is certified from Aruba, he can do it. If he doesn't it's complex and difficult. 

ClearPass from Aruba is complicated. However, it's a very good, powerful software.

The initial setup of Aruba Wireless is not complicated. In the past, it was complicated, e.g. We needed experienced technical people to do the configuration and the initial setup. Nowadays, even basic technical people can do it.

It has improved, but what we are expecting is that when new technologies arise, along with the new technologies, the configuration should be simplified.

The setup for the APs is straightforward; however, you need to be extremely knowledgeable to set up ClearPass.

The product has been very easy to set up. It's straightforward to implement. It did not become overly complex. Under ten access points only takes about five minutes to set up. 

We only need one person to manage the solution. 

The initial setup is very easy.

Once the cloud is set up, you assign each AP a license through the web portal. You plug it in, make sure it's in a port that's configured for our Wi-Fi network, and it works. It's a three or four-step process and it's very simple to do.

In terms of setting up Aruba Wireless, if everything goes well, usually there's no problem, but sometimes if you need something specific, it becomes very tricky, particularly in terms of finding the right support for your setup issue. It's not easy. As for how long the deployment of Aruba Wireless takes, it didn't take too much time, though I can't give an exact timeframe.

The solution is simple to install. It's not overly difficult or complex. For half of the preconfig process, it might only take 15 minutes. 

Then, there might be one and a half hours for testing, to fix the access IDs and other access points to match everything in the data center. 

We only need two people to install and set up the solution. 

It's pretty simple. Once the master controller and the local controllers are set up, it's just a matter of syncing the configurations, so you do the configuration once on the centralized controller, and everything gets replicated to all the local controllers at each campus. Adding, removing, changing, bringing on new controllers to replace old controllers is a pretty simple process.

The setup is complex for new users. Cloud deployment is easier than on-premise deployment. The deployment can be done in one to two days.

The initial setup was easy.

The initial setup for Aruba Wireless was easy. It was so simple. My organization used it as a standalone solution.

Deploying the product took approximately six months.

The initial setup of Aruba Wireless is simple, including a wireless plan used. If we have instant access points and change them to computer access points, it is simple to do.

The initial setup is very easy.

The initial setup was a little bit complex because our environment is complex. Because of that, I would say the initial setup was complex. It may not be as complex for other companies.  

It took almost a year for deployment. But there are two sides to the setup. One is the product is good and it can be configured to do what we need. But our environment was complex because it involves some legacy devices and some really advanced new devices and technologies as well. It is good that the product is able to support both of those needs.  

Installation is relatively easy.

Configuration was not all that complicated, but there were some forums online that helped us just in case. They shed light on the deep config options.

We only had a summer to deploy.

Regarding the deployment process, it keeps showing updates.

The initial setup is straightforward. 

The initial setup's level of difficulty depends on how we design the network. It can be very complicated if we're talking on a campus level and there are a thousand touch points. 

The initial setup was pretty straightforward and took just a couple of hours.

The setup is straightforward, it's not complex. Things are quite easy with Aruba.

The initial setup is absolutely straightforward.

The initial setup is pretty straightforward and the deployment is quick. With our experience, it is pretty easy to do.

The initial setup for Aruba Wireless is straightforward. There's nothing complex about it.

I've been a part of the implementation process and found it to be quite straightforward and simple. It's not an overly complex or difficult process at all. 

We can have it deployed in an hour. It's pretty quick to get everything up and running.

The initial setup is very easy. You just need to configure the main device. If you have a standalone or virtual appliance, you can just configure it and install the rest without connecting to the main device.

Deployment time varies, but usually, it's very fast. Most of our customers need 10 access points on-site. For me, this only takes roughly 15 minutes to install.

I used to use Ruckus. Ruckus takes a long time to configure. Cisco takes longer too. Aruba is the easiest to install. Just configure the main device, and install the rest. Nothing else is required.

I'd like to mention something else. Last week, I installed roughly 37 access points — Aruba 303 I believe. Our clients complained about the coverage. Their access points should be able to cover 50 meters, but Aruba was only covering 25 to 30 meters, max. I know Aruba, and like anything, there are advantages and disadvantages. I like Aruba for its easy installation, management and because they provide the best and most optimized connection.

In my experience the initial setup of the Aruba EAP solution is straightforward. We can call on all the APs and then you have everything connected. Now they also have a Soho gateway solution that it is integrated. It is very easy to turn on this solution. I can install the Soho add-on instantly for the Aruba solution. I think that they are doing very well to keep the customer in mind when building and testing their products for ease of setup and use.  

Our deployment did not take a very long time. Even initially. For clients, the deployment takes more or less time than ours. It depends on the size of the implementation. If you have to do only 10 APs in a small deployment, it can take only two or three days to complete the whole thing. If you have a bigger implementation, it depends on the size of the project. It could take weeks for the deployment if it is a very large one.  

Installation is pretty straight forward.  

The initial setup was straightforward.

It only takes a few minutes to deploy. I would say that it is about as long as it takes to reboot the access point.

Setting up the controller is complex. The SSIDs, Authentication methodology, Access, is all quite complex to set up. Not for a novice.

The setup is not a problem, it only took five minutes or so.

Setup is straightforward.

The setup is easy and normally it goes smoothly. 

For our customers, we deploy both on the cloud and on-premises.

The initial setup of Aruba Wireless is easy, but the controller device is difficult.

The virtual controller process is very simple. For example, configuring a user portal or a cap portal is extremely difficult.

To configure a user, I must log in to the user portal, with a username, and password. It's extremely difficult in the device controller.

We installed one first, the first AP, the first equipment, and the others' equipment could connect without a network cable - just by mesh, like a network without cables. We increased the capacity of the network with this type of technology solution.

It is very easy to use. You just load an app on your cell phone from the Apple Store. You can continue with this application on your cell phone.

The initial set up of Aruba Wireless is in the middle, i.e. not so easy and not so complex. You need to learn to understand the process through the provided documentation.

The initial setup is straightforward. Configure one IAP and all the rest self-configure to that one.

For a person who has been brought up with Cisco devices, I could say it was complex when I started working in Aruba's CLI.

The initial setup tends to be both straightforward and complex. Although I haven't done an initial setup in a while, everything just clicks together very well. When I did do an initial setup, the wireless controller was up and running within a few minutes. Deploying new controllers into the cluster takes seconds. There are a lot of wizards and guides built into the controllers for setup. So it's very easy.

ClearPass is a little harder, and AirWave is medium difficulty. ClearPass is the hardest part to get going without a good amount of training.

Aruba Wireless has been straightforward to set up.

I rate the initial setup of Aruba Wireless a four out of five.

Initial setup was very straightforward. We set up the switches and APs, then took it from there. 

It's very easily set up.

Default settings are sufficient to get a functioning wireless network up and running fairly easily. Complexity increases add vLANs, security policy, dot1x, redundancy, etc.

The initial setup was pretty much straightforward to be honest. You only configure one AP and when you plug the other ones into the network, it recognizes that that AP is the master and gets the configuration off that.

Initial setup was straightforward. We followed the very basic instructions (connect to the new WiFi network, then go to a website, make some simple changes, save, reboot, done); updated the firmware, and we were on our way.

The initial setup is straightforward and not overly complex. A company shouldn't have any trouble handling the process. 

We had it up and running in a day or two. The deployment is fast.

The initial setup was not complex. There's a CLI, much like Cisco. Aruba's certification is also very similar to Cisco's, which is not very difficult.

The solution's GUI for configuration is complicated. Thus, it is easier to implement if you have experience using it. There should be drag-and-drop features to make it more easier. I rate the process a four out of ten. It takes a month to complete.

For us, it's easy to set up. I don't know if this is the case for everyone, but for us, it's easy. We have people that are certified in solutions, including Aruba. We know how to handle implementations quite effectively.

The time it takes for the deployment depends on the size, however, usually, the process is one to two weeks.

The setup was a little bit complicated. It really depends on the person. If you really don't know and it's your first time that you are touching an Aruba device, then it takes a lot of time. You're not going to get it, if you have never actually touched an Aruba Wireless Controller. You have to have an experienced engineer with you to show you what to do: how to add an AP, how to proceed with all the other configurations. Once you have had your hands on it a couple of times, then it becomes easier.

The initial setup was very simple. There were some settings which were confusing and unlabeled when trying to use the online help with the newer firmware.

The initial setup is straightforward and easy to set up. Simply plug and play and it will automatically block calls. You can change it every Friday or by favorites.

The initial setup is complicated because you have to modify many options, and you have to spend time handling those options, and sometimes you need attendants for these options.

Initial setup was very straightforward. You just plug it in with a few settings.

Everyone has their own method of deploying this product. Each company is different. It may be pretty straightforward or more complex depending on an organization's needs.

It's easy to get going. You can take an access point out of the box and have it running in minutes.

I would say complex, mainly due to the lack of good documentation. All together, it took me about a week to fully get the product in a production state. Coming from a Cisco background it seemed much more cumbersome than their products.

Setup is straightforward.

The initial setup was very complex because we deployed a new controller in a small network. It is useful for large networks, but for small networks, it is very difficult to understand all the models. If you don't use Mobility Master, the configuration and deployment are very complex. It took us six months to deploy it.

You just plug them in, and once you get them configured, they're great from there.

There are ways to sidestep the complexity available with Aruba, but if you do not need the advanced features of Aruba then Aruba instant or another vendor may suit your needs best.

The setup is quite straightforward. The solutions can be deployed based on best practices.

The initial setup is okay. It is straightforward and we have no issues with it.

I have been involved in setups for our customers. It's not too complex. Of course, you need to know the solution very well.

As always in complex systems, initial setup required a lot of work that might be seen as complex. On the other hand it was also logical and among the professionals, straightforward. Initial setup of single equipment is easy, but it only allows you to start configuring it.

The initial setup was simple to do.

It was pretty straightforward.

It's just plug-and-play.

The initial setup was very straightforward.

The initial setup was straightforward. We deployed all of the hardware and configured the controller and watch the AP’s authenticate and associate with the controller.

It is straightforward.

Initial setup was complex, but when you finally set up the whole network, there are no problems.

The initial setup for the 7000 is straightforward for us. We're trained and certified engineers. But for someone who isn't, it's very complex.

It was pretty straightforward.

Sometimes, the initial setup is complex. For example, if I need to integrate with other vendors then there can be issues and we have to do a lot of work to solve these kinds of problems.

The length of time required for deployment depends on the size and density of the network. There are a lot of parameters that dictate how much time it takes, but the average for us is a three to four-day deployment.

I wasn't involved in the setup about four years ago.

The initial setup was not difficult. We had an issue during the implementation, but we fixed it when we contacted support.

The initial setup was very easy and intuitive.

It is straightforward.

You need training on configuration of Aruba products since it deals with a vast range of technology apart from wireless.

The initial setup was straightforward. We have some prior experiences with various types of access-point networks, so it was not an issue.

I think the setup and the configuration of Aruba is complex.

Basic initial setup is very easy when it comes to a new user on-premise.