Windows Virtualization Team Blog : System Center Virtual Machine Manager

Visual Studio Lab Management 2010 beta 2

porourke — Fri, 06 Nov 2009 06:20:00 GMT

Hello, this is Bryon Surace again. I’m a senior program manager on the Windows virtualization team at Microsoft.

Recently, the Visual Studio 2010 and .NET Framework 4 beta 2 became available for public download. Part of this release is the Beta 2 version of Visual Studio Team System 2010 Lab Management; an integrated solution to give you all the benefits of virtualization for application lifecycle management. Congratulations to the Visual Studio Lab Management team for reaching this milestone!

Beta 2 Improvements:

§ Simplified Virtual Environment creation

§ Lab Environment Viewer with full-screen capability

§ Manual and automated testing in virtual environment

§ Build-deploy-test workflow for virtual environments

§ Enhanced workflow process parameters UI and report

§ Network isolation with support for domain controller VMs

§ Setup & Config – verification and auto provisioning of accounts

§ Virtual Machine templates

§ “In-Use” support for shared environments

The main features of Lab Management are:

Easily manage more complex test configurations

Lab environment as a first class entity for managing multi-machine test environments
Setup multiple configurations for testing quickly
Consistent, reliable access to test environments
Create multiple copies of test environments for parallel testing

New “clean” environment in minutes

Environment snapshot: lightweight and efficient
Facilitates exploratory testing

Scheduled build/test cycle on steroids

Snapshot to clean environment
Build triggered app deployment
Testing in more realistic environment

Rich bugs with environment snapshot

reduce the number of no-repro bugs

Visual Studio Download Page – you can download all the required components from there. This video can guide you through the download and installation process of TFS. And check out the Lab Management blog.

Thank you,

Bryon Surace

Re-blog: Microsoft Site Recovery Solution Launch

porourke — Wed, 04 Nov 2009 07:27:00 GMT

I'm re-blogging here. Over at Virt Planet blog, Jim wrote the following:

This week Microsoft is launching a comprehensive solution to help customers implement cost effective, end-to-end site recovery programs. Built on proven capabilities in Windows Server 2008 R2 and the System Center management suite, Microsoft is helping IT Professionals leverage Windows Server Hyper-V and Failover Clustering along with tools like Virtual Machine Manager to deliver cost effective site recovery.

The Microsoft Site Recovery Solution ecosystem is ramping with a broad range of storage replication partners like Double-Take Software, EMC, HDS, HP delivering solutions that take advantage of the Microsoft Cluster Resource DLL. With cluster integration IT Professionals can deploy streamlined and operationally effective site recovery.

You can learn more about the Microsoft Site Recovery Solution by joining the Microsoft team and Enterprise Strategy Group on Thursday, November 5^th at 10:30am Pacific for a webcast Building Effective and Highly Available Disaster Recovery Solutions Using Microsoft Virtualization This webcast looks at key drivers for site recovery solutions and reviews practical deployment considerations (you can view the recorded version of the webcast after the 5^th). Microsoft and select partners will also be demonstrating Site Recovery Solutions at TechEd, so if you plan to be in Berlin during the week of November 9^th, make sure to stop by the Virtualization Solutions kiosk in the Technical Learning Center.

Patrick

Upcoming Webcasts on Best Practices for Virtualizing MS Server Applications

porourke — Tue, 27 Oct 2009 22:25:00 GMT

We’ve got some great webcasts coming up in the next few weeks to discuss recommendations for virtualizing MS server applications and the benefits of choosing hyper-V + System Center as your virtualization solution. Each technical webcast will focus on a specific server application- Exchange, SQL and SharePoint. Please see below for detailed information.

TechNet Webcast: Microsoft Virtualization Best Practices for SQL Server (Level 300). Thursday, Oct. 29, 2009 at 10am Pacific time

Virtualizing business critical applications will deliver significant customer benefits including cost savings, enhanced business continuity and an agile and efficient management solution. This session will focus on virtualizing SQL Server using Microsoft solutions, the benefits over key competitors such as VMware, and guidance for virtualizing SQL server for Production and Test/Dev scenarios focusing on consolidation, scale, load balancing, dynamic provisioning and high availability. We will go into technical details with best practices. Customer evidence and results from lab deployment tests will also be discussed.

TechNet Webcast: Microsoft Virtualization Best Practices for Exchange Server (Level 300) Wednesday, Nov. 4 at 10am Pacific time

Virtualizing business critical applications will deliver significant customer benefits including cost savings, enhanced business continuity and an agile and efficient management solution. This session will focus on virtualizing Exchange using Microsoft solutions, the benefits over key competitors such as VMware, and guidance for virtualizing Exchange for various Production scenarios. We will go into technical details with best practices. Customer evidence and results from lab deployment tests will also be discussed.

Virtualization: desktop to datacenter

porourke — Tue, 20 Oct 2009 21:54:00 GMT

It's been a while since I've posted a blog ... but that one really caused a stir in the Virt circles in the Bay Area. Hopefully it doesn't mean I can't hit up those people for Sharks tickets.

I've stumbled across some interesting items that I wanted to share with you.

Microsoft Desktop Optimization Pack 2009 R2 is now available. The big thing is support for Windows 7. Read the blog here. Here's an excerpt:

If you are an MDOP customer, you can download MDOP 2009 R2 through Microsoft Volume Licensing Site (MVLS). For others who wish to evaluate MDOP products, the MDOP software is available at MSDN and TechNet (in accordance with your MSDN or TechNet agreements, except for AIS).

MDOP has been licensed for over 21 million desktops worldwide! In a recent survey completed for Microsoft by Answers Research, and including 1000 IT professionals across five countries, we learned several interesting facts:

66% of MDOP customers deployed three or more of the MDOP products

52% of them deployed MDOP across more than half of their PCs

94% of MDOP customers said they would recommend MDOP to a colleague

When comparing MDOP and non-MDOP customers, customer satisfaction with Software Assurance increases by 25%

Microsoft Enterprise Desktop Virtualization (MED-V) V 1.0 SP1 - This updated tool will support Windows 7 and enable enterprise deployment of virtual Windows XP environments to support incompatible applications. A Beta version of MED-V 1.0 SP1 will be available by the end of 2009 and final release is scheduled for the first quarter of calendar year 2010.

On the server side, the latest is from Gartner Symposium in Orlando. Gartner announced their top 10 strategic technologies for 2010. Not surprisingly, virtualization is named or underlying several of the strategic technologies. And speaking of, Gartner also shared data on server virtualization adoption today and forecasted through 2012. Read this article. Here's an excerpt:

According to Gartner, 18% of server workloads this year run on virtualized servers; that share will grow to 28% next year and reach almost half by 2012. But growth is anticipated among the small-to-midsize businesses (SMB), and it's in this segment that Microsoft has a good chance to build a customer base. By 2012, VMware's share is expected to shrink to 65% but the base of VMs will have grown to 58 million, a 10-fold leap. By that time, Gartner believes, Microsoft will hold 27% share, Citrix 6%, Red Hat 2% and others about 1%.

Along those lines, I had a great email exchange a couple weeks ago with Steve at PoundHost in Maidenhead, UK. I was giving a presentation at IP Expo / VM Expo conference in London, and wanted to highlight PoundHost's business results since switching to Hyper-V and System Center away from VMware tools, and since PoundHost has deployed the Dynamic Datacenter Tookit for hosters. PoundHost has a very compelling story of how technology can really help a business transform itself and create new opportunities. The Microsoft case study doesn't really do it justice. Here's some of what Steve shared with me:

Cost. "It meant we could offer Linux and Windows at the same price (when we went live with the beta of R2 we had Linux guests but we don’t now). It means we can offer low cost VMs on high quality (and cost!) host servers which ultimately give the end user a better experience. [It] works out about £1.00 per guest assuming 60 guests per host."
Common management tools. "We were also very impressed with a demo we had seen of System Center Virtual Machine Manager and Ops Manager so we now use both in our infrastructure."
Choice. "I’m a VCP and have a lot of experience with ESX but I’d never use it again now I’ve used Hyper-V under R2"
Grow business. "[We've] expanded our Hyper-V/System Center offerings into our managed services company Server Arcade "
Grow business: profitability boost by 55%
Customer service. "We’re also doing the customer control panel now for Poundhost which is based on the Dynamic Datacenter Toolkit."

Check out more about the Dynamic Datacenter toolkits and partner alliance at their blog.

Patrick O'Rourke

Announcing the availability of the updated Infrastructure Planning and Design Guides for Virtualization and System Center

vtango — Thu, 24 Sep 2009 17:03:00 GMT

Microsoft has a comprehensive portfolio of technologies when it comes to Virtualization ranging from Presentation Virtualization with Remote Desktop Services to Server Virtualization using Hyper-V with many more in between as below.

· Server Hardware Virtualization. Also known as a hypervisor, Server Hardware Virtualization runs a very lightweight core operating system. The hypervisor can host independent virtual machines (VMs). This form of virtualization requires hardware that has embedded virtualization awareness capabilities. Since the hypervisor is very lightweight, there is little overhead in the system, which allows for more scalability in the virtual machines.

· Server Software Virtualization. An operating system, such as Windows Server® 2003 or Windows Server 2008, runs an application that is able to host virtual machines. Each virtual machine runs a completely separate operating system and application set.

· Presentation Virtualization. Centralized systems host multiple user sessions, and all processing is done on those host systems. The user sessions are isolated from each other. Only the presentation information, such as keyboard and mouse inputs, and video updates are sent between the client and the host system. The client can be a full Windows-based workstation or a Windows-based terminal device.

· Application Virtualization. An application is isolated from the underlying operating system by means of wrapper software that encapsulates it. This allows multiple applications that may have conflicting dynamic link libraries (DLLs) or other incompatibilities to run on the same machine without affecting each other.

· Desktop Virtualization. This is similar to Server Software Virtualization, but it runs on client systems such as Windows Vista®. The client operating system runs a virtualization application that hosts virtual machines. This is often used when a specific person needs to run one or a limited number of legacy applications on a legacy operating system.

With the richness and breadth of these technologies, customers should evaluate their needs against the capabilities and solutions that each of the technologies is targeted at. The Solution Accelerators team has been working furiously to create guides for customers and we are really excited to announce the availability of the Infrastructure Planning and Design Guide for Virtualization updated for Windows Server 2008 R2, which can help customers start their planning and deployment process for Virtualization using the Microsoft portfolio. With detailed documentation and simple flowcharts customers now have a powerful tool in their hands as they plan their deployments. Once the decision to go with a particular technology has been made, detailed guides are available for each of the technologies as well giving business decision makers, infrastructure stakeholders, and the organization as a whole a comprehensive tool for designing their virtual deployments.

As Tom Bittman from Gartner had said “Virtualization without good management is more dangerous than not using virtualization in the first place”. Our System Center suite of products provide a full suite of management solutions for this environment and the Infrastructure and Planning Guides for System Center have been updated for System Center Virtual Machine Manager 2008 R2.

Vijay Tewari

Principal Program Manager, Windows Server Virtualization

Microsoft Virtualization: Best Choice for MS Server Applications

porourke — Wed, 02 Sep 2009 19:21:00 GMT

Hello, I’m Zane Adam, general manager of Virtualization and Systems Management. As more and more customers are looking at virtualization to help reduce cost and decrease complexity in their infrastructure, we are seeing lots of questions around virtualizing MS server applications such as Exchange, SQL and SharePoint. What benefits should I expect to see? What do I need to consider when virtualizing these mission critical business application? Should I virtualize all roles within a server application?

We have worked across MS application groups to test our products with hyper-v and we believe that MS virtualization is the best choice for MS server applications. First, MS server applications are built for Windows Server, and because hyper-v is part of the operating system, there is no need to add complexity of support and interoperability by adding a 3rd party virtualization layer. This means there is just one stop for all of your support needs and also assurance that the stack of applications and hypervisor works well together. Second, to help ensure optimal performance Microsoft has specific deployment guidance for virtualizing MS server applications which results in a mixed physical and virtual environment. System Center is the management solution that allows you to view both physical and virtual instances from one console. Third, as you know MS virtualization is up to six times less expensive than other virtualization solutions in the market, which makes running your server applications even that more affordable.

The folks who developed the MS server applications have developed specific guidance on virtualizing individual applications based on deployment scenarios. You can hear more thoughts from them on the following blogs:

Exchange Server: http://msexchangeteam.com/

SQL Server: http://blogs.technet.com/dataplatforminsider/default.aspx

SharePoint: http://blogs.msdn.com/sharepoint

Also, for more information please visit www.microsoft.com/virtualization/solutions/business-critical-applications .

Thanks-

Zane

Update: What you won't see at VMworld 2009

porourke — Thu, 27 Aug 2009 02:30:00 GMT

This post is for the readers out there that will be attending VMworld, or have colleagues attending VMworld.

There’s been some speculative statements made in the press and blogs in the past 24 hours, so I want to try to set the record straight:

1. Microsoft will be exhibiting at VMworld 2009. Can't wait! We have a 10x10 booth, #2422. If you have a chance, please stop by booth. It's right next to the Blogger lounge. See more below.

2. Unlike prior VMworld conferences, we’re no longer allowed to sponsor the event. We can only be an exhibitor. Why? Let's look at excerpts from VMworld’s rules (my highlights):

VMworld 2009 Sponsor and Exhibitor Rules and Regulations

Booth/Session Demonstrations (pg. 2)

Sponsors and exhibitors must market or demonstrate products on the exhibition floor and in the sessions

which are complementary to VMware products and technologies. Complementary products and services are

defined as products/services that do not overlap/substitute with VMware’s products/capabilities, and help

expand the reach and solution scope of VMware’s capabilities solely as deemed by VMware. All sponsors

and exhibitors must adhere to following guidelines in regards to booth demonstrations (please also review

the “Promotion, Giveaways, Contests” section below):

Eligibility (pg. 4)

To sponsor or exhibit at VMworld a company must be a VMware partner in good standing in our TAP,

Strategic Global Partner or VIP Partner Programs. Companies that are not VMware partners may be allowed

to exhibit at VMworld under exception by VMware.

Both sides (us and VMware) agreed that, apart from the features in System Center Virtual Machine Manager that manage ESX, Microsoft products aren’t complementary to VMware’s products. We discussed and confirmed their intent of these clauses in early August, and had a follow-up Aug. 11 email from VMware, that reads in part:

As I mentioned, the rules require all exhibitors to market and demonstrate products that are complimentary to VMware products and technologies. We are open to reviewing any proposals for complimentary positioning of Microsoft products and demos at the show…

As a result, based on the clause above, phone/email with VMware employees, we don't believe we have the right to demo our products in the booth. This decision runs counter to Microsoft’s geek culture, as you can imagine, but we've also become more pragmatic over the years :-).

So what is Microsoft doing at VMworld?

We’ve learned over the course of 4 years attending VMworld (first was Vegas 2005) that there are many attendees who use, admin, manage, sell, support Windows Server, SQL Server, Exchange Server, Windows XP/Vista, System Center, etc. They want the opportunity to engage and receive information from Microsoft virtualization experts. So we’ll have Microsoft virtualization experts in the booth. These experts will be there to answer your questions. They’ll also be Tweeting about their experiences and impressions as they talk to customers and attend sessions. I encourage you to follow them on Twitter - see the table below for their usernames.

Expert in	Name	Twitter Username
Disaster Recovery, Backup	Allen Stewart	dynamic_dc
Desktop Virtualization	Ben Armstrong	virtualpcguy
App & Desktop Virtualization	Jeff Johnson	JJ_VDI
Virtualization Management	Stuart Schaefer	Sshaffer_MS
Cloud	Isaac Roybal	DDACloudGuy
Business value	Edwin Yuen	edwinyuen
Workloads, partners, licensing	Kenon Owen	MS_Int_Virt
Server Virtualization	Vijay Tewari	vtango

We’ll also have two customers in the booth at different times. I’ll be there. See you there!

Patrick O’Rourke

What you won't see at VMworld 2009 - a demo of SCVMM 2008 R2

porourke — Tue, 25 Aug 2009 03:32:00 GMT

Ordinarily it'd be great news that we RTM'd System Center Virtual Machine Manager 2008 R2 ahead of schedule, so close to the RTM of WS08 R2 Hyper-V and one week before VMworld conference. You can't beat the timing of it all. And the ~10,000 beta testers of SCVMM08 R2 are a big part of why we were able to deliver a high-quality release in the time we did. Some of the early adopters included Continental Airlines, Lionbridge Techologies, Sporton, Indiana University Auxilary IT and MaximumASP. Thanks to all!

But unfortunately, next week at VMworld 2009 we can't show SCVMM 2008 R2, or any other products, in our booth. You've probably read about it. In short, it's their show, it's not an industry show, and they set the rules. So we'll make the best of it; always lots of Microsoft customers and partners on the floor. Stop by the booth to meet some of the best/brightest minds at Microsoft.

As for the RTM of SCVMM 2008 R2, Zane summarizes his thoughts here. Kerim blogged about upgrade path to R2 from SCVMM 2008. See here. And on May 11, Vishhwa provided some details on features of SCVMM 2008 R2 here.

As Cheng wrote in his blog (I can't say it any better)

Go download a trial and give it a try, go get it now, and unleash the virtualization power that Microsoft brings to you.

Patrick

Promotion of Brad Anderson to Corporate Vice President, Management and Services Division

larrygrothaus — Tue, 28 Jul 2009 23:16:00 GMT

It comes as no surprise to the regular readers of this blog, that a key tenant of Microsoft’s virtualization strategy is that customers should be able to manage their physical and virtual IT resources from the same set of easy to use tools. It seems that customers agree, as demonstrated through the growth of the Microsoft Management and Services Division (30% growth year over year) offerings during some challenging economic times.

Today we’ve announced that Brad Anderson, one of the key drivers behind Microsoft’s management offerings, including the System Center suite and products such as VMM, has been promoted to corporate vice president. We wanted to share the news with those of you that have worked with or met him over the years through events such as the annual Microsoft Management Summit conference. Congratulations Brad!

Microsoft’s new VDI licensing: VDI Suites

porourke — Tue, 14 Jul 2009 00:48:00 GMT

Hi, my name is Manlio Vecchiet, and I am a director of product management on the Windows Server marketing team. I'm in New Orleans right now attending the Microsoft Worldwide Partner Conference (WPC), and wanted to update you on new licenses we’ll offer for hosted virtual desktops, or virtual desktop infrastructure (VDI).

When deciding whether to implement or even pilot VDI, most customers look for technical integration of the key VDI building blocks:

· the hypervisor,

· management of the virtual machines and the (physical) VDI host,

· a brokering and remoting infrastructure, and

· an application delivery technology for dynamic provisioning of applications to virtual desktops.

But customers also look for a simple and cost-effective way to license this scenario, as they will compare the technical and business benefits of VDI with more traditional desktop deployment options, such as session-based desktops and rich clients. Today we introduced two new licenses for VDI – the Microsoft Virtual Desktop Infrastructure Standard Suite and the Microsoft Virtual Desktop Infrastructure Premium Suite. These licenses make it simple for customers to purchase the comprehensive Microsoft VDI technologies while providing excellent value compared with competing VDI offerings. The new VDI suite licenses will be available via Microsoft volume licensing in calendar Q4.

This is a pretty big deal, so let me explain what we mean by comprehensive, simple and excellent value. First, both new offerings include licenses for all the key technology components mentioned above when used in a VDI scenario: Hyper-V Server, System Center Virtual Machine Manager, System Center Configuration Manager, System Center Operations Manager, Remote Desktop Services (CAL) and MDOP. The Premium VDI Suite even includes additional use rights for Remote Desktop Services (RDS) as well as App-V for RDS, to enable mixed environments with not only VM-based remote desktops, but also session-based desktops and applications. With these two new offerings, the only additional license you will need to correctly license a VDI environment from Microsoft is Virtual Enterprise Centralized Desktop or VECD (you will need VECD even to deploy VDI on a non-Microsoft platform)

By now, you are probably wondering how the licensing of these new VDI Suites will work given their standalone components have very different license schemes. The two new VDI Suites are designed to match the VECD license (which is a device subscription), so the math has become very simple now: As with VECD, the number of VDI Suite licenses equals the total number of client devices that accesses the VDI environment. The subscription-based license will ensure that customers always have access to the latest versions of the software.

But now comes actually the best part. At only $21 per year per device, the VDI Standard Suite is about one-third the cost of a corresponding VMware View edition (the comparison is based on the cost of licenses and software maintenance over a five-year period, which many customers tell me that’s what they base their desktop infrastructure investments on). Similarly, our VDI Premium Suite is about half the price of the premier VMware VDI offering, and it also offers the capability to deploy session-based desktops and applications, in addition to VM-based desktops. And for those customers who are still missing a feature or need an enterprise-ready solution, you can add a 3^rd party connection broker for Hyper-V such as Citrix XenDesktop - and most likely still pay less than if you chose to deploy VMware. In fact, Citrix today announced continued alliance in the area of desktop virtualization.

If you would like to see a demo of Microsoft VDI solution running on Windows Server 2008 R2, please come to the Microsoft booth at WPC if you’re attending the conference. For all others, please post your comments in the section below.

Manlio

UPDATE: to answer morriswj's question. I'm excited, too, about this new single licensing for VDI’s server infrastructure, which will complement VECD for a VDI deployment. Regarding High Availability, it is included in MS Hyper-V Server 2008 R2 (the no-cost, standalone hypervisor) and will therefore be available as part of the VDI Suite offering. No other license other than VDI Suite (Standard or Premium) and VECD will be required for a highly available VDI deployment.

UPDATE 2: I'm responding to the question from cstalhood, and the similar question in Brian Madden's post today. For session virtualization using WS08 R2 Remote Desktop Services (RDS), you don’t need the VECD license. The Premium VDI Suite license includes full rights of the RDS CAL, in addition to the other components for a VDI solution. The Premium VDI Suite license, when available in Q4, will be available as a device subscription, while RDS CAL (the new name for TS CAL) is available as a perpetual user or device license. After all, some customers don’t want to buy on a subscription basis.

Windows Server 2008 R2 Core: Introducing SCONFIG.

WSV_GUY — Tue, 07 Jul 2009 16:27:00 GMT

Virtualization Nation,

It's been very busy in the world of Windows Server. With the launch of Windows Server 2008 R2 Release Candidate, Tech Ed and the announcement of several new Hyper-V R2 capabilities such as 64 logical processor support and processor compatibility, it's been pretty non-stop. In fact, it's been so busy, that we haven't even had a chance to introduce one more really cool new feature in Windows Server 2008 R2, but first, some background.

Windows Server 2008 R1: Core Deployment

In Windows Server 2008, we introduced the ability to deploy Windows Server in a core deployment. Server Core is a minimal server installation option which provides a low-maintenance server environment with limited functionality. Just to be clear, Server Core isn't a SKU. You don't buy "Server Core" it's simply a deployment option presented during Windows Server Setup. For example, here's a screen shot during Windows Server Setup, notice that there are options for Full Installations and Server Core Installations.

The benefits are smaller attack surface, a reduction in patches and reduction of server reboots. If you compare the number of reboots between running a server running Windows Server 2008 core deployment versus Windows Server 2008 a full installation, there's a substantial reduction in the number of reboots which, in turn, helps reduce management costs.

While customers like the idea of core installations, the fact that a server core deployment is a command-line interface (CLI) only (no GUI, no Start Menu, etc) with a very differently deployment mechanism introduces a challenging learning curve for those considering core deployments. For those of you who've never seen a Windows Server 2008 server core deployment it looks like this:

Pretty spartan.

As you can see, there's no Start Menu. It's all command-line all the time. For enterprise customers, this isn't a big deal because very often they deploy Windows Server in an automated fashion. However, for small and mid-sized customers a command-line only interface can make some of the most rudimentary tasks a challenge. For example, here are the commands to rename your computer and then join a domain via a Windows Server 2008 core deployment.

Rename your computer: netdom renamecomputer %computername% /newname:<new_computername>
Domain join: netdom join %computername% /domain:<domain> /userd:<username> /passwordd:*

Not the easiest thing to remember. We knew we could do better.

Improving Usability

While Windows Server 2008 R1 was in development, a few of us were quietly working on the Hyper-V Server 2008 standalone SKU which also uses a CLI. We spent time working on improving the server configuration experience with an easy to use CLI called HVCONFIG. Within hours of our first private releases of Hyper-V Server 2008 to testers, we received email asking/begging/pleading/cajoling/offering bribes for a similar tool for Windows Server as well.

Happy to oblige.

Introducing SCONFIG for Windows Server 2008 R2 Core Deployments

We are pleased to announce that in Windows Server 2008 R2, there's an easy to use CLI, SCONFIG. SCONFIG dramatically eases server configuration for Windows Server 2008 R2 core deployments. With SCONFIG, you can easily set your system up, get it on the network so you can easily manage the server remotely.

Rename your computer? Press 2 and you will be prompted to type in the computer name.
Domain join? Press 1 and you'll be prompted for name & password.

Simple and fast.

With SCONFIG you can easily have a Windows Server 2008 R2 Server Core deployment setup in minutes. I should also mention that SCONFIG is also localized in almost 20 languages.

Tasks include:

Domain join
Rename Computer
Configure Remote (Enable management via Server Manager, & PowerShell including properly configuring the firewall.)
Configuring Windows Update
Enabling Remote Desktop (in case you want to login remotely.)
Configuring Networking (static vs. DHCP and for multiple NICs)

All you have to do is type sconfig at the command line.

Great! Now What?

Remember, the goal with a server core deployment is to get the server on the network so you can manage it remotely. With SCONFIG this is a snap. Now from another system you can enable roles, run PowerShell scripts, manage it using System Center, manage it using Server Manager from another server running Windows Server 2008 R2, or manage it using the free Remote System Administration Tools (RSAT) for Windows 7.

In short, our goal is to provide customers multiple solutions based on their business needs.

Cheers,

Jeff Woolsey

Principal Group Program Manager

Windows Server, Hyper-V

System Center Virtual Machine Manager 2008 R2 - Quick Storage Migration

WSV_GUY — Thu, 25 Jun 2009 16:30:00 GMT

Hi, I'm Edwin Yuen, a Senior Technical Product Manager at Microsoft's Integrated Virtualization team. In today's blog, I'd like to discuss another type of migration being added to System Center Virtual Machine Manager 2008 R2, Quick Storage Migration.

Quick Storage Migration (QSM) In Brief

As you may have seen, we recently released the Release Candidate for System Center Virtual Machine Manager 2008 R2. One of the most anticipated features of SCVMM 2008 R2 is Quick Storage Migration (QSM) which enables the migration of the storage of VM from one location to another. For example, suppose you have virtual machines on a leased SAN (SAN 1). The lease runs out and you decide to upgrade to a new SAN (SAN 2) with more capacity, better performance and additional capabilities. Quick Storage Migration allows you to move the virtual machine which resides on SAN 1 to SAN 2. I have had a number of request for more details on how this works so we've written this brief guide to QSM. (In addition, we wanted to make this technology broadly available, not just the biggest enterprises. More on that below.)

QSM relies on Windows Server 2008 R2 Hyper-V and Background Intelligent Transfer Service (BITS). QSM can move the virtual disks of a running virtual machine independent of storage protocols (iSCSI, FC) or storage type (local, DAS, SAN), with minimal downtime.

QSM Is One of Many Migration Technologies Supported in Virtual Machine Manager's Portfolio

VM Migration Type	Platforms available on	Technology used for transfer	Expected downtime for VM
Live Migration	Hyper-V (2008 R2) ESX 3.0, 3.5	Windows Server 2008 Failover Cluster Hyper-V vMotion for ESX	None No service interruption while virtual machine is moved
Quick Migration	Hyper-V	Windows Server 2008 Failover Cluster Hyper-V	Under 1 minute in most cases VM is put into save-state while it is moved from one cluster node to another using the cluster failover mechanism
SAN Migration	Virtual Server Hyper-V	Windows Server 2008 Hyper-V and Virtual Disk Service (VDS) Hardware Providers N-Port Identification Virtualization (NPIV) on Emulex and QLogic Fibre Channel HBAs iSCSI on EMC, HP, Hitachi, NetApp, EquiLogic arrays	Under 1 minute in most cases VM is put into save-state while it is moved from one virtual machine host to another using unmasking and masking operations at the SAN level
Network based migration (aka LAN migration)	Virtual Server Hyper-V ESX	BITS for Virtual Server and Hyper-V sFTP for ESX	Minutes to hours (W2K8, W2K3 hosts) VM needs to be stopped or in saved state for the entire duration of transfer Under 1 minute in most cases (W2K8 R2) VM can remain running for the almost entire duration of the transfer of its virtual disks from once storage location to another VM is put into save-state for a brief interval to migrate its memory state and associated differencing disks.

Storage Migration Type

Platforms available on

Technology used for transfer

Expected downtime

Storage vMotion

ESX 3.5

Storage vMotion

None

No perceived service interruption while the virtual disks associated with a virtual machine are moved from storage location to another

Quick Storage Migration

Hyper-V
(2008 R2)

BITS and Hyper-V

Under 1 minute in most cases (W2K8 R2)

VM can remain running for the almost the entire duration of the transfer of its virtual disks from once storage location to another
VM is put into save-state for a brief interval to migrate its memory state and associated differencing disks.

Note on Processor Compatibility Mode:

To increase the mobility of a running virtual machine across hosts with different processor versions (with in the same processor family), Windows Server 2008 R2 Hyper-V offers Processor Compatibility Mode. This feature masks processor feature differences between the source and destination hosts. With this enabled, you can migrate a virtual machine from a host with Pentium 4 VT processors to a host with Nehalem processors. Processor Compatibility Mode does not require advanced processor features like Intel VT Flex Migration or AMD-V Extended Migration. For more on Processor Compatibility Mode, check out Jeff's Blog a few weeks ago where he goes into detail here.

How QSM Works

QSM uses native Windows platform technologies: Hyper-V and BITS. There are 2 scenarios of interest:

Scenario 1: VM Storage Migration: VM Compute Stays on the Same Server and the VM Storage Migrates from One Storage to Another

1. In the SCVMM console, a new action labeled Storage Migration is now available.

2. When the user right-clicks on a running virtual machine and selects the Migrate Storage action, a wizard is presented. The user provides the path to the new location to be used by the VM. If all the VMs files (configuration and VHD files) are to be placed in a single location the user has only to provide the "Virtual Machine Path". If one or more VHD files for the VM need to be placed at a separate location, the user can explicitly change the location of each VHD by selecting it from the list under "Disks" and clicking the "Browse" button next to it to specify the path for the VHD.

3. SCVMM takes a Hyper-V snapshot of the running virtual machine. This will create a differencing disk for each VHD connected to the VM. All disk write operations from that point forward go into the differencing disk. The original base VHD is no longer changing since it is in a read-only state.

4. With the base VHD in a read-only state, SCVMM starts to transfer the file from the source location to the target location using BITS. This represents the bulk of the data that needs to be transferred and the VM remains running during this transfer. In addition, QSM does not depend on storage types, and the user is free to select any storage destination that is accessible to the Hyper-V host.

5. Once the base VHD is transferred, the virtual machine is put into "Saved State".

6. In "Saved State", SCVMM can transfer the differencing disk created by the snapshot and memory associated with the "Saved State" to the destination location for the VM.

7. Once all the files are transferred, SCVMM exports and then re-imports the virtual machine on the same Hyper-V host with any necessary modifications to the configuration.

8. The snapshot created on step 3 is merged back into the base VHDs

9. Virtual machine is re-started from saved state

10. Job completes

11. The diagram below illustrates the steps performed by QSM on a Hyper-V R2 host.

Scenario 2: VM Migration (Relocation): VM Compute Moves to a News Server AND VM Storage Moves from One Storage to Another

1. In the SCVMM console, the user right-clicks on a running virtual machine and selects the Migrate action, a wizard is presented to help with the migration. The Migrate action initiates the migration of a VM from one host to another host. As part of the VM migration, all of the VMs files are moved to storage that is attached to the destination host. Storage Migration technology enhances the experience by allowing the move for a running virtual machine and limiting the down time of the VM to just the window required to move the save state files (as explained below).

2. The user first selects the destination host based on the desired star rating presented by Intelligent Placement. The user then provides a destination folder for the configuration file and the associated virtual disks. By default, the wizard will put all disks in the same location as the configuration file. After completing the wizard, the migration job is submitted.

3. SCVMM creates a placeholder virtual machine on the destination host. The virtual machine is not powered on so there is no need to reserve CPU or memory resources at this time. Intelligent placement has already accounted for the impact on the destination host of the VM being migrated.

4. SCVMM takes a Hyper-V snapshot of the running virtual machine. This will create a differencing disk for each VHD connected to the VM. All disk write operations from that point forward go into the differencing disk. The original base VHD is no longer changing since it is in a read-only state.

5. With the base VHD in a read-only state, SCVMM starts to transfer the file from the storage location on the source host to a storage location on the target host using BITS. Since QSM does not depend on storage protocols or storage types, the user is free to select any storage destination as long as the Hyper-V can access it.

6. Once the base VHDs are transferred, the virtual machine is put into Saved State.
In Saved State, SCVMM can transfer the differencing disks created by the snapshot and associated memory state.

7. Once all the files are transferred, SCVMM exports the virtual machine and transfers the exported virtual machine configuration to the target host and then imports the virtual machine to Hyper-V host with any necessary modifications to the configuration.

8. The snapshots are merged back into the base VHDs as part of the import process.

9. Virtual machine is started from saved state

10. Job completes

How QSM Compares To VMware Storage VMotion

	VMM 2008 R2 + Windows Server 2008 R2 Hyper-V	VMware (vCenter 2.5 + ESX 3.5)
Migration of virtual machines across two hosts with independent storage	Supported	Not Supported
Migration of virtual machines with snapshots	Supported	Not Supported
Migration of Virtual machine with Virtual Disks	Supported	Supported (persistent mode)
Requires sufficient resources to support two instances of the virtual machines running concurrently	Not Required	Required
Additional Licensed Required	None	VMotion License
Number of concurrent storage Migrations allowed	10	4
Storage Migrations supported in the Administrator Console	Yes (QSM and Storage vMotion)	No
Storage Migrations supported in the CLI	Yes (QSM and Storage vMotion)	Yes
Protocol agnostic	Yes	Yes
Support for migrations of VMs and storage between hosts with different processors versions (same manufacturer)	Yes (use Hyper-V R2 Processor Compatibility Mode to increase the number of compatible hosts )	Not Applicable

Microsoft: Driving Down Costs

One thing our customers have been telling us loud and clear is that they are very, very happy we are offering Live Migration for FREE with Hyper-V R2. With Quick Storage Migration, we knew we had another opportunity to drive down the costs for storage migration capability that has been largely priced out of the reach of most customers. Specifically, VMware Storage VMotion is only available in their Enterprise/Enterprise Plus SKUs ($2875 & $3495 per processor respectively). Contrast this with the fact that Quick Storage Migration is included with System Center Virtual Machine Manager 2008 R2 both the Enterprise Edition and the Workgroup Edition which will be available for starting at about $500.

For a small five node cluster consisting of two and four processors servers, that would cost at a minimum:

	Virtual Machine R2 QSM	VMware
Three Nodes; Two Processor Servers	~$500	$11,500
Five Nodes; Two Processor Servers	~$500	$28,750
Five Nodes Four Processor Servers	~$500	$57,500

That's customer focus.

Cheers,

Edwin Yuen

Sr. Technical Product Manager

Guest post: Hyper-V gives every Windows shop a free pass into “innovation”

porourke — Mon, 22 Jun 2009 21:39:00 GMT

Hi, my name is Matt Lavallee and I am the Director of Technology at MLS Property Information Network, Inc., based in Massachusetts. Although you may not recognize the company name, we are one of the 700+ multiple listing service (MLS) companies that provide data warehousing for the Real Estate industry in the U.S. As my company took the early step to virtualizing our environment on Hyper-V last year, Microsoft asked me to share my opinion on the results of its recent survey on the state of IT infrastructure investments, conducted by Harris Interactive.

One point that stands out on the survey — and should surprise no one — is the shift to belt-tightening in IT: 84% of US respondents cited improving business efficiency (51%) and reducing IT costs (33%) as their priorities in light of the economic downturn. However, I personally disagree that this new mindset is a direct reaction to the economy or that the decreased allocation of IT budget to innovation (29% in the US) are necessarily bad things.

First, let us consider that the IT budget is a relatively fixed value year over year — while it may respond to inflation and some cyclical purchases, the vast majority of budget is spent on payroll, annualized licensing, backups, ISP costs, and the regular refresh of equipment. To me, this eliminates a significant stratum of budget from consideration for “innovation” unless you just built your environment last year on five-year-old technology.

Second, the actual varying allocation of budget goes to “special projects”, which, for lack of a better term, includes “innovation”. Here is where the survey findings drew too many conclusions and where I feel the indication is astray from real trends.

Consider my environment: We recently made the switch to virtualization and the broad deployment of Hyper-V. This included a change in direction for our hardware refresh (bigger servers), incremental SAN purchases, and some new investment in networking (10GbE)… perhaps enough to reflect the 25% investment in “innovation”, per the survey. A balance sheet, however, would not reflect that we redesigned the entire infrastructure and now run up to 60% more efficiently: all you will see is a marked decrease in operational overhead at the end of the year (i.e., improved business efficiency and reduced IT costs, as the survey reflected).

So why is there no correlation between advancing the infrastructure and innovation spending? I believe that the technology ecosystem has afforded smarter IT spending, particularly with the (dramatic) rise in computing density, the problems it has solved and challenges it introduced, and the tools that were created (or improved) to meet those challenges. PUE (Power Usage Effectiveness) and “green” concepts were alien just five years ago, but now dominate most datacenter conversations. Virtualization via Hyper-V gives every Windows shop a free pass into “innovation” and grants us many new opportunities that were previously out of budgetary reach.

Some question whether this change indicates that IT is no longer aligned with business goals and driving success… I offer that our current focus clearly demonstrates that we are doing exactly what the business needs us to do.

Matt

Re: Windows Server 2008 SP2 Hyper-V

porourke — Wed, 17 Jun 2009 19:51:00 GMT

Hi Isaac Roybal here. I’m a technical product manager on the Windows Server team covering Hyper-V.

It’s been 3 weeks since the release of Windows Server 2008 Service Pack 2 (SP2) and we’re seeing great adoption. From a Hyper-V point of view, we’re excited because the final Hyper-V release is an integrated feature in SP2 making it easier and faster to deploy Hyper-V. If you recall, when Windows Server 2008 was released, Hyper-V Beta was included. This meant to get the final Hyper-V release, you needed to go to Windows Update, download and go through the update process.

With Windows Server 2008 SP2, Hyper-V final bits are included so there’s no need to pull down individual downloads which speeds up deployments. There are also some notable updates in SP2, including scalability enhancements for running on systems with up to 24 logical processors which enables support for up to 192 running virtual machines, update for Hyper-V when managed with System Center Virtual Machine Manager 2008 and updates for backup/restore of virtual machines with the Volume Shadow Copy Service (VSS).

For those of you who have already deployed Hyper-V, SP2 is a simple upgrade. Here are a couple of top-of-mind things to think about when you’re planning your upgrade or fresh install of SP2:

· In-place upgrades of Windows Server 2008 to Windows Server 2008 SP2 is supported for both the parent partition and child VMs.

o If the Hyper-V role was enabled on the parent partition prior to the upgrade to SP2, it will be automatically enabled once the upgrade is completed.

o Uninstall any prerelease versions of SP2 that might be installed.

· If a fresh SP2 install is being done and you’d like to move VMs to it, export the VMs from the originating Windows Server 2008 host and import them on the SP2 host.

· Integration Components (ICs) for the child virtual machines must be updated to the SP2 version.

o If you’re doing a fresh install or an upgrade of SP2 on the parent partition, it does not update the integration components inside the virtual machine. Be sure to update the VM ICs after SP2 is installed.

o If you have virtual machines created on the Beta version of the Windows Server 2008 Hyper-V role, and you installed the Beta version of the integration components on those machines, you must uninstall the integration components and reinstall the latest SP2 integration components.

o When upgrading to SP2 inside a Windows Server 2008 child VM the ICs are automatically upgraded.

o If you are running a supported Windows operating system other than Windows Server 2008 as a VM, you need to use vmguest.iso to upgrade the integration components

Isaac

UPDATE. Responding to question by Ed051042

Yes, your assertion is correct. Follow these steps when upgrading a cluster to SP2:

1. Evacuate the cluster node of VMs via quick migration (assuming you’ve extra capacity) to other nodes in the cluster.

2. Upgrade the node to SP2 while it is still part of the cluster

3. Once the SP2 install is complete, quick migrate those VMs back to node and update VMs’ ICs. The last bit is important.

4. Follow the same process starting step #1 until entire cluster had been updated to SP2

For more info see KB 174799 which outlines how to install SPs on a cluster and Microsoft's Failover and Network Load Balancing Clustering Team Blog which explains a rolling upgrade of a cluster.

Check out the Visual Studio Team System blog

porourke — Fri, 12 Jun 2009 20:54:00 GMT

Many of you will be interested to learn more about forthcoming lab management capabilities in Visual Studio Team System 2010. Or you may have lunch or meetings with a dev who you want to know more about VSTS 2010 Lab Management. That last part is a nod to "that darn reality" post at SharkTank.

So check the VSTS Lab Management team blog.