The setup is easy and everything you need is preloaded. Deployment takes a two or three hours and includes configurations. 

The setup requires some knowledge of infra or it might be complex. Once you are used to the solution, it is quite simple to cable, connect, and implement. 

Training courses, guides, and instructions are comprehensive and included on the solution's support page. 

The initial setup is not so easy. It has a medium level of difficulty. On a scale from one to five, the difficulty could be three.

Depending on the operating system, however, it could be 20 to 25 minutes. We need less than ten people for deployment and maintenance. Likely, within a year, we'll be buying as we migrate over from Blade to Synergy. 

I am sure that that initial setup was complex, but Pointnext made it look really easy.

We purchased it already configured in the rack, which was huge because you roll it into the data center, then everything is already cabled, except for your outside connections. This saves you at least two days, if not more, of putting the Legos together of the system. Then, we were able to plug the system into our network and immediately able to start to configure it. This maybe took two hours to fully configure a three-frame enclosure with 20 compute modules in it. That was extremely impressive.

Within the two hours, we were using the compute modules. Other than getting people to move off of their older servers into the frame, which is more of a business thing than technical, because you have to arrange outages, we were able to use the system immediately.

The initial setup is easy.

It has been very straightforward to set up. We have had no real problems. Even from the onset, it's helped us out with stuff quickly.

The initial setup is very simple. 

It is easy to set up the solution. 

The deployment did not take very long. It just takes a couple of days to set up the infrastructure.

The installation may take some time. You have to plug in all of these things and do fail testing, et cetera. We did use Oracle databases and sometimes they might fail. The snapshot and remote snapshot, for example, were not happening on time. That takes time in terms of resolving those issues if they come up. You might have to run a script for contact support.

The initial setup is straightforward.

The initial setup was very complex. The cabling was such that it had to be done a certain way. It is one of those things that you want to not touch once it's stood up. That is our initial impression.

The implementation was pretty fast. It's easy to manage and integrates well with everything. Sometimes integrating storage with other vendors can be a bit tricky. However, it can be done. 

The initial setup of HPE Synergy for us is straightforward. We provide the knowledge to our customers if they choose to deploy it themselves. However, when the customers do the process it takes time and is technically demanding.

The initial setup was complex. We had a couple of bright engineers working on it, and they figured out a lot of things that they don't know. They don't always have experience around certain platforms. The problem was that they couldn't find documentation easily, to walk them through setup when they just didn't know the platform.

The deployment of HPE Synergy is easy and takes approximately three to four hours.

The initial setup is straightforward. I worked on it a lot for one year. Synergy is a little bit different, but I got enough training initially. In addition, HPE deployment guys were there for the initial setup. Later I did it myself.

The initial setup was very straightforward. It took us around six hours to set it up. There were no complications at all, because Synergy comes as a box. You don't have to do anything. You just have plug it into the network, and that is it. It's done.

The initial setup was straightforward. We've been using HPE products for a long time. We've been using blade servers for a while. We were coming off a c7000 solution, so it was really easy to understand what they were doing and just jump right in. It wasn't a big, major shift. Just an evolution to a better product.

The initial setup was pretty straightforward. We did run into a little issue with the depth of the box, so we had to order a deeper rack. That just delayed it a bit. However, we could have avoided this ahead of time if we knew that it was a bigger than a standard chassis.

The implementation process is straightforward. It is not complex.

The initial setup was complex. It's due to understanding the environment. My team had zero knowledge about the environment so we significantly leveraged resources from the reseller. Most importantly, we depended on them to bring all the technical expertise. We then got onboard to do what we could manage.

The initial setup is very easy and straightforward. 

The initial setup was complex. It was slow and just didn't work. Even HPE couldn't make it work for 45 days.

The initial setup was very easy.

The initial setup was fairly straightforward. It was just the basics that we would have expected in using a product that we were already familiar with in OneView.

We did use HPE’s Pointnext services, and our experience was okay.

The initial setup, because it was still in beta, was complex. We discovered several bugs in the networking and bugs in the way some of the iLO functions worked. We were one of the more prolific groups in the beta program. Those issues should be fixed and we'll confirm that later.

The initial setup was fairly straightforward.

The initial setup was pretty easy. There's a learning curve to it, just like there is with anything else. There are "ifs," "and's," and "but's," but they cabled it up for us. It was pretty straightforward after that.

The initial setup was definitely different from what we were used to, so there was a learning curve. However, the more experience that we gain with it, the easier that it becomes. Every implementation has been sort of faster and easier than the previous one. We are to the point now where it is pretty straightforward for us.

The initial setup was pretty straightforward. The only issue that we had was our rack was too small. The product is heavy, so it took a lot to get it in there.

The setup was pretty easy, but we did have familiarity with OneView prior to deploying it. That probably helped.

The complexity of the setup was medium, but it was good. We didn't have to map things out. It was still faster than setting up what would have been with the c7000s, but it wasn't just a drop in, turn it on, and it worked. We had to configure the composer, figure out all our networks, and things like that. We had to do some network configuration, but there were white papers for all that. So, the setup was medium, and we were able to get through it pretty much ourselves with the help of AdvizeX.

The initial setup was straightforward. It was pretty easy to start up and use it.

The initial setup was somewhat new, not just to us, i.e., the customer, but also to the implementation team.

The initial setup of this solution is complex. The interconnects would not connect and nobody knew why. It took at least forty days to complete.

Configuration was difficult because it's so new. Even the people at HPE weren't well-versed on how to configure it correctly. So it took a lot longer to configure than we thought it would. But once we got it configured, it functioned very well.

It took us about a month to get it configured, to get all the bugs worked out. Then we were able to utilize it for about two months as part of our proof of concept.

Ninety percent of it was straightforward. The ten percent that was complex was only complex because it's not very intuitive. You have to know where to go within OneView to find the options that you need. And because it's not intuitive, it's not easy for someone who has never done it before to do it. And it wasn't easy for the people who were supposed to know how to do it, either.

The initial setup is straightforward. The infrastructures as code enables you to fill out the configuration before you even deploy it, then it is just a one-touch deployment.

I just switched companies. My old company did not use Pointnext services. This new company does use Pointnext services, and it's a lot easier to get the hardware on demand. You don't have to worry about making those hard upfront capitol purchases.

Its initial setup is very easy.

I don't remember any problems handling the initial setup. Everything was described and really detailed in the documentation. 

We work with a really small team. Two guys handled the deployment and maintenance. It's not necessary to have a huge team to deploy and run the production.

We found the initial setup to be a bit complex. It wasn't exactly straightforward and simple. It would be ideal if they could simplify the process in the future to make it easier.

The deployment took about one business day.

The initial setup isn't too complex. It's straightforward. With the team we had, it was fairly easy. We also had assistance from HPE throughout the process, and having their insights were helpful.

In general, the maintenance is handled by HPE. We don't have to worry about it.

The setup was straightforward.

The initial setup was straightforward. The expansion was complex, because adding a second frame onto the original frame caused an outage.

There was a certain level of complexity to this because this was the first time for our staff in using this platform. There was some complexity. There are different options for the interfaces for the staff. It's a little bit different than what they're used to doing on the onboard administrator for the other blade enclosure. It was a matter of getting to know the new features. They took their time to understand all the capabilities.

I wasn't involved in it, but my guys were. They were trained, and I think that they said it was much easier than what they used to previously. So, they're fine with it.

I was involved in the initial setup, from a guidance point of view. I worked with the HPE engineers who did the original deployment and then on a day-to-day basis, just setting up the final bits and pieces. We added things as we went along. It was lengthy and I think we had a reasonably unique deployment, which took a bit of “to and fro” to get the completed solution in place. There are enough differences between Synergy and the old c7000 platform that you do need to put effort into your design. HPE helped with that process and we have ended up with a well implemented solution because of that.

The initial setup was a little complex because it was a new system for us; different than the c7000 enclosures that we used before.

Our environment is very complex. That had a fair amount of bearing on deploying this platform. The OneView tool promises to make things simpler. Sometimes, it overlooks some of the really edge cases of the configuration to make things simpler, and that's what we found. There would be another tool to go to behind the scenes to go do what we need to do or troubleshoot. So, we have challenged the HPE team: "OneView should be the one thing to go to. There should not be something else behind it, telling me to go login here, but rejecting me because I don't have that username and password, then making me call support to login." We don't like that.

The initial setup was very easy. I installed and deployed this solution within a day. We have one engineer managing and maintaining this solution.

The initial setup is very simple and straightforward. It's not complex or overly difficult. A company shouldn't have any issues.

The initial setup was straightforward.

The initial setup was straightforward.

It has gotten better. The initial setup we did was on 3.0 and that was overly complex. With 3.10, everything's been changed, revolutionized, the guided setup made things a breeze. I've been able to walk colleagues of mine through it. I'm able to demonstrate to customers how easy it is to set the frame up and get things going right out of the box. That's been an incredible change.

We've gotten enough training that we're able to set the product up for our customers and walk customers through it without the need for having HPE expertise on site. Worse case scenario, they're a phone call away, but it's been so simple to use, it's been fantastic.

The initial setup was quite complex and it is being done by the HPE support department. It is not yet ready for customers to do themselves. In the end, it will be more straightforward. You will be able, at a later time, to automate and script it, so that eventually when you connect a new device, you will be able to have it automatically installed.

The initial setup was complex and this can take around three weeks to a month. 

The initial setup was fairly straightforward.

The initial setup was straightforward. We met them at the data center for four days. We racked, stacked, and deployed it. They showed me the ropes. It was easy.

There is more to keep in mind with Synergy. Remember that our customers are coming from BladeCenters. Where after 10 to 15 years of it, and everybody found it fairly simple at this point, then they have this new paradigm of scaling out to many multiple frames, and so many more modules. It is a change in mindset. Therefore, some people will say that it is complex simply because of that. It is not that difficult though.

The installation was very straightforward.

It was pretty complex. We weren't allowed to do the setup ourselves, we had to have an engineer from HPE. In my book, that's complex, if I cannot do it myself.

The setup was a little bit complex, because it was the first one. It is a new product, so nobody knows it too well. We are kind of learning on the way, but it is OK. It's a new technology, so I think it's normal. It still needs a little bit of ironing out to be completely integrated with OneView. There are still some issues.

We were shipped the very early solution and it's installed in a data center in Michigan and we had other people do it. We helped them do it remotely but it wasn't hands-on for us. The kit is owned by HPE but it's managed by an external company and we work with that external company to use the kit and help set it up. Our experience with them during the setup was great.

The main challenge we faced was that when it was installed it just did not work. There were faulty components and it took weeks of troubleshooting to find the faulty components, get them replaced. Getting help from HPE was difficult. Nobody knew about the product. It was a brand-new product and people had not been trained on it. That part was not a great experience.

The setup was very complex. The intention for Synergy is that it's auto-discovery. You turn the power on and everything happens and it's all done for you. It absolutely did not work that way. If you have one faulty component - and we had several - it just does not do what it says on the tin. Again, it was an early production model, so we understand things go wrong. But again, getting support for the product was very difficult because nobody knew about the product because it was brand-new.

Overall we've had a good experience. We have had a little problem during startup because the OneView software is older than the last release. During the update, we had some problems, but HPE solved them quickly and perfectly.

The initial setup was straightforward.

The initial setup was complex. From what I was told, there were issues initially with getting the SFPs on the floor for our data center and something with the image, but I think that was on our service provider' side. They couldn't get the image to deploy with the right drivers and stuff.

One of my things I do in my company is write technology blog which is quite technical for the type of audience that I have.

I don't have a Synergy enclosure yet in my home lab, a.k.a., data center in my garage, but I'm quite sure that it is simple enough that my nine-year old daughter could install it.

I was not involved in the initial setup.

The initial setup is pretty straightforward. An organization probably wouldn't have too many issues. I have struggled with the configuration aspect, however. That can be a bit difficult.

I cannot remember exactly how long the deployment takes in its entirety. It's maybe an hour or so, for the physical installation. After that, the deployment and configuration depend on the organization and its requirements. Sometimes it's a couple of hours. Sometimes it takes two days.

You only really need two people for deployment and maintenance.

Because of the cabling between FLM modules and a composer, the initial setup is complex. We are more familiar with IPv4 than IPv6. I think the initial setup is more complex than for UCS or c7000.

The initial setup is done by a partner and it is straightforward, but it takes time.

It took about a day to implement this solution.

It was easy to follow the guides. It was straightforward.

I think we needed HPE only for the hardware install. After that, I don't think we really needed them.

Straightforward.

I was involved in the setup and it was easy.