The initial setup was straightforward. Deployment took a couple of minutes and involved five people who are system engineers. 

I was involved in the initial setup. It was rather simple.

We add solutions that allow us to manage them remotely. We can connect them remotely through a port called iDRAC that we need to add. We can then configure them fairly easily.

We used an intermediary company, and it was very comfortable and easy to implement in our company.

It simply included a pre-installation session to see what we had to do exactly. The rest was very easy. The implementation was nothing out of the ordinary. It was a piece of cake.

Our environment is all private. We have it divided between Azure and AWS cloud. We use Dell PowerEdge Rack Servers at a single location.

The deployment was very straightforward. The T150 came pre-installed with Windows Server 2022, out-of-the-box. Everything was there, including the drivers. It was perfect. There was just a very small custom setup of the Microsoft part. But out-of-the-box, I turned it on and it just worked. They keep it simple. It was seamless, a turnkey solution, for a Windows Server OS install.

The initial deployment unfolded with unexpected simplicity. The seamless integration and pre-configuration of the server components, coupled with the foresight of ordering my VMware directly from the factory, streamlined the process to a handful of minor configurations. As a result, the system sprang to life effortlessly. It truly was a plug-and-play experience – unpack, install, power on, and everything runs.

Our deployment strategy generally revolved around the substitution of aged server units. The process essentially amounted to a seamless sequence of insertion, installation, network attachment, activation, and rudimentary baseline configuration. This enabled the initial decommissioning of the legacy servers, facilitated by the meticulous pre-configuration undertaken in collaboration with Dell. Essentially, they delivered the system precisely as per our specifications.

The deployment is easy. A basic installation might take 15 to 20 minutes. 

The initial deployment was straightforward and took me a few hours to complete.

We are using the version we bought seven years ago and we'll be replacing it in the next month. 

I was involved in the initial deployment. It was more complicated as we went from actual service to VMs so there was a bit of complexity there. We ran the kit side by side and then migrated each server one at a time over the course of a month.  

The deployment of PowerEdge Rack Servers was new for me since I used to work with HPE servers. The setup was a little bit different, but it was easy to catch up and do the installation.

It took several minutes to determine how to work with PowerEdge and configure the BIOS. The one thing that surprised me is the ability to configure the BIOS from the iDRAC, not going directly inside the BIOS in order to do so.

I was not a part of the initial setup.

I was involved in the setup of the product. It was both easy and difficult to set up. However, thanks to the partner, it was more easygoing. There were a lot of people and it was useful to have somebody help as well.

We have a pretty big platform. It took two and a half months to implement the solution. That said, for our needs, it was pretty fast. We had to deal with multiple locations and we migrated everything to just one. We centralized the entire platform.

I was involved with the new infrastructure. It was very simple because the new PowerEdge servers that we ordered were vSAN Ready Nodes. We get our own machines. We do the hardwiring. We switch them on, and we immediately have our ESXi installed. Only the configuration is left to do. We only need to integrate new nodes and new servers in the bay centers and ESXi in our clusters at the bay centers. We then do the configuration. That is the administration part, and then, we link VMware. So, the integration has been hugely simplified by the fact that we have some vSAN Ready Nodes.

The deployment time for Dell PowerEdge Rack Servers depends on the project. For longer planning phases, it can take up to three years, while in more straightforward cases, it is a matter of weeks. The actual installation is easy and tool-free, involving simply clicking on the hardware, connecting it to the network, and using remote access for configuration.

Its deployment is very easy. Anybody can deploy it. They provide everything. Its deployment is easy and user-friendly.

For deployment, we have customized ISO for our environment. We use that. For ESXi, we are using the Dell custom image that they provide on their website. We can download that directly from there, and that's it.

The setup is my team’s responsibility. The initial setup is very simple. It is quite easy.

In terms of the implementation strategy, we have had a strategy of testing before rolling out. When there are several sites, we would roll it out only at one site as a single deal to test the technology that is fairly recent. If it is quite new for us and we have not tested it yet, it is an opportunity to get to know it and understand how to go about it. It is also an opportunity to validate our choice as a good one. Once that choice has been validated by the first site, we can place a more global order, and as a result, we can carry on with the other sites and equip them by using the same technology and experience that we had from the first one.

It is very quick to deploy. It takes something like 30 minutes to an hour for us to deploy.

I recommend reading the documentation before you deploy the product.

I was involved in the initial setup. It is extremely simple.

In terms of the implementation strategy, we had two delivered. We watched how they were cabled up, how they were built up, and we put the others. We had ordered together with a guide, and there were no problems.

We meticulously constructed the comprehensive foundation for a cloud service, laying each digital brick-and-mortar. Although the initial deployment presented a labyrinthine challenge, we were able to navigate its intricacies with measured steps. As anyone who has embarked on such an endeavor knows, erecting a full-fledged infrastructure, be it geographically dispersed for enhanced resilience or traditionally redundant for local fault tolerance, is no simple feat. It demands constant vigilance and adept stewardship to ensure its smooth operation.

We constructed the comprehensive network infrastructure, weaving the intricate cabling throughout the designated pathways. With resolute focus, we configured and installed the potent server hardware, ensuring its seamless integration. And most notably, we adeptly orchestrated the deployment of the robust cloud stack, paving the way for unparalleled scalability and agility. 

The initial setup is pretty easy. It is an out-of-the-box experience. It's plug-and-play. We click it in, attach the cables, and start.

They are pretty easy to deploy.

I am involved in the deployment of these servers. I work in a research laboratory. We are about 100 people, but we are a part of the Paris Observatory. It is like a university with about 800 people. We all work daily together with the IT teams.

I am responsible for handling presales with the technical and salespeople from Dell or HPE. We are not in charge of the orders. We handle the equipment and install the machines, and we organize the rollout of the infrastructure, VMs, and all that. Afterwards, we also handle interfacing with users.

The initial setup is rather simple. We do not have any real problems, and even when we have had a problem, it was fairly quickly resolved.

In terms of implementation strategy, when you are a small company, there is no big strategy like big companies. We get there, we install it, and it works. There is no strategy.

The implementation was very simple.

They are currently deployed on-premises, with the possibility of a private cloud. We use Microsoft Azure. They are implemented at several locations. In the Galicia community, we have an implementation of PowerEdge with VxRail as well.

The setup is very simple. When deploying PowerEdge, we used the automated server and OS deployment features. Our clients are very familiar with the setup. It's straightforward and very fast. If someone is knowledgeable in IT, they are familiar with PowerEdge.

The initial setup is straightforward. We had 10 staff members involved in the deployment. The server bill team set up the hardware and the DMR team ran the virtualization layer over it. The security team completed the checks. We have about 55,000 users supported by this solution.

The initial setup is not complex but it is counterintuitive, specifically the chassis. The FX2S chassis holds up to four half widths blades and has a pre-built two-module network card and eight ports that mirror each other.  

The PCIe slots on the back of the chassis are hardwired and challenging to set up.

We did not use the automated server of OS deployment features. We installed the hardware and then installed the software manually. We are a dark site. Dell could be a little bit more friendly to dark site management. There's a huge customer base out there that just cannot utilize a lot of their solutions in a classified environment.

They are very good in terms of deployment. Our automated system is there, and there is no problem with using our deployment tool with it. I cannot think of a case where we have hit a problem. It has been fast. There is nothing to do with the hardware. There are no obstacles.

Deploying PowerEdge is straightforward. To get it up and running takes about an hour.

The rack and stack takes a couple of hours, maybe less. The overall installation depends on the use case. In general, it takes about two to three days to have a full working solution.

The initial setup is pretty straightforward. It's out-of-the-box, and I've never found a snag or anything like that in the process.

We deploy everything by hand; everything is manual.

It doesn't take that long, and we can even do it with our laptops and desktops. We do not do any ghosting or imaging, and a server usually takes me a day at the most, while I really take my time with it and get all the updates in.

The rails are difficult. The way they clip in seems good on paper, but when you are doing it yourself at a data center with a 30, 40, or 50 KG server, it is very difficult to try and line them up, whereas, with some of the competitors, you just kind of push in. They are much easier to put in.

In the environments I work in, they are almost entirely on-prem, but I am not involved in the deployment.

During the initial setup, especially for the iDRAC configuration, I created custom scripts to automate configurations for iDRAC, BIOS, and Syslog. This streamlining process allows for a quick server installation. Once placed in the bay and prepared, our team can efficiently install the operating system and other necessary components.

In terms of our deployment strategy, we configure everything directly on-site. This includes setting the IP address for the iDRAC based on its final location. I then deploy the system using a pre-defined password and run a script that configures the base settings. Following this, the NG systems, including both Linux and Windows, take over to install the operating system.

The implementation was simple. There was no specific implementation strategy for it.

We implemented Dell PowerEdge Rack Servers in a hybrid cloud model. For the public part, we used ESSENCE IT. We have our servers deployed in several locations.

The initial deployment is straightforward, and that improved over time. Our project management is pleased with the quick deployment; nowadays, we can even deploy remotely. Deployment takes no more than one hour.

Our deployment strategy is to work remotely; technicians install a rack on site, and I can deploy as soon as I get iDRAC.

Deploying the PowerEdge Rack Servers wasn't a problem. We just plug it into the rack with help from the university computer center. They let us know where to put it and connect it to the required network.

We take care of all the software, like the operating system, permissions, local security, data access, etc. This is all Linux-based, and we have experience, so it's straightforward. For maintenance, we use Dell's OpenManage console a little to tweak the configuration for performance, but we generally set up the system and let it go. We only update the operating system once a year and upgrade the environment.

We handed over the complete installation in September. We started in August. It takes time. You're coming into an empty room. You have to have power, you need the AC for the equipment there that has to be moved out. It takes time. The racks were pre-populated in Toronto and shipped to Montreal, and then in Montreal, they were set up and powered. We had liquid cooling and radiators on the rear of the cabinet for the heat.

We've done many of these installations, and it's pretty routine. There's nothing complex about it. The complexity is mostly that there are so many key parts in terms of getting it delivered on-site. There are so many parts from so many different vendors and there are penalties if you don't deliver on time. Nobody wants to pay penalties.

Deployment was relatively straightforward for us. The most labor-intensive part was the physical setup in the data center, handled by the data center team. After that, the installation of AHI was a breeze, making the overall process quite manageable.

My company's tools for deployment had to be modified to take care of the product's deployment phase. The product's deployment phase was not super complicated, but it did take my company a couple of weeks to build it up and to make it work, which was not too bad. The aforementioned process would have been the same for every other company as well, so it was okay, in my opinion, since it was not worse than the processes of some other tools.

The solution's initial setup is a bit complex because we have a fiber environment and a network environment, which we always have to configure. The fiber environment takes a lot of time. The network environment takes some time, wherein you install the OS and deploy your configuration file on it. The implementation is pretty fast and takes five to ten minutes. Then, you do all the configuring around it because you want to connect it to your power store.

It was straightforward with the help of the Dell wizard. I just needed to connect it to VMware. Obviously, someone has to study when preparing to deploy and configure PowerEdge Rack Servers. In my case, deployment and configuration of two PowerEdge Rack Servers with VMware, cloud, and integration with our storage took about three days.

My strategy was to launch these servers as quickly as possible. First, we made sure that there was communication. Then, we installed clients in VMware. After that, we started installing the PowerEdge Rack Servers.

It is a cluster, so you just plug and play.

It normally takes one day to integrate PowerEdge.

The initial setup was very straightforward. We knew exactly where we wanted to put it in our array and how we wanted to set it up, what the power requirements would be, where it would fit on my battery backup system, and the plan for system recovery in case it had to be gracefully shut down. It was super easy.

When deploying PowerEdge, we didn't get a chance to use the automated server and OS deployment features.

The deployment was scheduled for six hours and it took three. 

We actually had to migrate users off of an older version that we had onto the new box that we had. The implementation strategy was all about really getting our users off the box and making sure nobody was trying to access it. After that, it was just migrating users over, setting up the new box, putting it online, and running tests.

For maintenance, normally we use a server admin, myself, and maybe one other developer that helps us with the syslogs on it. There are probably three of us altogether.

Deployment took approximately a week. Initially, we required three people to do the deployment. After the deployment, we have three people dedicated to doing operations and maintenance.

They are easy to deploy. There are no problems with that.

We were well prepared, and we have the same type of servers in the bays. The wiring is marked, and we know that environment very well.

The deployment is not difficult at all.

The initial installation is easy. Through Dell software, we can create baselines. And with those baselines, we can automate the first steps of deployment. Stuff we would normally have to go into the data center, physically connect to a server, and do by hand, can now just be done after two simple steps.

Normally, deploying new hardware would sometimes take a couple of days, including getting it already for the business. Now especially on the tedious first steps of installation, we save time.

The initial setup is straightforward. I created a document explaining how to perform the task, and it was quite straightforward for individuals who are not familiar with PowerEdge systems. There weren't any complexities in the setup process; it's essentially a repetitive procedure. Once we've configured one PowerEdge server, the process is the same for all of them, as the product line doesn't substantially differ from a setup standpoint when utilizing PowerEdge servers.

Starting from the moment when ESXi is installed, the deployment takes approximately half a day to finish.

The initial setup is straightforward. For somebody with experience with Dell products, to begin with, it's simple. It's no more complicated than deploying the M1000, which was the predecessor chassis to the MX7000.

I can deploy and network an MX7000 chassis and have all the blades loaded with ESXi within a day. I make use of a lot of my own scripts and usually, I employ a script to mount the ISO images that'll be installed on all the blades through a shell script, and then the script also reboots the blades, and the blades mount the ISO image and install VMware. All of that happens quickly.

After that, I simply put in the network parameters for the ESXi hosts, add the host to the V-center, and then they're ready to go. I already have some predetermined configurations that I use for the network blades, the MX5108s. I use those as a template for all four blades on the back of the MX7000, and simply paste them in. I can usually have all four blades configured within 30 minutes to an hour.

I am involved in the implementation of these servers. The implementation is simple.

We know that we need half a day in the data center to do everything regarding the racks. Once that is done, we can also split the tasks because, although the servers are in the same bay, we do not want to be on top of each other when working. So, we can work in parallel during the installation of a certain number of servers without any difficulty. If you do not have a console, it is quite limiting because, with a screen at the back of a server, you are limited to working on only one server at a time.

The solution’s initial setup is easy.

The initial setup is straightforward.

There are no problems to report related to their implementation.

The initial deployment has been occasionally straightforward, but we have also come across instances where machines brought about challenging difficulties that were difficult to pinpoint. In the majority of situations, it's positive, but not consistently.

Given the confines of our restricted IT infrastructure, we opted for a meticulous, hands-on approach to server deployment, manually installing each one within its own designated space.

Its initial setup was very straightforward. It took a day. We have a certain process that we follow. We've had a server setup from a couple of years ago, and we follow that process. It's just making sure that all the relevant information is in.

While I wouldn't call it a problem, physically mounting the servers into the rails that come with the servers can be a challenge. They could be engineered to be a little bit easier to use. It's not that significant, we can manage it, but you need at least two people to do it together because they're a bit heavy. You have to slide them exactly into the rails. It's a little bit challenging, but not serious.

From unboxing it to preparing the rack and sliding the server into it, connecting everything, and powering it up, it takes about 30 minutes or so.

Integrating it into a particular environment is very simple. We set up an IP, connect it, and install a server operating system. It's a very rapid process. Within about an hour, it is up and running in the environment.

The initial setup is not intuitive. The first one took a while, but after that, we were done within an hour.

When deploying the PowerEdge solution, we were able to use the automated server and OS deployment features, but I had to talk to Dell support. They had to walk me through it. However, once you do it once, it becomes very easy.

I was involved in the initial setup of this solution. It was easy.

I was using the Power Servers for the last 14 years and it was transferred from the day I started working on the servers. It was always easy to set up for me and easy to train my employees. However, I don't do that anymore, my staff does it for me. However, it remains easy to set up.

The initial deployment was straightforward because we already had technical architects who knew how to deploy the solution.

The deployment took over a month.

Deploying Dell servers feels like rocket science, but as a seasoned professional, it is generally straightforward and intuitive for me. I rarely use manuals and rely on my experience. Occasionally, finding the right person with multi-disciplinary knowledge can be a challenge, leading to minor delays. Overall, the experience is good, but there is room for improvement in certain aspects.

The initial setup was easy.

It is easy to set them up. We could realize their benefits within a few months of deployment.

I am involved in their deployment as an assistant and not as the main person. Most times, it is straightforward, but it also depends on the spec that we get with different solid-state drives or hard drives. Sometimes, the RAID sets can be a bit more complex.

With regards to getting the server into a state where we can deploy our application, it takes a few hours. In a few hours, we can deploy the Windows operating system, do the RAID setup, and then it is ready for our in-house solution.

For me, the setup was easy.

The only maintenance is cleaning it and adding hard disks.

It did the initial setup, more or less, by itself. I did a little bit of fine-tuning here and there, but nothing drastic. It was very easy. 

I was the only person involved. I was responsible for everything from physically getting the stuff in the rack to configuring it and making it live, and everything in between.

The initial setup is straightforward. Deployment took two days. We implemented new power servers in a cluster one by one. 

The setup was of moderate complexity. It was normal.

When we set up the virtual infrastructure or when we update it, the strategy is always to do it in steps. We change each server separately and take small steps and obviously avoid any service outages.

In terms of environment, we have a private cloud and on-premise setup. We have different providers, such as Belorcio and Telefónica, and we have two large CPDS, one is in a private cloud that is outside the organization and the other one is on-premises.

I am a part of the decision-making core team and the approval core team, so I am ultimately the one who opts for one technology or another, one manufacturer or another, as long as the purchasing department finds the price fair.

The installation was very simple in the end. The strategy was to virtualize. Once you are already involved in virtualization, things are very easy.

We have a hybrid cloud. We work mainly with ANALEC, but the entire management part of the cloud migration is carried out from the headquarters in Mexico. We only participate. We do not make any decisions for the cloud strategy. We, of course, need to have visibility over the strategy from Mexico, and we use that when making decisions about the software solutions that run on top of the hardware. In this case, we will bet on VMware instead of IPV.

These servers are located in our main data center. We have some PowerEdge servers left. We opted for FX chassis a few years ago too, and we have some PowerEdge servers left.

It's easy to handle. You just put it in, connect it, and it works. The average time it takes me to set up a server and get it to work is about 15 minutes.

The initial setup is straightforward. The solution's deployment team that assisted are on top of their game. They are easy to contact and set it up fairly quickly.

Deploying Dell PowerEdge servers is straightforward and efficient. It saves us a significant amount of time since it's mostly plug-and-play, with minimal setup required. Our technicians have become accustomed to the process, with approximately fifty percent of the time previously spent on setup now being saved. As we continue to set up numerous Dell servers, we find the process consistently easy and reliable, with no major changes in the setup procedure.

We did the setup. We installed a Windows server and configured the hard drives.

The complexity of the setup is as complex as setting up any server. It's not as simple as a laptop but not excessively complex if you've done it a few times.

Our strategy was to set up the servers and then we migrated VMs from the old servers once the new ones were ready.

The initial setup is pretty straightforward. We haven't run into any complexities when setting up Dell systems for our end-customers.

For the deployment, one person is sufficient to handle it without any hassles.

The maintenance and management are pretty simple, and an administrator can manage hundreds of these systems efficiently.

Deployment typically takes no more than 20 to 25 minutes maximum if the customer is ready with the network and has taken care of any other environments.

We definitely want to leverage the automation capabilities in terms of deployment because the deployment times will be even less. Moving forward, that's the plan.

The initial setup is so easy. One just need establish a remote connection with the network console, allowing the applications database to be installed as desired. 

The initial setup is very easy, as is the management. The time required for deployment depends on the environment and requirements. For example, it will differ based on whether it is a cluster deployment versus a VM implementation.

I was not involved in its implementation. It was my team that was involved. What I know is that it was very easy to implement.

In terms of implementation strategy, we spoke with Dell and our specialists, and everything was very easy.

We have a hybrid cloud. We use Microsoft as the cloud provider. Dell PowerEdge Rack Servers are currently being used only in our department.

PowerEdge Rack Servers are pretty standard servers. You put them on the rack, you plug them in, and you set up the settings.

The initial setup was straightforward. 

Once we get a server, we can have it up in a day. One person can do it unless it's a heavy server. In that case, we need two people to lift it. Almost anybody on our staff can deploy this server if it's needed.

PowerEdge servers are easy to set up. You need about two or three people, including a specialist and an engineer, to maintain the solution. You usually need an engineer plus a specialist in Hyper-V or VMware.

The solution's deployment is pretty good, and we used ProDeploy from Dell. We gained a lot of information during the deployment, and it's also been a learning curve for us. It's very helpful that knowledgeable people are doing the ProDeploy so you can also learn about the implementation.

The initial setup is straightforward. Deployment took one to two hours.

I had a little bit of difficulty in the beginning when we used provisioning with automated tasks almost ten years ago, but after that, it was very straightforward.

Deployment is simple. Within one hour the server is up and working.

We didn't find the implementation to be complex. The initial setup was fairly straightforward. It was easy for us to handle. We were able to do everything ourselves in-house.

The deployment takes about an hour. To install just the racks only takes five minutes.

The initial setup is straightforward. It was easy.

The initial setup was very, very easy. 

There's nothing to work with on the server itself. 

You just handle the configuration, and you do some EFI configuration. In the last stage, you're going to install the operating system so that it is a fast service. It depends on the disks you put in. At the server level, so it doesn't have that much configuration. It's just installing Windows and any operating system. Then you build over that.

Except for the Bios updates and the drivers and the compatibility issues, you don't have any problem with compatibility.

The setup was extremely simple.

iDRAC is easier to configure, with the front LCD panel, on the non-XD models, being very handy.

The NFC option for the front bezel combined with the mobile app is great for on-site troubleshooting.

For a small, extra cost, you can get OpenManage Essentials with configuration management. This allows you to deploy pre-configured hardware templates making mass deployment easy.

The initial setup is straightforward.

The deployment time varies depending on the application being deployed. For example, the exchange took me a couple of days to get it up and running, and on a straightforward file sense server, it was less than three hours to get it up and running.

The security server also took a couple of hours to get it up and running.

We have four members to deploy and maintain this solution. They are made up of engineers, managers, and admins.

The initial setup is not complex. It's quite easy to set everything up, in fact. All of the underlying technology is the same on Dell, so we don't have an issue handling the implementation on the Dell servers for our customers.

If you're familiar with deploying servers, then it's not really complex. There is a bit of a learning curve when it comes to setting up the OpenManage server and agents, but nothing unsurmountable.

The initial setup is straightforward. 

It took two days to complete the installation.

We have one person to maintain it.

The initial setup was straightforward.

The initial setup is straightforward. We only required one or two staff members for deployment and maintenance. 

The deployment time depends on the size of the setup. So far, we haven't had any problems with the setup.

It took one hour to set up this solution. We have 20 staff members using it. 

The installation is easy and takes approximately one hour. The servers are okay for stand-alone deployments. 

The initial setup is not overly complex or difficult. We found it to be easy. It's straightforward. A company should have no trouble whatsoever.

The deployment only took a few short hours. It's pretty quick.

I cannot recall the amount of staff it requires for deployment and maintenance. It's my understanding that only one engineer is required.

The initial setup was straightforward, we had consultants do this for us with a 3-person technical team and it took one day. We currently have over 100 users. 

The initial setup was straightforward. The installation was okay.

The initial setup is quite easy. The Dell OpenManage interface is straightforward, Obviously you have to read through the documentation a bit before you set it up, but it is quite straightforward.

It took us, I would say, a day for each site, because we set it up at three different sites and they're each about 80 kilometers apart. Each site took a day because we had to rearrange our server room, how the cooling would be done, and the power and things like that. Obviously, there were other things contributing to the setup of the server, not the server itself.

The initial setup is very easy. It's not overly complex at all.

The deployment is also very quick and easy. It takes maybe 10 minutes to just install one rack mount server. Our engineers can actually take less than 10 minutes to install one server. We have eight engineers that handle deployment and maintenance.

It has a great deployment model.

The initial setup is very good, not complex at all.

The initial setup was easy.

We were already familiar with the hardware so it was straightforward to set up the web server for our requirements.

The initial setup is mixed between being straightforward and complex.

It was straightforward.

It is easy to set up because the Lifecycle Controller is very friendly, especially when you use the GUI for initialization. The system and the RAID controller take time, but in general, it is very easy to set up. You can check the Lifecycle.

It was straightforward.

The installation was simple for the IT department.

It was straightforward.