My impression is that the initial setup process is straightforward. It took about one week to complete the deployment. I think there is one person involved in the deployment and maintenance of this solution.

The initial setup for Ubiquiti Wireless was pretty straightforward, and I did it myself.

The product is very easy to install. My company only deals with the software configuration part of the product. My company is not certified to attach Ubiquiti Wireless to the ceilings or the walls since Ubiquiti has a set of electricians to take care of the fittings. My company only configures the product from a networking point of view. I see that the configuration part of the product is really straightforward.

One or two people are required to configure the product. It is even possible to configure the product from a remote location without having the need to assess the customer's headquarters.

Setting up Ubiquity Wireless is simple, and when something doesn't work, you can intervene via SSH. 

The solution is very easy to set up. It is not overly complex. 

It's fast to deploy and only takes two to three hours. 

We have six people that handle deployment and maintenance. 

We haven't had any problems with deployment.

The product's initial setup phase is fairly straightforward, but it all depends on how much of a complex infrastructure you have. In general, the setup process is straightforward. If a user wants to have some advanced stuff during the product's setup phase, the process can get a lot complicated.

With the controller part, the product's user can manage the devices on the cloud.

The solution is deployed on an on-premises model.

The time required to take care of the product's setup phase depends on how a user wants to deal with the setup process. For a simple connection, a straightforward setup process is required. For managing the complex stuff, the setup process can get complicated.

The initial setup was quite straightforward and the system is very user-friendly. You can start firmware updates right from your phone and configure the whole thing. The initial setup is via the web browser and connected to the cloud. It takes 10 to 15 minutes and then you connect the controller with your cloud account, add switches and access points. There is a good instruction manual that is simple to follow and the system is easy to boot. Once completed, search for new devices, and within 10 seconds all appear in your network. It does require basic IT skills, but it's okay. I installed it myself using the manual.

The system requires a Cloud Controller which collects all the metrics and statistics from the devices and then pushes the data to the cloud. It's a public cloud hosted by Ubiquiti Networks. It allows you to view all the collected data and options.

The initial setup is simple. However, it depends on the number of shipments per month. In our scenario, with ten shipments per month, the setup took around four hours. This time frame includes finding all the necessary information on websites, considering our need for prior experience with this equipment. Despite this, we completed the setup within the allotted time frame of four hours.

I rate the process a nine out of ten.

The solution's initial setup could be more straightforward. It takes half an hour to complete tests and finish the process after installation.

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

It is very easy to set up. If I am a new user, for example, I can search for instructions on YouTube. Many videos on YouTube will help. One time I used it to learn how to install and configure very easily.

As per the technicians' feedback, the installation is straightforward. We have a team of three engineers for the product maintenance.

The initial setup of Ubiquiti Wireless is easy and the implementation can take up to several hours.

It's a fairly easy setup even if you don't know Ubiquiti and it's your first time. You follow the instructions. Compared to something like NewCitrix, Ubiquiti is a million times easier to set up. So I think Ubiquity would be for a normal IT guy and whatever, Ubiquiti would be an easy setup where, specifically guys like that, that have to set up NewCitrix, you have to learn how NewCitrix works and then run with it like that. But from initial setup, I find Ubiquiti extremely easy to set up.

Ubiquiti is on-prem, but it has a cloud-based deployment and management system. You connect it to the system and do your setup as soon as you've done your setup, and you basically finalize your system, then you can take that cloud link away. Your system runs without it.

Our organization handles Ubiquiti Wireless maintenance and troubleshooting internally. We also provide managed services for some clients, managing all the day-to-day transactions and monitoring their wireless networks. We have about eight wireless engineers responsible for all technical aspects, including deployment and maintenance of Ubiquiti Wireless and other technical tasks.

It is quite straightforward to set up the solution. It is not overly complex. The deployment was fast and took less than a day.

The product's initial setup phase was easy.

The solution is deployed with the help of a router, switch, and Wi-Fi.

The solution can be deployed in an hour.

There is a professional person to handle this step-by-step process of setting up the device.

One person, who is the main engineer in our company, is required to take care of the deployment and maintenance processes of the product.

The initial setup is simple to set up. I did not take part in the process. However, I haven't heard of any issues. 

It takes about one hour to deploy and connect a node. It might take a month to set up a full network.

We have ten staff, including managers, that can assist with the deployment and maintenance. 

The initial setup of Ubiquiti Wireless is easy.

Setting up Ubiquiti Wireless is very simple, very basic.

To set up a network: getting access points installed, and depending on what I was using for a firewall, and getting an SSID secured and set up, it takes 20 to 30 minutes. That does not include mounting it anywhere, but just getting it out of the box, connecting it to a switch, then actually getting it configured. It's straightforward.

The initial setup is quite simple. It's not too complex. 

The deployment time depends on the device. For the Mesh system, each access point will take around one to two minutes. It will auto-set the device once it's connected to the network. Generally, it's pretty quick, however, if you have a bigger environment, it takes longer.

The amount of technical staff needed to maintain the solution depends on the size of the company using it. For example, if you have a hotel with around 50 wifi access points, you need around two to three people to maintain it monthly.

The solution is very straightforward. It's not overly complex or difficult. We didn't have trouble with the implementation process. 

The deployment only takes a few hours. 

This is occasional maintenance that needs to be performed, however, I don't know how often this activity is performed. We do have one of the technicians here that can work with the product in case of any problems. It's not one specific person; it's just one of the technicians. We have some IT specialists and some of them work in the role of support. We have a network engineer, however, the solution that we have here is quite simple. It's not rocket science to see what is happening with the access point. It's pretty low maintenance as a solution in general and is easy to manage.

It is pretty straightforward. Even non-technical people can set it up by following the videos on YouTube.

This solution is easy to install, but it's a premium product so not everybody knows how to install it, compared to the entry-level ones. If you set up a NETGEAR or a TP-Link or one of these, they are very similar. The adoption process with Ubiquity becomes too difficult if you don't know the setup scenario and without using Cloud solutions.

Generally, the initial setup is straightforward if you're connecting Ubiquity to Ubiquity and you've used components that are all theirs. If you don't understand the product and you try to say, for instance, put Ubiquity in with some legacy APs, then it's difficult.

Most laymen can set up a Ubiquity-only system from scratch.

We are certified and took Ubiquiti's training, which was a five-day training class. Deployment is fairly straightforward for us thanks to the training that we have had.

The initial setup is easy. The complete deployment took one week. 

We have three people involved in the deployment and maintenance. 

I don't do the setup personally, but I can see that once you understand how to roll the solution out, the process is relatively straightforward. Being able to adopt the device, see it on the management system and configure it, are all easy to implement.
Complexity also depends on what you're implementing. Setting everything up in the lab prior to on-site deployment means that you can complete the installation in less than an hour, which makes it look efficient and professional. If adjustments need to be made later it can all be done remotely, this is one of the benefits of cloud management and remote access equipment. 

While it can cause some problems in installation if you use a software controller, it's actually pretty easy. If you are familiar with the network protocols it is straightforward.

There's only one person that handles deployment and maintenance tasks. That's me. It's pretty low-maintenance. 

The installation was not easy. The documentation was not straightforward and they were not complete. They need to improve on this. We had to navigate the internet to find solutions to many of our issues. There was not one place we could have all the information needed for the installation to go smoothly. The deployment took approximately three days.

It wasn't complicated to set it up.

The initial setup was easy and took approximately half a day.

The installation took two days to complete. It was complex to install because of the radio server authentication and integration with the active directory.

Installing Ubiquiti is easy.

It is quite easy to set up.

It most likely took me an hour. 

The initial setup is straightforward.

The initial setup of Ubiquiti Wireless was complex. However, the second installation was easier.

The setup is easy and user friendly.

The solution is very easy to set up. 

We basically just propose the solution and the client will look at the price and agree to it or not. If they do, we install it. that's our basic implementation strategy.

You can deploy the product in about two hours. You only need one person to deploy it. It's not labor-intensive. 

Depending on the customer, we may have only one site or maybe multiple sites where we need to deploy the solution with one controller. Some customers have only one site, and others might have ten. All the sites may be interconnected by a VPN.

It depends. You can have a standard access point, which is very simple to install. It requires minimal configuration, depending on the typology of the customer. Or you could get into some of their higher-end gear, which could take two to three days to configure correctly.

It takes between a few minutes and an hour to install an access point.

The initial setup is quite straightforward. I'm not exactly sure that what I see is always something everyone is capable enough to do. We have a technical team to develop our own solutions within the technology and access points to make it more stable and functional. But for people without these resources, it could be harder to use.

The initial setup is not overly complex or difficult. It's very easy to set up. That's a great selling point, actually. The implementation rolls out very simply and it's quite straightforward.

The entire installation is very quick and takes less than an hour to execute.

We have two admins and four engineers that can handle deployment and maintenance responsibilities.

The product is easy to install, however, it's technical. You need to have a technical person involved, and if you do it will be an easy installation. 

This solution is easy to set up.

I've had instances where the setup has taken 10 to 15 minutes depending on how big the install is and depending on how complex it is but sometimes an adoption like that can maybe take half an hour.

Sometimes when you are trying to set up the access points it comes with old firmware which makes it have problems when setting it up on the controller. It can be very difficult. However, if the firmware is not too old it will work fine. 

The initial setup is very easy. The length of time required depends on how large the installation is. Some deployments are as little as one day, whereas others can take a month to complete.

Ubiquiti is easier to install than Mikrotik.

You can install Ubiquiti in 30 minutes, and Mikrotik will take two hours.

Ubiquiti doesn't present any issues for our engineers to maintain but Mikrotik is a bit more complicated.

The initial setup is straightforward, I did it myself. We have around 40 users in the company. We have three or four developers who were involved in deployment and still now in the maintenance of the solution. 

Installation is quite straightforward and quick.

The initial setup, at least the switches in and the access points, is very easy.

It took 10 minutes to install one device. We needed 2 administrators for installation and maintenance.

The initial setup is very straightforward. It's not complex at all.

Deployment is very, very fast. It only takes about three minutes or so.

We'll handle the maintenance for our client as required.

The initial setup is not complex. The implementation was very straightforward and simple.

In terms of deployment, a wireless setup takes about 15 minutes or so. It's pretty fast.

In terms of maintenance, you only need one admin person to handle it.

The installation is very easy and took approximately one.

The implementation is straightforward but it primarily depends on the length of the microwave links that you want to deploy. If it's a long link, it's a bit more complex and takes more time. Overall, however, it is very straightforward in the implementation. 

The initial setup is straightforward. The VLAN part is complex.