Over the course of the next few months, I’m going to “repurpose” this blog a little bit. We’re going to start using our team blog to focus on product announcements, features etc. It’s just easier to keep all of that information centralized and I will continue to link to that blog when major news is announced. With this blog, I’ll focus more on strategy/direction/opinion with our feature investments in SCVMM and also share some of what we’re hearing from our customers.
Recently at our annual Microsoft Management Summit (MMS) we demo’d some early work we’ve been doing to allow SCVMM customers to augment their on-premise/private cloud resources with hosted/public cloud resources. Cloud computing isn’t new but the appeal of what it offers is really starting to resonate with customers. Last year we conducted focus groups for SCVMM feature planning and not a single person brought up cloud computing as being near the top of their radar. This year we had lots of dialog on cloud computing with customers, most of it unprompted. What we found is that more and more, customers are looking to build a “private cloud” within their enterprise datacenters. Lots of customers told me that many of their internal business units are starting to leverage external public cloud providers and the reasoning typically went something like this:
“All they need is a credit card number and they get a server in a few hours or even minutes. If they call me (internal IT) we have this bureaucracy that takes weeks and that’s assuming I can even automate the provisioning process from networking, storage, physical servers, OS etc. If it’s for dev/test, it will take even longer since that’s less critical.”
Ultimately, as an IT shop, they want to provide their business users with the same level of responsiveness and all of the attributes of public cloud computing so that the decision of whether to go on premise or off premise is a business decision, not a technical one.
The definition of “cloud computing” has also been evolving but most definitions include the concepts of scalability, shared resources and abstraction of physical implementation. Virtualization is a key enabler for many of these scenarios but ultimately we feel it comes down to management as the differentiator (I know, I’m biased but that doesn’t make me wrong!).
Many vendors are advising customers to wait for better industry alignment before proceeding (Tom Bittman at Gartner has an alternative interpretation of this tactic) but waiting isn’t really an option for most customers who are already under heavy pressure in this particularly difficult economy. Over the next few blog posts I’ll be going into more detail but System Center and Windows Server will form the foundation of our technology stack so you can get started now knowing that we have your back on ensuring that your investments today line up with our strategy longer term. Customers are telling us that they want to manage both private and public resources using a consistent approach and using a single set of tools so that’s what we’re committed to bringing them. We showed an early glimpse of this at MMS but we are very ambitious and that’s just the tip of the iceberg – stay tuned!
We just pushed out the RC for SCVMM 2008 R2 and you can get the bits at https://connect.microsoft.com/
We've managed to add many significant new features to our RC since the beta release based on customer feedback and you can read about the details here on our team blog. Several of our early adopter customers are already running this release in large scale environments so we're feeling pretty good about stability but it's still "not quite" final. Please send us your comments/suggestions/bugs through MS connect website.
Rakesh
Since the R2 beta was released, we've been at work incorporating some feedback from beta customers and our early adopters. As a result, we've added some pretty significant enhancements to SCVMM 2008 R2. Check out our team blog for the detailed feature breakdown.
This QFE includes several fixes including one with VMware resource pools discussed in a previous blog post of mine. You can get the QFE details here and download it via Microsoft Update using SCVMM 2008.
Here we go again!
Since shipping VMM 2008 in October, we’ve been busy working on an update that supports Windows 2008 R2 and take advantage of the new features in the platform. Today, we’re announcing the Beta of VMM 2008 R2 (it was actually released to our beta community on Friday March 13).
There’s a lot in the beta so I want to take a moment to talk about the new features and also about fixes to some issues that customers have reported since we shipped VMM 2008. (If the suspense is killing you - you can download the beta from our MS Connect beta site and click on "server" under "categories" to quickly locate it)
New features in R2 include:
· Support for Live Migration: With Windows 2008 R2 adding support for Live migration, it’s now added as a new migration option in VMM R2. Live migration requires the source and destination host to be part of a failover cluster and that the VM is on a shared storage. Live migration means that there is no user perceived downtime; since the VM’s memory pages are being transferred, the hosts’ processors need to be the same (manufacturer and processor architecture). Our competition claims that Vmotion doesn’t require clustering but this only works for planned downtime and not for unplanned downtime. By combining Live migration and clustering, Hyper-V addresses both planned and unplanned downtime.
· Multiple VMs per LUN: VMM 2008 didn’t allow placing multiple VMs per LUN even though Hyper-V allowed it and the reason was that the LUN ownership was on a per host basis. This meant that migrating any VM on that shared LUN would result in all other VMs being migrated as well which can result in a confusing user experience (I’ve blogged about this at length). With CSV (Clustered Shared Volumes) in Windows 2008 R2, a single LUN is accessible by all hosts within a cluster. This enables a VM that’s on a shared LUN to be migrated without affecting other VMs on that LUN. As a result, with VMM R2, we’ll allow multiple VMs to be placed on the same LUN if CSV is enabled on the cluster.
· SAN related enhancements: We’ve done a number of SAN related enhancements in VMM R2.
o SAN migration in and out of clusters: With VMM R2, you can migrate a VM from one cluster to another or from a standalone host into a cluster or vice versa. Especially useful when you are deploying a VM from a test cluster to a production one.
o Multiple LUNs per single iSCSI target: VMM 2008 supported only initiator-based iSCSI target connection, which allows only one LUN per iSCSI target. VMM 2008 R2 adds support for masking-based target connections, which allows multiple LUNs per iSCSI target and expands VMM support for iSCSI SAN providers. This implies that we have better support for iSCSI products from Network Appliance and EMC for example.
· Network related enhancements:
o Network Optimization
§ Win2k8 R2 supports 2 types of network optimizations: VMQ & Chimney
§ During VM creation you can enable/disable network optimization
§ If enabled, VMM will configure the VM to use VMQ or Chimney, if available on the host
§ During placement, VMM R2 detects and shows availability of Network optimization on the host
o Some workloads such as Network load balancers need to be able to spoof MACs: There’s a new setting that allows admin to enable/Disable MAC spoofing on a per VM basis
o Ability to reuse port groups defined in VMWare VirtualCenter
§ In VMM 2008, port groups were always created even if the admin had already created them on the host.
§ In VMM R2, the admin is allowed to pick an available port group that’s already defined.
· Maintenance mode
o For servicing a host, VMM R2 allows host to be put in maintenance mode: When you do this, all VMs on that host that are running are live migrated off the host to avoid downtime.
§ Admin can choose to save state VMs if host is not part of a cluster
o During placement, a Host that’s in maintenance mode gets zero star ratings. This also p-prevents PRO from picking this host when migrating VMs.
o Maintenance mode is supported for Hyper-V, VS and VMWare ESX hosts
· Support for Disjoint domains: When a host has different FQDN in AD and DNS, it’s said to be in a disjoint domain. For example: server name is foo and FQDN in AD is foo.domain.contoso.com and FQDN in DNS is foo.contoso.com. For Kerberos authentication to work, SPN needs to be created for DNS Name
o VMM 2008 required custom SPN to be manually configured in AD
o VMM 2008 R2 automatically creates custom SPN for DNS name. (AD needs to be configured to give permissions to VMM for SPN read/write permissions)
As you can see, there are a number of enhancements we’ve introduced in R2 along with fixing some important issues reported by customers and partners. We are not done yet! In addition to responding to more feedback from beta testers, there are a few more features in the pipeline for post Beta so stay tuned.
Download the beta here and keep the feedback rolling in!
Rakesh
It has come to my attention that some of our competitors are making various claims about SCVMM 2008 and VMware ESX management capabilities. I guess we have officially crashed the party but I thought I’d put together a blog post to address some of these claims.
Let me start by saying that no software is perfect and we are constantly trying to improve and respond to customer feedback. In fact, the whole VMware ESX management feature was a result of customer feedback. Put simply, people want to use a single primary console for day to day management of virtual machines across multiple hypervisors so we went after this problem. As a result, multi-hypervisor management via SCVMM 2008 has proven to be enormously popular with customers and partners alike. Rather than offering customers an alternative or competitive cross-hypervisor solution, it’s unfortunate that rhetoric and FUD are being used, neither of which actually solve real customer problems. This is a pretty common tactic and as a result, I seldom respond directly to competitive claims (believe me, it’s tempting!) unless they come directly from customers because that’s ultimately our focus. In this case however it’s important to set the record straight on a few key issues because I don’t want customers to be confused or surprised so let’s get right into it…..
Why Does SCVMM remove templates from my ESX server when I import them?–SCVMM has the concept of a “library” which it uses to manage all of the building blocks of your VMs including ISOs, scripts, VHDs, VMDKs etc. - VMware doesn’t have this concept. When you choose to import ESX templates, SCVMM removes the template from the ESX host and puts it into our library. Keeping templates in both places results in multiple copies of the same template that you will need to maintain. For obvious reasons, customers typically don’t want to do this. Of course, importing the templates is an option and is not something that you are forced to do. You are free to create separate SCVMM templates for VMware directly though our UI if you feel like that’s a better approach and want to keep different versions for the different environments. Creating a template in SCVMM takes only a few minutes.
When I create a VM with SCVMM 2008, how come the default settings through the wizard don’t work with ESX or Virtual Server? – When you first begin to provision a VM with SCVMM, we don’t know which hypervisor you’ll eventually select – Hyper-V, ESX or Virtual Server – so we can’t default things automatically. If you as an administrator know which hypervisor you want to target ahead of time and don’t want to reconfigure VMs in the wizard each time through, there’s a simple way to solve this – create a reusable template. SCVMM’s template creation process is simple and straight forward and is meant for the very purpose of avoiding the need to re-type parameters repeatedly.
VMware doesn’t have intelligent placement and they only support ESX so this is an issue that they can ignore even if you cannot – they always assume ESX and ask you to select the host yourself. Incidentally, if you select a VM that is configured in such a way that it cannot be run on a specific hypervisor, SCVMM’s intelligent placement gives you this information and tells you how to modify the VM configuration to make it compatible which you can use as part of your template.
Does SCVMM 2008 give me visibility into resource pools? - Yes. You can view resource pool properties by right-clicking on an SCVMM 2008 host group. SCVMM 2008 customers use host groups as their effective resource pools (or they consider a cluster to be a resource pool because it’s the radius within which live migrations or quick migrations can occur). SCVMM ensures that when VMs are auto-migrated via policy that they can remain attached to their native host group or cluster so in almost every practical scenario, you won’t have issues. With that said, we’ve received customer feedback that SCVMM should also retain mappings to underlying VMware resource pools and we have a patch that we’re preparing to release in the coming month (April 2009) to address this issue.
Does SCVMM prevent migrations that Virtual Center would allow? Sometimes it discourages them and that’s a good thing. As I’ve stated earlier, VMware doesn’t have intelligent placement so you select the host manually and this means that it’s much “looser” in what it allows. You can do the same in SCVMM and bypass intelligent placement and the associated analysis by using our Powershell interface but that’s not necessarily a good idea. In a recently cited example, SCVMM gives an ESX host that is out of physical memory zero stars in intelligent placement when in reality a customer could use ESX memory overcommit to actually run the VM on that host. Practically speaking (in the real world), this is a contrived scenario since the only way you’d have this problem is if *every* host that you’re considering for placement is out of memory and resources. If you’re not in that predicament, intelligent placement will find a more suitable location for you automatically (I suppose if I had to shell out all that cash for ESX/VI licenses I’d be trying to use every last MB before adding a new host as well but I digress). While the effectiveness and wisdom of memory overcommit is in a production environment is debatable, preferring a host that doesn’t require overcommit to one that does is undeniably the right thing to do. With that said, you can always bypass our intelligent placement via Powershell to move VMs to overcommitted hosts so you shouldn’t be blocked as some have claimed. In addition, we’ll look to integrate this with intelligent placement UI in our upcoming release for the rare case where you end up in this situation.
Can I reuse port groups that I created in ESX? We’ve added this feature to the upcoming release. This is more about nuisance/clutter and if you ask me, the whole concept of port groups is awkward and leads to confusion. We didn’t invent it but we’ve made some changes to accommodate the ESX model for better compatibility.
It looks like Virtual Center gives me more monitoring information than System Center, is that true? Of course not. If your job depends on keeping applications and services running and not on checking IP addresses and watching CPU charts, System Center does this for you with Operations Manager. Once again, like cross hypervisor management, VMware does not provide any solution. Try checking the health of your SQL Server or accounting application with Virtual Center….
Rather than throwing very rudimentary monitoring and health information into the SCVMM console (okay, so we did some of that anyways), we have a full featured extensible monitoring solution that provides in-depth knowledge about applications running within a VM with System Center Operations Manager and the over 100 vendor created management packs. The fact is that if you want to monitor applications, you need a management solution that monitors applications – it’s that simple. Treating a VM like a black box and monitoring hardware as VMware does is not particularly useful for making decisions and does not eliminate the need for health monitoring. Saying that SCVMM requires different software for monitoring is like saying Word requires different software for Spreadsheet work. For our part, Operations Manager and SCVMM are built on the same UI framework and SCVMM 2008 adds a new feature called Performance and Resource Optimization (PRO) which forwards alerts between the consoles. In the future, you can expect even tighter integration between these products.
With that said, you are of course free to use your existing monitoring system as well. Unlike ESX, all Hyper-V functionality is publicly available and exposed to any and all of our partners directly at the hypervisor level. In addition, anything you do in SCVMM through the GUI you can also do through our fully documented command line interface via Powershell. System Center can also patch and configure your VMs via Configuration Manager and back up your VMs with Data Protection Manager. While we (along with thousands of customers) think that they all provide great value and functionality as a group, you of course have the freedom to choose and decide for yourself.
If you are thinking of using SCVMM 2008 to manage VMware because you have a mixed environment (and we have many many customers who are doing just that), keep in mind that SCVMM does not require you to uninstall or remove VMware Virtual Center from your environment. In fact, you have to keep Virtual Center around because VMware does not expose some APIs (like Vmotion) through ESX. We’re a manager of managers so it is nearly risk free to try it out and make up your own mind about how effective we are.
We’re extremely proud to be the only deep cross-hypervisor management tool in market solving this important problem for customers.
Thanks,
Rakesh
We have just released an updated management pack for SCVMM 2008.
This release includes updated reports for all platforms that we manage:
· Virtualization Candidates
· VM utilization
· Host Utilization
· Host Utilization Growth
· VM Allocation
You can download the management pack here
Rakesh
Happy New Year everyone!
A few months into the release of SCVMM, we’ve heard lots of great feedback from customers and the response has been very positive. Keep sending feedback and suggestions on how to make the product even better in future releases!
One thing we’ve heard is that folks want to have multiple VMs stored on a single LUN and still get the capabilities of SAN/quick migration. One of the feature requests we get as a result is “can you guys unblock placing multiple VMs on a LUN in SCVMM 2008?” I thought I'd address this question directly in this blog posting.
At the end of the day, our file system only allows a LUN to be mapped to a single physical host at any given time. This means that the unit of migration using SAN transfer in SCVMM 2008 is the LUN (LAN migration works fine at the VM level). If you were to put multiple VMs on a single LUN, they would all need to move together when migrated which is not the behavior that most customers want. Really they want the ability to put multiple VMs on a LUN and continue to manage the VMs as individual entities so that they can be individually migrated, stored to the library etc.
One way to solve this is to create a completely new file system and have it enable simultaneous access to LUNs across servers. Some vendors have gone down this path but you just trade one problem for a new set of problems. Third party software doesn’t work on custom/boutique file systems, backup systems typically need to be re-engineered, storage security needs to be re-thought through etc. As an example, VMware’s consolidated backup solution goes to great lengths to expose ESX LUNs to Windows Servers so that they can be backed up with your existing infrastructure. You really shouldn’t have to do unnatural things to get access to your data. Windows has plenty of partners that are happy to offload your backup traffic from production to backup proxy servers using snapshots and the Volume Shadow Copy Services (VSS) built into Windows Server but it’s not required. That’s because sometimes it’s easier to back up directly from the production server (during off hours perhaps) since the source data is naturally already distributed and it helps you get your backups done within your backup window. Also, it doesn’t require complicated or expensive hardware and software but ultimately it’s your call on how you want to set this up and you can use either the direct or offload model for backup.
In Windows Server 2008 R2, we’ll provide a layer on top of NTFS that provides a clustered shared volume file system (CSV). Hyper-V and SCVMM Vnext will take advantage of this feature to enable multiple VMs per LUN scenario (Windows Server 2008 R2 will also enable live migration of VMs between servers). You can read more about this here. This solution has the benefit of snapping into your existing Windows environment without seriously disrupting existing processes or procedures. Of course we also work with partners to provide value-added solutions with additional features that help you extend the functionality even further.
Bottom line – we’ve heard the feedback and the solution that you need is almost ready.
P.S. – Most SAN/block level replication software replicates at the LUN level. This means that for most DR solutions (including our competitors and partners) failover typically happens at the LUN level so all VMs on that LUN failover together.
Rakesh
Well, SCVMM VNext of course.....the team is already hard at work on the next release to align with the Windows Server 2008 R2 hypervisor update. Like this release, there will be a short gap between the platform update and the management update but we'll align the releases as close as possible (incidentally, the reason it takes us a little extra time is because once the platform has shipped and everything is "locked", we still need to run through a final battery of tests and stabilization just to make sure everything works as advertised). As we showed back in September, Live Migration will make it's debut in Windows Server 2008 R2 and SCVMM VNext will take advantage of that feature in addition to all of the other new functionality going into the R2 release.
An "R2" server release isn't as large of an incremental update as compared to a completely new major release version of the server OS. This tends to make it easier to adopt since the retesting/certification of applications effort can be more scoped. Of course, if you're using Hyper-V strictly as a virtual machine host and running business applications inside of virtual machines, it will be very straightforward to upgrade to 2K8 R2 since the applications will be isolated from the hypervisor OS update. SCVMM 2008 already supports the VMware VMotion feature directly and indirectly via PRO so adding live migration support isn't going to "change the game" if you will. The key thing we'll continue to invest in and improve is providing the best possible application knowledge so that you know *when* to execute a live migration, *which* applications need calibration and *what" that calibration should be. The beauty of PRO is that it is fully extensible and we can continue to provider a richer experience with improved knowledge incrementally between major and minor updates to SCVMM. On top of that, we're not doing it alone - our partners are coming to market with PRO enabled management packs for System Center so stay tuned for more news on that front.
Over the coming weeks, I'll be blogging about some of our future direction along with more in-depth posts about getting maximum value from SCVMM 2008 features.
Rakesh
P.S.
I will be in Barcelona @ Tech Ed EMEA next week along with several members of my team. If you are planning to be there, please drop by our booth and introduce yourself. You'll also see a glimpse of SCVMM VNext in the keynote address.....
Well, if you’re wondering why this blog has gone “dark” for the past few weeks, now you know. We’ve been working very hard to get SCVMM 2008 out the door and today I’m proud to announce that we’ve officially released SCVMM 2008! I want to thank all of our early adopter customers (thousands of you) for helping make this day possible. You all provided fantastic feedback and ultimately, you’ve helped us ensure SCVMM 2008 is the product that you need it to be.
I’ve blogged at length about the various new features in SCVMM 2008 but let me just very quickly recap some of the highlights.
Comprehensive Hypervisor Management – SCVMM 2007 already lets you manage Virtual Server and now we’ve added support for Hyper-V (including Hyper-V Server) and even VMware based environments (ESX and 3i) through a single management console and a single Powershell command line interface. If you’ve been using virtualization for some time now, chances are that you have some VMware. If you have Windows Server 2008 deployed, you already have Hyper-V. Now, with SCVMM 2008, you can manage both in a seamless and fully integrated way – every feature of SCVMM works against each of the supported virtualization platforms but we still enable features specific to each including Quick Migration on Hyper-V and Vmotion on VMware.
Physical Resource Optimization (PRO) – By integrating the application specific knowledge provided by System Center Operations Manager, SCVMM allows you to calibrate your resource assignments based upon the real-time demands of your datacenter. Rather than migrating VMs around based on generic metrics like CPU and memory utilization, we’ve worked closely with partners to provide you with the best possible information (specific to your environment) before making changing to your infrastructure. In the coming weeks, look for new SCVMM PRO partners announcements on this blog.
Delegated Administration - SCVMM allows you to segment your environment and assign management authorization to each segment to different Active Directory users and/or groups. In addition, SCVMM provides an integrated web-based self-service user interface allowing authorized users to provision and manage their own virtual machines. Administrators can control which templates these users can provision VMs from, determine which actions they are allowed to take and even assign quotas for chargeback purposes.
Highly Available Virtual Machines – SCVMM makes enabling high availability for virtual machines as simple as a single click. Our intelligent placement feature ensures that the VM is deployed or migrated only to a highly available physical host (using Windows clustering for Hyper-V or VMware HA for ESX) and configures the VM for high availability on that host.
Integrated Physical and Virtual Machine Management – SCVMM isn’t an island – it is part of the comprehensive System Center family of products. System Center allows you to patch, monitor, back up, deploy and manage your entire physical and virtual infrastructure.
There are many more terrific features in SCVMM 2008 and we look forward to your feedback. The team is very proud of this release and we’re excited to get it into the hands of our customers. It’s no secret that we feel management will be the key differentiator when it comes to virtualization adoption and future datacenter initiatives. Thanks again for your help and support with this release. For additional information on today’s announcement, check out http://blogs.technet.com/virtualization
Rakesh
In case you hadn't heard, we're having a huge virtualization launch today in Bellevue, WA. You'll be seeing lots of announcements etc. across many blogs so I won't repeat all of them here. Instead, I'd recommend that you check out live webcast here. In particular, Bob is going to take the stage shortly and he'll show off the Live Migration feature coming in Hyper-V with Windows Server 2008 R2 for the first time. The webcasts will be available after the event as well I'm told.
It's no big secret that we've been working on Live Migration for some time. It didn't make it into the first release of Hyper-V but as you'll see today, we have it up and running and it's coming soon. While this feature is important to customers, I maintain that the more important part of the equation is the management that drives it. It's great to be able to move running virtual machines between physical hardware without downtime but knowing when to do it is really where the magic and differentiation lives. Whether you're using VMotion with ESX, Live Migration with Hyper-V or Live Relocation with Xen will increasingly become a less relevant discussion.
If you've been reading this blog for any period of time, you know that we feel strongly that everything starts with the application. Customers manage applications, not virtual machines. Understanding applications in detail enables System Center to make the right decisions to drive this platform technology.....it's an exciting day for us but this is just the tip of the iceberg.
Rakesh
Today I've got a guest poster from my team - Alan Goodman. Alan is the program manager responsible for SCVMM 2008's Performance and Resource Optimization (PRO) feature. PRO functionality has been described at length on this and other blogs but this post provides you with exact step by step details on how to configure and set up PRO. In future posts, Alan will be providing some best practices around using and calibrating PRO as well as authoring information for building your own PRO-enabled management packs so this post is the first of a multi-part series.
NOTE: The instructions described here pertain to the final version of SCVMM 2008 (i.e. not the beta). For those customers enrolled in our early adopter TAP program, you can use the latest release candidate to run through these steps.
----
Hi my name is Alan Goodman and I am a Senior Program Manager on the Virtual Machine Manager team. My main area of focus is VMM's integration with Operations Manager and in particular PRO. As we get closer to the RTM of VMM 2008 I wanted to take some time to help you better understand how to use the various aspects of this feature area. In this post we will start with looking at configuring the integration between VMM and Operations Manager. The following is a step by step set of instructions for walking you through this configuration.
Step by step instructions for configuring VMM 2008's integration with Operations Manager 2008.
The following steps discuss the best way to get through the configuration and ensure a successful configuration. First I want to be clear on two assumptions that are made by the following instructions:
- These instructions will not work with VMM beta, they are written assuming that you are using a post beta build of VMM 2008
- These instructions assume that you have already installed OpsMgr 2007 sp1. In order to try and keep these instructions clear, let's call the root management server opsmgr-01
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
1. Install Virtual Machine Manager 2008 Server (Let's assume this machine is names VMM-01)
Note: If the VMM server and the OpsMgr Server are installed on the same machine then skip step 2 and continue with step 3.
2. Install the VMM 2008 console on VMM-01
3. Install the OpsMgr 2007 sp1 console on VMM-01
4. Log into your root management server (opsmgr-01 ) with an account which has been granted Operations Manager Administrators access.
5. Uninstall any version of the VMM 2008 console that may have been previously installed. If the OpsMgr Server is the VMM server then uninstall the VMM console (don't worry it will be reinstalled as part of step 8).
6. Open the Operations Manager console and import the following MPs if they are not already imported:
- a. SQL Server MP (Download here)
- Microsoft.SQLServer.Library
- Microsoft.SQLServer.2005.Monitoring
- Microsoft.SQLServer.2005.Discovery
- b. IIS 2003 MP (Download here)
- Microsoft.Windows.InternetInformationServices.CommonLibrary
- Microsoft.Windows.InternetInformationServices.2003
7. If you have older versions of the VMM MPs imported then remove all of them.
8. On your root management server, run the setup from the VMM 2008 CD and select Configure Operations Manager and on each of your management servers just run the VMM Administrator Console installer.
Note: You must run one of the two setup wizards on each of the OpsMgr servers in your management group.
Note: This setup wizard will do the following:
- Import the VMM management packs, including all MPs required for PRO.
- Grant the run as account of your VMM server the necessary access to your OpsMgr Server.
- Install the VMM console.
9. Log into the VMM console and connect to your VMM server (in this case VMM-01)
10. Open the Administration tab and select User Roles.
11. Open the properties of the Administrators user role and add the Default Action Account for each of the management servers in the management group.
12. Open the Administration tab and select System Center from the tree view in the upper left of the console.
13. Open the Operations Manager Server item and enter the name of your OpsMgr root management server (in this case opsmgr-01)
At this point VMM and OpsMgr are integrated, and you can see all of the data from your VMM installation discovered into your OpsMgr installation by opening your OpsMgr Console and navigating to the Monitoring tab. From there you will find a newly created folder called Virtual Machine Manager 2008 Views. Inside that folder there should be a new view with the name of your VMM server. If that view does not exist, then you should check the Operations Manager event log on the OpsMgr Server (opsmgr-01). If there were any errors during discovery they will show up here.
Hopefully you have found this post helpful and insightful. I am looking forward to further discussion about VMM and OpsMgr and looking at other aspects of this feature area such as enabling PRO and authoring your own PRO enabled MPs.
Aside from overall performance, stability and reliability (things you might expect to improve from any beta), I thought I'd give folks a heads up on some of the things that we've added/changed for the final release next month which weren't in the beta. While the beta was advertised as "feature complete", we did take a bunch of the feedback that you sent our way and hopefully the end result is an even better final product.
Here's a list outlining some of the key improvements:
· Support for managing hosts in a Disjoint Namespace
· PRO
o Support for enabling PRO on non-clustered hosts
o Automated loading of OpsMgr MPs via Configure Operations Manager option in Setup
o View Script Option – now you can preview the script that PRO will run to implement the PRO Tip
· Admin Console
o Network Diagram View graphically shows how your hosts and VMs are connected to networks in your environment (some screen shots to follow)
o New, more polished UI
· Self-Service
o Allow users to mount ISOs
o Completely overhauled UI
· VMware management
o Support for VMware HA along with HA VM creation on VMware clusters
o Enhanced security for VMware management
o Management of ESX 3i
· Global Static MAC Address range – configure the range of MAC addresses VMM uses when creating new virtual network devices
· P2V improvements
o Support for offline conversion using static IP
o Storage and network driver detection for offline conversion
o P2V of domain controller
· VM Creation
o Creation of VMs without customization required (templates now have the option of “skipping” customization) so you can use non-Windows templates
o Product Key encryption by default in Guest OS profile
o VHD expansion
· Setup and Installation
o SQL 2008 Support
o VMM 2007 to VMM 2008 Migration
o Ability to install as a domain user in addition to local system
In case you missed it, we recently announced a more precise date for the final release of SCVMM 2008 - September 2008. Previously we had said that it would be the second half of 2008 but Hyper-V shipped early and we're coming down the home stretch as well. At this stage of the game, shipping software is as much art as it is science so it's hard to pin down an exact date. Our single focus for the past four months has been quality and that will continue to be our focus until we ship. We have been testing SCVMM in as many configurations and use cases as is humanly possible in addition to cranking up the performance and scale limits. We're working with a small group of aggressive early adopters in parallel with our efforts here in Redmond to ensure we're battle tested before the general release.
Stay tuned......
Rakesh
A popular question that seems to be floating on various blogs and message boards is related to why SCVMM integrates with Virtual Infrastructure by proxying requests through Virtual Center Web Service APIs as opposed to talking directly to ESX. There are several reasons for this and I'll go through them roughly in priority order to hopefully clarify some confusion.
1) ESX doesn't support all of the same APIs that Virtual Center does. Most notably, you can't use VMotion without going through Virtual Center and this was a key requirement from customers in doing SCVMM/VMware integration. There are other management constructs and features also exposed only through Virtual Center and in order to do a complete job of integration, we used that API route. There seems to be some debate across various blogs as to whether the APIs on ESX/Virtual Center are equivalent or not and it's a pretty cut and dry issue. This is from VMware's programming guide:
The full API doc is here, the snippet is from page 28.
2) Most VMware customers already use Virtual Center (in part due to licensing and packaging of Virtual Infrastructure features) and don't want to re-implement everything that they have configured in Virtual Center in SCVMM. With the current architecture and design, we simply synchronize and import the information from Virtual Center so you don't need to re-run lots of configuration steps. You can literally start managing your entire VMware environment in 5 mins and we demo this for customers with their actual live environments all the time.
3) For environments that already use Virtual Center, SCVMM effectively becomes a "manager of managers" which is an appealing and low-risk way of introducing SCVMM in the eyes of many customers. You don't need to rip out and replace your existing Virtual Center instances to begin using SCVMM (but of course, you will only be able to manage the VMware environment with Virtual Center whereas SCVMM manages ESX, Hyper-V, Virtual Server and eventually Xen). SCVMM can even let you manage multiple Virtual Center instances through our console, something VMware currently does not offer. Since we synchronize with Virtual Center instances bi-directionally, this means that any action you take on the VMware environment through SCVMM is automatically reflected in the Virtual Center UI and vice versa. Plus, we do all of this without installing additional software/agents on the VMware boxes. Our goal of course is to show you that you'll want to live in our console since it provides a more complete picture for mixed environments in addition to the value-add management capabilities.
4) Technically speaking, we have a dependency on the Virtual Center web service, not the console but you'll still need to use the Virtual Center console to on-board new ESX servers and a handful of other tasks. Again, our goal from a management perspective is to allow you to live in one console day to day and automate using one PowerShell interface across hypervisors. With that said, just as you occasionally need to access Windows features directly on the Hyper-V box (MMC snap-ins, storage configuration, bare metal configuration etc.), the same holds true of ESX.
Hopefully this helps clarify things.
Rakesh
