I did the implementation myself. 

We do not necessarily handle the setup and deployment totally by ourselves. We stay connected to the managing and support team. There are different product teams within the managing team. There is one for EDI (Electronic Data Interchange) Manager, there is one for Desktop Central, there is another one for the service management. There are many different parts at the support team level. Most of the installations do not require assistance but we can consult support when required. They will help us cope with any sticking point and we can move on from there.

In-house development. Difficult time finding vendor teams that are trusted and can bring expertise and efficiency. I would be interested in even using a resource like this today to help continue in adoption. 

We implemented it in-house. In terms of maintenance, it requires a fair amount of maintenance. It takes some time. You have to touch it every week and make sure it is working and pushing the code. You have to make sure you're identifying the gaps and the packages to be deployed. You need to build those packages, deploy them, and monitor which ones didn't fire. It is not an install-and-forget package. It is an install-and-use package.

In-house using white papers and previous tooling experience.

We implemented through an in-house team. 

I implemented it by myself, which took two days.

I received professional support for the initial setup.

We handled the implementation ourselves. We didn't need outside assistance. 

It is my understanding that the company had third-party support to do the implementation.

We can install the solution for our customers and do not need the assistance of third parties during implementation.

I did not seek any help from a third party for the deployment of the product. As I had used the on-premises version for three years, I found the cloud version was just surprisingly way easier to get started. Even someone without any knowledge of IT can probably get the tool to work.

The solution's deployment was done in-house. 

We were able to set it up ourselves in-house. 

In-house.

We use one person for the deployment of the solution. However, the deployment difficulty and time depends on a few factors, such as the size of the collection, how many computers are you deploying it to, how many users, and what is the size of the package and their complexities. Usually, once it's all replicated and the agents are online, if we tell it to deploy, it's almost immediate. Additionally, we do deployment based on off-hours, we can do them immediately or we can schedule deployments.

When the solution is up and running it does not require a lot of maintenance because it uses PostgreSQL, they have routines that manage the database. The only thing that you need to keep your eye on is the size of the repositories because as you patch more and you deploy more software, the size of your repositories grows and you need to keep a watch on this.

We deployed it in-house.

I didn't need support or a consultant to do the setup. I handled it myself and was very, very simple.

Our implementation was done through a vendor.

The solution’s deployment took 15 to 20 days.

I did the deployment of the solution on my own. I always upgrade the server myself, and I was the person who was managing the Desktop Central server and managing the Desktop Service Desk on my own.

I handled the implementation myself. If did not need the assistance of any integrators or consultants.

We implemented in-house.

Not with a vendor team, but with our talented staff of System Administrators who were able to read and study the verbiage of the documentation. 

I did it by myself in-house.

Implementation was done in-house and for the most part was straightforward. Once the client setup process is done I would suggest babysitting the automated pushes for a couple of weeks. We ran into some weird issues that we were able to resolve fairly quickly and completed the maintenance during our timeframe which otherwise would have just looked like the patching jobs failed completely when they succeeded in reality.

ManageEngine Desktop Central should not require a lot of maintenance that we have seen in the short time of our usage.

In-house. My recommendation would be to export all your computer objects, in .csv format for instance, from AD then import into ManageEngine. It would be simple and shorten the amount of time it would’ve taken, otherwise, to manually add each object and subsequently ease the process of deploying the agents to each object.

We deployed in-house and have no additional remarks about implementation.

We did not use an implementor or reseller to help us with the implementation process. We handled the entire setup in-house ourselves.

Just downloaded from manageengine.com and implemented and configured myself. Read an overview of this software beforehand so you know how you want and/or need to configure the software.

The implementation of the solution needs two or three technical executives. It is easy to implement as it is a cloud-based solution. It offers virtual tech support as well.

I did it myself for 300 workstations as you can leverage the program to install via Active Directory credentials.