Setup isn't complicated.

I would rate setup as four out of five. Setup took a couple of hours because of some of the requirements. It can take up to a month depending on how many policy configurations need to be done and how many users there are.

I would rate my experience with the initial setup an eight out of ten, where one being difficult and ten being easy to setup.

With regard to complexity, it largely depends on the number of redundancies that you require. For example, if you just have a standby setup with maybe two or three Zscaler enforcement nodes that your tunnels need to terminate on, it's fairly simple. 

However, the more redundancy and higher availability requirements that the company has, the more complex it gets. So it can get pretty complicated if you have some crazy requirements with regard to high availability and redundancy.

You just need one person to deploy the solution. One person can mostly do it. A lot of parts as well. 

You would require an endpoint specialist; someone who manages the endpoints. Additionally, you might need someone from your SOC to ensure that you're able to ingest all the logs and security alerts that are being dumped into the same solution. Perhaps one or two individuals for testing purposes. The policy installation process is quite straightforward and shouldn't take a lot of time. One person should be sufficient for that.

The initial deployment was quite straightforward. I wasn't really on board at the time the implementation of Zscaler took place, but overall, when new features and functionalities are added to the product, it's quite straightforward to implement them and to roll them out to large user groups, or globally. From a rollout perspective, it's quite easy to use.

Initially, one of our demands was that everything should be cloud-based, meaning we shouldn't have any agents on each computer. We learned the hard way that such an approach doesn't work well, because you need something to control the path from the user's computer to the Zscaler cloud. You need to be able to steer how the traffic goes. You can do that with PAC files. But ultimately, together with Zscaler, we figured out that a client was needed, at least for our needs.

Setup is about medium difficulty. We needed more background information on how to set up a proxy. Setup could be easier.

It took between 30 minutes and one hour to set up the solution, activate our Zscaler company profile, and to configure ZIA.

The implementation process is easy. The agent they use runs very smoothly.

We've only completed a POC and plan to roll out a full implementation soon. In the past, I have implemented it completely as well. We are planning to deploy for the sales users first. 

It's not a difficult process. Once the agent is installed, it needs to be verified with the console. The deployment takes between 30 to 45 days, depending on the level of support needed to complete the task. The issue is our sales team are work from home users. That can make the process longer. 

We also need to create user policies before the full deployment happens. Different policies are needed for different users. We may need to create three to four different policies for different user sets. 

ZIA's setup is not easy because of the multiple clouds. 

I rate the setup phase a nine on a scale of one to ten, where one is difficult and ten is easy. The setup phase was easy.

The cloud is deployed on-premises.

The time taken for deployment is around fifteen minutes.

One admin person is required for deployment.

The initial setup is straightforward. It is just a plug-and-play process. When the Zscaler client is installed on the machine, it works like a normal proxy. They're connected to the cloud. The solution is deployed on all the users’ machines, and the management and policy creation is done at the cloud level. It's a cloud proxy.

The initial deployment process is quite easy. I've implemented Zscaler Internet Access in large, multinational corporations and recently at a company that is in 64 countries in the world. The deployment is always fairly quick. I have also worked with smaller clients, and Zscaler deployment is even easier in these cases.

It was very complex, but there was training provided by Zscaler. That was very good for understanding it thoroughly. It was complex because we had to make sure that all our rules from previous platforms were migrated over so all our users had access to the same things that they had access to in previous models. 

We aren't yet fully deployed. We have been at it for about a year and a half. We currently have over 50,000 users deployed and another 120,000 to go.

The only pain points that we have are self-inflicted because of our slow rollout of the product, which is not actually Zscaler's fault.

The initial setup was pretty easy. The deployment took about three months.

The initial setup was straightforward. It took about three days to set up.

The solution’s setup is pretty straightforward, but it depends on your experience with Zscaler. It would get a bit difficult for a new buyer owing to multiple profile setups and configurations during the process. I rate the solution’s initial setup as a nine.

The setup is straightforward. If a customer orders all of the features there is a lot of configuration work to do, or they can choose to leave the features in the standard setup. We recommend they take a few days with one of our consultants who are familiar with the solution so they can point them in the right direction. The configuration is based on individual requirements.

The initial setup was easy - I would rate the setup process four out of five.

What I have seen when I am doing PoCs is you need some perimeters to start building this platform and integrating policies from day one. 

An improvement would be if they could provide an out-of-the-box experience, like 20 to 30 features all ready to go. In comparison, LogRhythm offers out-of-the-box features. With Zscaler Internet Access, there is firewall IPS, multiple security services, filtering, DLP, and CASB browser isolation. These are things that all users are going to be using. However, when an administrator or architect would start building this, I would definitely need to engage professional services to help clients do it.

Every customer is different. On average, it could be a two-week deployment. If you are using other devices, like Fortinet SD-WAN deployment, you definitely have to make sure your configured IPsecs are correct. You might have to review policies and your SD-WAN roles. You need to do a lot of cleaning up before you start deploying.

The solution is very straightforward and simple to set up.

Users just decide if they want to connect via desktop or remote VDI servers, and that's it. They decide on what ports and protocols they want to connect. Once that question is clear, then they just have to just create the connection between the cloud and between the enterprise. After that, it's all about the configuration once you are done on the portal.

The initial setup wasn't easy in our case, as we have thousands of users spread across different environments. Due to our extensive requirements, initial setup is never going to be easy.

Deploying Zscaler is quick and straightforward. You can easily onboard end-users to Zscaler Private Access once you deploy the application. There is a virtual application in your private data centers that detects the applications, and you can control access.

We have two or three engineer to deploy the solution. Two are usually needed  because there are different roles from a backup point of view, and we have a different set of people during the design stage. We need some people who understand identity solutions. We have a combination of two or three engineers who normally do deployment for around 1,500 users. One person is usually more than sufficient for maintenance because we don't get that many inquiries unless some changes are needed.

The initial setup of Zscaler Internet Access is very simple. The cloud configuration is very easy. The implementation took approximately three months due to Change process, however you can finish in 3 days if you are in small size industry.

The initial setup for Zscaler Internet Access is straightforward. On a scale of one to five, with one being the worst and five being the best, I'm rating my experience with its setup a four.

It's easy to set up. It took my network engineer about one week to prepare the environment, and our software network engineer is the person in charge of keeping it going.

The set up is very straightforward. It's a pretty easy process. The deployment scenario is pretty simple. You can just deploy it through a simple policy. You can deploy it even in terms of the distribution of hardware to users. 

To set it up took about three and a half weeks, from beginning to end. 

I'd rate the ease of deployment at a four or 4.5 out of five. 

After it is set up, there isn't really much maintenance. 

It is easy to set up. However, you need manpower and you need a team to deliver these kinds of things. It's not a plug-and-play thing. It has lots of configurations. We need to deploy the agents. We need to set up those configurations. If we have multiple offices, we need to understand the routing and what mechanisms are in place. That's why it takes a team.

The length of deployment depends on the company and environment. You're looking at the number of networks, the number of servers. 

I would rate the initial setup an eight out of ten, where one is difficult and ten is easy. The deployment process is quick, around 6 to 8 weeks. But that depends on the geographical locations we need to cover. If we only need to cover two to three locations, it's good enough.

There is a short learning curve on the setup, so it's not complex, but it's not necessarily trivial either. The entire deployment took two to three hours. 

We have about 1.5 persons who manage all of our internal IT apps.

The initial setup of Zscaler Internet Access is simple.

The initial setup was straightforward. The biggest thing for us was to build our own policies. The deployment itself was only a few hours.

It's a managed service. We are not exposed to the initial setup process.

The initial setup is very straightforward. They provide the cloud settings and then it's your responsibility to direct your traffic towards the Zscaler Cloud and they manage everything else for you. The infrastructure is managed by the vendor and themselves. We don't have to worry about any maintenance. 

The implementation process was pretty straightforward. We did not run into issues. 

We did have some issues in that there were professional services that were purchased already, however, we came to know very late that we had any professional services support available from the vendor. We ended up handling things ourselves. The professional services were okay, however, they just were able to help us at a high level with recommendations.

The initial setup was straightforward - Zscaler Internet Access is plug-and-play, and it's the simplest proxy solution I could recommend.

The initial setup was straightforward. It wasn't complex at all.

My understanding was that the deployment itself happened pretty quickly.

There was an announcement from our security, and by our CSO. Then it was rolled out and Pulse Secure was turned off. There was a migration phase in the project and that's it. It all happened rather fast.

It was very straightforward. Anyone with firewall familiarity will find it a simple process to download this solution.

The initial setup was straightforward. The solution is deployed on the cloud.

The initial setup is straightforward and the deployment took place over a couple of days.

It was probably in the middle in terms of complexity. Bits of it were easy, and bits of it were more complicated than we envisaged. I would rate it a three out of five in terms of the setup.

Its implementation probably took several weeks. It is deployed on-premises as well as on a public cloud.

From what I discussed with my colleagues from the network that we were working with, it wasn't a difficult process. I cannot tell you how long it took.

If you go for the MSS model, managed services model, then the initial setup is very straightforward. You register with the telco and the services are switched on. When you want to stop paying for that, you just turn the services off. That's how simple it is.

If you go for an on-prem model, there are going to be certain challenges surrounding how it needs to be deployed. It's dependant on the client. If the client is a cloud-native organization, it becomes easier. But if the client, SMB client or enterprise client, is not cloud-native, then it is a little expensive for them.

If all the prerequisites are met and the hardware requirements are met for an on-premises model, it takes about a week to deploy the solution. That would be for a small scale organization of about 300 users.

If it is an MSS, you can expect it to take one week. That's only if all the prerequisites are met. If the prerequisites are not ready, it can take up to three to four months. It also depends on the client and how they are looking to deploy it. If they want to go phase by phase or they want to do a full-time deployment, for example.

We bought Zscaler Web Security through our Internet Service Provider, so they handled most of the setup. So, from our part, it was quite straightforward.

The initial setup that I'm aware of was not very smooth. I would not blame the product. It was more of the global maturity of the organization we were implementing for. If the organization is not able to align their team, the deployment will be difficult. This deployment is ongoing. We started it four months ago.

After a proper implementation, the maintenance is very low.

The initial setup was okay but the problem is that afterward, you have to put in more time and money.