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.

Our use cases for Red Hat Enterprise Linux (RHEL) involve a lot of infrastructure; we run Ansible on it, and we run any other containerized utilities we're using on Podman. We run OpenShift as well, so I don't think we have any RHEL workloads on there, but we definitely use RHEL for a lot of our internal infrastructure.

The Podman feature of Red Hat Enterprise Linux (RHEL) is very valuable; that's probably the core of it—just a simple containerized solution that allows us to stand it up in a server really quickly. This feature and other features benefit our company since we are able to quickly deploy containers to support our infrastructure with minimal management needs from our engineering team. 

Red Hat Enterprise Linux (RHEL) helps us solve pain points such as automation, as well as supporting other file servers using NFS and other kinds of development workloads we're running on it.

My experience with RHEL has not been too complicated; most of our stuff is on RHEL 9 now. A lot of times, our security team comes to us for some of the patching and upgrades, so we're following their lead, however, it hasn't been too difficult for us. We manage our Red Hat Enterprise Linux (RHEL) systems for provisioning and patching using Ansible and Terraform a lot, so we've been happy with that management experience.

My assessment of Red Hat Enterprise Linux (RHEL)'s built-in security features is that using SC Linux is helpful for us to lock things down, and our security team is pretty happy with it whenever they're doing their vulnerability scans. From a security standpoint, we're happy with it.

Red Hat Enterprise Linux (RHEL) has helped to mitigate downtime and lower risk. If there ever is a problem, it's quick to stand up a replacement system.

It's pretty lightweight, so I'd much rather deal with a RHEL system any day versus a Windows system. If you compare it to a Windows system, which has a much bigger attack surface, there's a big reduction there.

When it comes to our security team having to scan for vulnerabilities and such, there is a lot less vulnerability scanning that needs to be done, so it's been a better fit for us for our infrastructure.

I am interested to see how Red Hat Enterprise Linux (RHEL) can be improved. It can be improved overall. Specifically, I'm interested in seeing some of the image incorporation with RHEL 10, as that might improve some of our upgrades and help in moving to the newer versions. I'm eager to learn more about that.

I have been using Red Hat Enterprise Linux (RHEL) in my company for ten-plus years.

It has been very reliable and stable; I have not had any major crashes or outages with RHEL.

Red Hat Enterprise Linux (RHEL) scales very well with the growing needs of our company, as we can spin up instances quickly whenever we add new environments or data centers.

I have been pretty pleased with the customer service and technical support; it's infrequent that we have to engage support, but when we do, they've been responsive and we've gotten some answers, so we've been happy. I would rate the customer service and technical support as eight out of 10.

Positive

We have considered other solutions before or while using Red Hat Enterprise Linux (RHEL). We've considered other Linux distros in the past, however, the ability to have a fully supported platform allows us to reach out to support from Red Hat if needed, which is the reason why we've stuck with Red Hat versus others.

In terms of deployment, it's been good standing it up and then maintaining it with patching through Satellite. Upgrades have been not time-impacted. They're pretty quick to get patching done. Everything is pretty easy. Migrations aren't too complicated. 

The biggest return on investment for me when using Red Hat Enterprise Linux (RHEL) is certainly the ease of use for the engineering team; they can get things done without taking a lot of their time.

My experience with the pricing, setup cost, and licensing of the Red Hat Enterprise Linux (RHEL) platform has been pleasing; it's pretty straightforward and we haven't had any major concerns with costs on it compared to others, so we've been happy.

Currently, we don't have any upgrade or migration plans to stay current with Red Hat Enterprise Linux (RHEL) as far as moving to RHEL 10; that's going to be coming, I'm sure. Most of it involves keeping on the latest versions, and sometimes it's just a driver for keeping Podman up to date whenever Ansible needs to run, as Ansible is core for us.

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

What could make it a ten comes down to us being able to have time to dig into some of the features we're not using, so it's probably just on us to get wowed by some of the stuff we're not doing today.