I use Red Hat Enterprise Linux (RHEL) to manage applications and for system administration. The latest version is Red Hat Enterprise Linux (RHEL) 10, which has AI with Red Hat Lightspeed inside the operating system, where you can write natural language in the terminal. I am using artificial intelligence inside Red Hat Enterprise Linux (RHEL). I am working with Ansible, which is an automation tool from Red Hat. I install Ansible inside Red Hat Enterprise Linux (RHEL) and make many automations.

Red Hat Insights helps in monitoring Linux servers, providing CVEs that need updating in the operating system, and giving information about server security.

In the latest release, there are three important new features: Red Hat Lightspeed with AI integration, image mode capability allowing Red Hat Enterprise Linux to be imaged and transferred to another VM, and Quench-key cryptography for enhanced security. The AI integration through Red Hat Lightspeed is particularly significant as it differentiates it from other operating systems.

SELinux is valuable for security purposes. SELinux is very good because we can give the correct permissions to the employees. 

Red Hat Lightspeed, added in the latest version, and image mode features are also significant features.

Red Hat Enterprise Linux (RHEL) is already good and perfect. They can continue to improve the AI features.

I have 10 years of experience working with Red Hat Enterprise Linux (RHEL). I worked as an operating system specialist for five years, performing administration tasks such as managing LVMs, users, groups, disks, and performing troubleshooting inside the operating system.

Their support is very good.

Positive

I worked with SUSE and changed to Red Hat Enterprise Linux (RHEL) because I worked at IBM for five years, and IBM bought Red Hat. All systems were integrated into Red Hat solutions. 

SUSE is very similar to Red Hat Enterprise Linux (RHEL), but I prefer Red Hat solutions because their support is much better. I believe that the support and updates from Red Hat are superior. For example, Red Hat has a feature called Red Hat Insights, which allows me to proactively manage incidents and identify vulnerabilities. SUSE does not offer these features.

The deployment is easy.

Red Hat saves time with integration with tools such as Ansible for automation. 

I am not involved in the pricing, but it is not very expensive.

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

I used it previously in environments for APIs, Apache Tomcat, and JBoss. 

The most valuable aspect of Red Hat Enterprise Linux (RHEL) is its reliability. The support is very good. 

The knowledge base offered by Red Hat Enterprise Linux (RHEL) is excellent. It is very easy to search for solutions to problems and apply new features. 

The main concern is the price. 

I used Red Hat Enterprise Linux (RHEL) for five years recently, and about ten to twelve years overall. The last time I used it was last year.

It's reliable. Red Hat Enterprise Linux (RHEL) did not help much with our uptime or security.

The support with Red Hat Enterprise Linux (RHEL) is good, and it is similar to Oracle. 

Positive

In the bank, we use Oracle Linux, but previously we used CentOS.

It was easy to manage in terms of provisioning and patching. We used other products to update the systems, though I don't remember the name. I had other teams to manage the environment. I was satisfied with the management process and the management experience.

It's expensive.

I would rate Red Hat Enterprise Linux (RHEL) a ten out of ten. I would recommend it to others. It is very stable.

My main use case for Red Hat Enterprise Linux (RHEL) is hosting applications.

My company benefits from using Red Hat Enterprise Linux (RHEL) by having more secure workstations and inviting more beginner users.

The feature of Red Hat Enterprise Linux (RHEL) that I appreciate the most is the new Boot C that's coming out. That's been pretty interesting. 

RHEL helps me solve the pain point of feeling disconnected from the community. I've been feeling more involved and considered. Previously, a lot of documentation was for connected instances, and I work for an air-gapped network. Now I appreciate seeing that the documentation actually has disconnected settings. It's neat to be included in there. 

I appreciate the documentation. The knowledge bases are pretty good. Usually, when I have an issue and find a Red Hat knowledge base, it addresses the issue.

Red Hat Enterprise Linux (RHEL)'s built-in security features are really well designed for simplifying risk reduction and maintaining compliance. I see many new technologies coming out are geared toward security or enhancing security. It's neat that it's continuing to evolve.

My upgrade or migration plans to stay current with Red Hat Enterprise Linux (RHEL) involve leaning on our unclassified environment before we can upgrade, as I'm in a disconnected network. As soon as we're able to, I'm trying to upgrade as often as we can. It's because I want to utilize all the new tools coming out in 9.6 and now 10. We just got to RHEL 8, and I'm already ready to leap RHEL 8 to get the newest features.

Improving Red Hat Enterprise Linux (RHEL) can be tough, however, a significant area is collaboration tools. We have many Windows users that use Outlook and Skype or Teams to collaborate on our network. They want Linux desktops due to the fact that they want to use containers. Their biggest complaint is, 'I need two workstations to do my container work and one to collaborate.' If somehow RHEL can start introducing or collaborating with Teams and Outlook so their users can work with their Windows peers, that would be great. But I don't think that's available yet.

Regarding pricing, setup costs, and licensing, there needs to be more of an education piece to it. For instance, when purchasing 10 or 100 node licenses, they could suggest, 'We also offer this 1,000 node license instead, and it'll save you specific amounts.' Just more education on their offerings would be helpful, because usually, we're coming out with the requirements, and then they just provide it to us. They could inform us about saving by bundling it differently or using alternative approaches.

I've been using Red Hat Enterprise Linux (RHEL) since 2012, which is 13 years now.

The stability and reliability of Red Hat Enterprise Linux (RHEL) have been pretty good. We haven't had any issues, major crashes, or anything similar.

The scalability of the Red Hat Enterprise Linux (RHEL) platform has been able to meet my company needs for servers. The workstations are a little difficult, but overall it meets our requirements.

Regarding customer service and technical support of Red Hat Enterprise Linux (RHEL), I really enjoy it. 

With many other vendors, I have problems with support and back and forth, getting escalated, routed all over the place. Usually, when a case gets assigned to someone from Red Hat, it's handled in a timely fashion, and it's precise. There's no guessing or reading from scripts. It's direct to the point.

I would rate the customer service and technical support of Red Hat Enterprise Linux (RHEL) an eight and a half to nine. The only reason for not giving a perfect score is that there could be more knowledge base articles or documents. There's not always a Red Hat instance for what I'm looking for, however, when there is one, it's always accurate.

Positive

Before implementing Red Hat Enterprise Linux (RHEL), I used CentOS and Fedora. The main difference between Red Hat Enterprise Linux (RHEL) and those prior solutions is the support.

I would describe the experience of deploying Red Hat Enterprise Linux (RHEL) as pretty simple and straightforward. The GUI is really interactive, and it's really easy to build from scratch.

The biggest return on investment when using Red Hat Enterprise Linux (RHEL), from a technical point of view, is that it reduces man-hours. 

With Ansible, it definitely reduces man-hours in patching or being able to configure or manage systems across the country with hundreds of systems. The approximate reduction of man-hours that RHEL provides is in the hundreds. I couldn't imagine administering a couple of hundred servers one by one. 

We have to implement quarterly security checks and remediations that come out in bunches of 30 at a time. Having to do that on each box would take forever. I could probably only do four or five a day with our few hundred servers.

We did not consider any other solutions while using RHEL.

I have been involved in migrations or upgrades of RHEL, and I just completed a leap upgrade from RHEL 7 to RHEL 8. We manage our Red Hat Enterprise Linux (RHEL) systems when it comes to provisioning and patching by using templates from VMware to deploy our RHEL boxes, and for patching, we use Red Hat Satellite to provide the patches. We also use Ansible platform to run the plays, to kick off the updates and the reboots.

I rate Red Hat Enterprise Linux (RHEL) a ten out of ten.

My main use cases for Red Hat Enterprise Linux (RHEL) now are mostly traditional workflows, web applications, and web servers.

Red Hat Enterprise Linux (RHEL) has benefited my company by offering great features such as Satellite and all the enterprise features that provide us value, which enables stability and maintainability.

Red Hat Enterprise Linux (RHEL) has helped me solve pain points by providing significant maintainability compared to other Linux distros.

It is very stable and enterprise-ready, giving me substantial stability and manageability. 

Red Hat Enterprise Linux (RHEL) has helped mitigate downtime and lower risk significantly.

With Satellite and everything else, we can effectively control which patches go to specific servers and reduce risk with different CVEs and insights, providing us with substantial control.

We manage our Red Hat Enterprise Linux (RHEL) systems using Satellite, which works really effectively, and we also use Ansible Automation Platform.

My assessment of Red Hat Enterprise Linux (RHEL)'s built-in security features shows many cool features in the new version. From what I have used in 8 and 9, there are good features such as built-in firewalls.

Although SELinux is complex as it does a lot. I cannot fully understand it, so that could be simplified. The only thing that I really have difficulty with is SELinux, so perhaps there is room to make it more accessible.

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

Red Hat Enterprise Linux (RHEL) has been able to scale to the growing needs of my company. We are not a huge company, so it works effectively.

The customer service and technical support for Red Hat Enterprise Linux (RHEL) is pretty good. We have used them extensively and they work effectively.

Positive

Before choosing Red Hat Enterprise Linux (RHEL), we were using legacy systems running on AIX, but all new implementations are now on RHEL. The main difference between AIX and RHEL is the support from third-party applications. When installing third-party applications, there is always support for RHEL and almost never support for AIX.

I would describe the experience of deploying Red Hat Enterprise Linux (RHEL) as really easy. It is similar to other systems, and I am really excited to explore Red Hat Enterprise Linux (RHEL) 10 and try Image Builder.

The biggest return on investment when using Red Hat Enterprise Linux (RHEL) is the manageability we receive, with numerous features in the packages that free up substantial time from the operations side of things.

The pricing, setup costs, and licensing for Red Hat Enterprise Linux (RHEL) are within normal operating system pricing ranges.

While using Red Hat Enterprise Linux (RHEL), I did consider other solutions. There are always many other options, such as another RHEL distribution, but RHEL is the only one that has extensive support for numerous other systems.

We have not fully implemented Ansible Automation Platform yet, but we are starting to integrate it and we really appreciate it. 

I would rate Red Hat Enterprise Linux (RHEL) from one to ten overall as probably a nine.

My main use cases for Red Hat Enterprise Linux (RHEL) are everything from research computing to hosting websites. We've run a gamut of different things with RHEL. 

I used to use it a lot for a healthcare company and healthcare software. Now predominantly, it's research that is very statistically intensive. So anything where we have to do data computations, data rates, we need to synthesize data, aggregating it from instruments all over the world or within the lab itself. We take all of that, and we also use it to produce applications for people, whether it's just interacting with it via a website or an actual homegrown application where they can go through, search, look at the data, and do their own data manipulation.

My favorite feature of Red Hat Enterprise Linux (RHEL) is the ease of use; it is streamlined, making it very intuitive to do things. 

The ease of use of Red Hat Enterprise Linux (RHEL) reduces time for my company. It reduces the time to do things, allowing us to do very complex tasks in a very short period, since it is very straightforward and makes it easier to get things done. 

It has been around for so long, and it's such a standardized platform that the knowledge base from the employee perspective is usually pretty high compared to other enterprise Linux distributions. Therefore, the overall time savings with RHEL is huge.

Our upgrade or migration plans to stay current with Red Hat Enterprise Linux (RHEL) involve adhering to a rule: once a version reaches end-of-life, we do not enter the extended life cycle. We plan that out ahead, ensuring that all of our systems get migrated and updated about a year before the end of life of any version. Some systems get migrated to the latest version while others remain and just get updated to whatever is current. It depends on the application and its external dependencies, but it's just a solid plan we follow.

Red Hat Enterprise Linux (RHEL) has helped us mitigate downtime and lower risks, as we've utilized virtual machines and process load balancing to minimize issues. While we've had downtime with any systems, there tends to be a lot less with RHEL. We have had some systems running just for fun for three years without any downtime, which reflects their stability. I would say that RHEL has reduced risks by at least 80% compared to open-source distributions based on experiences in recent years.

To improve Red Hat Enterprise Linux (RHEL), the biggest thing is the availability of some tools that unfortunately have to be paid for. While I understand that you have to pay for resources, it would be nice to have a centralized location where you can easily find those tools.

I have been using Red Hat Enterprise Linux (RHEL) for close to 20 years.

Regarding the stability and reliability of Red Hat Enterprise Linux (RHEL), we have systems that we've kept running for years without any downtime, so I have never had a problem with stability or reliability.

Red Hat Enterprise Linux (RHEL) has scaled right along with our growing company needs; the only exceptions to that are with supercomputers, but that's a whole different animal.

My experience with customer service and support from Red Hat Enterprise Linux (RHEL) has been good so far. I haven't needed to use it often, which goes back to its reliability. Whenever I've had issues reaching out, they've responded quickly with appropriate information.

We have looked at other solutions while using Red Hat Enterprise Linux (RHEL), such as Debian, Ubuntu (a Debian spinoff), FreeBSD, and some others, however, we keep going back to RHEL due to its reliability and available resources.

The deployment experience with Red Hat Enterprise Linux (RHEL) has been very easy; we've been doing it for years. The automation that they've built over the years to do the deployments just makes it easier and easier every year, transitioning from kickstarts to using things OpenShift. I'm excited to see how this Image Builder works with that, too, so it has continuously improved.

The biggest return on investment for me from using Red Hat Enterprise Linux (RHEL) is just overall time saved. 

We have looked at other solutions while using Red Hat Enterprise Linux (RHEL), such as Debian, Ubuntu (a Debian spinoff), FreeBSD, and some others. We keep going back to RHEL due to its reliability and available resources.

I would rate Red Hat Enterprise Linux (RHEL) overall at least a solid ten out of ten.

Our main use case for Red Hat Enterprise Linux (RHEL) at the moment is for our dev machines, as we do software engineering for automotive, and we have a lot of developers who need Linux. We had a bunch of systems and other things, and we are now rolling them all to be standardized on RHEL.

The management dashboard, RHEL satellites, Ansible, and all those integrations have been the most valuable features of Red Hat Enterprise Linux (RHEL) that really help us. 

The features of Red Hat Enterprise Linux (RHEL) allow our company to standardize our fragmented ecosystem, which consists of a lot of Windows systems and different development environments, so that we can move away from the 'it works on my machine, it doesn't work on your machine' issues.

We are deploying workstations with Red Hat Enterprise Linux (RHEL), and we also look at deploying on-prem. We already have some cloud deployments through third-party contractors, and we are trying to tie it all together into one system. We also have high-performance compute on-prem for doing GPUs, CPUs, and simulations, and we have workstations on-prem with potential cloud workstations as a migration area.

We are migrating some workloads, such as local development tasks, to Red Hat Enterprise Linux (RHEL), but we haven't really started with the servers yet. Currently, we manage our Red Hat Enterprise Linux (RHEL) systems using the cloud portal to build a custom image for our machines, but we want to move toward satellites and use that as our comprehensive management and patching tool.

Utilizing all the security features of Red Hat Enterprise Linux (RHEL) is really important for us as an enterprise with a lot of security focus in automotive and intellectual property, and we are easing into some features such as different security profiles to ensure a secure experience for our users.

We have been trialing on Red Hat Enterprise Linux (RHEL) 9.5. We are now looking at moving towards RHEL 10, which is going to be one of our migrations before we go full production launch on this, and we're looking at doing incremental upgrades as we go to have the latest stuff available.

With Red Hat Enterprise Linux (RHEL), there's a lot of fragmentation in the documentation across different versions, and ensuring that the right version is being read can be challenging. Features such as AI assistants would provide a more unified experience, which is really helpful for IT teams who may not be Linux-centric.

I have been using Red Hat Enterprise Linux (RHEL) for just a couple of weeks as we are starting to deploy it. We originally did not have any Linux systems with us and are now moving forward with that whole process.

The stability and reliability of Red Hat Enterprise Linux (RHEL) seems to be rock solid from our perspective, as we have workloads running continuously 24/7, and the only reason we shut it off is to install a full reboot update or if the workload fails due to our own issues.

Red Hat Enterprise Linux (RHEL) is definitely going to scale with our company's growing needs. Other elements of the company have been using RHEL in production, and from our perspective as a small R&D center, it provides the flexibility to manage multiple sites in California, Michigan, and keep them all synchronized, reducing the need to send IT individuals to California to fix problems.

I would rate the customer service and technical support of Red Hat Enterprise Linux (RHEL) a ten out of ten. We really felt that with our Red Hat partner, there's personal service that has helped us build better solutions for our team; it has been a truly awesome experience.

Positive

I have only been with the company for a year and a half, so I'm not aware of anything they've done with other Linux OS solutions, however, we have primarily been Windows from a developer perspective, and now we are starting to get into using Linux systems on a daily basis, focusing on workstations for now.

We purchase Red Hat Enterprise Linux (RHEL) through a roster indirectly, and that will be our deployment methodology for any AWS deployments of RHEL AMI images. My assessment of the pricing, setup costs, and licensing for Red Hat Enterprise Linux (RHEL) is that our finance team handles it, and I've been hearing good feedback; they find the licensing model much easier to understand.

For us, the biggest return on investment when using Red Hat Enterprise Linux (RHEL) has to do with standardization and the ability to manage a fleet of devices, whether on-prem, in the cloud, or servers, through unified portals using standard processes and reducing fragmentation among machines.

Before choosing Red Hat Enterprise Linux (RHEL), we looked at Ubuntu Pro and a couple of other options, however, we decided that RHEL fits better into our ecosystem, particularly in our adoption of OpenShift for DevOps, as it's best for our developers to have the same development environments from end to end.

On a scale of one to ten, I would rate Red Hat Enterprise Linux (RHEL) a nine.

My main use cases for Red Hat Enterprise Linux (RHEL) are for the core banking systems. It is a much more stable OS than other competitor operating systems, especially with Databases.
Most banks in Iraq use Linux, whether it is free like CentOS for a UAT environment or enterprise like Red Hat.

The Red Hat Satellite makes my life much easier when it comes to managing my Red Hat Enterprise Linux (RHEL) systems for provisioning and patching. Before few years ago, each server had to have internet access to make updates or deployments. After joining the Satellite, it's just one push, and all the patching is done. And all the datacentres prohibit having external access. So we can create a local repository at our Red Hat Satellite and then push it to other servers, with the option of choosing a specific version to push for all servers.

Furthermore, the IDM, which is FreeIPA, is great. I appreciate how it makes the management much easier for me, even when managing more than 500 users same time. Like when someone leaves the company or someone joins, it's easier for me to onboard or respond to other things. It makes my system more secure by monitoring all the user's activity, which is another important point since no one can have direct access to the server without being authenticated and authorised by the IDM.

The Red Hat Satellite makes my life much easier when it comes to managing my Red Hat Enterprise Linux (RHEL) systems for provisioning and patching. At first, we had to access each server to make updates or deployments. After joining the Satellite, it's just one push, and all the patching is done. All this distribution also helps us as we use it on-prem, and all the data centers prohibit external access. So we can create a local registry at our Red Hat Satellite and then push it to other servers without issues regarding version changes.

I am a big fan of Red Hat Enterprise Linux (RHEL) built-in security features, which simplify risk reduction and maintaining compliance, and I would just say we achieve 99% success. I remember a few years ago when there was a zero-day attack. Red Hat was the fastest company to respond. We found out about it at six o'clock PM, and the next day at eight AM, they had some fixes and pushed updates. So we could respond directly and implement the fixes. Any security breach with Red Hat, I do not want to speak about others, since we face worse responses from other companies.

My upgrade or migration plans to stay current involve understanding the concept of OpenShift, which has not yet become very popular in Iraq. I try to keep pushing the client to understand the concept of containers and other things. It will take some time, however, it's a good feature to move ahead with OpenShift containerization. Even with the Central Bank regulation, we have to remain on-prem, thus OpenShift supports this point and offers a flexible solution. Red Hat Enterprise Linux (RHEL) has helped me mitigate downtime and lower risks by about 80%.

I am a big fan of Red Hat Enterprise Linux (RHEL) built-in security features, which simplify risk reduction and maintaining compliance, and I would just say we achieve 90% success. I remember a few years ago when there was a zero-day attack. Red Hat was the fastest company to respond. They had some fixes and pushed updates in few hours from discovering the security breach. So we could respond directly and implement the fixes. I don't like to mention the other competitors, since we face worse responses from other companies.

My upgrade or migration plans to stay current involve understanding the concept of OpenShift, which has not yet become very popular in Iraq. I try to keep pushing the client to understand the concept of containers and other things. It will take some time, however, it's a good feature to move ahead with OpenShift containerization. Even with the Central Bank of Iraq regulation, we have to remain on-prem, thus OpenShift supports this point and offers a flexible solution. Red Hat Enterprise Linux (RHEL) has helped me mitigate downtime and lower risks by about 80%.

I can't pinpoint something specific to improve Red Hat Enterprise Linux (RHEL). I feel they are doing good. I haven't thought much about what they could enhance to become even better for me.

Currently, I manage an issue not related to the OS. It's more about how to purchase vouchers or training from them. Unfortunately, any MasterCard or Visa card issued by a bank inside Iraq is blocked by Red Hat without a clear reason.

While other vendors like Cisco, Microsoft, IBM, VMware, Veeam, Nutanix, etc., we can purchase learning and vouchers directly without any issue. Only Red Hat it's blocked, so to solve this, I have to travel to Dubai and buy it outside the country. This is a significant issue for me and all Red Haters in Iraq, and that's why I also develop myself with non-official content and stopped pursuing their certification since I must travel each time I need it.

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

Regarding stability and reliability, I didn't face any issues with that. It's 99%. Any issue I face with it is due to some mistake from a colleague or something pushed the wrong script, yet I haven't faced a sudden crash.

Red Hat Enterprise Linux (RHEL) scales to my company's growing needs very effectively; I didn't face any issues with scalability. Before working in my current company (Red Hat partner), I was a work at a payment gateway company. And we made a successful story by scaling out our datacenter and migrating the version from 6 to 8 without any major issues. Also, we did clustering with Enterprise Linux and other things, and all scalability was good, just requires specific knowledge. That said, it's manageable.

In my six years working with Red Hat, I only remember opening cases three times since the technical documentation on the Red Hat site is so comprehensive that if you carefully check it, you often won't need further assistance.

The support itself is satisfactory, and they solved my issues. They understood my concerns about the side effects of some changes, however, and they were perfect in their response.

Positive

I did consider other solutions before or while using Red Hat Enterprise Linux (RHEL), including Ubuntu, CentOS, and Debian. I am a big fan of Red Hat. This is why I will always choose them. When you love something that much, you just stick with it. That's why I will consistently recommend it to clients as a Red Hat partner.

For the first time, it was a little bit complicated. However, once you know how it works, it's very easy.

My experience with the pricing, setup costs, and licensing for Red Hat Enterprise Linux (RHEL) it's a little bit higher. I suggest that if they could make the price more affordable, it would be great. Some clients are just startups and when opening a budget with Red Hat, it doesn't cover what they need. Perhaps they could create a specific version for startup companies or offer discounts for first-time users.

On a scale of one to ten, I rate Red Hat Enterprise Linux (RHEL) a ten out of ten.

We have our in-house applications. We have several edge applications at our store locations. There is an in-house written app that we host on a basic Linux VM. Additionally, we have a few on-premises installations at headquarters. One of our major applications is being rewritten to be hosted on a Linux server, so that's in the process of migrating.

Red Hat Enterprise Linux (RHEL) helps me with configuration management. It has become a standard in many ways. There's substantial support and different applications that we run on it. The available options for configuration, maintainability, and stability are valuable, and it's not a rapidly changing base that we're working with.

My favorite feature of Red Hat Enterprise Linux (RHEL) isn't narrowed down to one specific aspect. As someone who grew up using command line interfaces, the ability to access a command line and have the system at my fingertips is beneficial. There are multiple options and different ways to approach tasks with Linux, allowing for creativity in the process.

The command line feature of Red Hat Enterprise Linux (RHEL) specifically helps me find ways to address problems. If there's a bottleneck, something slowing us down, or a manual process that we're spending significant time with, I can determine ways to either script around it or use an Ansible playbook. Having these different tools at our disposal is particularly useful.

While I don't have an immediate answer, there may be ways to lighten up the underlying system. There are many components I haven't investigated, making it difficult to pinpoint specific areas. It has always been reliable, and I haven't encountered many major issues. I've been content with Red Hat since I started using it.

We don't use SELinux because it gets in the way too much. It's a good product if you have the time to devote to it. A lot of management is involved in it. We typically set it to notify rather than completely disabling it, though vendors often request reduced security settings during application setup. Regarding areas for improvement, I can suggest streamlining SELinux, which currently feels heavy-handed in its approach to security. It's a system that requires deep immersion to understand. While there's probably justification for its current implementation, making the security component less intimidating for users would be beneficial. This is a recurring observation, as many users working on Red Hat systems or Linux systems tend to disable SELinux because it becomes an obstacle. With proper knowledge and usage, it could be beneficial, but it's similar to training a wild dog - it can be loyal, but without proper training, it becomes an impediment.

I have been using Red Hat Enterprise Linux (RHEL) professionally since around 2011, though I've been using some form of it since the late '90s.

We haven't experienced many problems with downtime. Our operating systems have been consistently stable regarding uptime. Any downtime issues have been related to upstream factors, networking, and power infrastructure.

In terms of stability and reliability, Red Hat Enterprise Linux (RHEL) is very stable. I rarely recall having issues where the OS wouldn't boot up. Any stability issues have typically been hardware, network-related, or facility-related rather than OS-related.

Red Hat Enterprise Linux (RHEL) scales with the growing needs of my company very effectively. We implement it in any place where we can find a suitable application.

The customer service and technical support for Red Hat Enterprise Linux (RHEL) are very good. I would rate it approximately eight or nine out of ten. It has been particularly good recently. Though there were past instances where support initially took a hands-off approach due to gray areas in their support scope, which was disappointing, they ultimately delivered when crucial support was needed.

Positive

We are largely a Windows shop. I'm probably the only Linux person on the staff. We have legacy systems, including HP-UX and Stratus VOS, with some RHEL outliers that are being phased out. While Red Hat will likely absorb some of that capacity, many people coming from a Microsoft environment are bringing Windows .NET applications. We're currently evaluating Azure as a hosting platform, which is already in place but not actively used yet.

I've been involved in Red Hat Enterprise Linux upgrades and migrations since Red Hat Enterprise Linux 5. We still maintain one Red Hat Enterprise Linux 5 server due to legacy applications. We have successfully removed all Red Hat Enterprise Linux 6 installations and currently maintain a large base of Red Hat Enterprise Linux 7 at our store locations, which we're migrating from. We've implemented both Red Hat Enterprise Linux 8 and Red Hat Enterprise Linux 9, completing the entire cycle. We've been through all the versions. We don't do in-place upgrades or anything like that. We just rehost the applications, which is probably pretty typical. This is largely a VM-based environment.

I use Satellite combined with the Ansible automation platform for provisioning and patching. I implement kick-starting via Satellite for most systems, with Ansible handling the final configuration. As Red Hat Enterprise Linux 10 approaches, I'm interested in exploring image options to streamline the process, particularly regarding CIS benchmark compliance.

We are going to move to Red Hat Enterprise Linux 10. We've been pretty good about getting up to the latest version once it's available. It took us a while with Red Hat Enterprise Linux 7, but we jumped to Red Hat Enterprise Linux 8 fairly quickly. I had my process down, so with Red Hat Enterprise Linux 9, I got right on to it and rewrote my configuration. I'm hoping to streamline that to get Red Hat Enterprise Linux 10 up and going once it comes out. I'll have a new service based on that. Our footprint is shrinking a little bit because a lot of our apps are being rewritten in a Windows .NET environment. It's not going to be as big as it used to be, but we're still going to have Red Hat.

The biggest return on investment when using Red Hat Enterprise Linux (RHEL) is time. Time is a crucial factor, and attempting this level of automation with Windows would be challenging. While automation is possible with Windows, it comes naturally with Linux. Being able to transform common manual tasks that previously took all day into processes that take an hour, half an hour, or even less, demonstrates clear value.

Management handles much of the pricing, setup costs, and licensing for Red Hat Enterprise Linux (RHEL), though I receive many of the invoices. While it isn't inexpensive, it has proven to be a worthwhile investment. The virtualized environment has provided good value. Each of our Satellite locations has its own physical license, which adds complexity, but Red Hat and our partners have worked with us to secure competitive pricing.

My rating for Red Hat Enterprise Linux (RHEL) is 10 out of 10.

My main use cases for it are servers, such as web servers, database servers, and any type of server that we need.

Red Hat Enterprise Linux (RHEL) helps us solve pain points related to security, CVEs, and patching. 

The benefit for my company is that it saves time on compatibility issues. I don't have any metrics of roughly how much time has been saved, but I just know we don't have the combat. I've done Ubuntu, and Ubuntu doesn't compare to Red Hat, so I just know when I need to install something, it works. There are very few times when I've had issues.

Security requirements were a major consideration when choosing Red Hat Enterprise Linux (RHEL) in the cloud because they have secure patching. We review all RPMs and stuff that we import, and that's the major reason.

The feature I appreciate the most about Red Hat Enterprise Linux (RHEL) is the DNF, yum updates, and RPM, which make it easy to install applications and customize it.

Red Hat Enterprise Linux (RHEL) can be improved by making the licensing easier for Amazon EC2 instances. When we try to do auto-scaling, the licensing is hard to automate.

I have been using it since Red Hat Enterprise Linux 4, so probably 2005.

It's very stable. I haven't had any issues. We don't have to worry about it crashing.

Red Hat Enterprise Linux (RHEL) scales very well with the growing needs of my company. I've done from one or two to thousands, so it's not a problem.

Their knowledge base is great. Anytime we have patching issues or anything else, we reach out to support, and they always have an answer.

Their technical support has been great. I haven't had any issues with that as they respond right away.

Positive

It has been very good. I've done from one or two to thousands, and I've never had a problem. The only issues were hardware-related. They've been able to support drivers and things like that.

We have a hybrid environment with both on-premises and cloud deployments. I specialize in AWS.  Red Hat Enterprise Linux (RHEL) supports our hybrid cloud strategy. When we have things that can't go into AWS, we can spin up a Red Hat Enterprise Linux EC2 instance in AWS to run legacy stuff or stuff that's not compatible with AWS.

We usually use Ansible for provisioning and patching. I am 100% satisfied with the management experience of Red Hat Enterprise Linux (RHEL) systems when it comes to provisioning and patching, and I have no issues.

From my point of view, the biggest return on investment when using Red Hat Enterprise Linux (RHEL) is probably stability, as I don't have to worry about it crashing. I've had issues with other forms of Linux, so it's been pretty stable.

It's been good, but I don't really get involved with that.

We did consider other solutions, such as Ubuntu, Amazon Linux, and Rocky Linux. but Red Hat Enterprise Linux was the one we went with. The biggest reason Red Hat Enterprise Linux (RHEL) leads the way is support and security.

I would rate Red Hat Enterprise Linux a 10 out of 10 because of the stability and security. That's the main reason I use it.

My main use cases for Red Hat Enterprise Linux (RHEL) are mostly development at first, and then after that, it's actually running full production loads on it.

One of the nice pain points that Red Hat Enterprise Linux (RHEL) addresses compared to other distributions is the polished applications within it. 

Their repository tends to be more foolproof. The SELinux feature in RHEL is pretty strong. 

SELinux is not something that I was ever using before in the open source community, and it was very confusing at first; however, after a while, it made sense why that layer exists. The SELinux feature and other features of RHEL benefit my company by allowing us to lock in the server more traditionally than we would be able to with special permissions. 

It's about getting very granular versus just putting an umbrella on some things, and security-wise, it's very effective.

The security features of Red Hat Enterprise Linux (RHEL), including SELinux and its features, make it easier to be aware of compromises.

The Insights tool is very good at providing CVEs to alert us about vulnerabilities quickly. I can't quantify the impact in percentage terms since I haven't faced specific situations. However, the outlook compared to other distributions looks good.

To improve Red Hat Enterprise Linux (RHEL), it would be helpful to have a step-by-step process to make setup easier. Cockpit needs more features to manage complex tasks such as RAID configurations, as most of that is reserved for the command line.

I have been using Red Hat Enterprise Linux (RHEL) for about a year and a half.

I find Red Hat Enterprise Linux (RHEL) to be super stable and super reliable.

I have not scaled Red Hat Enterprise Linux (RHEL) outside of using templates and cloning features. I haven't scaled it out with OpenShift yet; it's something I want to explore, as I now understand what tools OpenShift can offer to scale out RHEL machines effectively.

My experience with customer service and technical support for Red Hat Enterprise Linux (RHEL) is mixed. On a professional level, they are very responsive, which is part of the contract, but on a personal level, responses can take forever, and I often get pointed to community posts.

Positive

We did not consider any other OS solutions while using Red Hat Enterprise Linux (RHEL), although there have been discussions about using Ubuntu. I don't think it will go that way because we are very satisfied with what RHEL offers overall.

The biggest return on investment with Red Hat Enterprise Linux (RHEL) is that every time I put an application or tool in there, it's going to work. I don't have to second-guess it or go back; I know it will be a polished application.

Regarding the experience with pricing, setup costs, and licensing for Red Hat Enterprise Linux (RHEL), I would say it's beyond my pay grade. That said, it's not cheap at all. While it could always be cheaper, they provide substantial value for the money, and they consistently introduce new features that add value.

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

It's a great OS that has grown on me over time, and the more I use it, the more I understand its value and why it costs what it does.