I recently visited my nephews who had just got their new bicycles. Their new cycles did have a bit of assembling to be done before they could ride it. While elder one seemed keen and very happy to go over the manual and look for the instructions on how to put together, the younger one just wanted to take it for a race with his friend. He was upset that he had to fit the seat and hoped being the favorite at home, could get his dad to take care of it. Occasionally he would look at his brother, who seemed to be happy with putting it together just the way he liked it.

His dad on the other hand wanted this son to give it a shot and offered to only provide guidance. After a round of father-son “conversations”, he decided to give a shot. In a hurry to put it together he ended up overlooking some instructions and did not assembly them correctly. Upset at not being able to put it together, he decided to go back to his old cycle which at least allowed him to cycle. His friend who stopped by to see his new cycle, decided to help him out and soon they were off to race around the block. I spotted him outside the block and enquired “How is the new cycle”? he replied “It’s faster and lighter than my earlier one”. He didn’t care much about how the seat was fitted as long as it was comfortable for him to ride on it.


This got me thinking, my interactions with our customers would invariably lead to the following conclusions

  • Users, who inherited BladeLogic as a result of a transition ornew to the product, would often face difficulties in understanding what to do with it. They would eventually use BladeLogic for a small set of use cases that they could get to work or were already setup for them. Most users were instead running their tasks (semi) manually without realizing BladeLogic which was already in their environment could automate and alleviate their tasks.
  • Users, who had received help in setting up and using BladeLogic either via communities, service engagements or had a friendly sales consultant, were discovering the power of the product. They were figuring out more and more use cases that they could automate using BladeLogic.
  • Most customers were keen to adopt newer versions and explore new features if it was simple to do so.

For my nephew, it really didn’t matter how the seat was fitted as long as he could ride comfortably. Similarly if we could provide BladeLogic for users to easily plug it in their environment without having to seek assistance. Once it was up and running, they had  out-of-box utilities, packages, templates readily available for them to reference, it would transform the experience in leveraging BladeLogic for their use cases.


This week we are making available BladeLogic Rapid Deployment Stack (RDS) against v8.3 SP3. BladeLogic RDS is a virtual appliance with Bladelogic application server and its components preinstalled. It has options for the choice of database

  • Oracle XE is pre-bundled for those who like to quickly get started without having to configure a separate database.
  • Database dumps for Oracle & SqlServer for those who like to externally configure a database.


BSA RDS Review.jpg


BladeLogic RDS also contains

  • A home page that has utilities to administer the system, along with the UI client installers and agent bundles. It has references to product guides, best practices and community content for quick assistance.
  • Blade Zipkits that contain system packages for provisioning, operation utilities for configuration changes and server compliance packages for Windows and Linux
  • Latest regulatory compliance templates for CIS, SOX, PCI, DISA and HIPAA
  • Agent bundles and installers jobs for simplifying the process of server enrollment.
  • A quick start guide


BladeLogic RDS is available for download from BMC EPD download site.



We intend to have a 8.5 version available shortly that will also include BladeLogic Portal. Watch out for this space on updates around future versions.