The initial setup is not easy yet not over difficult either. It's easier than, for example, IBM servers. It's more out of the box. There isn't so much configuration needed. 

I'd rate the ease of the process seven out of ten. 

The deployment took around six months for us to deploy everything. It took a while to get the hardware. 

We had a team involved in the implementation. 

The initial setup for HPE ProLiant DL Servers is easy. When it comes to the setup process, it's not about the number of steps involved. It depends on the overall experience. 

Generally, these servers are not overly complicated from the beginning. However, if you encounter features like iDRAC (integrated Dell Remote Access Controller) in Dell servers, there may be a slight learning curve if you're not familiar with it. In such cases, it might require a few days or even a week to get hands-on experience and become comfortable. Similarly, for any new technology, it's advisable to gain some experience before providing a review. I don't think you should attempt it blindly. So, regardless of the number of steps, my opinion is that for personal infrastructure or within a company, the initial setup should be manageable.

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. 

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.

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

The initial setup was straightforward. We did have to do a lot of customization before the deployment due to wanting to standardize which markets could get a rate comparison, as well as the size of the company.

The initial setup for HPE ProLiant DL Servers is straightforward, and the HPE team also helped my company set up the product, so that's good for my company. Still, sometimes, if HPE doesn't support your hardware, then the HPE team cannot help you set up HPE ProLiant DL Servers.

Right now, the product supports one application on one hardware within my company, so once you complete the testing, the company can go ahead and use HPE ProLiant DL Servers, so deployment only takes a little time.

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 rate the product's initial setup phase a ten on a scale of one to ten, where one is a difficult setup phase, and ten is an easy setup process.

The solution is deployed on an on-premises model around 90 percent of the time. Customers prefer to avail of the cloud services offered by AWS, Azure, or the services from some local partners in India.

The solution can be deployed in an hour. For racking and powering up the server, it takes a maximum of an hour.

For the deployment process, you need to fix the rack rail kit to install the server and then go for power on, after which you need to do the initial configuration check before going ahead with VoIP installation.

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.

The initial setup was not complex and took about half a day for one technician to set up. We have one technician who looks after the servers, but there is not much that needs to be done to them in regards to maintenance. Over holiday breaks we perform maintenance checks to ensure that everything is working properly.

The initial setup is straightforward and took a few minutes. The deployment was simple. We only needed to install a Windows server.

It's straightforward but requires a little more configuration than Dell because this HPE has an ILO where you can run an independent operating system. A system integrator deployed the server, which took less than a day. Our deployment and maintenance team consists of four engineers and one manager. We followed the installation guide and the standard steps for installing a Windows operating system.

Configuring the ILO operating system added some additional steps that weren't required with Dell. It's running Windows 7 ILO, a step higher than Dell's operating system.

How difficult or straightforward the implementation process is depends on the customer's location. We have lots of customers in Turkey. Some of them are complex, and some of them are simple.

We have three admins that can handle maintenance tasks. 

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.

I was involved with the setup. It was very easy to apply.

I rate ProLiant servers nine out of 10 for ease of setup. The installation is straightforward. Most clients only need to give me a server name and IP address. After that, you need to configure virtualization if the customer wants that. They need to do the configuration training. 

Setting up ProLiant servers isn't easy, but it's not too difficult. It's a little complicated to install our operating system if you don't have drivers. For example, it's challenging to install with Windows Server and Red Hat. In the case of Windows Server, you need to install intelligence provisioning, but it's not used in most cases. It requires an engineer and a specialist to maintain the solution. 

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

Our deployment took less than 15 days. 

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.

We have different locations; in my location, I was involved in the setup. It was pretty straightforward.

The solution's deployment was easy. 

It can only get difficult depending on what application or operating system you want to install. Then it all depends on how good or how skillful one is with the particular application. But the installation and configuration is never a problem. There has never been a problem with the hardware that I can say, apart from the issues I have already mentioned.

We have different people for different specific assignments. For each team, we have a good number of people. We are thinking of expanding because the university is a multi-campus university, and it has about four campuses, even though the whole thing is being centrally run. We are thinking of having these services run 24/7, and then we would need to have more hands so no one is overwhelmed with the work on ground. Currently, for those manning the server, we have about five people.

While the product was delivered by a single contractor, the installation time was that of any other typical server. This only consisted of configuring the ILO, followed by putting on the operating system. That is all. Up to a certain operating level, the configuration of the product would not be a matter of days.

As the business services we provide are of a confidential nature, both for government and military purposes, we deploy strictly on-premises.

It's a data center. Things go in and out. I was a system administrator myself many years ago, so I set up a lot of HPE ProLiant systems. They were very easy to set up in the past. They have become even easier. I would say that half of the strength of the ProLiant servers is the software and the additional tools that HPE provides.

The initial setup was easy.

The deployment time varies with the configuration, something which does not take more than two hours. While installing the operating system is a discussion of its own, the actual configuration is easy to do. 

The initial setup is very easy. The ProLiant was complete, and we just had to plug it into power and check the hardware. We did not have to put in new parts, such as additional hard disks. They are made to order.

With some of the new software changes, the setup is getting easier and more consistent for us to apply across the globe; it's improving for sure.

They used the DL client before I started. I've been with this company for four years. As a service provider, we install the product for our customers.

The initial setup is easy. I give the initial setup a ten out of ten. The deployment took between one and two days.

Three people were used for the deployment.

It wasn't straightforward.

We had some issues with some failures initially. Though it was taken care of by HPE, we still had some failures, which was surprising.

We have a team of ten admins, engineers, managers, and data entry guys to maintain and deploy this solution.

The initial setup is not complicated for HPE or any other server.

I was not involved in the initial setup.

I wasn't involved in the initial setup.

The setup can be complex or straightforward, depending on the server model. One person can complete the deployment in about four days. 

It is easy. Getting them up and running is a piece of cake, but getting the VMware environment operation on them is very complicated.

It has been a couple of months so far, and we're still working on it.

The implementation is not complex at all. We find the initial setup to be quite straightforward.

The product was ordered and came complete and ready to go. It was basically plug and play, so that there really wasn't a deployment period per se. We just had to power it up and check the hardware. We put in the discs and had the spare parts on hand as well. They deliver it ready to go, so it's pretty fast.

We have five individuals that handle the implementation and maintenance. They are all engineers.

They were dead simple. You rack them, power them on, then you can use Intelligent Provisioning to install and configure the system. They just make a lot of sense. It's easy.

The solution's initial setup is straightforward. We need to follow the basic steps.

In the latest versions, such as G9 or G10, we have a very user-friendly installation. It took about 30 minutes to 1 hour. RAID is easy to install, and so is the server, but in earlier products or versions, it was somehow challenging. 

We have a different team that does all the initial setup.

I was involved in the installation. We ran it from the SmartStart CD to the online connection. (I don't know what they call it now.) It came with a supply kit and we could install it without an external connection. That's where we support it. In gaming, there is no connection to the outside world.

The server itself is quite good, easy to use. Configuration of it is a little bit tedious, you've got to be willing to spend a couple of hours just to get it set up before you can even start using it, because the reboots are ten - fifteen minutes long, and that'll kill you.

It was very easy.

The initial setup was pretty straightforward.

The initial setup is easy.

The installation is easy. The hardware installation takes approximately 20 minutes and the Windows installation takes another 20 minutes.

I was not involved in the initial setup, although my predecessor was. I've stood up servers and storage arrays from scratch, and I think it's not that complex. I think the user interface that HPE provides is straightforward. It takes away the complexity. That's my feeling, anyway.

Initial setup was straightforward.

It's simple. Use the included SmartStart media, and it seamlessly integrates with the OS of choice.

I've only been with the company about 18 months. The majority of the setup was done prior to me joining.

I was not involved in the initial setup. That's done by our engineering team.

The setup is so easy. It used to be SmartStart, but now they've changed that whole functionality. It's seamless to us. I don't really have any complaints from a "stand-it-up-and-support-it" perspective.

Very easy. It’s always an easy thing for us to install, as our staff has good knowledge.

The initial setup is relatively straightforward. The configuration is very smooth and can be done in about half an hour. Maintenance depends on the infrastructure of the client and how the solution is configured.

At the beginning, the initial setup was a bit difficult because there was a learning curve, but now it's easy and with HPE it is really easy to update the servers. We don't have a lot of servers. We are a small service and we have only five to six servers, but a lot of virtual machines, and it is really easy to upgrade the servers. In combination with VMware you can move your machine, so you have no interruption in the service. It's really easy to do. It can all be done remotely thanks to iLO, so you have a good management. iLO processor is a bit slow. though, it could be faster.

Setup was mostly straightforward, although as I mentioned, the iLO could do with providing more control, e.g. RAID/disk configuration like DELL have. Their intelligent provisioning does help a lot, particularly on their Gen9 range.

I was involved in the setup. I think our first installation was okay. When we are buying new models, sometimes the support doesn't feel like it's quite there. That might not necessarily be on the HPE side of things. This lack of support might be from some of the products that we use with it.

The initial setup is a little bit complicated, but after that, it's very easy to deploy the server. 

The installation is reasonably complex.

The length of time it takes to deploy depends on the software that we are installing, but it can take a couple of days, approximately.

We have two engineers and one technician to maintain it.

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

To install one server, it takes less than a day. Most of the time there aren't any issues.

You don't need too many people to deploy the product, however, it depends on how many servers you are setting up. For a few servers, you need few engineers and no more than that.

Initial setup was straightforward.

I was not involved in the initial setup, but from what I heard, it was pretty straightforward. It was not that complicated. If it would have been, they would have called an engineer from HPE to help us.

The initial setup was very straightforward with a step-by-step wizard to help me get the servers configured quickly. I’m especially impressed with the RAID setup wizard which makes setup of complex disk pools a breeze.

I would rate the tool’s setup an eight out of ten.

The initial setup took a few hours.

HPE ProLiant DL Servers is easy to deploy. 

I was not involved in the setup at this organization.

I was involved in the setup and it was straightforward. It gives you all the options that you want.

I used to guide customers with the installation, and the initial setup was always straightforward.

The initial setup was pretty straightforward.

I was involved in the installation. It was straightforward and not complex.

Very straightforward – we got them out of the box, racked them and they were good to go.

The solution is web-based making the installation straightforward.

The time it takes for the full implementation depends on the project. The time can vary if it is a small, medium, or large project. This time could also vary between the specific platform that we need to build. The time it takes is typically between three to four weeks.

The initial setup is not complex at all. It's very straightforward and quite easy. A company shouldn't have any issues with the setup.

You can install it in less than ten minutes. It's a pretty quick process.

It is fairly decent. It is straightforward most of the time. It takes less than a day for a server.

The setup is quite straightforward. It's really a bunch of servers but, of course, that involves getting all of the components together, having everything configured to order and then having it configured to the software stack. We incorporated HPE partners to do that for us and then we took over and said, "Okay, from now on, we involve this system until its end of lifetime." We went from the one version of the hypervisor to the current version of the hypervisor, and we're going to the next, and the next, and the next. Setting up is the first step but from that point on, you can take it yourself and drive it yourself.

The initial setup (such as network connections) is quite straightforward. The configuration part too is simple, considering that one must know what he/she is doing.

Initially within my company's IT space, I was not involved with the initial decision to go with ProLiant. I'll be honest, I came from a Dell background. The division that I had worked for prior to our globalization in our IT group was primarily Dell. There have been a number of elements to using HP's that have been more beneficial from my point of view.

We've been doing the ProLiants forever. It's getting a little tougher now. It used to be, you had everything on a CD or DVD, you pop that in, you run. Or you had the SmartStart disk. Now, you got their onboard administrator. They got the intelligent deployment guide or whatever the heck it's called. Sometimes it's a little less intuitive. Sometimes it's where technology can bite you, and it might be helpful to have a guy go on and say "Do this." Otherwise you pull it out of the box and go, "Okay, now what do I do?" We work through it, but some of my techs have had a little bit of trouble. I gave them a new server and said,"Deploy it.", and they're like "Well, how do I put an OS on it?" It took us a little while to figure that out. I know that somebody's thinking, "Hey, this is really great. It's all here, it's all inside." Great, some of us need a little more direction sometimes.

We are experienced in using the HPE servers so we don't have any difficulty installing new servers.

I was involved in the setup and it was straightforward.

Initial setup was relatively straightforward.

I was involved in the setup and it was straightforward. I can just plug in a server.

It was straightforward. At the time, we were a very small shop. I think we replaced six Dell servers that were there at the time with six ProLiants. Since then, our company has grown tenfold. Now we still have a few of the rack mount ProLiant’s but we have six blade chassis that we're now using.

We have others that handle any deployment issues.

It's straightforward. Putting that kind of server into the rack now is something like 50 minutes.

The initial setup is straightforward and easy. It will take about an hour to deploy, from scratch.

I've been in my company for 14 years. Initially we were using Compaq and now moved over to HPE. Thus, the setup took place a long time ago.

Actually, there are no comlexity in the setup everything is straightforward and clear.

The problem with the updates is sometimes our internal customer with the validation and qualification of the system. But the tools which HPE offers are working. It's really a question of change management.

The setup was straightforward.

The setup was straightforward. It's easy to mount the rack, it's got great rails. Power it right up, launch and then you can start configuring it.

IMHO, you cannot get a more straightforward initial setup.

The Gen8's and previous were pretty easy going. We just received Apollo 2000s that we're trying to deploy to now, and getting over the humps of learning the new UEFI deployment which is kind of mandatory. It pushed us over the edge from legacy bios mode to UEFI, so we've got some lessons to learn in our organization to deal with that change with the new Gen9's.

Very straightforward. Today, you have built-in the option to use SmartStart so it's very easy to set up the first time. It's very intuitive. For us, once again, that's very important.

I was more or less involved in the initial setup. It was complex. We host different types of environments, so some of them are simple, but some of them are complex. We deal with a lot of:

• Servers
• Storage
• Customers
• Software configurations
• Operating systems
• Relationships between all of those components

They take a long time to set up and they're quite complicated to build as well.

I've done a few installations of HPE ProLiant DL Servers and I would rate it as easy. The installation is straightforward.

The setup was straightforward.

ProLiant servers are easy to deploy. It's not difficult to put all the elements together and configure it for our customers.

The initial setup is very straightforward. We installed it within half an hour.

The initial setup is straightforward.

I was not involved in the initial setup. Though, we are going through a new setup and I will be involved in that.

It's straightforward. We use Red Hat, it's straightforward. We go from five to six or seven. It's no problem.

I was not present for the initial setup. I was present for the setup of the Synergy frames. It was straightforward, but we also had HPE's help setting them up and they gave us guidance.

It's very straightforward.

My colleagues who set it up said the initial setup was OK. It wasn't simple but it also wasn't complex.

Many times the setup had to be agreed and consulted with HP representatives and technical after-sales staff.

Initial setup was straightforward.

The initial setup is straightforward. It took a maximum of one and a half hours. The deployment duration also depends upon the operating system.

The setup was pretty straightforward.

The initial setup was very easy and straightforward.

It went fine, and it even came pre-installed with RHEL, however, we reinstalled it with SL.

The setup was easy and not complicated.

The initial setup was easy.

The installation was straightforward.

With blade technology, there are the blades and then the whole chassis surrounding the blades. This type of technology is more complex than the normal standalone servers.

My colleague has indicated that the initial setup was straightforward.

We have one person to maintain the solution.

The initial setup was straightforward.

The initial setup is straightforward and they take between a day and two days to deploy.

It's straightforward and clear if we read the manual.

As far as I know, the deployment is smooth and easy. If not, it goes to another department. Usually our technician can help us from far away. We don't even have to come physically. The software and the hardware work fine. Once it's working, it's working.

The initial setup was very simple.