Many of you would like to know how Virtual Server is being used at Microsoft. Here's a response from Jeff Woolsey, Lead Program Manager for virtualization. Thanks Jeff!

Virtual Server is being used in a variety of ways at Microsoft, including for test and development and online training, such as Microsoft Learning.

Test and Development

Virtual Server is used by test teams throughout Microsoft, including Exchange, SQL, SBS, MOM, and many others. This is because Virtual Server allows you to rapidly deploy test servers within virtual machines while minimizing hardware requirements. Also, Virtual Server makes debugging easier. Debugging typically requires that a test computer is attached to a developer’s computer via a serial cable. With Virtual Server there's no need for this. The process is as follows:

1. Testers reproduce the issue in a virtual machine.
2. The virtual machine is saved at the point the issue occurs.
3. The virtual machine is copied to the developer’s computer.
4. The developer connects the virtual machine to a debugger though a named pipe (a virtual serial port) and debugs the issue in the development environment.

Production Use by Microsoft Learning

In the past year, Microsoft Learning has converted the majority of their online training from scripted Flash-type demos to live interactive training using Virtual Server. They started off slowly and have been ramping up with the increase in demand. Users log in and perform step-by-step interactive training with Virtual Server. On the back end, this is all done using virtual machines and Undo disks. When the customer logs in, an Undo disk is created for the session. When the user finished and logs out, the Undo disk is discarded and immediately the virtual machine is ready for the next user.

Benefits

Microsoft Learning is servicing more customers than ever. This is a production environment in use everyday: 30,143 attendees in January (972 attendees daily) alone with a 206,390 YTD. Because of the huge success of this program, Microsoft Learning is adding more hardware to increase the number of available labs.

Here are a few of the positive results they’ve seen…

• The 90-minute lab sessions are the most popular.
• Lab session use has gone up.
• Time spent in the lab has gone up (averaging 75 minutes per lab now).
• Customer satisfaction is up (way up!).

Customer Comments

• I think this is the way IT was meant to be all along.  Thank You Bill and company. 
• The implementation is entirely innovative and gives administrators like me a chance to experiment away from production systems.
• Awesome. This is the type of thing IT training has needed for ages.
• Excellent. Very useful hands on training.  This module needs to be longer.
• EXCELLENT!  This is extremely useful hands on training.
• Great! This is what admins who need to implement your products need. What about providing other training on SMS site design configurations, clusters etc.? A virtual lab setup like that will again help admins who are looking to implement this product.

If you're connected to Virtual Server over a Terminal Services or Remote Desktop connection, you'll get a "Page cannot be displayed" error if you try to launch the Administration Website from the shortcut on the Start menu. Instead, you can provide this URL in Internet Explorer: http://server_IP_address:VS_port, where server_IP_address is the IP address of the computer running Virtual Server and VS_port is the port number assigned to Virtual Server, 1024 by default.

Alternatively, you can remote into the computer running Virtual Server and access the Administration Website in one step. To do this, click Start > Run, and then type: mstsc /v:server_IP_address /console.

If you want to turn off the beep that sounds when you turn on a virtual machine, you can run the following two commands. The first stops the BEEP service and the second disables it on subsequent reboots.

 net stop beep

sc config beep start= disabled 

(Be sure to include a space after the = sign.)

If you want your applications to install more quickly in a virtual machine, do this: After you install the guest operating system, install Virtual Machine Additions, restart the virtual machine, and then install the applications.

Here's a tip from Paul Adare (author of Paul's Digital Lounge and Cigar Bar). If you want an application to discover it's running in a virtual machine, you can do the following:

You could query the registry for the existence of the HKLM\SOFTWARE\Microsoft\Virtual Machine key. Or you could use an WMI query, such as this:

On Error Resume Next

strComputer = "."

Set objWMIService = GetObject("winmgmts:\\" & strComputer & "\root
\cimv2")

Set colItems = objWMIService.ExecQuery("Select * from Win32
_BaseBoard",,48)

For Each objItem in colItems

if objitem.Product = "Virtual Machine"