The setup wasn't complicated. A Trend Micro engineer deployed it for us. We had an Active Directory deployment and pushed it to all our branches using our management software. 

I tend to do POC setups and sometimes manage troubleshooting for customers. On-premises, we can install an agent from the console if there is an Active Directory. 

The deployment itself takes two to three minutes. 

If there's centralized management, it's fast. We might do a more manual process if it's a smaller organization. If there are more than 5,000 to 10,000 nodes, we need a team to help deploy it. 

Typically, one person is enough to handle maintenance. 

The initial setup is very straightforward. There were no complexities. It only takes one or two minutes to deploy. We have the product in multiple locations and branches.

The initial deployment of Apex One was straightforward. We have done both online and offline installations. If a local IT can deploy it they will. If not, it can be done online. The installation of the agent is very easy. If an agent is corrupted, we can use a tool to remove it and install the latest version of a new agent. It's very flexible in that sense. With other products, if an agent is corrupted, it's very hard to remove from the system. Here, it's very easy. You can just remove it and reinstall the agent package. 

With good internet connectivity, you can deploy the solution in 30 to 40 minutes. It's very fast. 

We'll download the MSA package from the console. That'll be given to the IT team, and what they do is push from the SCCM console. Once the systems are online, then they can push it to those systems. It can be done in silent mode without the knowledge of the user.

We have three people handling the deployment, and they are working with nearly 40,000 endpoints. Whoever handles implementation needs to have a good understanding of the endpoint protection software and its requirements and basic knowledge about the antivirus policies, as the policies may need to be altered or changed based on the country's requirements. Sometimes you need to have a scan exclusion and whitelist certain applications or URLs.

As a cloud solution, it doesn't require maintenance. 

Apex One was already deployed when I joined the company, but it's straightforward. You can do it alone, but I always prefer to have someone from the support team available to address any issues I might have. 

Deployment is complex, and most organizations use scripts to automate the installation process. Each environment is different, and deployments typically take two days to complete.

The deployment was straightforward and took approximately six hours to complete. The vendor provided us with resources in advance, including database and IS configurations, before arriving to implement Apex One. This facilitated the download, implementation, and licensing of Apex One. One person was required for the deployment.

The initial setup process was not easy or difficult. It was moderate. You do need to have some knowledge of the solution in order to deploy it effectively.

It was an on-premises solution. My team and I were involved in its deployment.

It took us about three to four months to completely implement it. We took our time. We first implemented it on some of the machines and saw the results. We then implemented it on other machines. Within one year of implementing it, we could realize its benefits.

I was involved in the local deployment of Apex One and not the corporate one. We have several offices, and I was just involved in this one. It was straightforward.

It took five days because we had to go to all the computers and implement it one by one, but we did not spend the whole day just doing that. We were doing it in phases and by departments.

In terms of maintenance, we had to change the version. It took two or three days to perform the change.

Its deployment takes time. If I have to deploy it in a huge company with over 10,000 clients, it takes a little bit of time. If I am using CrowdStrike, it would take only two or three days, whereas Trend Micro takes more time. I have not measured the exact time difference, but it takes more time compared to other solutions or the next-gen antiviruses. It also depends on the environment because organizational units are not available all the time.

I deployed it on the cloud and on-premises. It depends on the end-user scenarios and topology. In Turkey, customers mostly prefer on-prem solutions, but this is changing day by day. Customers in Turkey tend to have their information on-premises. If a customer wants an on-prem solution, then I offer them the Trend Micro product or Trellix product. It also depends on their budget.

Its deployment is not too complex in my experience, but from the customer perspective, it is a little bit tricky. It takes a little bit of time. They have to have a little bit of background knowledge.

The implementation strategy varies. Sometimes, I use third-party solutions, and sometimes, I am just pushing from the central management console. It depends on the customer's topology.

In terms of maintenance, it does require maintenance. It depends on the company budget because some of my customers have a few locations in Turkey, and sometimes, they have only one IT specialist. They send that one person everywhere in Turkey or to multiple locations. If they have more than one IT guy and if they are also distributed, they do not have to send those guys to other places. It depends on the customer's budget.

Our organization is responsible for the deployment of Apex One to all of our client's endpoints. The deployment is straightforward. The deployment took around five days. 

To deploy Apex One, we must first install it on the server. Then, open the firewall ports for all freelance clients. Next, check the availability of the client-server communication port. In the directory, place the login script and the existing agent. The client will then be automatically pushed to the Apex One Control Manager. The agent will be notified that there is new software available that needs to be migrated. The upgrade will take place, and the client will need to be restarted for the agent to be installed. The same process applies to roaming clients.

Eighteen people were involved in the deployment because there were 16 sites, including airports, landports, and seaports.

The deployment is straightforward. First, we deploy an SQL database to consolidate all of the organization's databases into a single, easy-to-manage database. We then download the Apex One Security Agent to the Apex One portal and install it on the target endpoints. Once the agent is installed, we receive the ports, IP addresses, and IIS names of the endpoints. We then install the Apex One Security Agent on the Trend Micro Apex One site and configure it to scan the agentless operating systems for integration with Active Directory.

Three people are required for the deployment.

The initial setup is straightforward. We usually plan and gather data before implementing. We ensure that there are no residual old endpoints installed in the system. We then set expectations with the client and proceed with setting up the management console. We install the system step-by-step and then work on the policies. We also integrate with other systems and transfer knowledge and troubleshooting skills. 

I usually complete the deployments on my own, but for our larger clients with over 2,000 endpoints in different locations, we need to be on-site. For a three-month deployment of those 2,000 endpoints, we allocated three engineers. There was also one time when we had to allocate a lot of engineers for a government agency with eight thousand employees.

The solution's initial setup is straightforward. We have installed the solution on two virtual servers with high availability mode.

I'm not a fully technical person, so I was not directly involved in the deployment. My pre-sales manager was largely involved in deploying and handling the dashboard as well as administering it to multiple end-users. If we run into any trouble, we can get help from Trend Micro sales. They can provide guidance. 

The solution is working okay. There is no maintenance needed. 

The initial setup was very straightforward.

Go to the site, answer a few questions and within five minutes, you're up and running.

The initial setup was complex. It was completed within a duration ranging from eight to twelve months, typically spanning from eight to eleven months.

We use it as a service. Its initial setup was straightforward.

It does not require any maintenance from our side. Everything is automated.

The initial setup of Trend Micro Apex One is simple if it is a fresh installation and can take only minutes. However, if there are other solutions set up prior it will take more time.

Apex One isn't complex to set up. The deployment time depends on the size of the company. It could take a few weeks in some cases. A five-person team deployed the solution. 

We had some initial challenges configuring high availability on our server, but it wasn't difficult otherwise. 

The solution is easy to implement. It took about three hours to implement it.

My team of maybe two or three people were able to handle the deployment. We have three people who can handle maintenance as well. 

Deploying Apex One was reasonably straightforward and took almost a month because we had to deploy it across multiple locations. Three or four engineers are enough to handle the deployment if you have any kind of organizational access and data purposes.

First, we had to identify and prioritize our assets. We did some testing on the low-level assets to analyze the solution's impact and adjust the policies. Some things might be inappropriately blocked. We deploy for a limited number of applications first to ensure they're running smoothly. After we install the antivirus, our full schedule is used for the other applications or on servers and production only.

The initial setup is very easy. The deployment was very fast.

The initial setup is not complex, but good documentation and knowledge are required. The person implementing the setup should be knowledgeable of all the features available, and the knowledge should be distributed among the end users so they are aware of what they will have and the benefits.

We completed the implementation within one week using three people. Our initial target was around three hundred users with endpoint protection and our deep security, which can virtualize our servers, as well as the additional features of the DLP.

I wasn't part of the team that implemented the solution. I wouldn't be able to say if it was complex or straightforward.

It's pretty low-maintenance. We do continuous updates and we also update the backend security appliance that goes with it, which probably happens three or four times a year.

The initial setup is easy. You just need to install the agent, which usually takes a couple of minutes. Moreover, maintenance is not required because the product automatically updates to the cloud.

My team was part of the deployment and from my end, it was a smooth process. The deployment took three days to complete. 

We utilized Trend Micro's auto-deployment feature via Active Directory to seamlessly uninstall the existing antivirus software and deploy Trend Micro Apex One.

The deployment required two people from the customer's side and one person from our end.

It is on-prem as well as on the cloud. I was involved in its initial deployment, but it was four years ago. It was simple. It was not too complex.

In terms of maintenance, it does require maintenance. 

I wasn't involved in the deployment. The client deployed Apex One, and I use it in my capacity as a SOC analyst. It doesn't require any maintenance from our side. I am using it remotely. However, the client may need to update agents and things like that.

The initial deployment took one hour and we had the assistance of the Trend Micro team.

The initial setup was very straightforward. I did the installation by myself.

Regarding deployment topologies, whether it's on-premises, a hybrid cloud, or a public or private cloud, installation is quite easy. It will be up and running within a couple of hours.

Once we deployed it, we had to connect the console to the dashboard. Once the dashboard was up and running, we could filter out threats by connecting to the Trend Micro Data Security Operations Center, which has a threat intelligence ability that highlights all of the threats. The data comes from the CMDB database and It shows us the CVS4 of each threat.

It was overall straightforward, but there were a few challenges. The reason we went for Apex One was that it is a cloud-based solution. 

It was pretty straightforward to enroll the endpoints. We integrated it with our Active Directory and all the devices were easily enrolled.

The removal of Trend Micro was challenging. When we moved away from Trend Micro, it was a bit of a challenge to remove the tool.

In terms of maintenance, it does require maintenance. From time to time, there will be new agent versions that need to be deployed. The first time also, we had to deploy the agents through SCCM. There are regular updates from Trend Micro. About 80% to 90% of devices get those updates and about 10% to 20% lag behind, so it does require regular monitoring and sometimes manual intervention to check why the updates are not happening. You might have to reinstall the agent on a device.

In a few scenarios, we did engage with Trend Micro where we had an additional or early release of the patches that can be deployed, and we did use that support.

I have experience with on-premises and cloud deployments. I prefer the cloud. The cloud setup is easy. 

The deployment depends on the client. If client requirements are clear, it is easy. Otherwise, it can be complex. In Pakistan, there are many problems that we are facing with the deployment process of Apex One because some clients are not pushing the agents to Active Directory or remote registry. We have to install it manually on every computer or place it on a shared server to install it on their endpoints.

The deployment duration depends on the number of endpoints. For more than 2,000 endpoints, it can take two to three months. If you are only installing the endpoint solution from a remote site without making any policies, then it does not take too much time. You just need to push the agent.

It requires maintenance. There are upgrades. They inform the customers and partners when they are having a major upgrade.

I would say that the initial setup was a little bit complex.

Installation is very simple when a web portal is available. You can log in and create the policy. The initial setup process took about one to two hours. 

Deploying the on-premises solution is a seamless process, especially when dealing with the application components. Apex One or Apex Central is the management console, with Apex One managing antivirus consoles, groups, and parts. Policies can be efficiently pushed through Apex Central. The agent itself is equipped with XDR capabilities for on-premises solutions. Conversely, an additional service installation on endpoints is necessary for cloud-based implementations. The deployment process is relatively quick, typically taking around half an hour

The solution was deployed on-premises. The company used Citrix Cloud, however, the machines that people worked on were local. There was no cloud-based machinery.

I was not involved with the deployment of ApexOne. I can't speak to how long it took. 

Uninstalling or removing the product wasn't easy.

The solution did require maintenance. Every month we did an image update of the VDI environment. We manually had to make sure everything from ApexOne was exactly right, and the update process was very tricky.

We had a consultant for the installation. He logged into our system and installed it. It took two days, which also included training.

It does not require much maintenance. It just works, and our system administrator does not have to work much on it. He uses it only if there is any issue. Otherwise, he does not touch it.

It's an easy product to set up, from my understanding. I don't recall discussing any complexities during implementation. The deployment likely took less than a month. It doesn't take too long. 

At this point in time, just a couple of engineers are needed to manage the solution.

The installation of Trend Micro Apex One is straightforward. Once we added the endpoints to the console the installation was not problematic in any way.

I would rate the migration and implementation of Trend Micro Apex One a five out of five.

Apex One was deployed before I joined the company. It requires some maintenance. Trend Micro's support providers contact me monthly about our problems. For example, when we upgrade the Apex One web version, we need to upgrade the Microsoft version. That's the problem for me in our business network. 

The initial setup is straightforward. It is easy to deploy the code. I give the initial setup an eight out of ten.

The deployment is quick.

The setup and implementation are not complex. It does take some time for many users or machines. Typical installations take about two days. 

Setting up Apex One was straightforward. When we moved from on-prem OfficeScan to Apex One, that migration was also smooth. We didn't need to do much. Usually, on-prem to cloud migration takes a lot of research and planning. Apex One installation is practically automatic, so it didn't take that much effort. We migrated the endpoints from on-prem to the cloud without much manual work. 

The installation process was not much of a challenge.

The initial setup is very easy, I deployed myself together with an assistant and I estimate it took us around 10 minutes per computer. We probably have around 150 users. 

The initial deployment was straightforward. It took about two months to deploy.

We have the solution deployed in multiple areas.

It does not require any maintenance. You just need to make sure it is up to date.

We only prepare the servers with Trend Micro Apex One for the customers. We give them VPN access with one server and their team is working on it to maintain it. However, we are receiving monitor reports from the solution. 

The product's initial setup is simple. We use the SaaS-based version of the product. You need to dedicate one person for the tool's maintenance. 

I cannot tell you exactly if it was straightforward or not because it was very long back that we installed it. At that time we faced some issues because we needed to identify what was missing. Those kinds of issues were there, and slowly, we sorted that out.

The initial setup of Trend Micro Apex One is easy.

The initial setup can be difficult. We had some issues, however, we worked with a local provider here in Bulgaria, and successfully performed this type of installation previously.

The initial setup is difficult because the process is long, and it took us about five to six months because CORETech is about that size.

The installation is very easy and quick, it takes approximately five to six hours to complete.

When you started doing some of the advanced things, it becomes a bit more complex when you start running the mobile device management and we're doing Apple enrollment because Apple is so difficult for the enrollment features. So when you're doing stuff like that and you're running it across the internet, that's got a fair bit of configuration that you need to know. Partnering becomes equally as important as the tool. With the right partners. 

The initial setup was very straightforward. It was only a matter of sending it to the console and it took care of the job for us.

I was not involved in the initial setup.

The solution has a moderate level of difficulty. It's not too easy and also not overly complex. For example, compared to Symantec, Trend Micro is more complex.

I'd rate the setup process a two out of five in terms of the ease of setup. You need to have prior knowledge. 

Installing and configuring Apex One is simple. It took maybe an hour. 

The installation is easy and took approximately 10 minutes.

The initial setup is straightforward.

We gradually upgraded everyone from the previous version to the new version. If I add up all of the time we spent getting everything done, it probably took us a couple of weeks.

There are two of us that manage this solution as well as Carbon Black.

The initial setup is straightforward, as long as the setup of the customer is also straightforward. There could be some complexities involved. It depends on the current setup or network set up of the customers.

Initial setup is straightforward, it takes a day. Deployment requires between two and five people depending on the size of the company. 

Initially, we tried to set up on-premises and there were huge pain points. Trend offered us their cloud solution.

We tried the cloud solution and it seemed to work much better.

The on-premises was daunting to set up, as there were a lot of issues and several challenges. We ended with their hosted solution, which addressed many of our pain points.

We had the cloud solution up and running within a day or so. The cloud solution is far quicker because you don't have to do all of the heavy lifting of installing it on-premises and all of those other features.

We have an IT team with five of us to maintain this solution, but it's generally done by two individuals.

The initial setup of the product is okay. We can do a few configurations and the implementation is pretty simple. We can manage it easily. It's easy to understand. 

The deployment took five to ten minutes. It does not take too long to set up. 

Trend Micro Apex One installation is not complicated, it's just straightforward. If you have some experience with the solution it is simple but if you are new to configuring the database it can be complicated. This is the one difficult aspect of the implementation, if they can do the database configuration everything else will be easy.

The installation process is straightforward. We are automating it, so I am not sure of the time that it takes to deploy. Installing it is done through our group policy.

I work with Trend Micro as a salesman, not a technician. However, what I understood from others is that the setup is okay. It's not complex. 

The initial setup is straightforward.

It was quite easy for us to migrate to Trend Micro Apex One cloud.

The solution's initial implementation is not difficult or complex. It's easy to deploy and quite straightforward.

Its initial setup was straightforward.

The initial setup was not complex at all. It was easy and very straightforward. We recently migrated from OfficeScan to Apex One, and it was a very simple process overall. 

The deployment took place before I joined the company.

The initial setup was straightforward. We did the migration ourselves.

From the manager's vantage point, the solution has a straightforward setup for the user. It's quite easy. 

The time the deployment takes is minimal, this process varying with the agent involved. 

The initial setup was straightforward and very easy.

The initial setup is quite straightforward. There are a lot of options after you set up the solution. After the initial setup, it's quite easy to do. It's not complex.

The initial setup is very, very straightforward. It is available under two offerings. One is on-premise, where we have to install the server and database. The other is the cloud. In the cloud, we have to just create our account, and we can just start using it.

The cloud option is very easy, and there is no need to maintain the server and no need to install anything. It will just create an account, and we can start using it within ten minutes. At the same time, the on-premise will take two or three of us to deploy it. We have to create three servers and then database services, and we have to install the application over that. It will take some time. Both are straightforward. They have created a guide for installation. If we follow the guide properly, we can get it installed properly.

There isn't a lot of maintenance needed for the cloud solution. If we choose an on-prem deployment, we will have to maintain the server and database. We also have patching from time to time, which we also have to test. On the cloud, the backend team handles any necessary maintenance.

The initial setup is not complex. It's pretty straightforward. 

The deployment doesn't take much time, however, it depends on the size of the organization. It's very slow to deploy the product to multiple clients. If your organization has a 10,000 user base, sit will take longer than if you have a 2,000 user base. It just varies according to the number of machines to which it will actually be deployed.  

We have about 2,000 users and we have a team of three or four people that handle maintenance.

The initial setup of Trend Micro Apex One is simple and easy to manage. The platform is easy to understand.

The implementation took less than one month.

The steps we took for the implementation of the solution were the installation of the server, the deployments from the clients, the agents in clients, and the configuration of the too,l such as rules.

The initial setup was very straightforward as we were clear on our scope and what we wanted to achieve with the solution. We had 700 work stations and about 250 servers and the overall deployment too two months.

The solution is easy to deploy.

The initial setup is not that tough. It's easy. 

The installation is very cool. It is so nice.

It took 20, perhaps 40, minutes.

The technical team needed for the deployment and maintenance can vary. It depends on the company's environment, or the project or contract involved. I am not referring to the 20 permanent users I mentioned but to the customers, the clients. The number may be 18, it may be 15. It varies.

The initial setup was straightforward. It takes a day to configure the server for configuration policies and other such stuff. For the deployment of the endpoints, it can take 15 days to set it up at the workplace.

It is not as simple as it appears, but there are numerous options available. They include mobile security, as well as many other features. So you'll need some tricky options such as the use of servers and other such things. It isn't as straightforward as Symantec. 

When I use Symantec, it's simple, but Trend Micro has a lot of features, such as DLP, security, cloud sandboxing, and more. It requires the use of three or four servers.

The initial setup and consult will take one or two days, but the deployment for the branches will take five to seven days. In total it can take up to 20 days to move the package.

We have a technical team of two administrators who maintain this solution,

Trend Micro Apex One is easy to administer. They have different consoles to manage different aspects of the solution. If you want to use XDR you have to use Vision One and that is not good.

Installation of this software was quick. It took just 10 to 20 minutes to complete the installation.

The deployment takes between two and two and a half hours.

The initial setup was straightforward. It's easy.

The initial setup was straightforward. It was not complex.

It was initially straightforward. It took multiple phases. 

Its installation has medium complexity. It is not very difficult, but it is also not that easy. It is an endpoint product, and the installation also depends on the number of users. The maximum number of individual deployments that we have done was about 8,000 users. We had around five engineers who worked for around three months for the entire deployment.

The initial setup is straightforward. The length of time required for deployment depends on the customer's environment and what other products they have. The average time to deploy Apex One is about two and a half months, which includes integration, client setup, and other things.

The initial setup of this solution is extremely simple. It is deployed from our SCCM solution, so it happens automatically. 

The initial setup is very easy and quite straightforward. A company shouldn't have any issues with it. The process is not overly complex or difficult.

A full deployment only takes three to five days, and therefore isn't too time intensive in general.

We have three staff members that can handle deployment and maintenance responsibilities.

Due to the solution's general user-friendliness, the initial setup is not too complex. It's pretty straightforward.

The policies tend to be a bit more complex to set up, so we do need some expertise in setting up the policies. This requires some preparation and knowledge.

The cloud services are straightforward, but the on-premises version of Apex One is not straightforward. It is a complex installation of Apex One.

The deployment duration varies. We have to first prepare all the prerequisites, which takes a lot of time. Overall, the installation takes up to two days. For a large enterprise, the deployment would take one to two days. 

It's very easy to implement.

Depending on the customer's environment and the features they are using, it can take two to three people to maintain and manage.

If they are using the device's central application to control everything at once for more than 2,000 users then a single person can't handle all of the modules. This would then require more people for maintenance.

Apex One is easier to install Kaspersky than other solutions.

The initial setup is very easy.

This is a simple product and the initial setup is straightforward. We have installed it in over 15 companies. Deployment usually takes around two hours and involves two or three staff.