Of course, DynamicOps recommends using WIM for all cloning purposes. WIM is a file-based disk image format that can be used to deploy Windows-based machines or in this case virtual machines. But this way of cloning only works with Windows based VMs and it does not work with Windows 2008 x64 at this moment. We could only import Linux VMs or clone them via the VMware clone method.

DynamicOps implementation of WIM Imaging was error-prone and the documentation was unclear, quirky and sometimes wrong on how to properly use the product. For example, when creating the WIM image for Windows 2008, which should be a relatively simple process, we had to create an unattend.xml file to be read by Sysprep (a Microsoft command that prepares a system for virtualization from physical to virtual conversion) to configure certain items like license keys and admin passwords. The manual also described a number of laborious WIM imaging choices, which could have easily been re-made into templates.

Seeing as you can create both Windows and Linux VM clones using VirtualCenter alone, we don't see the benefit of jumping through the WIM Imaging hoops.

When we created provisioning groups -- where you establish which users play which roles and belong to which groups -- we also set up resources for each group.

You can import your existing virtual machines from VMware only. Really, VRM seems to be mostly for setting up your environment. Even when we imported the machines, we couldn't copy them or really do anything with them. We still had to create separate templates, blueprints, WIM images and other setup related duties in order to do anything. Linux support is almost non-existent except for VirtualCenter cloning, while other operating systems are completely left out. There is no moving or migrating VM functionality at all.