The setup is simple. 

We had a complex initial setup. It wasn't that simple to execute. We do have help with deployment, however. We have a deputy to help us to deploy but Palo Alto also supports us as well.

The deployment itself was quick. In two months we were up and running.

We only have two people on our end looking at maintenance. The company that handled deployment had four people and also Palo Alto has some specialists and engineers. They had two guys, the implementer had four and we had two more - we were eight people in total.

In the beginning, the solution was hosted in a data center that was not owned by us but by Verizon. However, when we migrated to SD-WAN, it became cloud-based.

The infrastructure was managed by Verizon towards the end. Therefore, any issues or problems, as well as room modifications, were raised by us through a ticket, and they took care of everything related to the infrastructure. So, it wasn't something we had to deal with directly.

The solution is very easy to set up. I've been working for many years on this. I know the whole process is easy to start with some simple logarithmic management It's easy to manage. 

The deployment is fast. It usually takes about a day. On the first day, you get the management running on the UI. On the second day you need to get the traffic going through the certificate, and to do some proper security policies. That's all. Yes. To do it in one day is just a one-man job.

I manage the solution myself and maintain it every two months or so. Of course, if there are any issues in between these maintenance events, I also work on them.

The setup itself is very simple and straightforward. It's not overly complex. 

In terms of maintenance, in terms of security, we do require additional resources. Once the security infrastructure is compromised, it'll need a business outage. So we require additional resources in the firewall technology.

The setup of Palo Alto Networks Panorama is moderately complex. In my experience, the deployment of Palo Alto Networks Panorama involves considering accessibility, and if it's on-premises, it may face challenges like procurement delays. The cloud version tends to be smoother and more straightforward for deployment.

The initial installation of Palo Alto Networks Panorama is straightforward and the process takes a couple of hours.

I've been using it for two years, but I didn't actually deploy those instances at Panorama. When we recently moved to Azure, I actually deployed it in Azure, and I had no issues. So, I was a complete rookie in terms of deploying it because I'd never done it before. I did that with minimal assistance from Palo Alto or anybody. So, I would say it is easy to deploy in the cloud.

In terms of updates, PAN-OS releases come every month, six weeks, or so. You have to be running a higher or equal level of Panorama to the firewalls that you're managing. If you're keeping your firewall environments up to date, you also have to keep your Panorama up to date, and with that comes new features. You have to plan for firewall updates more than Panorama, which is just managing other environments. You can pretty much update Panorama whenever you want. There is no customer or firewall outage when you update Panorama. It is just the reboot time. You just download it, install it, and reboot it, and you're done. It takes less than 20 minutes.

The initial setup can be complex. As I mentioned before, making modifications is very difficult. Before implementing, you need to plan carefully.

Our engineer made some mistakes when he was setting it up; we still experience some complications due to that as everything is already in place and we can't change it. 

The initial setup of Palo Alto Networks Panorama took a long time to complete because there was not a lot of documentation.

It was pretty easy to set up. I did not find the implementation complex. I'd rate the ease of deployment nine out of ten. 

The setup process is simple and straightforward. 

Our technical team did the setup for us.

The initial setup of Palo Alto Networks Panorama is of a medium level of difficulty.

The initial setup for Palo Alto Networks Panorama was straightforward. I didn't see any complexity. It was a normal firewall configuration. I haven't done any new deployment of Palo Alto Networks Panorama, but in the cloud environment, it didn't take much time for me, and you can complete a setup within one to two hours.

The initial setup is very simple and quite straightforward. It was not overly complex. It's been two years now since I implemented the solution, and therefore I cannot recall exactly how long the deployment took. While the process was smooth, we did face some integration issues, for example, integrating the active standard Palo Alto to Panorama.

Installing Palo Alto Networks Panorama is easy, and connecting firewalls is a straightforward process. Deployment typically requires just one person, usually the firewall administrator. Maintenance is also easy, especially for those familiar with managing individual firewalls, and Panorama serves additional functions like log collection and setting up SD-WAN functionality, making it highly useful for networks with multiple firewalls.

Setup isn't simple, but it's easy to migrate from another vendor.

Right now, we use 40 employees to manage the solution.

The initial setup of this solution is very easy. The length of time for deployment depends on how many policies you have, but the basic configuration should not take more than one hour.

For policy tuning, you need to review and tune the devices. Palo Alto has several tools to help with migration from the legacy approach of port-based policies to application-based policies.

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

We sometimes have difficulty with the deployment configuration.

The initial setup takes around one week and is complex. All other firewall configurations are easier than Check Point. If you face any configuration issue, the only solution is to contact the Check Point team. Deployment generally requires an engineer. 

I did not handle the initial setup process. I can't speak to how it went. 

It was quite straightforward. In terms of technology, it was okay. As our environment is quite complicated, we had to deal with several phases of the implementation because we don't have only one appliance installed. We have implemented four Palo Altos. That's why it took some time, but it was just because of the complexity of our environment, not because of the solution itself. The whole project took one year.

We did some POCs to understand this solution. We had a lot of discussions in terms of the best way to implement this solution in our environment. It took the effort that this kind of solution normally takes.

The initial setup is kind of easy. I think it takes about half a day to set it up properly. 

The installation was straightforward in a complex environment. That means that we could have had far more issues were the product not well-designed from an installation standpoint. We are a big organization. Deployment can be a matter of weeks or it could be a matter of months depending on what jurisdiction the installation happens to be in.  

The initial setup of Palo Alto Networks Panorama is easy and takes approximately one day.

It is not so straightforward, but it is also not complex. It is acceptable.

The initial setup isn't too complex. It's pretty straightforward.

The production instances take about an hour or so. Deployment is fast.

We have ten admins that make sure the solution is working properly at any given time.

The initial setup of Palo Alto Networks Panorama is simple.

Configuring firewall rules is generally straightforward and user-friendly. Certain advanced tasks, such as setting up local collectors and changing log types or indexing can be challenging for end-users. In such cases, assistance from partner companies or Palo Alto Support may be required.

The initial setup for Palo Alto Networks Panorama could be pretty easy if you've had some training. It's not like you can go and do it and find it easy without a guide or training. Before implementing the product, you'll need at least one to two weeks of training because it'll be complicated to go hands-on without some Palo Alto Networks Panorama training.

The setup is generally straightforward. Deployment times vary, according to the client's environment and if they have multiple branches, etc. It can take anywhere from one to three days. After that, you have to fine-tune a few items, and that can take another two or three weeks. So the entire deployment process, depending on the organization, can take anywhere from three days to three weeks. Maintenence only takes one person, once again, depending on the setup of the company itself.

Another division handled the initial setup, but they said the deployment should be easy as it doesn't require complex tasks. It's simple to open the software and configure the tool.

The initial setup for Palo Alto Networks Panorama is not complex.

Initial setup is very easy. After working with a few new installations we were able to put together a script to apply the new firewalls to setup the management access, Panorama location, high availability (HA) configuration and the initial IP stack. This makes it easy to start the OS updates and initial rules from Panorama. By having the HA setup scripted, it also makes the OS updates a single download instead of a download for each device. The HA connection allows the firewalls to copy the OS over to the other firewall with the single download. That is important because there are several large downloads necessary to update the OS to the current OS levels.

I found the initial setup for Palo Alto Networks Panorama easy.

It's really straightforward to implement. It's not something where you need some special engineer. Palo Alto has a really great document portal, docs portal, where you can find all the needed information to deploy this. That said, it is really straightforward for any administrator who deployed something before. You just click next, next, next, you just then need to change a key, and that's all.

I wasn't involved in the installation because, as I previously stated, I just started working for my current organization. 

I wasn't directly involved in the transition, but it went smoothly.

I did not install Panorama from scratch. Palo Alto Gateway is quite easy to deploy and has a decent setup.

In terms of maintenance, it doesn't require too much effort. We usually check the best practices from their website. We update the Panorama server according to the best practices and the compatibility with the gateway.

My IT team handled the setup and it was very easy because they have the needed skills. We use three people for deployment and maintenance: one engineer and two technicians. 

The initial setup is easy. It is not that complex. There are articles and documentation, readily available on the Palo Alto website, the Palo Alto Portal, which can help you figure out how to configure the device.

Our deployment strategy for any new customer is to directly implement it in a testing phase. In a testing phase, we try to see if all the requirements that the customer wants to see if we will be facing any challenges. We want to initially try and replicate that in a lab scenario. That way, if there are any issues, we can get back to the team at Palo Alto and ask them questions. If it works, then the customer goes into production.

We don't have any dedicated person for maintaining anything. The antivirus, everything, can be directly, automatically updated on the firewall. That is not an issue. On top of that, if a particular device is getting into trouble then we get the NMS alerts for that device. In such scenarios, once we have a device failure at a particular site, we can have that device replaced. We can open a case with the vendor and once we give them a particular serial number or the VM instance, we can initiate an RML to replace that device with a new device. It takes a couple of days for that to happen.

In the initial setup in our case, we are using the single setup firewall with panorama. the usual templates, stacks, and devices group is works good with multiple firewalls. But with single firewall setup This whole process has become very complicated and very confusing. There should be some provision for a single setup firewall to avoid the template stacks and templates. 

It wasn't easy, but it also wasn't very difficult. I would say it was medium. The deployment took around three months.

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

The deployment is easy and uncomplicated. It takes about an hour or so, if not less than an hour. It's pretty quick.

However, we have 800 or more devices. It takes about six months to deploy everything, especially if I have to do everything manually.

We have eight to ten people who manage deployment and maintenance.

The initial setup isn't very complex, it's user-friendly. The deployment time depends on your capacity planning - how many firewalls will be managed and how many logs or discs you require.

I cannot comment on the initial setup, as I was not involved with it. 

The initial setup was not handled by myself. It was handled by a colleague. However, I do not recall them struggling with the implementation. The setup seemed to be quite straightforward. It's not overly complex, from what I witnessed.

The initial setup is easy and takes less than three hours. The setup time does depend on migration activity and how much configuration needs to be done, as that takes additional time. 

The initial setup is straightforward and it took a couple of weeks to deploy.

The initial setup was straightforward because we used a consultant of the company to do the installment. They did a good job with it.

My implementation strategy was to install Palo Alto Networks Panorama first, and then implement and integrate it with all my other files. It took us about two weeks to deploy the program.

It was very straightforward and very simple. I helped them roll it out and watch them spin it up. I didn't do anything configuration-wise, but I think it took us 10 minutes. It was that fast.

It is pretty straightforward. It is not very complex.

It was straightforward. The gateway integration with Panorama was also a pretty straightforward configuration for us. 

We deployed it site-wise. For each HAPS, it took us around two hours to take an existing production gateway behind Panorama.

The initial setup is straightforward.

The product's deployment was simple. 

The setup for Palo Alto Networks Panorama is quite difficult, because you're essentially building this one machine, then you have to create all the log ins, then once you've done that, you start registering your files, but you have to do an ingestion on them. You have to bring the file all in, and then it takes the config then puts the config back out again, but that config will then be a "protected config", so if I was logging onto that machine locally, I can't change that file.

The setup is quite easy just to build the machine, but to get it to work is quite difficult.

It's easy to install, but the configuration is not simple as the installation. Nevertheless, the deployment should take less than ten minutes.

The initial setup was very easy and deployment took about four hours.

The initial setup of Palo Alto Networks Panorama is simple. The implementation is done in stages. The first stage, takes approximately three to four hours.

The initial setup of Palo Alto Networks Panorama was simple. The time of the implementation depends on the environment.

Its initial setup is very simple.

The initial setup was not complex. It was actually quite straightforward.

The installation process was very easy, however, installation times can vary quite a bit. For us, it took roughly a month and a half. 

The initial setup is straightforward. It's not complex at all. Deployment was only two to three hours in total. For implementation, we only needed three people, including someone from Security and someone from the Network team.

We had some challenges with the initial setup, but it was more on a learning curve basis. The support and team for the setup have been pretty seamless with minor tweaks here and there.

I was not involved with the setup.

The initial setup is a bit complex and requires expertise. Configuring a firewall is a bit easier than configuring multiple firewalls at a time through Panorama. To create device groups and templates, and to manage everything is a bit difficult the first time.

The initial setup is easy, but I have done it like a thousand times before with a bunch of other products. The product is not much different than anything else.

The initial setup is somewhat straightforward, you most likely will need assistants.

The installation process took several steps. First of all, we needed to do all the media files. I basically just downloaded the media files from the folder. Then we deployed into the VM. We added a management tool in Palo Alto. After that, we needed to ensure that the Palo Alto and Panorama were using the correct serial number, and we needed to set up a template to get a US2. We then purchased a warranty and listed the policies from the Panorama to Palo Alto. 

I'm not quite sure how long the full deployment took.

The installation and setup are very straightforward.  

We hired a consultant for the initial setup. None of our staff are firewall engineers. We're more like firewall administrators and our environment is quite complex. 

Its initial setup is straightforward. If you have a basic knowledge of Palo Alto Networks, you will be able to spin it up.

The initial setup was straightforward.

The installation of Palo Alto Networks Panorama is straightforward.

The deployment time is based on the client's input. The deployment can take one day, and two days for testing.

We have more than 20 engineers to maintain more than 50 locations.

With respect to deployment, they have both the virtualized product as well as the offline version. The initial configuration might take two to three hours, with an additional hour for configuration. I would budget four hours in total.