The solution's setup is easy and deployment took one hour to complete. 

The initial setup is straightforward; it consists of a three-tier architecture with one console, which can be installed anywhere other than the application server, an application server, and a database. These three components are necessary.

The setup was straightforward, but it depended upon the initial setup tool. Once we get the essential details from the customer, we deploy the setup for the two types of automation. It takes two days to complete the process. 

I wasn't involved with the backend build but carried out deployments for some of the repeaters. It's pretty straightforward, but you have to be careful with your license keys for Red Hat and make sure your systems can talk and you have the licensing to do the Microsoft patching. It sometimes seems like the documentation is a little inadequate. We've actually had to put in several calls to BMC to have them make improvements in the processes.

The architecture is big, so the initial setup is not a straightforward task. However, we don't find it very difficult. But in terms of configuration, the minimum hardware requirements are quite high. As there are a lot of additional tools like Grafana or YellowFence, which are integrated, it becomes a heavy tool.

Setting up Server Automation is straightforward. It's a three-tier architecture with one console you can install anywhere except the application server. The other two components are the application server and database. 

The initial setup was fairly standard. 

I've done a lot of installs of the software. There are certain strategies that we developed in the post-sales consulting we did - as opposed to pre-sales - for how we would set up environments. We did that because it made it easier for support to support the product because they knew that we had a consistent methodology for how we built out the environment. We followed the standard playbook that we had in consulting. We based the size of the environment on the number of servers and estimated job counts, to be able to hit the thresholds. 

It's been a while since I've been there. I've been with this company for eight years now, but at the time we had a really good setup, playbooks for how we did the initial installations.

When you are installing any sort of new tool or application into the enterprise, not all enterprises are the same. We did have a few teething issues when we first stood it up, but that was fine. We got around those teething issues. The platform is there today working. We haven't really had any problems with the application. It has been running happily.

When we had our requirements integrate into a different scanning tool, we found that it isn't plug and play. There is bespoke development that needs to happen to be able to integrate it with those tools. This is something I would like them to improve.

The initial setup is straightforward, unless you need most of the custom configurations.

The initial setup for this solution is straightforward.

We are just starting to deploy the product. Right now we're sampling about fifty systems to do automation, such as updating and rebooting systems.

The setup is not too complex compared to SCCM. 

I came to the project without any knowledge of BMC BladeLogic. We started going through the documents from the BMC BladeLogic KB articles and then we started working on the BMC tools. That was it. We didn't have any training on BMC BladeLogic.

The initial setup process is easy. The deployment time depends on specific project requirements.

The initial setup was very complex; Not straightforward at all.

The initial setup of this solution is complex, but it was specific for me and my company. When it came to deploying the endpoint, it needed a long time to get it together. For me, it was complex.