Red Hat Enterprise Linux (RHEL) Reviews

I use Red Hat Enterprise Linux (RHEL) for its specific security features.

Red Hat Enterprise Linux has specific security checks that are beneficial. We follow its support and it helps with security verification.

The security features are the most valuable. The long-term support for weekends is also beneficial.

Risks, for example, specific to Linux, need improvements.

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

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. 

Positive

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. 

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 for disaster assistance. 

This solution has increased the speed of our technology. It is easy to troubleshoot using RHEL. RHEL's built-in security features and security profiles for helping to reduce risk and maintain compliance are good. It has also improved our organization's management and efficiency.

The cost of this solution could be improved. 

I have been using this solution for four years. 

This is a stable solution and we have not had any major issues when using it. 

The customer support team are very responsive and always provide the help we need. I would rate the support a nine out of ten. 

Positive

We used to use JBoss at my previous company.

I would rate this solution a nine out of ten. 

For applications, we are the OS support. We build servers and deliver applications.

RHELs overall effect on our organization's management and efficiency has been good. It's easy to support and involves no downtime. It is simple to handle, apply patches and maintain.

The most valuable feature of this solution is how easy it is to use.

When there is down time from a system admin perspective, this solution could improve how they communicate why this down time is happening. 

I have been using this solution for seven years. 

This is a stable solution. Our machines reside on vSphere and when a server goes down, we have to find out the root cause. This requires pulling information from the vSphere. 

I would rate the support for this solution an eight out of ten. 

Positive

We previously used Solaris. We moved to Red Hat because it is easier to manage and more cost-effective. It is also easier to manage patches and security using Red Hat. 

I was only involved in testing this solution during the deployment process. During testing, it was easy to make changes to configurations which also support our decision to use Red Hat. 

This is a cost-effective solution.

I would recommend this solution to others. It is easy to use, manage and handle with very little downtime. 

I would rate this solution an eight 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. 

Typically, we use this solution as a base to create and secure container images. Sometimes we use SELinux through RHEL and sometimes we only use RHEL. It is easier to apply STIG baselines to a RHEL system than other systems. We mainly use it for building and securing containers.

RHEL is different than any other Linux distribution folder. Folder locations are different and using this solution makes us more secure.

We are assured of added security because of the STIGs, automation and all the repositories that exist for securing Red Hat and SELinux. We have scripts that can automate the STIGing out of an RHEL machine, RHEL container or an RHEL BM.

It is also easy to troubleshoot using RHEL and follow the same process as other solutions such as Ubuntu, Debian, or Arch.

RHEL's effect on our organization's management and efficiency is noticeable because we check all the compliance boxes when we run STIG machines. It helps us because Red Hat is trusted in the governmental space. It also helps management save people's time by just having use of templated containers.

There's a lot more automation for STIGing out a Red Hat machine than there is in a Ubuntu or a Debian machine and this is one of the most valuable features. 

Since it's based off Fedora, I don't like the DNF package manager. 

I have been using this solution for six months. 

It's very stable. I've never had any breaking issues when upgrading packages or versions. 

We run this solution on a really small scale. We are a development group so we're not working on large-scale systems. We generate proof of concepts and then show that to the company for them to use so I can't really speak to how it scales.

Red Hat's tech support and customer service are really good. The Red Hat team are my favorite people to work with. They are easy to work with and genuinely care. I would rate them a nine out of ten. 

Positive

The initial setup is mostly straightforward depending on the specific setup. We build our own containers and that is more complex but there are simplex supported setups. In both scenarios, maintenance only involves a few commands and is simple. It is maintained by two security engineers. 

From an ROI perspective, this solution helps us win contracts. Contract values are negligible to what the RHEL licensing cost is. It has a really large effect on our contract deals because it gives our work and service credibility.

I would advise others to read up on the solution first. Try Fedora first before you get into Red Hat. There are some similarities and a lot of what you know about Linux transfers over. 

I would rate this solution a nine out of ten. 

We are internet service providers in Bangladesh and resellers of this product to our customers to manage their network infrastructure. 

I think this solution is more secure than others because it's not open source. Red Hat will ensure the details when you purchase the package. Having a certification will offer value. 

We've found that there is a huge demand for it. 

Although the security features are good, I'd like to see more added in the security sphere.

I've been using this solution for just three months and still not completely familiar with it. 

The solution is stable. 

The documentation is sufficient for my needs. 

The initial setup is easy, it takes around 10-15 minutes. 

I rate this solution eight out of 10.