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.

Our main use cases for Red Hat Enterprise Linux (RHEL) are for our centralized O&M platform, while on the edge we use CoreOS.

My company benefits from RHEL features by avoiding drifts in our solution. If it gets out of engineering, we don't exactly know if the solution is going to drift if someone implemented manual configuration.

Red Hat Enterprise Linux (RHEL) helps me solve pain points such as security, upgrades, patching, and all that is related to long-term support. 

The feature I appreciate the most in the newest version is the image mode and the upgrade in an immutable way. 

Security requirements are a consideration when choosing Red Hat Enterprise Linux (RHEL). It's the platform that really allows for longer-term support in terms of security patches, which is also one of the requirements from our customers; this is why we are on Red Hat Enterprise Linux (RHEL) for those services. 

When it comes to managing my Red Hat Enterprise Linux (RHEL) systems for provisioning and patching, I start from zero. We provide a golden image scenario, and we install based on that golden image while customizing the product through our software itself, providing new bundles and everything around there. Patching is very similar; we provide additional packages and everything around the upgrades, and I'm looking forward to the image mode so that we can provide steps and immutable AB upgrades.

They should try to converge all the different product lines, in both Red Hat Enterprise Linux (RHEL) and CoreOS and OCP based on CoreOS, to get to a single point where it would be easier to move from one to the other. 

Sometimes we build products for one specific application or product, and it would be beneficial to move to CoreOS due to further requirements, however, it's not always straightforward. All the different teams working on the different Red Hat products are pretty much self-contained, which is understandable, but if there were more of a common baseline, it would be much easier to consider moving from one license to another, from one product to another.

In the company, I've been using Red Hat Enterprise Linux (RHEL) directly for three years. Before then, we have been partners and have also been using CentOS and Fedora for a longer time, approximately ten years.

The stability and reliability of the platform are top class.

Red Hat Enterprise Linux (RHEL) scales pretty transparently with the growing needs of my company. It scales effectively when we need to add additional resources or knowledge, and it's straightforward for people to gain those and for our structure to implement even more servers around these others. Both technically and knowledge-wise, Red Hat Enterprise Linux (RHEL) scales effectively.

The customer service and technical support are excellent, especially through the partner program. It's easier to get support over specific issues, and I have noticed when we had bigger issues that could have prevented market problems, there was a good escalation path towards the right people to get answers.

Neutral

I have considered other solutions rather than Red Hat Enterprise Linux (RHEL).

When we were considering getting out of CentOS, we were evaluating everything, including other open solutions such as Rocky, as cutting-edge solutions such as Fedora. 

I personally pushed for Red Hat Enterprise Linux (RHEL) since it was the best solution for us at that specific moment. I understand there are other solutions such as SUSE and Ubuntu that are all in the same market, however, with different approaches. I prefer the Red Hat Enterprise Linux (RHEL) approach.

The deployment is generally very easy.

The biggest return on investment while using Red Hat Enterprise Linux (RHEL) from my technical point of view is the continuous patching and security fixes that are constantly being added and the support around it. If we are having an issue, we can directly reach the right people for support.

I would rate Red Hat Enterprise Linux (RHEL) as a product today at a solid eight out of ten, considering improvements already in place for the roadmap. With the features coming in RHEL 10, I could provide it an overall nine out of ten.

Our main use cases for using Red Hat Enterprise Linux (RHEL) revolve around building managed services, as all of our Linux workload runs on Red Hat, and there isn't a different Linux distribution in our company. For most customers, it really depends, as we handle all kinds of business applications basically.

Red Hat Enterprise Linux (RHEL) helps us solve pain points by allowing us to offer support for our managed services, including very high service-level agreements in terms of availability and everything around CVEs, which is also what most of our customers are interested in. The features of Red Hat Enterprise Linux (RHEL) will benefit our company by addressing certain customer use cases we haven't explored yet, particularly with functionality rollbacks and making patch management a bit easier. As we are moving a lot to cloud-native technology, having a similar approach for our Linux operating system as we have for cloud resource orchestration containers is very useful, especially since the German market is a bit slower than the US market.

To manage our Red Hat Enterprise Linux (RHEL) systems regarding provisioning and patching, we use Ansible and also Red Hat Satellite as we are a Red Hat partner, and we are very satisfied with that management experience.

I am really excited about the new Red Hat Enterprise Linux (RHEL) 10 and the Image Builder, which are the features I most appreciate and am definitely going to check out.

We consider security requirements a top priority due to the highly regulated nature of the German market and the sectors we work with, including automotive and financial institutes, so it really depends on the customers, however, having a secure operating system is crucial.

Red Hat Enterprise Linux (RHEL) supports our hybrid cloud strategy by allowing us to deploy virtual machines in both clouds without really feeling the difference between a private or public cloud.

The knowledge base offered by Red Hat Enterprise Linux (RHEL) is pretty good and we use it heavily. We also contribute to it by raising issues so that they may be solved and verified.

Red Hat Enterprise Linux (RHEL) could be improved slightly even though the new RHEL 10 just came out and there are many helpful features in it. For instance, while Image Builder is good, improving the image mode could be beneficial, although it might have already been improved in RHEL 10. 

Additionally, for using third-party software, such as security scanners or patch management systems not from the Red Hat family such as Azure Patch Management, sometimes there could be improvements regarding support, as it can take a year or one and a half years to receive support for certain RHEL major versions, so partnerships on the Red Hat side and collaborations with Microsoft would help.

I have been using Red Hat Enterprise Linux (RHEL) internally for our managed services functions and for our customers since it became available. We are a partner of Red Hat where we do consultancy and resell RHEL and Red Hat Ansible, making the answer to this question complicated since we have been using it for about five and a half years.

The stability and reliability of Red Hat Enterprise Linux (RHEL) are very good.

Regarding scalability, Red Hat Enterprise Linux (RHEL) scales very well for our company needs.

Customer service and technical support for Red Hat Enterprise Linux (RHEL) are very good, as we are a platinum partner with some benefits. That said, even the regular customer support is most of the time very sufficient.

Positive

I did not use another solution before Red Hat Enterprise Linux (RHEL) in my company.

My overall experience when deploying Red Hat Enterprise Linux (RHEL) is simple.

We deploy RHEL in both the cloud and on-premise, utilizing a hybrid cloud strategy.Security requirements are definitely a consideration when choosing Red Hat Enterprise Linux (RHEL).

I have been involved in upgrades or migrations of Red Hat Enterprise Linux (RHEL), especially during the significant shift from RHEL 7 to 8, which included many upgrades and migrations.

We have many customer projects where customers use us as consultants to migrate from other Linux distributions.

For the Red Hat internal migrations, we use the tool 'convert2rhel' all the time.

The biggest return on investment when using Red Hat Enterprise Linux (RHEL) is stability, which benefits both us and our customers, since we do not have to use as many human resources to administer those machines.

I don't have too much to complain about pricing, setup costs, and licensing since we handle everything via a distributor in Germany and we work closely with them on Red Hat Enterprise Linux (RHEL).

I did not consider another solution while using Red Hat Enterprise Linux (RHEL).

I would rate Red Hat Enterprise Linux (RHEL) a nine out of ten. To make it a ten, improving the ecosystem with more support from third-party software would help.