HPE ProLiant DL Servers Reviews

With HPE ProLiant, you can run a Windows operating system or a Linux OS based on Intel architecture. We also use several applications like iLO to manage the servers within the architecture of our serverless AMD processors. 

Alternatively, you can use another monitoring solution like HP OneView to manage ProLiant Servers. It's a product for monitoring and managing the servers. In addition to monitoring software, ProLiant can be managed with a cloud-based solution. For example, HP's cloud-based InfoSight solution lets you monitor your server and storage, including ProLiant and Intel. 

ProLiant can be mounted in different types of server racks, like a CD or tower. The tower solution of ProLiant is for a small site or office. With this type of tower server, you can add a kit as well. ProLiant has several servers: 150, 350, 380. And there is another ProLiant architecture that you can install in a Synergy and BladeSystem enclosure. 

HPE's iLO server management software is a handy tool to install and deploy. OneView is also suitable for management, but you need a license for it. You can use OneView's monitoring features for free, but you need to pay for management capabilities. In the latest generation, Gen10, you have to add a license for iLO. In addition, generation 10 requires an ISO license to use iLO for management. And if you're working with Synergy, there is another new product like SimpliVity. SimpliVity has a helpful product that is based on ProLiant and another type of architecture similar to Apollo.

It would be great if HP could use a ProLiant Server to run HP-UX, the Unix build from HPE. Right now, HP-UX cannot run on the ProLiant architecture. So if HP made HP-UX compatible with ProLiant Servers, it would be pretty helpful. On the other hand, Linux is also replacing HP-UX, so maybe HP doesn't need to integrate this architecture into ProLiant. 

If you look at ProLiant's trajectory, I think the next generation will be focused on adding memory. Currently, there is a gap in the memory technology, so I'm predicting that the internal disk for the next generation of ProLiant will be RAM only. I believe this high-speed disk will be available in the next generation. I think the disk will be integrated into the RAM architecture. 

With the improved RAM architecture, the disk will be faster than the first-class disk because there are other protocols between memory and disk. If you have your disk, you look at the disk in terms of the motherboard. If you add to the processor, it would be faster. All disks in this architecture will be in the solution's memory.

I've been working with ProLiant for almost 10 years. And two or three months ago, I implemented several ProLiant Servers running Windows. It was a very short project — a  small solution for a small customer. The majority of my experience has been with HPE servers like ProLiant and Integrity. I've been working with HPE products for about 18 years, including HPE infrastructure, storage, and servers products. So I've been working with HPE since my first job after I graduated.

ProLiant Servers are stable because they have redundant elements built in.

I would say ProLiant Servers are scalable, but it also depends on the architecture. You can scale up with Synergy. For example, you can add two servers into one node. So if it's part of the cluster, it also depends on the operating system that's running. 

When our customers deploy a ProLiant server, we're usually the ones providing support. We have a three-year contract for hardware and software support. The procedure for escalating to HP is pretty straightforward. You contact an HP call center then they verify your system handle or serial. If the server has an active contract, the response from the engineer depends on the conditions of the contract. Some contracts are six hours. That means they're going to solve your problem in six hours.

Installing ProLiant is straightforward. There are different ways you can deploy. You can deploy it locally using the graphical user interface, or you also have the option to set it up using a shell. You only need some basic knowledge to install ProLiant. The procedure is pretty similar to setting up a PC or a laptop. ProLiant has an array of tools, so you can easily install the servers without any experience. The installer has a simple Windows-based GUI, so you just click through the wizard and provide some information to the servers. 

You don't need a deep understanding of the architecture. If you have a fundamental knowledge of operating systems like Windows, you can handle this with no problem. Also, HP has a lot of information available online, including video tutorials on installing your ProLiant Servers. HP has several channels to provide information for customers and engineers.

The time needed to deploy depends on the scale and your environment. If you want to deploy just one ProLiant server, it takes maybe 30 minutes. If you're going to deploy a Synergy of BladeSystem with different modules inside, you might need to spend an entire workday on it. Maybe it takes a day to install all your servers or maybe less. But installing a single ProLiant rack-based server can be done in 30 minutes, including installing the operating system. Installing the operating system, updating your system, etc., will take maybe 30 or 40 minutes.

10 out of 10. The latest generation is the best, but Generation 6 was very stable. It was a good one. Now Generation 10 is the best. I don't know why they took so long to upgrade this generation. Still, Generation 10 has improved a lot in memory and processing, so you can operate in an environment that supports ProLiant. That's why I think HP-UX will disappear because Linux can run this environment on the ProLiant architecture very well.

For example, the range of velocity and processor speed is four or five times greater than before. You can run every Linux environment, which can replace the Unix environment. You can run this Linux environment inside the ProLiant and get the same service as a Unix environment. That's why Linux and ProLiant run very well.

The solution is used for storage.

The solution is stable. I have not had any problems with it.

The product must provide time travel features. Oracle Flashback Database provides such features. If there’s an error, we can travel back in time and revert it. If someone imports a wrong request, we can ask the system to go back in time so that the system has no problem. Backup and recovery are the most important features.

I have been using the solution for 20 years.

I rate the tool’s stability a nine out of ten. We had a problem three years ago. We fixed it. It’s normal for such issues to occur.

The tool’s scalability is adequate for our company. We have 150 users in our organization. It is not extensively used. We do not have plans to increase the usage. We might migrate to the cloud in the future.

I have used IBM. It was very expensive and was not scalable.

The solution is deployed on-premises. Our organization bought and installed the solution, and we use it.

The return on investment is quite good.

I have little knowledge about hardware. I recommend the solution to others. Overall, I rate the tool a nine out of ten.

Previously, I was working as an IT contractor for several companies, so the model depended on the size of the business. They were using the smaller, cheaper series of HP ProLiant servers. My current company is relatively large, so they use rack-mounted DL servers that are designed for bigger companies.

HP servers are deployed physically in your office, and you need to maintain them. You are responsible for keeping them online and servicing the end-users at all times. We have about 1,000 users. It's a hybrid environment. We have the same services on the cloud and on-premises, so they are redundant and faster.

HP ProLiant servers provide redundant solutions for almost everything. You can set up multiple power supplies, with a primary power source and a secondary power supply connected on UPS. If the power goes out in the building, the UPS will supply power to the host at all times. The solution can run on batteries for many hours, depending on your battery and UPS capacity. 

ProLiant servers also offer multiple networking interfaces, so they can be connected to various network equipment concurrently, allowing you to avoid disruptions from the network or internet connections. They are redundant in every area.

I would like to replace a hard drive that might be saved on the fly, on the server that I'm using currently, but I can't do that. I'm forced to power off my virtual machine, turn off the server, disconnect it from the power, replace the drive, rebuild the storage, and power it on again. 

That's a lot of downtime, and it affects the services. I know that HP provides this kind of solution to another series for a bigger budget of course. 

I've used HP ProLiant servers for at least six years, but I worked with a different series in the past. 

ProLiant servers are highly stable. They're redundant in every area. We have counted on them for years, and we are satisfied with them.

I would say ProLiant servers scale well. Servers come with multiple storage loads that you probably won't ever use, but they are available to extend your storage if necessary. 

They have removable power supply interfaces that let you extend your redundancy. This applies to CPUs. You can add CPUs, memory, etc. 

They have been using ProLiant since before I joined the company. I don't know why they decided to use HP. However, I've used Dell servers as well. Personally, I think HP servers are easier to implement and maintain. Maybe that's why.

Setting up ProLiant servers is straightforward. In the past, you needed deep knowledge to configure a server from scratch, but now they have a temporary web interface that allows you to connect to the server and configure everything on a wizard-like installer. If you know what you want to achieve, the implementation is easy.

Once you get the HP part from the vendor, it takes a couple of hours to put it on the rack, install the hard drive and CPU, install the operating system, and connect it to your network.

You only need to pay for the hardware, but you can also purchase a license for Integrated Lights-Out technology, which gives you the option to connect to the server like you are physically on site connected with the mouse, keyboard and screen directly on the server. 

It's an extra feature that you need to pay for, but we are not using it. It's an amazing feature, but I have no idea how much the license costs.

I rate HP ProLiant DL Servers 10 out of 10 because I never had a breakdown in six years, and the price is decent. ProLiant gives you something that's stable, reliable, and powerful for an excellent price.

The only thing that we might need is an extra interface to connect the server to the network with the fiber instead of a copper connector. It's something that we never did. And I would advise someone to implement this from the beginning because it might be a bit hard to configure. It will be fantastic if you do it before it goes into production. 

Our primary use case is as our domain controller and file services, our local CR applications, and our ERP, local ERP. The main service we're using is the local ERP with Oracle DB.

Technical support is helpful.

It's very easy to set up.

The product has a more flexible infrastructure and management consultation in comparison to Dell.

It's energy-efficient. It's consumed less energy than the previous solution and the performance is great.

We'd like the solution to be more energy efficient so that we need less cooling or less dependence on a cooling system. 

Its management console could be better. There should be some tools and tips added so that, if a beginner's level goes for management, you can easily find tools and tips, and help them manage everything in case of emergency before going to technical support from HP.

We've used the solution for a year. We started using it last March.

The on-premises version is quite stable. The performance is good. There are no bugs or glitches. It doesn't crash or freeze. In the time we've used it, it has been issue-free.

It's easily scalable and you can expand it pretty well.

We are 48 in-house users, and our remote users are more than 200.

Technical support is very cooperative and helpful. 

We have a contract where they can give us support. Within the next 30 minutes, they will respond, for HP and for VMware as well. With VMware, we can get support online and from a remote desktop or remote services. They will always provide us support for hardware and technical support from HP, which we have contracted. The largest delay we deal with is the next business day, however, typically, they come to us within 30 minutes to one hour time.

We replaced Dell with this solution as Dell is no longer present in our country. While we were satisfied with Dell, we had to replace it. There are only a few Dell vendors left however they aren't so good in terms of support anymore now that they aren't in the country.

The initial setup is straightforward. It's not overly complex or difficult. 

Our deployment took less than 15 days. 

Setup assistance was provided by HP as well as VMware. They moved our VM from the old infrastructure to the new one.

In terms of ROI, for what we have invested in it, we are getting the same amount out. 

We purchased the license for HP with technical support included.

We have a three-year license that we pay for yearly.

It is affordable. After three years, we are going to have SLA with them, like the way we previously had with Dell.

I'm just a customer and an end-user.

We are using the on-prem version of the solution as the connectivity is not very stable. We cannot afford a cloud solution.

We have a service contract with VMware and HP as well for support.

I'd rate the solution eight out of ten.

We have installed VMware on DL Server, and the operating system sits on this DL Server host.

This is all I've ever used. These servers are strong, and they have very few failures on them. They are also easy to manage and monitor.

They are pretty solid servers, but, just like all servers, they become obsolete after some time.

They can maybe provide a console to monitor the health of the servers. There should be some kind of console to which you can log in to remotely check on the health of a server, even when the server is off.

The servers that we have are only scalable to some extent. They have got a limited amount of hard drive that you can insert. Their scalability should be improved.

I have been using this solution for more than ten years.

They are pretty stable servers. The hardware failures are very minor. We do have one or two hardware failures but very far spaced. The major failures are mostly operating system failures, but on the hardware, they have been working pretty well.

They are scalable to some extent. For instance, you can only put a specific amount of hard drive on the base. You can insert the hard drives of a limited size, which makes them not very scalable. This could be dependent on the servers that you have. There are probably models that are more scalable than what we have.

We have about 200 people on the site, and they use it on a daily basis.

We have not contacted them. We didn't have any major issues to escalate. The few issues that we had were easily resolvable. You can also use online support to check. There are quite a number of people using these servers. You can share problems and get some advice from someone who has faced the same problem before.

We will be switching to a combination of Cisco and Dell EMC. For computation, it will be Cisco, and for storage, it will be Dell EMC. The main reason for this switch is group policy. The group has decided that we move from HP and use Cisco with EMC Storage.

The initial setup is a simple process. The old ones used to have a CD that would guide you through the process. Newer ones should also have a system where you go step-by-step and install your operating system and configure it.

I deployed it myself. I got servers from a company and then installed and configured them. All servers were not deployed at once. I deployed just one server at a time. Typically, deploying a server, including the operating system and everything else, takes less than two hours. I also do the maintenance.

Proliant DL Servers have a reasonable cost. They are not as expensive as the Cisco servers. Everything is included when you purchase a server. You just have to install and configure it.

I would recommend these servers. I would rate HPE ProLiant DL Servers a nine out of ten.

We have local storage. We typically use the service for processing. We have a visual solution, and we are connected to the storage directly. In our company, we have around 1,000 virtual machines. We have more than 200 production servers.

We like that the solution is very easy to use. Many companies use it in our market. In Iran, we don't have many options, and HP is one of them. 

It works well overall. 

It can scale.

It's reliable and stable. 

We find the solution easy to set up.

I don't have any information about other servers. I can't compare it to other products. 

I'd like the solution to be a bit more stable. Most of the servers we use are okay. However, sometimes, you need to change the parts. We'd like the solution to be more robust. 

In the past, we've had to buy some RAM and hard drives, and sometimes we find they are refurbished and not actually new, and this is a problem for us in our market. 

I've used the solution for a long time. I've used it for about ten years. 

The solution is stable for us. It is reliable. There are no bugs or glitches.

I'd rate the stability seven or eight out of ten. The stability, of course, could be a bit better. 

We have 500 people using the solution. Most of them are developers, and they're using it in testing, production, and development environments. We do have plans to increase usage. It's ongoing usage, and sometimes we have to add servers. 

It is scalable. I'd rate the ability to expand eight out of ten. 

We've never dealt with support as we have sanctions against us. We don't have access to support. 

I used to work with Synergy, and we had issues with the blade. 

The solution is easy to set up if you have enough information and experience with it. 

The deployment does not take a lot of time. We prepare all of the virtual software, and we simply add a server to the cluster. We just install it and join it to other servers. We always deploy using direct internet and the local network. It's on-premises. 

There are eight of us that can handle deployment or maintenance. However, we only really ever need two people for the tasks. 

I don't deal with licensing. I can't speak to the exact cost. 

I'm not sure if we are using the latest version of the solution. I am familiar with the 300 and 500 series.

I'd rate the solution eight out of ten.

I'd recommend the solution to others. 

We have multiple use cases for HPE ProLiant DL Servers, such as setting up VDS software.

The most valuable features of HPE ProLiant DL Servers are convenience and the interface is good.

The price of the solution could be less expensive to be more competitive.

I have been using HPE ProLiant DL Servers for approximately two years.

The stability of HPE ProLiant DL Servers is very good.

HPE ProLiant DL Servers is a scalable solution.

We have three to four clients using this solution.

The support from HPE ProLiant DL Servers is good.

I rate the support from HPE ProLiant DL Servers a nine out of ten.

Positive

I have used Dell and Lenovo, I found that HPE ProLiant DL Servers are a better solution.

The initial setup of HPE ProLiant DL Servers is straightforward. The full implementation process took approximately six days.

I rate the initial setup of HPE ProLiant DL Servers a nine out of ten.

I have seen a return on investment using HPE ProLiant DL Servers.

There are less expensive solutions than HPE ProLiant DL Servers. However, there is a lot of value in this solution.

The price of the solution could be less expensive.

I would recommend the solution to others.

I rate HPE ProLiant DL Servers a nine out of ten.

We do work for defense and government clients. 

ProLiant servers are more reliable than other platforms.

My customers are tilted toward GPU users, and the mixed version of the enabled hard drives require — flash drives, SSD, NNL, and PLAS — all mixed and matched in a single box. These are requirements I've already shared with the HPE account manager. 

Customers want the tiering concept inside a box, which is currently part of the storage system, but customers require it in a server. They want the operating system over PLAS and the IO-related things on SSD.  The rest of their data is on NLSF. 

I've worked with ProLiant servers for 10 years. 

Stability is where HPE dominates competitors like Dell and Cisco. The servers are highly reliable, and we are impressed with the technology HPE offers.

Scalability in terms of GPUs and storage is a concern. 

I have a direct connection with the HPE account manager responsible for the government and defense verticals. I am happy with the person. We rely on our own in-house support for servers. However, we use a professional service for storage and three-power or CI systems.

HPE servers are highly user-friendly. It takes two or three hours from start to finish for bare-metal installation. With virtualization, it'll take four to six hours.

We are working with the customers in government and defense, where HPE already has a foothold. The requirements come from the customer, and they use HPE, so we do, too. We have to consider the customer's stability and comfort level. 

I rate HPE ProLiant Servers nine out of 10. In my country, it's better for customers to rely on the vendor who delivers the solution. We think the HPE server is better than others for that.