Whether in an effort to reduce costs or preserve its IT department’s ego, many companies are tempted to handle the transition from a conventional network to a virtualized desktop infrastructure (VDI) alone. Addressing the project without help from a virtualization specialist does not automatically equate to failure, but the approach is a perilous one, wrought with injurious pitfalls every step of the way. In other words, any company looking to go it alone needs to do things the right way, or it risks complications.
The VDI design and implementation process is very sophisticated and reading software installation manuals isn’t enough to make someone an expert. Since most businesses lack an in-house IT member specializing in VDI deployment, sending staff for training is usually necessary.
Common risks of a DIY virtualization include:
- Extended development process – IT departments charged with reinventing an expansive companywide network, plus tasked with regular day-to-day obligations, can hardly be expected to provide a VDI solutions quickly.
- Use of outdated software – If a company lacks in-house VDI specialization, chances are they are not completely up to date with the latest industry developments. Such companies are at risk of using soon to be obsolete technologies, which means a systems update would be soon to follow, demanding additional time and capital.
- An unusable final product – This is the biggest danger, and the one most often realized. When a final product is unusable, or no better than the one that it succeeded, it produces the following results:
- Lost productivity – Internal resources are wasted.
- Time lost – Time is wasted on a project that leads to no changes.
- Financial loss – The capital lost from the unsuccessful VDI implementation is only half of it. Now the company has to pay the cost of a solutions provider to fix everything, plus redevelop the VDI.
- Damaged user perception – Users of the network experience downtime or a poor final computing experience, which causes them to lose faith in company IT.
Though some companies are tempted to develop their own VDI, only those with sufficiently educated IT members should try. While capital can potentially be saved by going DIY, the cost of failure is much greater. In the end, gambling with a might-be-ready team just isn’t worth it.