HP Wireless Comfort - mouse - 2.4 GHz
Mfg # H2L63AA
CDW # 2744156
| UNSPSC 43211708
Quick tech specs
- Mouse
- 2.4 GHz
- for Chromebook 11MK G9; Chromebook x360; ProBook 44X G7; ProBook x360; Stream Pro 11 G4
- wireless
- USB wireless receiver
Know your gear
The HP Comfort Grip Wireless Mouse features a 30-month battery life and a bold, modern design that integrates seamlessly with HP Business Notebooks.
Enhance your purchase
HP Wireless Comfort - mouse - 2.4 GHz is rated
4.40 out of
5 by
7.
Rated 5 out of
5 by
Luiz Canario from
A stable and scalable solution with useful features and good support
What is our primary use case?
We have about 30 APs and a lot of sites with centralized management on controller 7030. We use it to control the network in standalone mode and handle the active and standby modes.
What is most valuable?
All features are useful for me. It lets me perform some specific configurations depending on the site or the client. All WAN features are valuable.
What needs improvement?
Their documentation needs to be improved. Aruba's documentation is poor.
For how long have I used the solution?
I have been using Aruba Wireless Controllers for about a year.
What do I think about the stability of the solution?
Its stability is okay. There is no issue with stability.
What do I think about the scalability of the solution?
Its scalability is okay.
How are customer service and technical support?
Their support is good. When I need to open a case, I get a fast response. I can contact the technician immediately. I would rate them an eight out of ten.
Which solution did I use previously and why did I switch?
I also use Cisco solutions. Both solutions are very good and suitable for different kinds of networks. Cisco is very good for certain kinds of networks, and Aruba is good for other kinds. Cisco is simpler to deploy, whereas Aruba is more complicated and complex to deploy.
How was the initial setup?
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.
What about the implementation team?
We got help from a third-party vendor, not Aruba. They were okay. We didn't have any problem.
What other advice do I have?
You should know about the topology of the Aruba Wireless solution. It is very important because it depends on the size of the network. Otherwise, you might end up buying something that's not adequate for large networks.
I would rate Aruba Wireless an eight out of ten.
Disclaimer: My company has a business relationship with this vendor other than being a customer:Partner
Date published: 2020-12-06T00:00:00-05:00
Rated 5 out of
5 by
MichaelZhang from
A stable solution with efficient support
What is our primary use case?
We provide Wi-Fi to all staff and students at the university. They just have to connect to it. They use Aruba Wireless for teaching, learning, administration, and research.
For how long have I used the solution?
We have been using Aruba Wireless for more than three years.
What do I think about the stability of the solution?
It's a very stable system.
How are customer service and technical support?
They provide very efficient support.
What's my experience with pricing, setup cost, and licensing?
I think it would be better if they lowered the price.
What other advice do I have?
On a scale from one to ten, I would give Aruba Wireless a nine.
Disclaimer: I am a real user, and this review is based on my own experience and opinions.
Date published: 2020-12-08T00:00:00-05:00
Rated 5 out of
5 by
DImo Dimov from
Stable, scalable, and flexible featured with helpful customer service
What is our primary use case?
We use the product predominately for beacons and peer devices.
What is most valuable?
It has very flexible features.
What needs improvement?
I believe more security options are needed.
For how long have I used the solution?
I have been using the product for seven or eight years.
What do I think about the stability of the solution?
We have not had any problems with the stability of the product.
What do I think about the scalability of the solution?
It is a scalable solution.
How are customer service and technical support?
When we have had to use support, everything from the service was helpful.
Which solution did I use previously and why did I switch?
We have used Cisco products in the past.
How was the initial setup?
The setup is not a problem, it only took five minutes or so.
What about the implementation team?
We used five technicians for the deployment of the product.
What other advice do I have?
I rate Aruba Wireless a nine out of ten.
Which deployment model are you using for this solution?
Hybrid Cloud
Disclaimer: I am a real user, and this review is based on my own experience and opinions.
Date published: 2020-12-16T00:00:00-05:00
Rated 5 out of
5 by
reviewer1312101 from
Overall a good product that provides role-based authentication native to the controller, but has code stability issues
What is our primary use case?
We run a number of guest wireless networks with captive portals with layer 3 networks. We run .1x for corporate SSIDs or wireless networks for additional certificate-based and/or WPA2 security.
How has it helped my organization?
Aruba has a lot of features that work particularly well. One of the things that Aruba is trying to do in most of its product ranges to make sure that all of their products now have a fully functioning northbound set of APIs. That basically means that you can plug it into any kind of system that you have for some operational pieces. For example, if you want to have Tufin, but more in line with things like change management. We're a ServiceNow shop, so we use that for change management and orchestration.
The ability to use the APIs that are available in the Aruba Wi-Fi controller means that you can get information from the system very easily by using APIs, or you can push changes to it. So, if you want to lock administrators there and restrict the type of functions that people can do, you don't have to give them access to the systems anymore.
This functionality has been useful for us because we have recently outsourced a lot of our lower operational tasks to an outside vendor. With that, obviously, other people need to access systems, but we don't always want to give them direct access to the system. So, we can provide them with APIs to be able to perform basic tasks without giving them access to our dashboard services.
What is most valuable?
Aruba is an industry leader. The hardware is on par, and its performance is also on par with anybody else. The Aruba brand really only focuses on wireless, so they're not competing their R&D for switching data center products and cloud security. They're really focused on that and their underlying key pieces.
They provide a role-based authentication that is native to the controller. A lot of other systems don't do that. They won't provide you the ability to basically have everybody join the network, regardless of whether or not they share the same network space, the SSID, or the wireless LAN. You can segment it down to a specific user role based on any kind of attributes that you like. That's their differentiator. If you need per user, per device, or per port segmentation, you can get that with Aruba. There isn't another vendor who does it.
What needs improvement?
Currently, the stability of the code is the basic underlying problem for us. They had an 8.6 release that came out two weeks ago, but we had to migrate twice because the code wasn't stable. We can't get things to work the same way. Version 8 was a big change for them. They made a change so that it is forced to be a managed hierarchical system. It means that you make changes at the top, and it pushes them downstream. There are a lot of problems with the 8.6 version code. I ran into four bugs in one week and was informed that we should just move onto the next one because all of those fixes have taken place. The feedback loop for fixes is not always really relayed back to you.
I don't have a lot of strong things to say about version 8.6. When we had version 6, the controller was pretty much rock solid. We had no problems. We made a heavy investment to migrate a lot of stuff to take advantage of things like WPA3, Wi-Fi 6, and all that kind of stuff, and we haven't been able to turn those features on because we are not confident that they are going to work just yet. So, right now, we're still very much stumbling through the version 8.6 code and just trying to make sure that it is safe before we turn on some of those features.
In terms of the marketplace, they are one of the top three leaders. In some respects, one of the things that they focus on is wireless. Therefore, there are some things that should be beyond reproach, as far as I'm concerned. In terms of the stability of the code, there are always going to be bugs, but the core stability of the code needs to be there. When it is not stable, that's a real problem for me because you lose a lot of confidence in the products.
For how long have I used the solution?
I have been working with Aruba Wireless for about four years now.
What do I think about the scalability of the solution?
It is pretty good. There are a lot fewer people in the office, obviously, because of COVID. Under normal situations, we were probably about 2,000 users a day. Between 40% to 50% of that would be corporate users with mobile devices, such as iPhones, as well as laptop users accessing corporate resources and the corporate LAN. We also have guest users.
They are really moving towards making it cloud-based and less attractive for you to use on-premises. There are still a number of limitations with the cloud. One of the reasons we don't use cloud controllers is that they're not able to support more than 250 access points per tenant instance. For example, you have two sites. One has 200 APs, and one has 300 APs. You could put one site in the cloud so that you wouldn't need to have on-premises wireless controllers. You could manage it all from the cloud instance, and you would have zero hardware and all that kind of stuff.
However, you wouldn't be able to deploy the second site in the cloud because you can't put more than 250 APs. So, now you have got to go back to doing it the old-fashioned way, which is to have on-premises controllers or two management suites. You don't want to do that because the way this new code works is that it is hierarchical, meaning that you build your configuration centrally, and then you push it down to your access points or your local controllers. So, if you've got one management session in the cloud and one management session on-premises, you would have to manage them at two places.
I do understand that you can configure that local hardware. So, for the site that has 300 APs and a local controller, you could plug that controller into the cloud, but it is still for two different models. So, the companies that just want to have a very simplified setup or want to make it less complicated, they can just say that we're going to go cloud or just stay on-premises, but now you have to have a combination of both, or you just stay with on-premises. There are still some basic limitations preventing us from doing wireless deployments where controllers are based in the cloud.
How are customer service and technical support?
I use them a lot. Sometimes, I use them every day. They are pretty good. There is a problem in getting hold of people. That may be just because of COVID, but it is very much dependent on when you call and the type of issue that you have.
If it is a fairly standard issue, if you need assistance with a programming or configuration change, or if you need to know how to do something, you can normally get a very quick resolution. The meantime for resolution is pretty quick. It is within that call, half an hour, or one hour. You can generally speak to somebody. If it is some of the things that I have experienced or a bug, it can be very problematic. It could take days or weeks to get resolutions.
The basic stuff is really good. Anything past that, you probably need to have a dedicated support engineer on your camp if you're big enough, or you need to have resources that really know how to do the legwork beforehand.
Which solution did I use previously and why did I switch?
I worked for a company that had Cisco for many years. Actually, towards the end of that, I switched them from Cisco to Ruckus. I did a POC and a pilot between Ruckus and Aruba, and Ruckus came out on top because of its simplified approach to wireless networking. I have also used Meraki, which is Cisco's cloud-only based AP solution.
Cisco is like the other de facto. A lot of shops are all Cisco. Their hardware is probably on par with Aruba in terms of processing and handling capabilities. Features are also probably the same. It is more like a Ford-GM question. If you were brought up in a Ford household, you are probably going to buy a Ford sort of thing. I don't think there is much to them, to be honest.
The differentiator for me is that Cisco has a product, which is its network access control system, called ISE or identity services engine. That's a terrible product. It really is an awful product. It is very cumbersome, and it makes adding network access control to your wireless and wired networks very problematic. Aruba's product is called ClearPass, and it is a very flexible tool and easy tool. It is a much more reliable tool. While it doesn't have all the features that you can use with Cisco, it is a standard network application system, which means it will work with any vendor for any system. So, you can do 90% to 95% of the stuff you want, and it is a much more stable and capable system. This difference and the price are differentiators for me.
From a purely wireless perspective, I think that Aruba is number one. Cisco is a very close number two, and then Ruckus is actually a distant third. Ruckus doesn't have all of the advanced capabilities, but what it does, it does very well. If you want a very basic entry-level wireless that is cheap for K-12 schools or a lot of environments like that, you can use Ruckus. If you need some of the advanced stuff, then you're going to have to pick one of the other solutions.
How was the initial setup?
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 com...
Disclaimer: I am a real user, and this review is based on my own experience and opinions.
Date published: 2020-10-22T00:00:00-04:00
Rated 5 out of
5 by
Gaurav Vyas from
Good functionality, straightforward to set up, and the technical support is okay
What is our primary use case?
We are using this solution to provide office internet for our clients.
What is most valuable?
The functionality is very high and we can properly meet the clients' requirements.
What needs improvement?
When we connect to Wi-Fi devices it could be easier because sometimes, it takes a lot of time to complete.
It is not as easy as some other products to configure, including setting policies.
Otherwise, everything is fine.
For how long have I used the solution?
I have been working with Aruba Wireless for the past four years.
What do I think about the stability of the solution?
I have not found any bugs or glitches in this product.
What do I think about the scalability of the solution?
We have more than 100 users.
How are customer service and technical support?
Technical support is alright.
How was the initial setup?
The initial setup is okay. It is straightforward and we have no issues with it.
What's my experience with pricing, setup cost, and licensing?
The price of Aruba Wireless should be cheaper.
What other advice do I have?
For the most part, there is nothing that needs to be added and I can recommend this product.
I would rate this solution an eight out of ten.
Which deployment model are you using for this solution?
Hybrid Cloud
Disclaimer: I am a real user, and this review is based on my own experience and opinions.
Date published: 2020-10-22T00:00:00-04:00
Rated 5 out of
5 by
Huthaisa Al Saaideh from
Easily manages of all your wireless devices
What is our primary use case?
I have worked with versions 2.207 and 3.303 and 305. Because I am the service provider for my customers, I've worked with Ruckus, Aruba, Cisco, and UniFi. Most of my customers ask for new wireless solutions. Last week I installed 37 access points. My customers are very satisfied.
What is most valuable?
Configuring the main controller is very easy; with Aruba, it's just plug-and-play. The roaming features are great too.
What needs improvement?
Most of the access points don't include the chargers. If you want to increase your coverage, then you need to have a charger. When our customers ask about access points, we always recommend Aruba; however, when we tell them that they need to buy the chargers separately, they become upset, saying: "We already bought Aruba access points, the chargers should come with it".
This is my main concern. In the last five years, I've installed nearly 300 Aruba access points and most of my customers have complained about the chargers. If this problem was addressed, I wouldn't have any other complaints.
For how long have I used the solution?
I have been using this solution for five years.
What do I think about the stability of the solution?
I have not experienced any bugs, software, or hardware issues with Aruba.
What do I think about the scalability of the solution?
This solution is both very stable and scalable. I want to mention something about Aruba's compatibility between various model types. If you already have version 207 installed and you want to switch to version 3.3, it's not compatible; you can't add it to your network. You need to create a standalone network for this access point only.
How are customer service and technical support?
I only spoke with Aruba's technical support one time. With Aruba, you don't need a lot of support. It is very easy to use.
How was the initial setup?
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.
What other advice do I have?
The most important thing is the heat map; you need to have a good heat map and make sure it's configured correctly with Aruba. If you don't have a heat map, you may have issues.
Here in Jordan, some providers will go to a company that requires 10 access points and tell them they only need five. In reality, they just want the job and the client. Then, after everything is said and done, the client complains about the five access points not covering the whole area.
Some preparation is required before you can get started with Aruba. The total amount of power needed for the access points needs to be calculated. I would recommend doing this yourself as some companies just want to sell their products.
Companies in Jordan were quite loyal to Cisco, but in the last five months, I have installed roughly 500 Aruba Switches. Version 1920 is very popular; it's very fast and great for network stability.
Cisco and Aruba offer the same features. My customers don't need advanced features. What's the point in spending an extra $300-400 dollars for features you won't even use?
On a scale from one to ten, I would give this solution a rating of eight. If they increased their coverage, I would give them a rating of 15, not simply ten.
Which deployment model are you using for this solution?
On-premises
Disclaimer: My company has a business relationship with this vendor other than being a customer:Partner
Date published: 2020-10-18T00:00:00-04:00
Rated 5 out of
5 by
Jorge Aldana from
A scalable solution that provides a great user experience
What is our primary use case?
We provide services for clients, so it's always a different use case. For example, we work with a retailer and we focus on electronic tasks. Another is corporate offices in a bank, one of the biggest banks in Mexico. Another is massive events like the Olympics with different sponsors. There's a big difference in the type of use cases.
What is most valuable?
In the case of the contacts or the callers, Aruba Wireless offers a good user experience. For example, there are a lot of the contacts in the retail store, we are talking about 100,000 users connected at one time. After evaluation, Aruba Wireless was considered best for large numbers of users like this.
What needs improvement?
The network times for protocol synchronization can be improved. Sometimes it's complicated, and we need to tweak it to coordinate or synchronize it to the clock at the network access point.
I have some issues with the introductory domain with the frequency that we use. For example, it's very common to have a box with a frequency channel with the introductory domains in Mexico. The access points have some issues in this release; I think it's version eight.
Sometimes the documentation is confusing. You have to figure out a lot of different placements on your own because of the outdated information.
For how long have I used the solution?
I have used Aruba Wireless for about five years.
What do I think about the stability of the solution?
Aruba Wireless seems to be very stable. I don't remember having any issues with stability.
What do I think about the scalability of the solution?
Aruba Wireless is scalable. You can add more people. You can use the same configuration for 50 or 2,000, or 5,000 users.
How are customer service and technical support?
Aruba Wireless technical support is too slow, or it used to be. For example, to test a domain in Mexico, they would spend about three months.
How was the initial setup?
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.
Which other solutions did I evaluate?
We always evaluate options to see what's best. For example, sometimes, the ARM is more relative, and Aruba is more efficient than others. Cisco has the same functionality, but sometimes the main link will disconnect the users. You don't have that problem with Aruba Wireless.
What other advice do I have?
For those interesting in using Aruba Wireless, I would recommend taking a simplified approach to the license. They should analyze options relevant to their systems as it can get more complex. At this moment, there are a lot of licensing options.
On a scale from one to ten, I would give Aruba Wireless a nine.
Disclaimer: My company has a business relationship with this vendor other than being a customer:Partner
Date published: 2020-12-23T00:00:00-05:00