SC-VMM provides limited view of VMware-based VMs

13.04.2009
The final version of SC VMM -- which began shipping in November -- is much improved over the beta code we last fall, but it has still got some rough patches in terms of integration with Microsoft's Operations Manager (needed for monitoring and trending) and as supporting non-Windows VMs goes.

SC VMM now conveniently manages VMware's ESX-based VMs, but that support requires that VMware's own VirtualCenter management application (which VMware charges for) already be in place to perform much of the actual work when managing ESX VMs. This condition exists for other products tested as well.

Hosting SC VMM requires hardware resources that depend on how many hosts you plan to install. Each machine that runs the SC VMM management console needs at least a 2GHz x64 processor, 2GB of memory and 10GB of hard disk space. (See a .)

Windows 2008 Server is required as well. You also need to deploy (on a separate machine if you like) Microsoft Operations Manager (MOM) 2007, a prerequisite for the Performance and Resource Optimization (PRO) tips tool that handles monitoring, alerting and trending tasks. The list of other required Microsoft piece parts includes Windows PowerShell 1.0+, Windows Remote Management, WAIK 1.1 and IIS 7.0.

Starting up

Using SC VMM to initially make a VM image instance wasn't easy or intuitive.