It is very straightforward to set up. It's not complex. 

The length of deployment depends on the way that you configure the Blades. For example, if you're going to work with VMware, the time could be at least 25 to 30 minutes. It is not going to depend on the BladeSystem; it is going to depend on the time of the operate system deployed. 

The number of people you need for maintenance depends on the monitoring system that you have. For example, if you have a good monitoring system for this platform you're going to need less than ten specialists, but if you don't have a monitoring system to check the platform, probably you're going to need more than ten people.

The setup was straightforward.

It took about a day to deploy the solution.

Speaking about the steps taken while deploying the solution. I would say we're using the normal HPE solutions if I put it like this.

For deployment and maintenance, I need two people who can manage the servers.

The installation is not difficult

When we initially deployed BladeSystem, it was a little complicated but once you're set up you don't need to think about it. The main difference between the HCI and Blade is that HCI is easier when it comes to setup.

It is very straightforward. The application configuration is somewhat complex, but we'll be migrating. So, it'll be very straightforward.

The setup and installation were easy.

The initial setup process is a ten out of ten. It takes an hour to complete.

The initial setup of HPE BladeSystem is not complex. The deployment is typically dome done within one day, a maximum of two days if it includes the OS or virtualization.

I rate the initial setup of HPE BladeSystem a nine out of ten.

It's very easy to maintain and to keep updating.

The initial setup of the HPE BladeSystem was easy. The time it took for the deployment was approximately two days.

The initial setup of the HPE BladeSystem is complex with the OneView console.  You can see a lot of tabs and a lot of settings. The configuration could be more user-friendly in OneView, which will be helpful for the customer to manage all the testing.

The setup was a little bit challenging because we didn't get enough training from HPE for setting up the cluster servers.

The setup is okay. We have a technical team that takes care of deployment and maintenance.

The initial setup is easy and can be completed within two days.

Depending on your knowledge, the solution can be very easy or a bit complex to set up.

These are rack servers, so most of the time goes into acquiring them. Once you order them, it takes around four to eight weeks to get them. Once you get those servers, they can be deployed in a week or five days' time.

How many people you need for maintenance depends upon the technical guys as well as the applications themselves. If you're maintaining, then you just need two or three guys. However, it would take more resources if you talk about connectivity and application maintenance and other parts. It also depends upon the number of servers we have installed. 

The initial setup was not hard because our expert technicians handled it. It might be a little bit confusing to do the BIOS setup if you don't have much experience, but if you have expertise you can handle it. 

The initial setup of HPE BladeSystem is straightforward.

It's my understanding that the initial setup is very straightforward and simple. However, I was not directly involved with the initial setup. It was two or three years ago.

I'm not sure exactly how long the deployment process takes.

We have five or six people on staff that can handle deployment and maintenance tasks. They are all engineers and one is a team leader.

The initial setup is not complex. It is straightforward.

The installation was very easy.

There is no complication at all when setting it up, either setting it up as an experienced user like myself or having HPE set it up for you using their services. No problem at all.

BladeSystem setup was one of my first projects when I joined the company, there was a learning curve to it. It really actually was fairly straightforward except we were trying to do everything boot from SAN, and that added some complexity and learning curve. The actual hardware solution - it was fairly straightforward and made a lot of sense. Blades were brand new back then too, so it was a foreign concept, but it wasn't terrible. I would say maybe a a six out of ten or something initially, but if I had to do it now, it's probably a lot easier.

There are enhancements to the HPE BladeSystem. These enhancements are crucial for the installation and ownership of the product. They are similar and alleviate concerns regarding technical aspects and approaches. Additionally, they will contribute to improvements in broadband performance. 

The initial implementation is not complex. It's a pretty straightforward process.

We deployed the solution over 100 servers, and it didn't take too long to deploy.

We have about ten to 20 people managing the solution.

Aside from some issues around .EXE files not downloading properly, the initial setup is pretty straightforward. 

In terms of deployment times, each blade hardly takes one or two hours to set up. It might take one or two days in total based on the already gathered requirements and whatever the company made already.

You only need about two people to deploy and maintain the solution. Once it's deployed completely, likely you only need one person to maintain everything. 

The initial setup has been straightforward in that HP has provided "Smart Start" kits to assist in getting their systems up and running very quickly. These kits typically prepare the systems for NOS installation and provide the necessary drivers to successfully discover all of the hardware components installed.

It was very easy.

The initial setup was different than anything we had done before. It was a little bit complex to get initially set up. But, once it was set up, the ongoing management has been fairly easy.

If I had to do it again, it would be very easy to do, now that we're familiar with it.

We rolled it out over time. We modified our implementation a little bit as we went along, as we discovered different features and different capabilities.

I maintain the solution. It only requires one person.

It was never really a big risk for us, because we've been on HPE for a while, so getting to the new system was pretty low risk, and when it came time to do the migration or the upgrades to stuff, it's always been kind of non-eventful. We've never tried to minimize what we're doing, but we take precautions like calling HPE ahead of time, making sure that there's support there, that they're aware of when we're doing a migration so if anything goes wrong, they're there to support us. We haven't had any issues with that.

I wasn’t involved in the initial setup, but my colleague says that it was good.

The initial setup was fine. It was more that we needed to know some of the technical error ins and outs regarding that, because we were using multicast mechanisms across the WAN and wanted to know how good the traffic flows worked; the ingress on the chassis and to the BladeSystems.

Deployment is easy. We just slide the blade in and put an OS on it and we're done. It's a lot easier than dealing with the rack mount servers and it is a lot faster.

The reliability, has gotten better; initially it was bad. I don't think there's anything bad to say at this point beyond those initial first impressions.

After I had training in the HPE BladeSystem the initial setup was not difficult. I was able to do the configuration of the equipment with ease.

Regarding the setup, it is easy for the blade itself, but the integration with the network devices needs to be done by someone who knows the product.   

The setup is easy if you install only one cabinet, and you know what to do and what to expect from the platform.

When you plan to grow your infrastructure to more than 16 blades, it becomes a little bit complex. You need to think about how to manage Virtual Connect Domains, MAC virtualization, and WWN virtualization.

If you design your platform based on that, everything will go fine. You will know what to do when a problem arises.

I'm not that hands-on too much on the setup piece.

Pretty straightforward. The tech talk documentation is very good (cookbook). They have standard scenario templates for blade chassis and they walk you through the whole configuration for whatever your needs are. They’re not brand-centric, so we can use whatever switch we’ve got, we can configure all the ports very easily, and it's straightforward to do so.

HP’s tech talks are significantly better than the market, especially Dell’s, and it’s easy for me to compute my blade chassis without too much headache.

I’d say that setup complexity depends on the type of system you get. We went for the blade chassis, and they were great. We recently dropped virtual connect and initially went with more traditional blades from Cisco, and they seemed to be fine. They were very clunky to set up, however, and I was disappointed. But setup for HP blades were fairly simplistic.

The initial setup was straightforward. Just follow the steps in the manual and you’re ready to go.

It was not really complex. Straightforward.

The initial setup was complex because of our HA requirements. The installation of the BladeSystem itself is easy and straightforward.

The modules are hot-pluggable. OA and iLO are easy to configure.

The most complex part was configuring the Virtual Connect module with VLAN tagging, shared uplink sets, and general network configuration.

The web UI is good, but it lacks tips and it's a bit complicated.

It wasn't complex because I had prior experience using Blade servers at another company.

It was very straightforward, seamless and very easy. My team did not have a lot of experience, and within a day they were experts. They were able to figure out the system and deploy.

We did not handle the installation ourselves. I can't speak to how easy or difficult it was to execute.

We have about 20 people that can handle any maintenance.

Its initial setup is very easy.

The early stages weren't as smooth as they should have been. I was involved in the initial setup and it was complex because of the nature we wanted to use it in; a very virtualized network and storage capacity. It wasn't quite straightforward and it meant a great deal of complex planning to make sure we got it right in the first place and the initial setup didn't cause problems later on.

HPE BladeSystem is easier to implement because of its size than other solutions. It's easy to install, easy to build up the BladeSystems, but the enclosure is too heavy.

The initial setup is complex. You need the help of a consultant.

We have two people to deploy and maintain this solution.

We did use some technical support, like through the professional services. We actually found some good, and some not so good, in terms of the expertise that we had. They didn't know enough. When we came around to setting up our VMs with the network they had, we had some challenges. There was a bit of a learning curve on both organizations. Not all positive.

I wasn't involved in the setup.

The initial HPE BladeSystem was easy.

I was involved in the installation and it was straightforward. We had support from the local vendors as well.

We have a vendor from here in Las Vegas who came up and helped put it together. I kind of watched over the shoulder and stayed out of the way, but that has been more or less my responsibility ever since. The setup was fairly easy. Ever since, any changes have been fairly easy to do.

It's quite straightforward. This is also outsourced to HP, so we just send the requirements; we want this kind of server, it is to be installed in that place, and then it's all processed by HP.

The initial setup of a blade system is very straightforward. In less than five minutes from the time you power up the system, you will have it ready to be managed and the OS deployed.

The installation was easy. It's usually quite intuitive since their operations team, and our team both have extensive experience in this type of facility, so that did not involve a special effort.

They’re pretty straightforward. It’s all automated so that their tools are deployed for us.

Straightforward, 90% of all installation you can just refer to the server cover for RAM sequence, CPU installations or RAID expansion.

I have not found the initial setup to be overly difficult or complex. It's straightforward. The process is simple. 

The tool was up in two hours, fully migrating blades from old to new c7000 included to this timing. Fiber zoning and ethernet configuration is a breeze. As long as you know your products from the last generation, it’s quite intuitive.

There's always a learning curve when you start with a new product. When you past the learning curve, then it's straightforward.

Initial setup is quite complex. You have to think before you start.

Very easy to setup and maintain, one to two days of training is sufficient for an expert to understand the philosophy. In case the level of the user is medium to low, some extra training might be required which is more to cover the basics of networking, consolidation and interfacing in an efficient way various systems together.

The initial setup for the HPE BladeSystem Enclosure is straightforward and you don't need to be an expert in data center infrastructure.

I was involved in the setup. It was good. We had someone from HPE come in to help us and that was useful. You have to learn the product and use it. It was a straightforward installation.

The initial setup took about an hour-and-a-half from start to finish, including taking it out of the box. But we did an awful lot of pre-implementation work that wasn't necessarily perfect, though at the end, we had a usable system in under two hours.

Setup was fine. The installers didn’t complain.

I'm not an operations person. I can't speak to how easy or difficult it is to implement the solution. It's not an aspect I worried about or specifically had to deal with.

The solution was implemented by the provider, as indicated it was in a simple way.

The solution was implemented by the provider. It was done in a simple way.

It was not easy as we had to get vendor for deployment because of lack of internal skills and time constraints.

No

The initial setup was quite straightforward.

The initial setup is not so complex, but regardless I strongly advise you to get vendor support.

Initial setup was relatively straightforward.

The initial setup was straightforward using a wizard.

It was a very straightforward migration.

It did take us quite some time to make the business case and to get the funding, but once we got all of that, the project went smoothly. We never had any issues.

For the technical part of the setup, we brought in professional services from HPE and they did the initial configuration and the racking and stacking of the systems.

It was easy. We leveraged VAR resources to help get up to speed with some skills training after installation.

The installation is very straight forward. We set up the hardware and there is nothing unique or complicated.  

The amount of time the deployment takes depends on the number of servers that need to be deployed. For the typical deployment, we have an HPE engineer on site. For each server it is very quick, let's say one week. The complexity is not very high.  

We have a gentleman who's primarily our BladeSystem expert.

The initial setup was complicated. You have to understand your environment before you let yourself expand through it.

The initial setup was pretty straightforward.

The initial setup was a turn-key installation.

The setup is not simple but if the low-level design is correct, then it is a straightforward implementation.

The initial setup was pretty straightforward. I've done most of the design work and specifications, but we actually brought in a third-party company to actually do the installation, and worked with them to do it. That all went nice and smoothly.

It was a straightforward installation.

The initial setup is always straightforward.

The initial setup is mixed between being straightforward and complex.

It is quite straightforward, as there is a wizard. I think newbies with simple documentation can perform the initial setup.

The setup is quite easy once you configure the Integrated Lights-Out (iLO) server.

It was not complex for us. We built our server installation.

It was straightforward.

The setup was quite easy to get going, although the virtual connects were a bit more problematic in the beginning.

The initial setup was straightforward.

The initial setup is easy.

The setup was straightforward.

Initial setup is straightforward and easy.

The setup is easy or complex depending on what you want to do.

I do not have experience with putting the solution together, as it comes pre-configured. The installation is easy. 

It was quite straightforward. You have to decide the right power supply option for your enclosure. The best solution is to have PDU in the racks and let the enclosures get power from them. We made the wrong decision with our first enclosures, which were delivered with 3Ph power supplies built in, which made the initial preparation and later relocation more expensive for each enclosure. Today, you can’t buy the 3Ph power supplies.

Initial setup is straightforward for the physical servers, but took a bit more time to configure the virtual connect switches inside the chassis.

The initial setup was intermediate - not very easy but not too hard.

It is straightforward. We followed the procedures.

It was straightforward.

The initial installation would be difficult for new users without training. I do not find it difficult because I have the HPE professional certification.

The setup went smoothly.