The initial setup for Forescout is complex if you don't know anything about it. It took a couple of weeks to set it up. We were a test base, so we had the vendors out here setting it up. They did all the training and everything with us. It took a couple of weeks.

Because of the way it is deployed, the initial setup was complex.

I would rate the initial setup a three out of five.

It took a long time to complete. It's a massive deployment, depending on the agency, it could take at least six months to get it up and running and collect the data we require. Some of it is still ongoing.

The time frame for the implementation can vary depending on what needs to be configured. It is important to have support from the vendor for the setup, it is not easy.

Forescout Platform is very complex to implement because it has a lot of features, and all of them need to be configured.

Initially, the implementation of the Forescout Platform took some time to figure out. The reason is we are a manufacturing unit and we have certain silos that are insulated areas where certain systems will not connect to the internet or to the LAN. Since there are many parts of it, we have to have an inclusive view of all those systems. It took a while for us to initially implement, but after a few months, everything worked well.

I rate the tool's ease of deployment a ten out of ten. It is easy to manage and implement. With the help of our partner, it took about one to two weeks at most to deploy this solution. This includes setting up the policies, implementing them, and ensuring the product is operational. Building the policies initially took around two to five days. However, refining and enhancing the policies took approximately three weeks in total.

We required a team of one senior engineer and one regular engineer to deploy this solution. The regular engineer was primarily responsible for implementing the Forescout Platform. In contrast, the senior engineer was involved in specific areas, such as integration and troubleshooting issues during deployment.

We currently only need one engineer for maintenance. The solution is mostly up and running, requiring minimal intervention. On average, the engineer spends about five minutes daily checking for issues or addressing complaints.

The initial setup was straightforward and not complex. The deployment process took six weeks. It's shorter than the typical six months for similar products.

The deployment process involves an initial assessment, checking the security policy against the required tasks, preparing the network for deployment, and then the deployment itself.

Deploying Forescout is complex and takes about four hours. You have to configure the devices before you can send packets. If you miss any of those devices, the application endpoint security will be compromised  In other solutions, you don't need to start the configuration before you can access the network advice. It pushes a policy based on the outcome of the process.  

Forescout Platform is very simple to deploy. We did the deployment within a few hours, and I gained visibility at the end of the day. I had visibility across my whole network.

An advantage of Forescout Platform is that it is easy to deploy.

The deployment process took around a week.

With regard to initial setup, it can take a bit to customize policies. Forescout requires in-depth knowledge to customize policies to monitor endpoint visibility.

It takes around one or two hours to deploy the software and have it up and running. This includes configuration and integration with the existing network. Customization takes a long time because some departments require more customization.

Our network is fairly complex. However, the setup of this application was straightforward. It has great documentation on what ports/protocols are needed when communicating with other devices. The documentation was easy to read.

The solution’s initial setup is very easy.

The initial setup was straightforward.

The initial setup is fairly complex and it would be a good idea to employ Forescout Professional services for this phase. Special attention needs to be paid to SPAN sessions or taps to allow Forescout to listen to the wire. 

The complexity of the initial setup depends on the environment. I am managing an enterprise environment, so any deployment or any implementation will not be easy. Generally, however, Forescout is not difficult to configure.

The initial setup is straightforward. We had to implement the solution in a short timeframe and we managed to do it in one month as a managed service.

Forescout Platform is easy to deploy. It's the fastest NAC solution that you can deploy in a large environment. There is the opportunity to improve as you go. It can be the first deployment, and you can improve as you go without any big disturbance to the environment. It's very flexible when it comes to implementing a certain security policy. You can have very complex security policies for the Forescout Platform. It makes the deployment much easier than others.

The solution is straightforward to set up. It is not complex at all. 

We're currently working with a third party that is auditing the implementation process. I also need some help from Forescout to validate how the implementation is currently done here.

The solution is very easy to set up. It's not overly complex or difficult.

I'd rate the solution a four out of five in terms of ease of setup.

The level of maintenance depends on the organization. If you are using more resources, you'll need more people. For an environment of maybe a thousand users, you can deploy one engineer. He can manage everything.

The initial setup was not complex. It was pretty easy. Installation maybe takes one or two days, and the implementation in total takes around two weeks.

We have a partner from Forescout in my country. He came to my company to meet with us. He helped explain a few things and assisted with network displays. 

There were about eight people that handled deployment between our end and the technical support side.

The initial setup is very simple. The logic behind policies makes it very straightforward. With that being said, policies can be very complex, and if you are not careful, they could have unintended results.

Device setup is straightforward - NAC itself is always a complex thing due to its profiling of EVERY device that connects to the network.

It was straightforward, although I recommend having a strong relationship with network-asset owners to ensure SNMP rights are looked after.

The initial setup of Forescout Platform is very easy because it is pre-configured. I would rate it a five of five for the ease of setup of this product.

Straightforward. Setup is simple with a solid, pre-defined set of policies that you build on and customize as you learn.

The initial setup is straightforward. Large infra may take few days to deploy.

The initial setup was very simple.

I think the initial setup was fairly straightforward although I was not involved on a technical level. We had the advantage that the technical engineers knew our networks and how to carry out the implementation and we also had some assistance from British Telecom. We initially focused on our main plant or main location, and then moved to our other locations, which are far smaller, and have a lower risk profile. That was our strategy and implementation took around nine months after the initial implementation which took about a week. At that point, we realized there were more devices than we thought and the process became more complicated. It took a while to get a handle on everything. There were just a couple of us involved in deployment. 

Setup was anything but straightforward, but this had nothing to do with Forescout. This is the nature of NAC solutions in general. 

Setup takes significant preplanning. Don't expect to just drop it in, then have it up and running, even if you already use an alternative NAC product. However, it is worth it.

We have completed significant deployments which are more than 4,000 endpoints. There was a complex network architecture.

All of the implementations have gone very well and the customers are satisfied.

My understanding is that it was complex simply because my mandate is to zero-in back to the user.

The initial setup is not complex at all. It's straightforward. It's pretty easy to manage.

The initial setup is a bit complex.

The initial setup was very straightforward, but due to our backbone switch/network configuration, we had to make last minute tweaks to get the product to see all our traffic. Also, we struggled to get our rules properly configured so that students weren’t negatively impacted by misconfigurations that would either prevent them from getting on the network at all, or repeatedly require them to log in.

Our third-party consulting firm (Konsultek), hit one out of the park in helping us, and they made sure we were up and running before the start of school, despite our tight timeframe for implementation.

It was pretty straightforward. I've been in a number of roll-outs and this one was pretty easy.

We have one CounterACT appliance that does our Chicago office. A second appliance, which does our other four branches who are a little bit smaller. We separated that work and then we also have somewhat of a redundancy. As far as the configuration and getting things up and running goes, it starts with a nice, very high-level baseline. Then you kind of incorporate the rules that you want to incorporate as you go along, which makes it nice.

The setup for this solution is very straightforward, but full deployment can take a number of years.

The initial setup is very, very simple. It's more complex to tune the product in the company environment and usually, that requires two days. I need a few days to tune the product correctly. I do also need to do a lot of tests during the initial implementation.

I joined the department when it was all setup already.

It's a little bit too complex. A little bit of simplification when it comes to deployment might actually be better.

With the assistance of the support engineer, it wasn't too bad. But it depends upon the state of your network. If everything is set up correctly, it will go much smoother. For example, having SNMPv3 activated everywhere is a requirement so that ForeScout can see everything.

The initial setup of the Forescout Platform is very straightforward when compared to Cisco.  Cisco ISE is very complex.

The time it takes for the deployment depends on the availability of the customer, and the team. If the customer can provide some information as soon as possible then the deployment can be done within 60 days for a large organization. This can be between 1,000 to 20,000 endpoints.

The initial setup was easy to integrate with the customer's environment. It doesn't have any downtime. I rate the setup process an eight out of ten.

The initial setup was not that straightforward and configuration took a long time and required technical specialists. When assisting customers, we need to have a technical specialist onsite to deploy the solution. 

The initial setup is easy, taking no more than two or three weeks.

The initial setup is pretty straightforward. The length of time required for deployment depends on the number of use cases that we want to implement. For example, integration with different products will take longer to deploy than a simple REST API access or integration with Active Directory.

I would say that on average, it might take between two weeks and one month to deploy.

The initial setup was straightforward. We have help from the manufacturer, so to put it in place it was straightforward. We have been using it for two years now with no issues.

Initial setup is very straightforward because there are only a few network configurations needed to be done. It does not require any downtime and could be deployed at any time during production hour. There are a few endpoint configurations that need to be done, which users can do so through their Microsoft ActiveDirectory or desktop management tools or software.

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

It took us about one week to deploy the solution. It didn't take long to set everything up.

The solution is not that simple, however, it's not complex, either. It's a solution that does so much it needs a bit of understanding to properly use it. Once team members go for basic training, they should be able to handle it. The basic training will also give team members a networking background to be able to master the solution. It's not very difficult, but a person will have to be a bit technical.

It was not so easy to deploy in our environment, the learning curve for this solution is quite hard.

The initial setup was straightforward, as the steps were simple to understand. It only got complex when creating policies that are not simple.

The amount of time it takes for deployment depends on how many branches you have, whether it's a central deployment or a hybrid. It depends on how you want to use the solution. It varies but if it is only central deployment for a couple of branches, we can do it in a minimum of one month.

The number of people it takes for deployment just depends. One engineer can do it, but you also need support from the customer. You should have very good system administrators, or some network engineers to support you in terms of various authentication integrations. There should be a minimum of one from the deployment side, two from the customer side.

The initial setup of Forescout Device and Visibility Control Platform is fairly complex.

The initial setup was very easy, very simple to deploy. We didn't have problems or difficulties with the implementation.

The initial setup was complex, but that was due to the nature of the network architecture.

The initial setup was complex.

It's straightforward to set up.

Initial setup was straightforward. All it required was to integrate traffic sniffing/monitoring and management ports into our core switch, and instruct the core switch to mirror every traffic to the device through the sniffing port. The rest was simply to define all our network segments on the device and integrate all access switches via SNMP.