My use case is to serve the complete IT environment of the telecom, including all cloud applications. I use HPE Synergy servers for my private cloud and for network management systems. 70% of my workload is running on HPE servers.

Our customer initially deployed a blade system, which was later upgraded to the Synergy chassis. We transitioned the system and migrated our data, finding the experience straightforward and reliable. The decision to upgrade was driven by the aging of the previous system and the opportunity to implement a more robust virtualization solution with Synergy. The Synergy unit is connected to an HPE 3PAR storage, which remains unchanged and performs well.

I typically recommend HPE Synergy to companies in the banking sector, government, and telecom operators because of its centralized management and ease of administration.

I'm using the solution for managing cloud infrastructure for data centers. We are using it to manage the center. We manage and store data over there. We use it for RMCV and RMCVO.

Our use cases depend on each customer's needs which might include running standalone services or creating orchestration for VMware or Hyper-V clouds.  

Our team looks at each use case to determine needs, the environment, and strategies for achieving goals. We then match hardware and software to goals and cooperate across teams to implement solutions. 

We have 50 staff members across various teams who manage implementations and maintenance.

Our company has 2,000 developers who use the solution for integration with OneView to manage servers and enclosures. 

We have multiple racks set up with different platform servers like DL, C7K, and Synergy. At least three enclosures are linked together in Synergy which is a prerequisite.  

We set up multiple blade servers, install ESXi hosts, and add the blade servers to VMware as a host. We manage our 30-40 ESXi hosts through vCenter which is private. From there, we test and develop products that will be used in the vCenter application. OneView integrates with vCenter to manage resources. 

The use case is related to the platform Binware. We grade the platform of Binware, the old version of Bingware to the new version of Binware since the old version has an obsolescence issue. We've been successfully migrating all Bingware options and the Bingware version to the new one in this new Blade Synergy.

We use the solution for infrastructure and business applications. We have the mini virtualization and physical servers. We need to consolidate all the servers in one management.

Our standalone servers and Windows hypervisors are running on the product.

Customer workloads of extensive computing

We are providing solutions to our end customers. So I work in a distributor company, so we are still using this product and providing solutions to the store.

The primary use case of HPE Synergy is for invoicing. Our Brazil office uses the solution as we do not have Oracle ERP there. It is a legacy system.

It's an HCI solution. I've also used it for on-prem and GreenLake solutions for consumption model requirements.

It's typically for enterprise solutions that are multi-data centers and multi-sites. There are several Synergy frames.

We have deployed HPE Synergy in a data center. Customers are using HPE Synergy for production running VMware Hypervisor, Microsoft Hyper-V, and standalone servers. However, the customers are mostly using it for the VR solution.

We use it for public cloud right now. It covers a plethora of workloads. We have everything from the small, mom-and-pop, five-user accounting shop running QuickBooks, all the way up to data analytics running machine-learning on it.

I'm a system integrator and service delivery manager dealing with strategy. We are an HPE partner company. 

We mainly use it for virtualization. We are using Generation 10 model.

It's a little bit more complex than Blade Enclosure. It's like any virtual environment, probably. If you have virtualization on the top of the Synergy Frame, it works well.

We primarily use the solution for VM virtualization and Oracle standardization.

It's useful for virtualization, and we run all our applications in HPE Synergy.

We primarily use the solution in order to deploy an on-prem client.

We have built our on-premises private cloud on top of HPE Synergy connected to 3PAR SAN storage. Our cloud was built above Hyper-V hypervisor, and that's the computing node of it.

Virtualization is our primary use case.

We use this solution to run both our production and non-production environments. We currently do not have any cloud initiatives, but we bought it so that we can be future protected for the cloud.

We use Synergy for VMware and some physical servers.

We do a lot with ESX and virtualization of workloads.

We use it for our infrastructure. We have multiple servers, therefore we use it as our main infrastructure for applications to host our servers.

We don't have a hybrid cloud environment. We use on-premise.

It has made our IT infrastructure teams more efficient. Previously, we had a standard infrastructure, which was compute, power, and storage. They had to run from one place to another to create a virtual machine. Now they can do everything in one shot.

• Graphical workstations
• Replacing the c7000 systems
• Analytics
• DevOps, using containers.

Moving virtual machines over to Synergy.

In a hybrid cloud environment, the solution enables us to do SQL. We are able to move it up and take it down.

The primary use case is VMware hosts. Since most of our environment is virtualized, it is our primary compute.

Our primary use case is virtual desktop infrastructure. We use them to run VMware Horizon View for engineering applications and higher-end desktop users.

The primary workload is workstations using NVIDIA Tesla cards. It helps our engineering students to run CAD applications no matter where they are on campus, instead of having to go to a lab to do it.

VMware is our primary use case for this solution. We run all of our production servers and non-production servers. That's what our cloud delivers virtual workloads to.

We use it primarily for hypervisors at the moment. We're looking at expanding into VDI, but it's primarily for hypervisors.

The primary use case is really a replacement for the BladeCenter. Though, we would like our customers to see it more in the composable fashion that it has been positioned. The primary use case (as our customer see it) is they can't go further with BladeCenter, so they are choosing Synergy.

Traditionally, our customers have been using their BladeCenter, and now Synergy, to run any type of mid-tier applications or virtualized platforms that, for whatever reason, don't fit in the hyper-converged area. 

From a hybrid cloud perspective, Synergies are more seen for the potential of integrating into orchestrated and automated deployments, so they can have cloud-like functionality on-premise. They are not quite at that yet, and in the couple cases where we have deployed it, that has certainly been the goal.

We're using it for our production server loads and for disaster recovery purposes. In terms of a hybrid-cloud environment, we use it for our database workloads. We have records management systems and dispatch systems which have critical databases which we run on these platforms.

Our primary use case is primary compute. 

For us, it is a server refresh. We moved away from c7000 Enclosures.

The primary use case is virtualized workloads. The workload are typically packages and things that run on Linux. They are just general-purpose, virtualized workloads.

We use it for ESXi installations. It is for private clouds with application servers.

Our primary use case is data center and tech refresh/cloud.

This product is basically a step in our transformation to be more hybrid.

We use Synergy for everything: Exchange, virtualization, and SQL. Most of our stuff is still on-premise. We are not really doing anything with hybrid cloud from Synergy right now.

The primary use case is virtual machines. We run VMware on them and virtual servers, so applications, web servers, and things of that nature.

The solution enables us to run VDI, backups, and web platforms for our organization in a hybrid cloud environment.

We use it as a VMware host. We're a highly virtualized environment, so we run several VMs per blade.

We use the solution for data centers. It supports hybrid cloud management tasks.

We use HPE Synergy for infrastructure virtualization.

I don't remember the models. However, there are Synergy nodes built in the cloud infrastructure with a design utilization. Some of the project was within two Synergy baskets with a full load installed.

We are primarily using this product to build a private cloud infrastructure.

Most of our use cases are under NDA. I can't speak to how specific clients use it.

Use cases can vary by quite a bit. Generally, companies can use it as a computing system, as a database, or for virtualization. There are very different use cases that can be covered by this product.

We are resellers of HPE Synergy and I'm the CTO. 

We use the Synergy Frame to host the main infrastructure for a big project. We have multiple Synergy Frames that are all managed by a single OneView interface.

The uptime and the performance meet our expectations, plus the integration with 3PAR is very good.

We're using Synergy primarily as a replacement for our C7000 Blade servers, which are going out-of-life.

We use VMware ESX across all of our Synergy nodes. On top of that, we have a mixture of workloads from web servers, application servers, and Microsoft SQL databases.

We use it for our analytics platform.

We use it for mission-critical applications and mission-critical databases. An example is that we host development servers on it.

We give out certification training on HPE product lines. Synergy is one of the product lines. It's part of our composable infrastructure in our hybrid IT training. We use Synergy for giving customers and partners hands-on experience.

We use it for converged infrastructure (compute). We are using it for Hyper-V and our SQL environments right now. We are doing some DevOps on it, as well.

It is where we do most of our compute for the various different things for our homegrown software that we developed and use. We also use the product for a third-party software that we do, using cloud-based services. 

In a hybrid cloud environment, the solution enables us to a lot of databases, then different homegrown in-house developed stuff that we use for media servers and compression servers. We can also do management for workforces and optimization for workforces, in terms of the products that we provide.

Right now, we are mostly using it for building out data center services. The biggest things that we are using it for are large scale virtual farms. We have recently even started using it to have large shared database resources for shared platforms, like Informatica.

We were evaluating it to replace some of our older infrastructure. We have Dell M1000e Blade chassis. We were doing a proof of concept for the last three months with it.

It would cover all kinds of workloads. We have Oracle Databases, we have SQL databases, we have web servers. There's a VMware environment with VMs that manage all sorts of workloads.

It's our day-to-day production device. We deploy our workloads and VMs in clusters on it.

The primary use case is for processing our analytics platform. The solution enables us to do all of our analytic workflows in a hybrid cloud environment.

We are using it for SQL servers on HPE servers. We use the service across the company. We are in three countries. It serves all our users.

Our primary use case for this solution is virtualization.

The primary use case would be our virtualization platforms, ranging from our presentation layers to just commodity workloads. 

I don't know that we're too much focused on hybrid cloud just yet, since we're a service provider. A lot of our clients are paying us to host their workloads. It's not like we're running our own IT and putting it in the cloud, as well. However, as we do move things there, these workloads are probably the ones that are most opportune to move to the public cloud. So, it would generate a hybrid scenario, as these are Citrix presentation systems, and also Windows and Linux VMs, which can move back and forth.

We are going to use it for the SQL server and hypervisors, thus for virtualization. From our point of view, it is the compute power that we are really looking to use. So, expanding on what we have been doing with the C7000 series, and moving it into Synergy.

Primary use is data storage.

Performance is about a seven out of 10.

My primary use case was to familiarize myself with this new HPE product because I know it is a replacement for the old C7000 chassis, so for me it was interesting to see the new features, to know the product as a whole.

Primary use case is for Oracle Servers to store a large database.

Right now the performance is good, but we have only had the solution installed in production for two months.

Internally, we use it for VSAN as well as Docker, with the flexibility to flop between the two solutions at will. We also demonstrate the solution for multiple customers.

Performance is fantastic.

We're doing a new product line, we're now doing Big Data. We had the help of HPE on it. They advised we use this platform, so that's why we have it.

The use case is to replace all stakes in all the different kinds of servers. We had some Dells, we had some old HPEs, Generation 6, Generation 7, and so on. We decided to put everything together and create a new datacenter, and move our computing power to a platform that will enable us to be more flexible with our old applications.

We are just in the middle of the migration, and the problem is not the new stuff, the problem is to persuade our old stuff that it must perform more than one gigabyte per second. So HPE is helping us to replicate directly through the old datacenter to storage that we have underneath our Synergy Servers. 

We use HPE Synergy for digitization and containers. 

We work with the Synergy OneView 5.4 version.

We use the solution for hypervisor infrastructure.