The initial setup is not complex at all. It's very straightforward.

I would rate my experience with the initial setup a seven out of ten, where one is difficult and ten is easy to set up. It's not straightforward.

The initial setup is easy and takes an hour.

It is very easy. It is simple to understand. Even though I had requested training for BigFix, I would have been able to work with it without training.

The initial setup of BigFix is a seven out of ten because BixFix is not easy. BigFix is easy for the customer to use, but it is obviously going to be the details the customer provides. 

The deployment might take approximately one to two months. But if the customer's network is bad, and they haven't done patching for many years, then it might extend well up to three to five months.

The deployment factors are going to be on three aspects. One is, how we work. What the customer's expectation is, then we have BigFix architecture, aligning it with the customer's expectation, and then deploy the central servers, put the relay servers, install agents, and start applying patches.

For deployment, we require a minimum of one to two people, and the maximum depends on the scalability of the business.

The initial setup was not overly complex. The complexity was the handling of configurations. 

The implementation was fairly straightforward. Documentation was online, so you just have to read it and follow instructions. It's pretty straightforward.

The deployment strategy more or less depends on our current environment for the company. It took me a while, not due to BigFix, just due to the company restrictions for onboarding employees. You have to have permission to access this and that. So it took a little longer than it would if it was on a local system, my private system, or something like that. 

Currently, we have two teams that can handle deployment and maintenance. There are those on the Window side, for managing the Windows servers, and there's the Linux OS applications team. They both pretty much do the same thing for two different operating systems.

When it comes to the root server, you have the option to use either Windows or Linux. Deploying the root server is a straightforward process. Deploying the root server is the first step. After that, if you're considering deploying the complete infrastructure, you'll need to follow the capacity planning guidelines. It will help determine the appropriate infrastructure requirements. For instance, if you have 10,000 devices, it is recommended to use a server with at least 128 GB of RAM, 32-core processors, and a robust server configuration. You can choose to host it in a cloud-based environment or a dedicated environment, but it should meet the necessary specifications in terms of RAM and processor capacity.

Once you have the server set up, you will define your release strategy. This involves setting up top-level releases and renewal releases. The reason for having multiple releases is to distribute the load and avoid overburdening the root server. Top-level releases communicate with the root server and receive data from it, which they then distribute to the lower-level releases. These releases, in turn, distribute the data to the endpoints.

As for the installation process, it is quite straightforward. Once the root server is installed, you need to install the console. Once the console is installed, you can proceed to deploy clients or agents on the endpoints. 

BigFix provides a built-in client deployment tool called the Data Tool. Using this tool, you can leverage your active directory credentials to scan and analyze your network, identifying devices that have or do not have BigFix installed. Once the scanning process begins, the tool will start deploying the agents to the appropriate endpoints. The installation of the agents does not require a reboot. However, when deploying the infrastructure itself, a reboot may be necessary. But for clients deployed on agents or endpoints, whether it's servers, Windows 10 machines, or Linux machines, the agent installation does not require a reboot. 

Once the agents are installed, they automatically refresh themselves every 15 minutes. They communicate with the nearest relay to check if any new content needs to be deployed to that particular endpoint. The agent keeps checking with the relay and deploys content if there is any to be received.

The deployment process of BigFix was straightforward. You need to have a small number of programming skills or scripting skills to complete it. If you have skills, it is very easy to deploy. For somebody who's experienced, and has knowledge of some programming or scripting skills, it's very easy.

The initial setup of BigFix was easy because we started from scratch, we didn't have a CCM before. The deployment of BigFix is a powerful feature, it is simple to do.

The deployment of BigFix is complicated. There are a lot of firewall ports that need to be configured and with a company with 50,000 employees, this can be a challenge. The configuration could improve by being more streamlined in the future.

We were assigned a project manager from the BigFix team who provided us with a comprehensive list of requirements for establishing effective communication. However, implementing these requirements across multiple countries and coordinating with various network teams posed a challenge, particularly in terms of opening the necessary communication channels through firewalls. This was a daunting task, especially if the application utilizes codes that are commonly blocked by firewalls.

The full deployment of the solution took three months.

I rate the implementation difficulty of BigFix a five out of five.

If you choose, for example, Microsoft SSM Configuration Manager, you need a lot of servers, databases, and the configuration of firewalls, et cetera. It's a tremendous cost before you get up and running. With BigFix, in 10 to 15 minutes, you're up and running. Everything is working well.

The initial setup was easy. 

Yet, there are many other criteria which must be taken into account because there is a need for the distributed network. As such, it is important to understand the bandwidth that it will consume when it comes to pushing the latest updates. This means that the solution must be designed in such a way that the implementation would not choke the bandwidth or consume much of it or other activities, as the appliances it contains would also be consuming the same bandwidth. 

We are not talking about putting a separate network or network connectivity for pushing the patches. We usually use the same connectivity. We see that the designing stage is of critical importance and, if done correctly, the implementation will follow more easily. 

It was straightforward, but it took some time for us to settle down and get started. There were a lot of things to learn online. The deployment took about two to three months.

The initial setup is very easy. 

I did not set up the system. It was set up when I got the task to take care of this product. It was already installed.

The product itself doesn't require a lot of maintenance. Of course, the server and client updates would be good as the tool has clients. The clients install them on all machines. However, the topic itself needs a lot of maintenance. If you want the data in BigFix to be up to date in case of an audit, you have to take care of the insights of BigFix. BigFix itself is running. However, the list of the servers needs to be correct, et cetera.

The initial setup is straightforward. It involves sizing and designing the architecture to put BigFix in place and set up the proper relays. We experienced no issues doing this.

To begin the setup, we tried to identify the baseline of the customer to see how many endpoints the customer has. We also looked at the locations to know if we do need to put a low-level or top-level relay in place in each one of the data centers. In our case, as it's a huge environment, we set up two top-level relays and then a low-level relay in a different data center to not put a high load into network bandwidth when we try to transfer patches over the network.

It is pretty easy to implement.

The documentation is good. Follow the recommended configuration by HCL and you will be up and running very soon. It's pretty easy to set up with some knowledge. Be aware that DNS-isssues can be a challenge if the server is not visible at Internet by a public IP during the initial setup. The configuration at firewall can a challenge especially to get SQL-server vissible for the BigFix-server.

The solution's initial setup is simple and not complex. I have done the full server installation and configuration thrice, and it's not complex.

I helped with the installation process for two customers. The installation was reasonably swift; however, the actual consideration and moving the patching products across into BigFix that can take a long time. The configuration took six to 12 months. 

A massive gain for BigFix would be if it was able to go and interrogate products like SCCM and import the patching sequences and groups, it would make it much easier. 

I'd rate the initial setup process seven out of ten. It does take quite a long time to bring everything across from other products. 

The setup is easy. I would rate it as five out of five.

It requires maintenance every month. Only two or three people are needed for maintenance.

The initial setup was very straightforward. It's simple infrastructure to set up in comparison to other tools, like BladeLogic or SCCM, very simple infrastructure to set up.

I was not involved in the initial setup. A coworker of mine actually set it up and got it going, and I came in on the back end. Right now, I'm actually going to be taking that over.

The setup was straightforward. I don't think it was too complex. I know that we have some complexities with the way some things are set up in our environment, but the product itself is pretty straightforward.

It is very important to use the solution effectively. In most installations, we deploy without configuring all the features and implementing them, so we do not gain much from it. Therefore, I think some automation processes can be adjusted to prevent the zero-rate thread.

The deployment phase was somewhat complex due to the need to open many firewalls within the network. Considering the large scale of the company, with fifty thousand employees around the world, I believe that in my previous job, we could have improved communication by reducing the number of ports required for the servers to communicate within the network.

We had a project manager assigned from the BigFix team who listed out all the requirements for effective communication to be established. However, the challenge of implementing BigFix in multiple countries and coordinating with multiple network teams in order to open the required communication between the firewalls was a seemingly hopeless task. If the application uses specific codes that are common in nature, typically those ports are already allowed in the network.

The deployment took us three months.

The installation is straightforward.

We rebuilt it three years ago from the ground up and the setup wasn't complex.

I wasn't involved in the installation process.

Our initial setup was very complex because we not only have it set up for our internal use, but we also have a managed service platform in which we service multiple clients. We have a cloud-based solution with it as well. We're called in for a lot of the crazy deployments that are out there in the customer world where they have massive amounts of endpoints and really complex network systems.

The initial setup was complex. There are a lot of steps to set it up, at least on the Linux side.

We had one of our clients with over 30,000 endpoints, and within two days all of those 30,000 endpoints were installed and reporting back, and they were ready to patch. Installation is fairly simple.

The setup could be simple or it could be complex. It depends on your environment.

I was involved in the initial setup. It was very straightforward. The implementation was pretty easy.

The initial setup is very straight forward. Depending on the customer, it can be complex as far as doing the necessary planning. Some customers can miss the point of doing a lot of that planning up front. If done right, it's not complex at all. You get really fast ROI from the tool.

The initial setup was straightforward. Installation was easy and a basic configuration is enough to start to work locally in the same network. But it is more complex when you need to deploy it worldwide.

I was not involved in the initial installation.

The initial setup was straightforward. 

Its initial setup is straightforward.

I self-taught for this online, so the initial setup was a little difficult to pick up at first. I had to create a couple of testing environments and destroy them in order to learn how to use it. There was a lot of trial and error, a lot of reading of the manuals. 

The initial setup was pretty straightforward, but that was 2006, 2007. A lot has changed. It would be a little bit more intense right now.

The initial setup was straightforward on the BigFix side. We had some internal stuff that caused some issues but otherwise it's pretty straightforward. 

IBM BigFix is one of the easiest client management tools to install. Once the operating system and database are installed and configured, installing the IBM BigFix server takes about 30 minutes to complete. After that, enabling content (Windows, AIX, etc., patching) takes a couple minutes. Once this is ready, deploying the agents can be done with a client deployment tool provided by IBM. This tool is capable of deploying to Windows and non-Windows systems. To deploy to one system will take about two minutes, but the tool is capable of parallel deployment, so deploying to 20 systems would take about five minutes. We were able to deploy about 400 Windows agents in a morning.

The first setup was complex. The second time was much simpler, when we knew what we were doing.

The first setup was kind of wedged in and we had a very small time frame. It was a brand new tool that we didn't know much about. We also didn't know that we had engagement support available to us. That is why the second setup went smoother.

The initial setup is straightforward. 

From our perspective, it's pretty easy engagement. It's not just for our network, we use this for our engagements with our clients so the complexity is typically not introduced by BigFix but by the customer client networks and their specific requirements.

The initial set up was very simple, single server. We've since grown to a server plus an array of relays and we even use relays to get into some difficult to reach network areas. It's been pretty useful.

The setup is pretty straightforward provided you have planned well for the deployment. Know the environment well prior to deployment: The architecture needs to be drawn up prior to deployment. Plan the deployment of main server, database server, BigFix application(s), relays, console, and finally the deployment of clients.

Once you've done the setup once, it's not that complex. Initially, it can be a little bit complex to get your head around, but now that I've done it a couple of times, I don't deem it to be overly complex.

I was not involved in the initial setup.

The setup is very easy. I usually have to tell them how hard it is, but then I can do it within a day. So, this is also a very big feature.

Regarding installation, I needed help from either support or our actual business partner or vendor. As I was just an operator previously, I never had to set it up from scratch. Actually it was pretty easy. Of course I had help, I had support, but it was nothing that was too difficult to do. Everything went seamlessly, went smoothly, and like I say we have been thoroughly enjoying it for the time we've had it.

The initial setup was not complex.

The initial setup was was complex because it was new. The help that they gave us and the documents that they gave us were really straightforward. The first time I set it up there was a learning curve, but the second time it was real easy.

For us, initial setup wasn't complex because we are a fully owned subsidiary of a company that already had it all built out. Basically, they just added us in. For us, it was super straightforward, just like a simple click.

I wasn't involved in the initial setup for this company.

The setup was very complex. It was very bumpy and we had network issues. But, they worked with us and we are happy now.

I did the initial setup, it's fairly straightforward.

I was not actually involved in the initial setup because we've had it for over ten years, but I've helped transform it from being a tool into a platform. The technical part of that transformation was not very complex. It was more of the internal challenges, getting support, and more the political side was a little more difficult than the technical side.

Initial setup is very simple. With the Web User Interface, it makes the learning curve very short.

I was not involved in the initial setup.

The initial setup was very straight forward and very easy to set up.

The setup is pretty straightforward, if you have a good knowledge about the geographical spread of your clients, so the relays are appropriately mapped.

The implementation is really straightforward and it's easy to implement with the environment.

I did not do the initial setup.

The initial setup is straight forward. I deployed it in around three weeks. I started with installing the servers and the primary relay, then I installed 2 relays per subnet,  made the relays deployment points and then installed the BigFix clients locally from the deployment points.

The initial setup is straightforward and took us a day to implement.

I did not find anything difficult in the implementation process.

We have complex requirements.

The initial setup depends on the network infrastructure. Sometimes it will be very easy to implement, and sometimes it may become complex. I did the entire solution implementation in four hours but I took almost four months with another implementation because of the complexity. Sometimes it's straightforward, sometimes it's complex.