Red Hat Enterprise Linux (RHEL) Reviews

Red Hat Enterprise Linux is the underlying licensing system that our third-party tool uses. It offers convenience. We can open a case when we want to escalate anything. 

The tool's insights included with licensing is good. Security patching is also a good feature for us.

I don't like the UI changes that come with different versions. 

The tool's support is good. Sometimes, support comes from India. I try to wait and ensure remote support is from the US so that it fits the timeline. 

The product's deployment is straightforward. 

We are a big data shop that has around 700-800 nodes.

Red Hat Enterprise Linux Leapp was very helpful. It is very easy to use. 

Our servers run for 500 days, and we reboot them every 600 days. 

I search through Red Hat Enterprise Linux's knowledge base daily. 

We use Red Hat Enterprise Linux 8.6 since the third-party tool is compatible with it. 

We use satellites for the operating system and Ansible to do the configuration. 

I rate Red Hat Enterprise Linux a nine out of ten. 

Red Hat Enterprise Linunx's most valuable feature is patching. 

I am not happy with Red Hat's support. It is difficult to find knowledgeable people. It's hard to troubleshoot. 

I have been using Red Hat Enterprise Linunx since 2009. 

We used Solaris before Red Hat Enterprise Linux. Solaris' environment is closed, while Red Hat Enterprise Linunx is open-source. 

Red Hat Enterprise Linunx's knowledge base is good, and you can find answers there. 

I rate the product a nine out of ten. 

We use containers to create RPM packages for graphics drivers.

The main reason to use Red Hat Enterprise Linux is to maintain support for creating images for various purposes, including what we use for gaming. We rely on a range of supported tools and resources, and this enables us to build images tailored for specific target devices.

The RPM manager is paramount for us, as we need to generate these packages for our customers, enabling them to install the packages on their systems at a later time. The knowledge base they offer has proven to be quite efficient and we haven't encountered any significant challenges.

The technical support should be improved. I believe it would be beneficial to notify the customer in advance of any planned maintenance so that we can better coordinate and plan our customer interactions accordingly.

We have been using it for six years.

Recently, we encountered issues when the Red Hat server was in maintenance mode, and we attempted to capture images directly from another server for our builds. Although I set up alerts for planned downtime on the Red Hat server, I didn't consistently receive these alerts. I would rate it seven out of ten.

Neutral

We follow a weekly patching schedule to fetch the latest updates. Our process involves applying these patches to the image and then generating containers, which we subsequently upload to our registry. We accomplish this using Ansible.

The only inconsistency we've noticed so far is with the server, which might be the only aspect we could potentially raise concerns about. Overall, I would rate it eight out of ten.

We use this solution as our operating system.

The security, ongoing support, and ease of taking a system and getting authorization from a government agency have helped the way our organization functions.

The built-in security features support certain security standards such as encryption. It is simpler to meet FIPS 140 encryption requirements such as the ATOs.

The ease of use of this solution has been most valuable. 

The cost of this solution could be improved. 

I have been using this solution for two years. 

This is a stable solution.

We previously used Linux. Red Hat meets our needs more comprehensively.

Our main ROI is in the ability to readily get ATOs.

For somebody familiar with the Linux platform, it is not difficult to troubleshoot when using this solution.

I would rate this solution a seven out of ten. 

We use this solution for different projects. It's great as a realistic training platform and we've also used it for humanoid robots. We are platinum partners of Red Hat and I'm a digital solutions architect. 

We chose to go with this solution because it's easier to use than other operating systems. It provides illustration ability and better permissions. It has good compatibility which is an issue I have with other operating systems. I find it to be a more flexible product.

Most of the complaints people have about this solution revolve around security. It's not easy to increase that. 

I've used this solution for almost a year. 

The solution is stable. 

The solution is scalable. 

We use the online community for our support and it's great. I can find the answers to all my questions there. 

I previously used CentOS, which is related to Red Hat. It was our client who decided to switch to Red Hat. I've also used Ubuntu which is an open-source solution with low security and therefore not suitable for enterprise-size organizations.  

The initial setup was straightforward because I'd already had some experience with Linux. Even without experience implementation is relatively easy. Deployment time depends on the project and usually takes longer with android applications because the deployment is not one process. We usually deploy on cloud, sometimes private and sometimes public. 

I think the licensing costs are reasonable. 

I recommend RHEL because although there's not much difference between it and CentOS, it does provide full support. If you have any issues you know where to turn and they can be solved. 

I rate RHEL nine out of 10. 

We deploy front-end and back-end software applications on RHEL, and it's our app server. Most of our app servers and our production servers are on RHEL. They're running on RHEL, and that's why they are profiting from it. I2C is the issuer in the processing payment industry. Basically, we do the issuer processing for credit cards, and all the bank magic that happens when you swipe a credit card is handled by us. We're also using RHEL servers for processing debit card payments.

Customer support is valuable. Because most of the Linux distros are open source, most of them don't have customer support. RHEL isn't open source, and that's why I prefer it more than other distros.

Their pricing and documentation can be improved. They need to have developer variance that's more developer-friendly and less costly. They have a free developer version, but that's very limited in terms of features from RHEL. They also need to build their own open source community.

I've been using RHEL for about four months.

RHEL is very stable. Unlike Kali-Linux or Solaris, RHEL solutions are very stable. We have licensed projects, and they must be stable to provide all customers with instructions. They're stable, compared to other Linux options too.

It's very scalable. When you're using the right machine and the right settings or right parameters, it's highly scalable

Technical support from their customer service team is very good. They give responses unlike other Linux distros, and I think RHEL has better customer support.

My current company was using Solaris before. I was using Core Linux for three to four years. From Ubuntu, I shifted to RHEL and Solaris because I changed companies and jobs. We are using RHEL and Solaris in my current job, and I had to shift to these operating systems.

I have used the Ubuntu Linux base, I have used Kali-Linux and Debian. Of all those Linux systems, I think RHEL is much better, but I find Ubuntu much easier to use than RHEL.

Ubuntu is Debian-based, and Red Hat is, I think VM based. Another difference is open source systems have less support. Still, the community of Ubuntu is very strong and answers your query very promptly. But Red Hat is a certified, licensed product, and customer support from them is very good.

RHEL is expensive. The servers or cloud images are quite expensive. But I guess the client groups they target can afford that kind of a license. If you're a small business owner or a student and want to shift to RHEL, you must spend a lot of dollars. The developer version of RHEL has minimal functionality, but it's given away for free.

I would tell potential customers that they should go for the latest releases. If they want to buy it, they should get a developer account from RHEL first and use that dev account before buying it. They might have some hands-on experience before spending too much money on Red Hat.

On a scale from one to ten, I would give Red Hat Enterprise Linux (RHEL) an eight.

I use it for running RAID servers, Database clusters, and a lot of other open-source tools. I have also used it as a firewall.

We have on-premises dedicated servers located in some data centers. We also have cloud servers on the public cloud. I am currently using the latest version, and I have also worked on previous versions as well as Template.

Its security is the most valuable. It is very stable and has many features. It also has good performance.

Some of our clients were using Windows servers and products. I suggested Red Hat Linux to them and described the features. They switched to it, and they really loved it. There were around 50 servers in my last company, and they switched all those servers from Windows to Red Hat. I used to manage those servers.

It is mostly better than other solutions. However, it is sometimes difficult for disaster recovery, so we have to plan accordingly.

I have been working on Linux for the past ten years.

Based on my experience, it has been stable. I did not experience any issues.

It is scalable. I scaled it in a way that I put a load balancer and a few servers running behind that. When working with clients, we scale or expand usage based on the need.

I used to work on and manage a website, which was just like YouTube. Around 1,000 users used to use the site, which was definitely putting a load on this server. There were around 30 servers managing the traffic. I could manage 1,000 simultaneous users.

I have never used their support. I just do some research to resolve an issue.

I have also used Ubuntu and CentOS in different companies and for different clients. The utilization of packages, commands, and configuration files are different in Ubuntu. For example, if you want to restart a service, the commands are different in these solutions. They also have different firewalls. Red Hat uses firewalld and Ubuntu uses ufw.

The deployment is actually okay. It is not too easy and not too complex. It is easy for experienced people, but if you don't have the experience, it can be a little hard. 

The deployment duration depends on the type of deployment that we are doing. It could take from a day to a week or two weeks. We can also use Jenkins for auto-deployment.

I worked with a Cloud hosting and deployment company that provided different Cloud services to their clients. They had servers based on Red Hat. It does require regular maintenance. We had a team of ten people.

Red Hat Linux is inexpensive. Linux solutions are generally inexpensive.

I would definitely recommend this solution. It is my most preferred solution. I like using terminals, and with Red Hat, I get to work on terminals and shell commands. It has good security. 

I would rate Red Hat Linux (RHEL) an eight out of ten. I find it excellent, but no system can be 100% perfect.

Business: workstation and server.

Open architecture allows for accelerated growth while secure repositories guarantee stability.

• Multipath
• Yum 
• LVM
• Selinux

Workstations: More applications for graphics.

Servers: More applications for monitoring (e.g., nmon).