I rate the initial setup phase a ten on a scale from one to two, where one is difficult, and ten is easy.

The solution is deployed in an on-premises model.

The solution can be deployed in two to three hours.

The solution's deployment phase is very straightforward and easy.

During the deployment process, our company tries to understand a customer's environment since architectures vary, and some customers may have multiple sites for whom we can make decisions on how to get the solution to work optimally. ManageEngine ensures that good documentation is available to users explaining the best way to do things. Understanding an IT environment helps the people from our company to decide on the robustness part of the solution. It also helps to understand the requirements from the beginning of the deployment phase. If people from our company know the IT environment of our customers, then it helps us to do proper planning, after which we just need to go ahead with the deployment phase of the solution. In general, planning and understanding of the architecture are areas that take time during the deployment phase, which follows after it can be done quickly.

The solution's initial setup process is simple.

I rate the initial setup phase an eight on a scale of one to ten, where one is difficult, and ten is very easy.

As per the law in Cambodia, the solution is deployed on an on-premises model. No solutions can be deployed on the cloud, but eventually, I hope we can move to the cloud. Some solutions are also deployed on hybrid cloud, but people mostly prefer on-premises as an option.

The time taken for the solution's deployment process depends on the environment and size of the company, but it can be done within 30 minutes on average.

For the deployment process, you need to find and study the patch and then scan the computer to decide which agent is installed on the system. Once the scan is completed, it will show the endpoints or computers where there are missing patches, then the solution also recommends patches before showing you which patches are applicable, and then it shows you which patches are critical, low, medium, or high, after which you can go through the process of test and approve. After the test and approve process, you can go ahead and install the patches and deploy those patches to your computers. You would also have to add policies, and though it has existing policies, you can also create custom policies for the deployment. For example, you can choose between a policy to deploy the solution now or deploy after business hours, which is a big process in the final deployment process.

We completed the deployment in two phases. 

The initial setup was straightforward.  The initial setup was easy.

The tool's deployment is easy. It takes one to two hours. 

The initial setup is straightforward. 

The deployment took approximately one week.

Two people were involved in the deployment, and we have one administrator who takes care of maintenance.

The end-users need to set up their file-sharing properly, so sometimes we have issues with that before we set it up. It has to be done manually.

I did not complete the installation but from what I understand, the initial setup is straightforward and easy to do. It involves installation on the server, as well as the endpoints. It takes approximately one day to do.

The initial setup was not complex at all. It was very straightforward. 

Deployment took just over a week. Within three or four days we were up and running. The server itself took about two or three days to implement. Two days were spent actually setting up the server. After that, we just had to install and configure everything. Then we deployed agents to workstations and that took about three, four days. It was a week or so in total, from beginning to end.

About five people were involved in the deployment process, including support from the local team. Three people, who were server administrators, from my organization and two people from the local support team were involved.