There's a name from the past that I'd intentionally forgotten. Whenever I used to go to customer sites to install VCS, one of the first things I did was ask "you don't have any CM tools like eTrust loaded on these machines, do you." The eTrust (and similar) utilities were a bane for many products' installation. Weird part was, customers running these tools never thought about their presence when having vendors come in to install products - even if they've been burned by it, before.

First time I ran into eTrust was on a large-scale, multi-system/multi-vendor installation. I'd lost a day to eTrust (an hour to identify it as the culprit, the rest of the day to get the expedited exceptions to be allowed to turn it off) and went about my way. Two days later, another vendor's consultant, working on a separate set of systems for his application-set, was exasperatedly telling me about the mysterious problems he'd been having all week. Other vendors' consultants chimed in, similarly. I'd said, "sounds like my eTrust issues" - which it turned out to be for them, after they got out of lunch and investigated my suggestion. 

In total, I think eTrust cost the customer over a dozen man-days of consulting time. Because of the delays for the other consultants, the customer had to buy an additional week of the other consultants' time. Use of eTrust ended up costing the customer at least $100K in extra consulting hours. If the system owners would have either turned it off before we all arrived or even just after the first problem, they could have saved themselves a lot of consulting money. 

Lesson: site-prep is key and, if you're a site owner and want to save money, make sure you understand the impacts your security tools might have when people are brought in to do installations. I see similar problems caused by use of SELinux in environments hosting non SELinux-aware apps (which is the vast majority of non-RedHat apps).