My main use cases for Red Hat Enterprise Linux (RHEL) include maintaining a stack of servers where we perform monitoring, provisioning, certificate provisioning, and checking patch status across the servers.

The most valuable feature within my systems is Satellite. The features that I appreciate most on a daily or on-demand basis are those provided by Satellite. This feature benefits my organization by providing provisioning for every instance, as we have approximately 100 instances under Red Hat and another 20 under Ubuntu. Currently, we use a single user interface to control them all.

Red Hat Enterprise Linux (RHEL) could be improved by providing end-to-end support for customers because we are seeing that it is more distributed. For all the Red Hat services, we use Satellite, but other services are on the cloud, and some things are hybrid cloud. This means we have multiple platforms to monitor each time. Another area for improvement is the false positives. We have the Red Hat alarm system, and it is good, but it just fires and reports, sending an email every night for us to check our duties. This is really unpleasant for us.

I have been using Red Hat Enterprise Linux (RHEL) for four years.

I have experienced downtime, crashes, or performance issues seldomly. It is good and can solve 80% of problems. Sometimes I seek consultants for help to rebuild the model or to see what the root cause is. Sometimes this problem occurs many times, requiring someone to show up and thoroughly investigate it.

Red Hat Enterprise Linux (RHEL) scales with the growing needs of my organization as it is stable, and I see that with Android development. However, I think it has only increased our usage by 3%. I think it is stable and we will not decommission it, but we still compare the benefits of cloud solutions and the Red Hat solution. I have expanded usage on Red Hat because Ubuntu is an open licensing and very unmanageable, so we are trying to reallocate resources to Red Hat.

I evaluate customer service and technical support as great. My own company has a consultant who is very timely in dedicating support to our services. We can call at any time to seek urgent consultant services. Overall, it is good. We find that rebooting or rebuilding is tough for us. We want to make sure that the service is ready to use, but for some unfortunate situations that happen, we seek 24-hour support to solve the problem as soon as possible. Every second that passes represents a loss for us.

Prior to adopting Red Hat Enterprise Linux (RHEL), we were using Ubuntu, and now it depends on what this product and what this pipeline built initially. If they used Ubuntu at the beginning of the startup, we just use it. We make sure they are up, make sure they are stable, and do not care about anything else. If they use Red Hat, we just keep running with it.

I would describe my experience with deploying Red Hat Enterprise Linux (RHEL) as manageable. It is not out of control. For every server instance, we get notified, and I get an alarm at a very early time, so we can manage to replicate it. This instance has some broken files, which is helpful for the developer to debug and understand it.

When I was deploying Red Hat Enterprise Linux (RHEL), the deployment, particularly the hotfixes, is a real challenge. We have some big instances with the front-end code and back-end code in one service. We have to do this really quickly to deploy hotfixes and implement new features. We need to make sure that the code is consistent across all the services at that time. We can do the Ansible playbook, which is a very good template that we can reuse to replicate the problem.

I have been involved in Red Hat Enterprise Linux (RHEL) upgrades or migrations, as for version upgrades, I have been involved. We still have some Red Hat Linux consultants who support us in doing the migration. I think it is helpful. The seamlessness of the process with the consultant depends on the service difficulty because sometimes everything is hard to ensure that it is correct. It depends on the project size.

I do not touch the pricing and the cost of the solution, but I think compared to some cloud costs, it is good because our team is relying on that. We just make sure that the service is up.

The other solutions I considered before selecting Red Hat Enterprise Linux (RHEL) are that in our company, we have two choices: one is Red Hat and one is Ubuntu.

My security requirements and considerations in choosing Red Hat Enterprise Linux (RHEL) include that this is our manager, and we want to have some endpoints tracking any attack and detecting the status of anything broken. My assessment of Red Hat Enterprise Linux (RHEL)'s built-in security and compliance features is that right now, I think it is simply risk reduction. I am just maintaining it. For maintaining compliance, I can say that the first priority is to keep it safe. The second priority is to keep it up. We make sure they are okay, available to use, and available to maintain. For any other new features, we do not require that. We just make sure of these two things. Beyond this point, we are seeking some cloud help.

My upgrade and migration plans to stay current with Red Hat Enterprise Linux (RHEL) are that we need to upgrade it every year, or just when you have a vulnerability, you need to come up with it and upgrade it. From my perspective, we are not doing really timely upgrading because we do not want to disturb the current pipelines.

For the knowledge base offered by Red Hat, such as the Confluence page, it is helpful. For Red Hat Enterprise Linux (RHEL), the knowledge base is helpful. I try to look up and check many of those pages, and they give me detailed ideas on how to implement the system. Sometimes the problem is really unique, and I can get help or try to get support to formalize some questions and help us understand the solutions. I still need to seek a senior consultant's help on migration. Some documentation is outdated.

My advice to other organizations considering Red Hat Enterprise Linux (RHEL) is that if you use Java, you should use it. If you have many massive servers to maintain, a Red Hat solution with the pipeline and Satellite is beneficial. If you have some old legacy systems, you do not have to set up new labor on monitoring. I give this product an overall rating of 8 out of 10.

My main use cases for Red Hat Enterprise Linux (RHEL) are extensive, but mostly we utilize it for our clients as a base operating system.Red Hat Enterprise Linux (RHEL) solves pain points related to security patching and support.Security requirements for choosing Red Hat Enterprise Linux (RHEL) in the cloud depend heavily on the client's business. For some clients, we don't have any special regulation, but for domains such as oil and gas, there are very strict security requirements that we must meet. In most of the current products, we can find the appropriate and certified product for our clients.

The features of Red Hat Enterprise Linux (RHEL) I appreciate most are centralized account management and SSO. The integration of SSO features, particularly with Azure Active Directory, benefits our organization greatly because it is very easy to grant appropriate access to the operating system.Red Hat Enterprise Linux (RHEL) has helped to mitigate downtime and lower risk.

I don't believe there are any additional features that should be included in the next release.

I have been using Red Hat Enterprise Linux (RHEL) for more than ten years.

What works well for me is that it is pretty stable over the years, and I don't face many challenges with it.I have not experienced any downtime, crashes, or performance issues.

Red Hat Enterprise Linux (RHEL) scales well with the growing needs of my organization.

I evaluate customer service and technical support as brilliant.I regard that support as pretty good.

While I sometimes use other solutions, we are not limited to Red Hat Enterprise Linux (RHEL), and for some cases, we use Canonical products. A long time ago, we used SUSE, but not recently.

I would describe my experience with deploying Red Hat Enterprise Linux (RHEL) as easy.Managing Red Hat Enterprise Linux (RHEL) systems from a central management console is a form of centralized management.I am satisfied with that centralized management console.

I have seen ROI with Red Hat Enterprise Linux (RHEL).

When selecting Red Hat Enterprise Linux (RHEL), the other solution I considered was Canonical, which is direct competition at the operating system level. However, Red Hat provides a more complete integration between the operating system and platforms.What stood out to me in my evaluation process was how easy it is to integrate Red Hat Enterprise Linux (RHEL) into the existing IT processes of our clients, which is the main driver for us as cost concerns are not my focus. Maintaining security patching and support over the long term is also crucial for enterprise clients.

I have expanded usage of Red Hat Enterprise Linux (RHEL) for myself and my clients.My advice for other organizations considering Red Hat Enterprise Linux (RHEL) is that if you are talking about long-term solutions, you need to choose a base infrastructure that is supportable for a long time.I would rate Red Hat Enterprise Linux (RHEL) overall as a nine out of ten.

Red Hat Enterprise Linux (RHEL) basically runs the bank's apps as my main use case.

I like the feature Satellite the most because it has services to manage my multiple Linux servers.

Satellite has no parallel in the Linux distro world, especially for an enterprise, enabling me to manage my servers, patch them, create content, get them binaries, updated security updates, and all that. It makes it easier for admins and reduces the need for a lot of manpower, especially with Ansible that enables me to do configuration management of 20,000 Linux servers.

Red Hat Enterprise Linux (RHEL) scales with the growing needs of my organization very well as we are expanding ourselves.

Red Hat Enterprise Linux (RHEL) has helped mitigate downtime and lower risk because the servers can run for more than 300 days of uptime. I do have to reboot them for patching, but otherwise, they are a very stable operating system that doesn't crash for no reason. If I experience kernel panics, it often involves EDRs or agents such as CrowdStrike, but otherwise, it's very stable with proactive features. We had issues with CrowdStrike; they identified the issue with their kernel drivers that used to crash my OS and provided a patch to address it, so they take care of us.

The implementation had challenges like whenever we bring out new products, there's always one issue: Red Hat Enterprise Linux (RHEL)'s documentation is not complete. I have to really have an enterprise account because I get access to their support, which sorts me out since every environment is unique. It's not a cookie cutter; I would deploy RHEL 8 in a way different compared to a retail store. So when it gets to those niche deployments, they don't have anything documented. I really have to get hold of the support, saying, "Hey, I'm trying to do this. It's not working," and then they will give me a solution, but I would expect that a document would have solved that issue without raising a ticket. That's my only complaint.

The area for improvement in Red Hat Enterprise Linux (RHEL) is documentation. I don't have any other suggestions. I think it's just the documentation that needs improvement. Otherwise, technically, I don't have anything to suggest.

I have been using Red Hat Enterprise Linux (RHEL) for ten years.

I have experienced downtime or security incidents as a result of the solution when proper practices are not followed, especially if I am using any third-party security. You have to manage kernel options; otherwise, the base OS itself is very stable.

Red Hat Enterprise Linux (RHEL) scales with the growing needs of my organization very well as we are expanding ourselves.

I would evaluate customer service and technical support based on my experience. I felt naive about being a small enterprise versus a big enterprise, but the response time of tickets is consistent. I haven't seen a difference; I thought I would have a slower response being on a small account, but the speed of our calls is the same.

I considered other solutions before choosing Red Hat Enterprise Linux (RHEL), but it was a default choice for us. I see that they have expanded; earlier, it was just a bare-metal OS and not an ecosystem, but now they are in OpenShift, providing Kubernetes and everything.

I wasn't using another solution to address my needs prior to adopting it.

The upgrade or migration is straightforward if I have applications that depend less on what the OS is, but in our case, it was not that simple. We had a business requirement, so we had to shut down the older one, provision a new one, and move everything.

I have seen ROI from using Red Hat Enterprise Linux (RHEL) in terms of uptime itself.

My experience with pricing, setup, and cost of the solution is that it's a service based on how many cores, not sockets.

My deployment model for Red Hat Enterprise Linux (RHEL) is on-premises, but I am just starting off with cloud.

For security requirements in the cloud, I don't do SELinux; I just depend on my ACLs because my servers are not internet-facing. We trust Red Hat Enterprise Linux (RHEL) with the binaries, with nothing on the base OS such as firewalls or SELinux.

I use AWS and Azure as my cloud providers.

I manage my Red Hat Enterprise Linux (RHEL) systems for security, updates, and patches with Red Hat Satellite, which makes it very easy.

I have been involved in upgrades from RHEL 6 to 7 and from 7 to 8.

My assessment of Red Hat Enterprise Linux (RHEL)'s FIPS and security compliance features is that it's the best in the industry. They have FIPS, which I think is more for federal clients, and although I haven't used it, I know they offer it by default on their Linux.

My upgrade and migration plans are to always try to stay on the current version all the time, unless there's a legacy application. Any apps I manage are always on the latest Red Hat release, and we keep migrating them as Red Hat provides the first-ever release out, which is a requirement for our Satellite to support the latest version.

The area for improvement in Red Hat Enterprise Linux (RHEL) is documentation.

I would assess the knowledge base offered by Red Hat Enterprise Linux (RHEL) as paywalled, so if you don't pay for it, you wouldn't be able to access their system. The KB is pretty good, but you need to have a Red Hat account.

My advice to a company considering this solution is to go for it. It is supported by enterprise support from Red Hat, which I don't think any other enterprise can offer. While I know Canonical does it for Ubuntu, SUSE is another good option; however, the adoption is not there, and you don't have a lot of sysadmins. Red Hat Enterprise Linux (RHEL) is a bible due to the abundance of resources in the market. I would rate this solution a 10.

The main use case for Red Hat Enterprise Linux (RHEL) is to manage the database and the server.

The solution helps solve pain points for monitoring servers, for example, databases and servers.

The most valuable feature of Red Hat Enterprise Linux (RHEL) is the security and also the performance for scheduling and tasking for the memory.

These features benefit the organization because we have hundreds of servers, databases, and many files, and we have the ability to use Red Hat Enterprise Linux (RHEL).

I am interested in migrating to the cloud platform, so we are trying to implement that in the organization.

I have been using Red Hat Enterprise Linux (RHEL) for five to seven years.

I have not experienced any downtime, crashes, or performance issues with Red Hat Enterprise Linux (RHEL).

Red Hat Enterprise Linux (RHEL) scales well to meet the growing organizational needs.

We are looking for containerization for scalability, and it is easy to scale out and scale in.

We have expanded usage and tried manually to increase the number of servers, and we see the disk increasing exponentially, which is why we are looking for scaling.

I would evaluate customer service and technical support as quite good, since I technically get 24/7 support if I encounter issues from updates or new features.

I would assess the level of support from Red Hat Enterprise Linux (RHEL) team as very informative; we learn a lot from the documentation from the Red Hat support team.

Before selecting Red Hat Enterprise Linux (RHEL), I considered the availability of resources and security, as we have files and a lot of data with not enough time to handle that from the internet, and distribution is mostly for security.

The experience deploying Red Hat Enterprise Linux (RHEL) was easy, as we use different methods, such as installing or using some source files by using some servers to deploy.

The most common challenges faced with the deployment are mostly enterprise related, such as resource compatibility and making automation instead of active compatibility.

The opinion on pricing and its cost-effectiveness for Red Hat Enterprise Linux (RHEL) is that it is quite good for production on-premises.

The advice I would give to other organizations is that they should mostly rely on the Linux operating system; it is quite reliable and easy to use, install, deploy, and manage, so I would advise them to use it.

I would rate this product a 10.

My main use cases include running our application in Red Hat Enterprise Linux (RHEL) since all our applications are based on a Red Hat server. Everything we use is Red Hat Enterprise Linux (RHEL).

As SecDevOps Lead, I drove the adoption of Red Hat’s Ansible Automation Platform, which transformed our deployment process. Previously, manual scripts led to inconsistencies and delays; now, we achieve consistent, error-free deployments in under 10 minutes. Weekly RHEL patching, integrated into our CI/CD pipeline, has strengthened our security posture—critical for meeting regulatory requirements. These improvements have directly supported our business goals of agility and reliability.

A key area for improvement is the ability to apply patches without requiring a full server reboot. This would minimize downtime for mission-critical applications. I’m actively evaluating Red Hat’s live kernel patching solutions and advocating for their adoption to further enhance our uptime and operational efficiency.

I've been using Red Hat Enterprise Linux (RHEL) for almost seven years.

I assess the stability and reliability of Red Hat Enterprise Linux (RHEL) as good since I didn't see much downtime with the servers or any random problems coming up with Red Hat Enterprise Linux (RHEL). I would say it's good in terms of stability.

Red Hat Enterprise Linux (RHEL) scales well with the growing needs of my organization because whatever solutions we are trying, we are able to do in Red Hat Enterprise Linux (RHEL). It's coming along well.

I evaluate customer service and technical support as something I'm not sure about because I didn't directly work with them.

I didn't consider any other solutions before Red Hat Enterprise Linux (RHEL), and I haven't used any other solution to address similar needs.

My experience with deploying Red Hat Enterprise Linux (RHEL) is nice, but I didn't deploy anything from a Linux perspective. Overall, I think it's a nice experience that I have with Red Hat.

When it comes to managing my Red Hat Enterprise Linux (RHEL) systems for provisioning and patching, it has come up well over the years. Before, I think it took a lot of time to provision a server and patch it, including securing and hardening the server. Nowadays, it's very easy. I didn't work directly, but I have provisioned.

I feel that we've seen ROI since I'm not involved in purchasing, but I can feel that it's a good ROI.

My experience with pricing, including cost and licensing, is that I'm not sure.

I haven't expanded any usage of it, apart from using Ansible and Red Hat Enterprise Linux (RHEL).

My assessment of Red Hat Enterprise Linux (RHEL)'s built-in security features when it comes to simplifying risk reduction and maintaining compliance is that it's pretty good from what I've heard when I talk with the team, even though I'm not directly working on that.As for my upgrade and migration plans to stay current, we recently upgraded to Red Hat 8. If we want to do another Red Hat 10, it's good.Red Hat Enterprise Linux (RHEL) has helped to mitigate downtime and lower risk as it allows provisioning servers very easily. In case the servers go down, it comes up very fast as well.I assess the knowledge base offered by Red Hat Enterprise Linux (RHEL) as very good. Recently, I had a walkthrough of a trial, and it's pretty much simplified and whatever we need is there.My advice to other organizations considering Red Hat Enterprise Linux (RHEL) is to just use it. It's easy. I gave this review a rating of 10.

My use case for Red Hat Enterprise Linux (RHEL) is for dockerization; I use it for Docker or Postman. We use it for microservices, for example, to install JBoss and deploy some applications and pipelines for processes such as CI/CD. A summary of what I do includes microservices for applications such as Tomcat or JBoss, or for microservices in Postman, and installing Jenkins and launching pipelines.

Red Hat Enterprise Linux (RHEL) has helped reduce downtime and lower risks for me. There are rarely crashes or errors.

Image Builder or system roles feature is beneficial because it is a feature that allows you to create small images for what you need. With these images, you can go to a registry or whatever with VMware or KVM, and you can deploy them very quickly and efficiently. I tested it because it's better than having to install another machine all over again and losing much time. With Image Builder, you can create a small image tailored to your necessities. It is a good solution; you have to embrace automation, and the Image Builder helps you automate the creation of servers and images.

I appreciate all the Red Hat products available and the support provided when encountering any issues or needing help. You can open a case, and they answer very quickly.

The other reason is it is a very strong OS for your needs. For example, I work in a banking system and in a financial system, and all kinds of products that you have—the problems may come from development, not from the server or machine.

In the knowledge base of Red Hat Enterprise Linux (RHEL), I can find everything I need. I don't have to go elsewhere. There are some videos with practical advice, all in one place, and all for free. I'm very happy with this kind of resource and knowledge base.

I find Red Hat Insights very helpful and beneficial. In all IT departments worldwide, I find it important because when I call my colleagues or other companies, this is a very significant feature. Insights gives many opportunities, particularly regarding security, and provides more facilities to improve security in your servers. In my opinion, the most important security feature in Red Hat Enterprise Linux (RHEL) is Red Hat Insights. When you use Red Hat Enterprise Linux (RHEL), you can install an agent in your Linux, and this agent runs on your Linux and gives you all the CVEs or security issues you have. For me, as an administrator, this is very helpful because with minimal clicks, I have the solutions and instructions on how to solve them. You only need to connect to Red Hat, and they provide a deployment, scan your machine, or all machines with Ansible, and give you a summary of your vulnerabilities, and you apply the solutions they provide.

The areas that have room for improvement in Red Hat Enterprise Linux (RHEL) include having more case bases and possibly more forums or places. A community that is not just informal but rather official could be beneficial. Everything else is good.

I would suggest improving compatibility. Sometimes I find that Red Hat is not aligned with the rest of the world. They create their own solutions, such as Docker, Podman, Kubernetes, and OpenShift, which can be better than what others offer. This can be both good and bad, depending on the situation. On the positive side, their innovations can enhance the overall quality of the company’s offerings. On the downside, when you need certain images or components that deviate from industry standards, it can become confusing. I find it difficult to understand why they choose to differentiate themselves from the rest.

I have been in IT for 24 years, working with Linux and Red Hat Enterprise Linux (RHEL) for about 10 years.

I would rate the stability of Red Hat Enterprise Linux (RHEL) as a nine out of ten.

Red Hat Enterprise Linux (RHEL) is scalable for my business. It is very important, and I cannot imagine working without it.

I would rate the technical support of Red Hat Enterprise Linux (RHEL) as an eight out of ten.

I have worked with Ubuntu and SUSE, but I prefer Red Hat Enterprise Linux (RHEL) because the support is better than others. All solutions, how the machine or OS works, and all the other products, for example, OpenShift, I appreciate. I feel very comfortable with Red Hat Enterprise Linux (RHEL) because it is a solution based on CentOS and Fedora, and since my early career, I studied and learned in this distribution.

The deployment of Red Hat Enterprise Linux (RHEL) is very easy.

Red Hat Enterprise Linux (RHEL) has saved me about 40% to 50% time.

I would recommend Red Hat Enterprise Linux (RHEL) to other users; it depends on the company size. For medium and bigger companies, it is necessary because all the components needed, such as support and stability, are available. I cannot help much with the pricing because I do not work with licenses; this comes from another department. I discuss with my boss about how many machines or servers we need, and they coordinate with the commercials. I do not have information about whether it is cheaper or expensive, but I hear that they are very comfortable depending on how you deal with them.

I would rate Red Hat Enterprise Linux (RHEL) an eight out of ten.

My main use cases for Red Hat Enterprise Linux (RHEL) are that it has been part of our core delivery solutions for many industries, mostly for telecom.

The features of Red Hat Enterprise Linux (RHEL) that I find most valuable include all of the features since system V.

In my organization, Red Hat Enterprise Linux (RHEL) provides an agnostic interface for many storage vendors that we deal with, which helps us to have a wider spectrum of offerings in our consultancy offerings.

Red Hat Enterprise Linux (RHEL) can be improved by adopting a feature similar to YaST from a big European competitor, which would significantly enhance Red Hat technologies.

I have been using Red Hat Enterprise Linux (RHEL) since 2005 when it was in release four, which makes it 20 years.

I would assess the stability and reliability of Red Hat Enterprise Linux (RHEL) as favorable, noting that during the last five years, we've experienced fewer crashes and downtimes compared to other commercial Unix and Linux distributions in the market.

Red Hat Enterprise Linux (RHEL) scales excellently with the growing needs of my organization, and I would rate it ten out of ten.

I evaluate customer service and tech support as excellent; with either the partner portal or customer portal, we receive very good RCAs and analyses for any case we submit to Red Hat Enterprise Linux (RHEL). On a scale of one to ten, I would rate customer service and technical support as ten out of ten.

Prior to adopting Red Hat Enterprise Linux (RHEL), I was using Commercial Unix, Oracle Solaris. The factor that led me to change was that during the last decades, Red Hat Enterprise Linux (RHEL) has absorbed many features straight from Solaris, enabling us to perform effective migrations from Commercial Unix to RHEL.

At the very beginning, at the earliest versions of Red Hat since version six, there was a kernel that was not compatible with many cluster vendors, and that's why we were adopting another vendor of Linux. However, we've seen that during these past years, Red Hat has been experiencing a lot of enhancements overcoming these kinds of barriers. And now Red Hat has become more versatile in accepting more hardware that allows us to standardize our Red Hat offerings in our consultancy services.

I have seen a return on investment with Red Hat Enterprise Linux (RHEL). For data points, in one of the key industries I handle, which is telecom, Red Hat Enterprise Linux (RHEL) has been one of the key strategic providers offering a good price to implement automation and containerization across all of the network elements we manage with several vendors, and in the latest five years, we have observed a good investment return in terms of ROI.

My experience with pricing, setup costs, and licensing is that I strongly believe Red Hat Enterprise Linux (RHEL) offers a good relationship between value and price, and despite it being quite pricey, it's definitely worth it.

Before selecting Red Hat Enterprise Linux (RHEL), I considered SLES, which is a competitor of Red Hat.

My advice to other organizations considering Red Hat Enterprise Linux (RHEL) is to have a good plan and to establish the relationship as a key strategic reference for any upcoming migration. The partnership and customer support provided is a high-value option. Red Hat Enterprise Linux (RHEL) has helped mitigate downtime and lower risk through high availability solutions and key features that enable network redundancy, allowing us to achieve this.

I would assess the knowledge base offered by Red Hat Enterprise Linux (RHEL) as excellent because it has become one of the key standards in the industry for following guidelines according to any topic in the RHEL environment.

On a scale of one to ten, I rate this solution an eight.