Setting up Aruba ClearPass is complex. It's a complex installation.

The solution was easy to set up. There was a feature that needed 15 to 30 minutes to load. This is a concern when there are hundreds of projects because it wastes time. The onboarding time still needs to be considered.

When deploying the solution, we do the pre-configuration at our office, so every device should be configured. Afterward, we send the devices to many customers' locations. That's why we need onboarding time to be reduced because we are not dealing directly with the deployment. We are using panels.

I would rate it an eight out of ten, where ten is the easiest and zero is the most difficult.

The setup was straightforward with no issues. Deployment took one month and was a challenge because we had to integrate 600 devices. 

The initial setup was okay for us. A partner managed it, and we had no troubles. The deployment took about six months because we had a lot of user migration and needed to change device authentication.

The deployment is a challenge. Some of it is environmental and specific to the end-user. It can be hard to get all of the information together and pre-check the environment. Depending on the size and complexity o the environment, it can be a bit easier or harder. 

From an implementation perspective, about one to three people are needed depending on the size. One would need to be really experienced. You'd need a pre and post-sales engineer working hand in hand.

From a maintenance perspective, it's mostly set and forget. You might need to check it from a firmware perspective or if there are changes in the environment. 

It's fairly easy to set up. The vendor we work with is good and we are quite familiar with how it works. We use other similar products and don't have issues with the setup. Similar to Aruba and then Aruba Wireless, it is easy to manage with one vendor or one full contractor and you leave it there.

I'd rate the solution nine out of ten in terms of ease of setup. 

We spent maybe three or four hours across two days doing the deployment. 

In terms of maintenance, you need to handle patching and vulnerability management sometimes. Historically, maintenance has been fine with the older versions. Recently, it is a little bit challenging.

We have three people who can the maintenance. Typically, one person is needed for the job.

Aruba ClearPass is very easy to set up.

The time it takes to deploy the solution entirely depends on the customer's needs. Installing the software is very quick which can take about an hour. However, customizing and configuring it with all the different options can take from one day to a week or two depending on what the customer wants.

I was not a part of the initial setup, however, Aruba is typically simple to set up. 

It is easy to look at the deployment phase in two parts. If you are looking at the base installation, then it was a very straightforward process, which I would rate an eight or nine out of ten. If you look at the tool's deployment phase from a fine-tuning perspective, I feel it was very complex.

The solution can be deployed in three months. Three to four people in my company were involved in the deployment process.

The configuration was very complex. It is not a product that normal users can use. A bunch of technologies are involved. There are a lot of other policies, which also include device posturing and management. There are many features involved in this product, best used by experts.

If you implement all of the modules, deployment will be perfect. Otherwise, it is not possible because it is very complex. You need to understand the entire system. Since we are just starting with this product, we need to redirect our switching and wireless traffic to the NAC solution. We need to know the network controller features and infrastructure.

The initial setup of Aruba ClearPass was simple.

We have had some issues with the installation of Aruba ClearPass. 

The initial setup for Aruba ClearPass isn't complex, but you need the training to set it up.

The deployment for the solution is very easy, and you can install it within half an hour, but this is a NAC solution. In terms of configuration, it's not a switch configuration or an IT configuration. Aruba ClearPass has one thousand scenarios in our network, and the problem is that you need a lot of information, so its configuration isn't as straightforward.

The initial setup was a bit complex and took a couple of days.

The initial setup of Aruba ClearPass was really very difficult.

The solution is deployed on-premises.

Aruba ClearPass' deployment process that involves the configuration from scratch can take up to a couple of weeks, especially if you are not familiar with the product.

The solution's GUI and configuration workflow could be clearer to understand. I rate its setup process a six. It involves analyzing customers' requirements and starting with a POC. Once it is done, we order equipment and a license. Next, we deploy the solution offline and integrate it with the production environment. The entire process takes around two to three months to complete.

The initial setup was straightforward and the deployment took almost a month. 

I rate the solution's initial setup a six on a scale where one is difficult and ten is easy. There are some difficulties when installing the solution. For our company, installation is not difficult since we are system integrators who are well-versed in Aruba ClearPass. However, one of our customers told us that it is difficult to manage the installation part of the solution.

The solutions deployment was quick because our company is well-versed in deployment. So, it took around twenty to thirty days. Usually, four L3 engineers from our company are involved in the deployment process. For the maintenance and deployment of the solution, we have a lot of people in our organization. So, our company has around 28 engineers, and we serve around 120 customers in UAE. Specifically speaking, two network engineers are handling the maintenance part of the solution.

Deployment took one day.

The initial setup was quite complex, it is not that easy.

It took maybe two weeks. It takes a long time because it depends on the customer's industry or location or on the user's computers. It's not that fast normally.

The initial setup is easy and there is no need to install anything whether you buy the virtual platform or the appliance. It's all very open and clear and a matter of configuring for policy enforcement. 

Installing Aruba ClearPass was quite easy. The deployment process for it was quite easy and quick. It took our partner less than two weeks to deploy the solution, so it was quite quick.

The initial setup is straightforward. 

The initial setup of Aruba ClearPass is simple. It is done through the CLI asking questions that need answers to be input. It takes approximately 20 minutes to complete.

The initial installation is simple. The deployment could be better since it has fewer capabilities than other solutions, it could be more flexible.

Initial setup was fairly straightforward following the “Start Here” wizard. Our only real “snag” was the Active Directory integration, but that was remedied by our SE.

The initial setup of Aruba ClearPass is straightforward. When you need to activate the rules it becomes difficult.

Like most security products, ClearPass is difficult to deploy. You need to use the CLI to implement security products from any vendor, so configuring the authentication is complicated. Some have a GUI, but the CLI is more powerful. However, after you get the authentication protocols set up, you can forget about this device. It's stable.

It is not easy, but it is also not complex. Anyone with some amount of implementation expertise can easily implement it.

The number of people required depends on the requirement. If the requirement is not big and the customer is an SMB, then one or two implementation engineers are enough for implementation. If the customer is an enterprise customer with a big network, you might need more than two or three implementation engineers.

The deployment duration depends on a client's assets. For a client with 400 or 500 assets, two to three weeks would be required. If the network is very big, it can take one month.

While the installation itself is not difficult per se, the process you need to go through before installing the solution is complex. There are a lot of configurations to do on the firewall network and it can take a while, depending on the company. 

While it's tedious before the installation, once you come to the actual installation itself, you'll realize it's not too bad.

We're working on a project right now that has ten deployments and that's taken us about four or five months. For this project, there have been five people involved in the deployment process.

The solution was implemented before I gained ownership of it. I'm not sure of the history behind it.

Initial setup of the solution is relatively straightforward. There are a lot of videos and documentation available on the internet.

When it comes to the initial setup, as a customer, you need to prepare your own decision matrix. Once the matrices are in place, the rollout of ClearPass is seamless. It is easy. However, if you don't do your introspection and homework then it could be a challenge for an organization.

Aruba ClearPass is complicated to install. Before our clients can use the solution they typically do a POC and we loan them some equipment for them to test with.

The projects from negotiation to acceptance take approximately three to six months.

The implementation can improve because it is challenging to explain some of the concepts to the client.

Whether the setup is straightforward or complex will depend on how you need to apply the product. It can be streamlined or be quite intricate.

Because of its newness it was complex, but the end result was pretty straightforward.

The basic network set-up is straightforward to get it on the network. Activating the licenses and getting the subscription key for ClearPass is a bulky and compression process with very little guidance or documentation. If there is an issue with the license, the only solution to almost always call Aruba tech support. Once the licenses are sorted out an upgrade needs to happen and the size of the update is 1.4Gb or more and based on the customers network, may take a long time. Finally, after ClearPass is on-line and fully updated, the configuration and basic troubleshooting is pretty straightforward. If it’s the first time someone is looking at it there is defiantly a learning curve.

The initial setup is straightforward and takes two months to complete.

The initial setup of Aruba ClearPass is very easy.

The deployment took about two years, and then it took about two weeks for the configurations to be activated. 

Initial setup is straightforward. It is recommended to read the manual before implementation.

ClearPass isn't hard to set up, but it takes a long time.

Aruba ClearPass was installed into the cloud and had the resiliency working. Then we had a test lab environment where we rolled out the configurations, to test it, and then we rolled out the overall configuration for all of the switches and access points around the network. The whole process was straightforward. The whole process took approximately three months from start to finish.

Deploying ClearPass is very straightforward. We are an Aruba integrator, and we've installed ClearPass for more than 10 clients. You can deploy it with two or three engineers, and the time needed for deployment depends on the client. Installing ClearPass for a larger client will take about one week, but a smaller client takes only about three days. 

The initial setup is straightforward. It takes around fifteen minutes to be deployed. Just one engineer can deploy the solution.

If you know what you're doing, deployment doesn't take much time. It requires first deploying a V-LAN schema so you have to keep that in mind. 

The initial setup was complex. The deployment was fast, but in order to tune the policy, install the agent, and do everything else, I would say it took around 4 to 6 months.

It was a little complex to set up. Following the installation guide makes the initial setup easy.

The initial installation is straightforward, but creating the services is sometimes a bit complex.

The time of deployment depends on the customer's use case, but the typical duration is approximately 10 days.

It was extremely complex in our heterogeneous, scattered environment. To be able to deploy a NAC solution without ‎causing downtime is a tedious task.

When there are a lot of requirements, the initial setup will be complex, so it depends on the organization’s requirements.

The initial setup for Aruba ClearPass is not that simple, yet it's not that complex. Setup-wise, it's a five out of ten.

It is really easy to set up. It is very user-friendly and easy to configure.

It doesn't take a lot of time to deploy and configure ClearPass. It takes about a week or a maximum of 10 days for the whole deployment.

We deployed it with assistance from our distributor.

It was too complex. There is too much functionality in one device such as RADIUS, Guest, Provisioning, On-boarding, and NAC.

We plan deployments considering all the configuring that needs to be done on the other integrated devices. The setup always ends up smooth and straightforward.

Generally speaking, setting up a network access control solution is complex. You have to integrate the use cases.

The initial set-up was straightforward.

The initial setup was quite complex because of the lack of detailed documentation.

The initial setup is straightforward and easy to do. It took less than a week to deploy.

It was hard at first because I didn’t have any training and was trying to figure out the best way for us to use this product with deploying 802.1x.

It is complex in a good way that gives you full flexibility to do a lot of scenarios.

It depends on the scenario, but if the use cases and prerequisites were defined correctly before the implementation then it will be easier to implement.