(This is the last article in a five-part series.)

Some organizations find that the hardest aspects of introducing virtualization aren’t technology issues. They’re people issues.

For example, many business executives have trouble understanding what virtualization is and how it works. As a result, they often balk at funding virtualization initiatives, or object to entrusting critical line-of-business applications to a virtual server. “Every organization we face has some level of resistance from people who don’t yet understand how virtualization works, and therefore need to be educated to see the benefits,” says Casey Crellin, president of Virtual Technologies LLC, a virtualization integrator in Denver. Crellin uses customer success stories, concrete ROI studies, and small-scale proof-of-concept deployments to counter such executive anxieties.

You may need to use similar tactics with your company’s internal application developers too. Development teams often resist porting their systems onto virtual servers. “It’s another set of things that can go wrong,” explains Bob Gill, managing director of server research for analyst firm TheInfoPro Inc. of New York, N.Y. Gill advises virtualizing a small number of less critical applications initially, to offer developers tangible proof that their systems will continue to perform properly on virtual hardware.