First, you need to establish the connection to Operations Manager since now in VMM we make our reports available exclusively from within the OpsMgr console. We did this for one big reason; to leverage the rich capabilities of object pickers available in the OpsMgr reporting infrastructure.
Detailed instructions on how to configure the connection between OM and VMM is located here: http://technet.microsoft.com/en-us/library/hh881887.aspx .
Once that link is established, you should be able to see all of our reports from within the OpsMgr console. Here is a listing from my installation.
As you can see from the listing above, all of the legacy reports available in VMM 2008 R2 are carried forwards and we have added a handful of new reports with the intent of giving you a good understanding of capacity usage across your datacenter at an aggregate level.
One of the most useful ones (my favorite one) among this set of new reports is the Capacity Utilization report which let you pick a set of host machines in your environment and gives you a birds-eye view of how all the hosts are doing from a capacity usage perspective. It covers CPU utilization (considering not just the first moments or averages of usage but also takes second moments into consideration; which means it accounts for bursty-ness in CPU usage as well), Network and Storage usage, Memory usage and Disk IO all in one report to give a holistic view of the entire datacenter if you choose to do so.
Here is a snapshot of the Performance Impact and Resource Utilization report run on about 10 host machines:
Like I said earlier, now you can pick objects even in legacy reports since we rewrote them to use the new controls. No more typing host names or keeping them in a notepad and updating that list.
Here is a run of host group resource usage forecasting report that you can use to forecast and help you in planning for provisioning resources for your physical infrastructure before the resource pool runs super hot. A similar report also exists for forecasting SAN storage usage that works off of SAN Pools that are being managed by VMM. Both of these forecasting reports use SQL Analysis Services forecasting functions to project data into the future and hence require integration with SQL AS .
And here is an example of Power Savings report showcasing the savings obtained due to Power Optimization feature of Virtual Machine Manager. The way it basically works is we capture the Power On/Off events from VMM to the host machines and log them in the warehouse, and then they are used when generating this report.
Last but not least, is our new allocation based Chargeback report. We built this one more as a template showcasing the types of chargeback you can provide your customers by using this report as a canned example you could use as a baseline. It will let you assign a cost per unit of resource allocated to the VM as well as a base cost per
Chaitanya Garikiparthi | Program Manager
Get the latest System Center news on Facebook and Twitter :
App-V Team blog:
http://blogs.technet.com/appv/
ConfigMgr Support Team blog:
http://blogs.technet.com/configurationmgr/
DPM Team blog:
http://blogs.technet.com/dpm/
MED-V Team blog:
http://blogs.technet.com/medv/
Orchestrator Support Team blog:
http://blogs.technet.com/b/orchestrator/
Operations Manager Team blog:
http://blogs.technet.com/momteam/
SCVMM Team blog:
http://blogs.technet.com/scvmm
Server App-V Team blog:
http://blogs.technet.com/b/serverappv
Service Manager Team blog:
http://blogs.technet.com/b/servicemanager
System Center Essentials Team blog:
http://blogs.technet.com/b/systemcenteressentials
WSUS Support Team blog:
http://blogs.technet.com/sus/
The Forefront Server Protection blog:
http://blogs.technet.com/b/fss/
The Forefront Endpoint Security blog :
http://blogs.technet.com/b/clientsecurity/
The Forefront Identity Manager blog :
http://blogs.msdn.com/b/ms-identity-support/
The Forefront TMG blog:
http://blogs.technet.com/b/isablog/
The Forefront UAG blog:
http://blogs.technet.com/b/edgeaccessblog/