We'll be updating our Configuring a Remote Instance of SQL Server topic very soon with some new information, as noted below - feeback welcome.

Configuring the Remote Instance of SQL Server

On the remote instance of SQL Server that you specify during Setup:

·         Enable remote connections.

Note   By default, Microsoft SQL Server 2005 Express Edition, Microsoft SQL Server 2005 Evaluation Edition, and Microsoft SQL Server 2005 Developer Edition are configured to allow only local connections. For more information about these configurations, see SQL Server Books Online (http://go.microsoft.com/fwlink/?LinkId=98779).

Do one of the following:

•  Assign the instance its own TCP/IP port, and then connect explicitly to that port.
•  Turn on the SQL Server Browser service.

Important   Turning on SQL Server Browser allows connections from the Internet to your computer. For security purposes, you might want to leave SQL Server Browser off on computers that are directly connected to the Internet. For more information, see SQL Server Books Online. By default, the SQL Server Browser service is disabled in SQL Server 2005 Express Edition.

·         The SQL Server must running with the Local System account. If is running with the Network Service account or a domain account, you must create a Service Principal Name (SPN) for the SQL service as described in article 811889 in the Microsoft Knowledge Base (http://go.microsoft.com/fwlink/?LinkId=88057).

The issue arises if you install with a remote instance of SQL, and the instance starts under a domain service account instead of network service.  This causes VMM to fail to connect. If you then start VMM service with a network service account instead of local system, the SQL connection works but other things (like P2V) fail.

VMM does not install VM Additions for you. For example, assume you have just converted a physical server (P2V). You need to install the VM Additions. There are two ways:

• Administrator Console
• CLI 

If you have to do this once, you will probably have to do it again. First copy the VMAdditions.iso file to your Library. 

The VM does not need to be running in order to attach an ISO to a Virtual DVD drive, but the VM does need to be running in order to install VM Additions.

To install Virtual Server additions in the VM:

1.        In the Administrator Console, select the VM and view Properties.

2.        On the Hardware Configuration tab, select the Virtual DVD Drive.

3.        Choose Known Image File and Browse to VmAdditions.iso.

4.        Select Use ISO from Library instead of copying.

5.        Go into your Guest, run the CD, and install the additions.

6.        Allow the Guest to reboot as needed.

PowerShell Script

# Install-VMAdditions.ps1

$vm = $args[0]

if ( $vm.Status -eq ‘Running’ )

{

$vmadditions = get-iso | where { $_.Name –eq ‘VMAdditions’ }

Set-VirtualDVDDrive –VirtualDVDDrive $vm.VirtualDVDDrives[0] -Link –ISO $vmadditions

}

else

{

write-host "The VM must be Running before you can install VM Additions."

}

To use this script, enter the following commands:

$vm = get-vm –Name “My VM”

C:\Scripts\Install-VMAdditions.ps1 $vm

The VM Additions installer will launch automatically inside the guest OS.

The following information on scripting the installation of VM Additions using VMM/PowerShell is copied from the VMM Scripting Guide, coming to the SCVMM Library on TechNet soon.

InstallVMAdditions.ps1

You can use the InstallVMAdditions.ps1 script to install Virtual Machine Additions on virtual machines that are managed by Virtual Machine Manager.

For any virtual machine to function well, you must install Virtual Machine Additions on that virtual machine. Virtual Machine Additions, which is provided by Virtual Server 2005, improves the performance of the guest operating system, enables the free movement of the mouse between the virtual machine window and the host operating system, optimizes video drivers, and supports time synchronization.

For a related script that identifies which virtual machines in your Virtual Machine Manager environment do not yet have Virtual Machine Additions installed, see NeedVMAdditions.ps1 in the topic, "Sample Job-Related Scripts" in the VMM Scripting guide.

Define Variables for InstallVMAdditions.ps1

The first commands in InstallVMAdditions.ps1 define variables that the script uses to install Virtual Machine Additions. As indicated in the comment introducing $LinkIso, you have the option to set $LinkIso to $TRUE or $FALSE depending on whether you want to link to the VMAdditions.iso or copy it onto the virtual machine.

####################################################################

# Define variables.

####################################################################

$VMMServer = "localhost"

$VMNameToInstallVMAdditions = "VM01"

# If you want to link to VMAdditons.iso in the Virtual Machine Manager

# library, set $LinkIso to $TRUE; alternatively, if you want to copy

# VMAdditions.iso to the VM, set $LinkIso to $FALSE.

$LinkIso = $FALSE

Connect to the Virtual Machine Manager Server

The next command in InstallVMAdditions.ps1connects to the Virtual Machine Manager server so that subsequent commands can access objects in the Virtual Machine Manager database.

####################################################################

# Connect to the Virtual Machine Manager server.

####################################################################

$C = Get-VMMServer $VMMServer

Get the Virtual Machine on Which to Install Virtual Machine Additions.

The next command in InstallVMAdditions.ps1 retrieves the object that represents the virtual machine whose name was stored earlier in variable $VMNameToInstallVMAdditions.

####################################################################

# Get the VM on which you want to install VM Additions.

####################################################################

$VM = Get-VM | where {$_.Name -eq $VMNameToInstallVMAdditions}

Install Virtual Machine Additions or Display an Error Message

The next set of commands in InstallVMAdditions.ps1 performs a series of nested tests to determine whether it is possible to install Virtual Machine Additions and, if any test fails, displays an error message indicating what you need to do to solve the problem.

·         Is the virtual machine installed on a host?

·         If yes, continue to the next question.

·         If not, the script ends and displays a message indicating that it cannot install Virtual Machine Additions because the virtual machine is currently stored in the library. You must deploy the virtual machine on a host and then run the script again. For more information, type the following command at the command prompt:

Get Help Move-VM -detailed

·         Does the virtual machine have at least one virtual DVD drive?

·         If yes, the script does the following:

Stores host object. Stores the object that represents the host on which this virtual machine is deployed in variable $VmHost.

Stores ISO name string. Uses the command segment $VmHost.VirtualizationStack to determine which version of Virtual Server is running on the host (because Virtual Machine Additions varies depending on the Virtual Server version); concatenates the Virtual Server version with the string " VMAdditions"; and then stores the resulting name in variable $Isoname. The example assumes that Virtual Server version plus " VMAdditions" is the naming convention that is used to identify different versions of Virtual Machine Additions.

Gets ISO object. Gets the object that represents the Virtual Machine Additions .iso file in variable $VmAdditions.Iso.

Continue to the next question.

·         If not, the script ends and displays a message indicating that it cannot install Virtual Machine Additions because no virtual DVD drive exists on the virtual machine. You must configure a virtual DVD drive for this virtual machine and then run the script again. For more information, type the following command at the command prompt:

Get-Help New-VirtualDVDDrive -detailed

·         Does at least one Virtual Machine Additions .iso file (of the correct version) exist in the library?

·         If yes, continue to the next question.

·         If not, the script ends and displays a message indicating that it cannot install Virtual Machine Additions because no Virtual Machine Additions .iso file exists in the Virtual Machine Manager library. You must add an .iso file for Virtual Machine Additions to a Virtual Machine Manager library share and then run the script again.

After you add the .iso file to a library share, the Virtual Machine Manager refresher automatically scans the share, discovers the new .iso file, and adds an object that represents the .iso file to the library catalog. Alternatively, you can use the Refresh-LibraryShare cmdlet to refresh the library share immediately.

For more information, type the following command at the command prompt:

Get-Help Refresh-LibraryShare -detailed

Note   You can copy the VMAdditions.iso file from Microsoft Virtual Server 2005, which is installed by default with Virtual Machine Manager. You can find the VMAdditions.iso file in Windows Explorer at <C>:\Program Files\Microsoft Virtual Server\Virtual Machine Additions.

·         Do you want to link to or copy the .iso file? 

·         Link to? If you have set $LinkIso to $TRUE, the script uses the pipeline operator (|) to pass the first virtual DVD drive (indicated by [0]) on the virtual machine to the Set-VirtualDVDDrive cmdlet, which links to the Virtual Machine Additions .iso file in the library.

The command segment -Bus $VM.VirtualDVDDrives[0].Bus -Lun $VM.VirtualDVDDrives[0].Lun must be specified when changing the attached .iso file of a virtual DVD drive. In this case, the script does not modify where the virtual DVD drive is attached, so it simply sets the -Bus and -Lun parameters to the current Bus and Lun settings. Finally, the script stores the resulting object in variable $DVDDrive in case you want to use this variable later on.

·         Copy? If you have set $LinkIso to $FALSE, the script uses the pipeline operator (|) to pass the first virtual DVD drive (indicated by [0]) on the virtual machine to the Set-VirtualDVDDrive cmdlet, which copies the Virtual Machine Additions .iso file onto the virtual machine.

The command segment -Bus $VM.VirtualDVDDrives[0].Bus -Lun $VM.VirtualDVDDrives[0].Lun must be specified when changing the attached .iso file of a virtual DVD drive. In this case, the script does not modify where the virtual DVD drive is attached, so it simply sets the -Bus and -Lun parameters to the current Bus and Lun settings. Finally, the script stores the resulting object in variable $DVDDrive in case you want to use this variable later on.

Note   The second command omits the -Link parameter but uses the $FALSE value specified earlier. By default, if -Link is omitted, the Set-VirtualDVDDrive cmdlet copies a file rather than linking to it.

·         Link to or Copy—same result: After the script either runs the command to link to the Virtual Machine Additions .iso file in the library or runs the command to copy the .iso file to the virtual machine, the script displays a message indicating that the Virtual Machine Additions .iso file is now attached to the virtual machine and requests the user to start the virtual machine and install Virtual Machine Additions from the virtual DVD drive.

####################################################################

# Install VM Additions or (if not possible) display an error message.

####################################################################

if($VM.HostType -eq "VMHost")

{

    if($VM.VirtualDVDDrives.Count -gt 0)

    {

      $VmHost = $VM.VMHost

      # The segment$VmHost.VirtualizationStack returns the version

      # of Virtual Server running on this host.

      $IsoName = $VmHost.VirtualizationStack +" VMAdditions"

      $VmAdditionIso = Get-ISO | where {$_.Name -eq $IsoName}

      if($Null -ne $VmAdditionIso)

        {

          if($LinkIso -eq $TRUE)

          {

              $DvdDrive = $VM.VirtualDVDDrives[0] | set-VirtualDVDDrive -ISO $VmAdditionIso -Link -Bus $VM.VirtualDVDDrives[0].Bus -Lun $VM.VirtualDVDDrives[0].Lun

          }

          else

          {

              $DvdDrive = $VM.VirtualDVDDrives[0] | set-VirtualDVDDrive -ISO $VmAdditionIso -Bus $VM.VirtualDVDDrives[0].Bus -Lun $VM.VirtualDVDDrives[0].Lun

          }

          echo "Attached " $VmAdditionIso.Name " to VM" $VM.Name " Please start the vm if not running and install additions from dvddrive"

      }

      else

      {

           echo "Can't install vmadditions on VM " $VM.Name " as $IsoName ISO not present, please add it to library and retry"

      }

  }

  else

  {

      echo "Can't install vmadditions on VM " $VM.Name " has no VirtualDVDDrives present, please add a dvddrive and retry"

  }

}

else

{

    echo "Can't install vmadditions on VM " $VM.Name " in library, please deploy to host and retry"

}

InstallVMAdditions.ps1 - Complete Script

Copy the following complete version of InstallVMAdditions.ps1 into a Notepad file, and save it as InstallVMAdditions.ps1.

# Filename:    InstallVMAdditions.ps1

# Description: Create a System Center Virtual Machine Manager-based

#              hardware profile and operating-system profile; use

#              these profiles and a sysprepped VHD to create a

#              template; use the template to create 'n' number of

#              virtual machines, adding an additional VHD to each

#              new VM; and deploy each virtual machine on the most

#              suitable host. Display progress messages for each task

#              and display a final status message for attempt to

#              create a virtual machine.

# DISCLAIMER:

# Copyright © Microsoft Corporation. All rights reserved. This

# script is made available to you without any express, implied or

# statutory warranty, not even the implied warranty of

# merchantability or fitness for a particular purpose, or the

# warranty of title or non-infringement. The entire risk of the

# use or the results from the use of this script remains with you.

####################################################################

# Define variables

####################################################################

$VMMServer = "localhost"

$VMNameToInstallVMAdditions = "VM01"

# If you want to link to VMAdditons.iso in the Virtual Machine Manager

# library, set $LinkIso to $TRUE; alternatively, if you want to copy

# VMAdditions.iso to the VM, set $LinkIso to $FALSE.

$LinkIso = $FALSE

####################################################################

# Connect to the Virtual Machine Manager server.

####################################################################

$C = Get-VMMServer $VMMServer

####################################################################

# Get the VM on which you want to install VM Additions.

####################################################################

$VM = Get-VM | where {$_.Name -eq $VMNameToInstallVMAdditions}

####################################################################

# Install VM Additions or (if not possible) display an error message.

####################################################################

if($VM.HostType -eq "VMHost")

{

    if($VM.VirtualDVDDrives.Count -gt 0)

    {

      $VmHost = $VM.VMHost

      # The segment$VmHost.VirtualizationStack returns the version

      # of Virtual Server running on this host

      $IsoName = $VmHost.VirtualizationStack +" VMAdditions"

      $VmAdditionIso = Get-ISO | where {$_.Name -eq $IsoName}

      if($Null -ne $VmAdditionIso)

        {

          if($LinkIso -eq $TRUE)

          {

              $DvdDrive = $VM.VirtualDVDDrives[0] | set-VirtualDVDDrive -ISO $VmAdditionIso -Link -Bus $VM.VirtualDVDDrives[0].Bus -Lun $VM.VirtualDVDDrives[0].Lun

          }

          else

          {

              $DvdDrive = $VM.VirtualDVDDrives[0] | set-VirtualDVDDrive -ISO $VmAdditionIso -Bus $VM.VirtualDVDDrives[0].Bus -Lun $VM.VirtualDVDDrives[0].Lun

          }

          echo "Attached " $VmAdditionIso.Name " to VM" $VM.Name " Please start the vm if not running and install additions from dvddrive"

      }

      else

      {

           echo "Can't install vmadditions on VM " $VM.Name " as $IsoName ISO not present, please add it to library and retry"

      }

  }

  else

  {

      echo "Can't install vmadditions on VM " $VM.Name " has no VirtualDVDDrives present, please add a dvddrive and retry"

  }

}

else

{

    echo "Can't install vmadditions on VM " $VM.Name " in library, please deploy to host and retry"

}

There is a new community site for Test open today over on MSDN at: http://msdn2.microsoft.com/en-us/testing/default.aspx 

"At the Tester Center, our goal is to provide a community where software testers can share knowledge and learn from each other about testing, our day-to-day job functions, processes, the tools we use, and the various roles we play. As you look around the site, you’ll see videos, articles, blogs, and other information. "

Featured technical articles include:

Best Practices: Code Reviews | by Josh Poley, Microsoft Corporation, August 2007
Learn some nuances of the C and C++ languages and the Microsoft Windows APIs that can lead to hard-to-diagnose bugs.

.NET Matters: Debugging Finalizers by Stephen Toub, Microsoft Corporation, November 2007
Find out how to use finalizers as a way to warn developers who use your custom types when they are garbage collected without having been disposed of correctly.

The new white paper "Managing Virtual Server Host Clustering using System Center Virtual Machine Manager 2007" is available in the download center at: http://download.microsoft.com/download/3/2/8/32849b7a-4f69-4c20-a988-333d954b3500/VMMandVSHostClustering_final.doc.

"This document provides an introduction to the methods and concepts that Information Technology (IT) professionals can use to manage Virtual Server clustered hosts using VMM. Virtual Server host clustering allows you to use a small number of physical servers to provide a wide variety of services, while maintaining the availability of the services that you provide. If a physical host server requires scheduled or unscheduled downtime, another host server is able to quickly begin supporting services. "

The paper also includes an updated Havm.vbs script you cna use to ensure that in a Virtual Server host cluster managed by Virtual Machine Manager, the virtual machines function correctly when a command is issued from the VMM Administrator Console or from the Cluster Administrator snap-in. The script is configured as a Generic Script resource in the cluster.

NOTE: use the updated script from Appendix A in this document instead of the Havm.vbs script included in the Virtual Server Host Clustering Step-by-Step Guide for Virtual Server 2005 R2. The updated script in Appendix A already contains the correct variables for usage with VMM.

Interesting article here says the Beeb (well, BBC.com) will start advertising on the sites accessed by non-Brits. Funny kind of "audience targeting" if you ask me...<emphasis mine>

"There are a number of reasons behind this decision. The bulk of the BBC is funded by the UK licence fee paid by every household with a TV in Britain. However, under the new BBC charter, we are not allowed to use licence fee funding for the benefit of international audiences. The BBC website has a large number of international users and advertising seems to be the obvious way for them to contribute to the costs of the site. In addition, profits from the site will be reinvested in the BBC's journalism and we believe will enable us to more strongly develop the site for international users."

The System Builder's Shop Talk blog yesterday links to the some useful Virtualization Cookbooks, including:

Microsoft® Virtual Server 2005 R2 Service Pack 1 and Microsoft® System Center Virtual Machine Manager
The goal of this cookbook is to provide the steps and guidance necessary for you to successfully install and configure Virtual Server 2005 R2 SP1 and System Center Virtual Machine Manager. You may then create and manage virtual machines, and perform P2V migration.
http://download.microsoft.com/download/2/b/9/2b99fd0d-5437-40d7-a430-23e31cac7ece/Deployment_Cookbook.SCVMM_FINAL.doc

Microsoft® System Center Data Protection Manager 2007, Microsoft® Virtual Server 2005 R2 Service Pack 1, and Microsoft® System Center Virtual Machine Manager
The scenario presented in this cookbook will take you through the steps necessary to install Virtual Server and SCVMM, and then convert a workload to a virtual machine. This cookbook also includes the steps necessary to install DPM and to back up a running virtual machine, as well as information about monitoring and reporting using DPM.
http://download.microsoft.com/download/2/b/9/2b99fd0d-5437-40d7-a430-23e31cac7ece/Deployment_Cookbook.SCVMM_DPM_FINAL.doc

Note that the “Microsoft® Virtual Server 2005 R2 Service Pack 1 and Microsoft® System Center Virtual Machine Manager” cookbook tells how to deploy and configure Virtual Server 2005 R2 on hosts before you deploy Virtual Machine Manager. Although you can add existing Virtual Server hosts to Virtual Machine Manager, you also have the option of adding qualified computers as hosts without pre-installing Virtual Server. When you add a qualified server to Virtual Machine Manager as a host, Virtual Server 2005 R2 is installed automatically along with the VMM agent.

Detailed planning content for VMM is in review and will be available on Technet in November. However, the following topics are already available in the Virtual Machine Manager TechNet Library (http://technet.microsoft.com/en-us/library/bb740737.aspx), and will give you an overview of the features, capabilities, requirements, and deployment of VMM:

·         System Requirements (http://technet.microsoft.com/en-us/library/bb740949.aspx)

·         Getting Started (http://technet.microsoft.com/en-us/library/bb740744.aspx) – A roadmap to the resources for evaluating, deploying, and using VMM

·         Installing Virtual Machine Manager (http://technet.microsoft.com/en-us/library/bb740755.aspx) – Procedures for installing all components of VMM

·         Configuring Virtual Machine Manager (http://technet.microsoft.com/en-us/library/bb740765.aspx), in VMM Help, provides a roadmap to configuration tasks to be performed after VMM is deployed, with detailed feature descriptions and a full set of procedures in the following areas:

o   Adding hosts: http://technet.microsoft.com/en-us/library/bb740880.aspx

o   Adding library servers, library shares, and files to the VMM library: http://technet.microsoft.com/en-us/library/bb740779.aspx

o   Preparing for SAN transfers: http://technet.microsoft.com/en-us/library/bb740857.aspx

o   Setting up reporting: http://technet.microsoft.com/en-us/library/bb740871.aspx

o   Setting up virtual machine self-service: http://technet.microsoft.com/en-us/library/bb740803.aspx

o   Configuring global settings for Virtual Machine Manager: http://technet.microsoft.com/en-us/library/bb740881.aspx

NOTE: You can help the VMM content team develop content that meets your needs by providing a rating and suggestions for topics posted in the TechNet library. To do this, click the Click to Rate and Give Feedback link in the top-right corner of the screen.

You want update 942372 from http://update.microsoft.com/microsoftupdate.

Find the related kb article at http://support.microsoft.com/default.aspx?scid=kb;EN-US;942372 

Please ignore the

APPLIES TO

...Bug filed on that, 'nuff said.

Some folks have asked "Where is the <non-english language> installer for VMM already?"

It's in there. The "English" download includes all the languages VMM supports: English, German, Spanish, French, Italian, Japanese, Chinese simplified, Chinese traditional, and Korean.

So, for example, even tho the trial download refer-page says

"The Virtual Machine Manager trial software is available in the following languages:

English"

Please download and install and choose your supported language during setup.

Enjoy, genießen Sie, goce, appréciez, goda di, 楽しみなさい, 享用,즐기십시오.

The Infrastructure Planning and Design Series beta releases for SoftGrid Application Virtualization and Windows Server Virtualization are available as open beta downloads.

Windows Server Virtualization Guide

A virtualized computing environment can improve the efficiency of your computing resources by utilizing more of your hardware resources. Windows Server virtualization enables you to create a virtualized server computing environment using a technology that is part of Windows Server 2008. The Infrastructure Planning and Design Series: Windows Server Virtualization guide discusses Microsoft virtualization options using Windows Server virtualization in Windows Server 2008 and Microsoft Virtual Server 2005 R2 SP1. The guide explains design considerations at critical decision points and helps with plans for an optimized server virtualization architecture to meet organizational goals for performance and consolidation.

To join the Infrastructure Planning and Design beta, follow these steps:

1) Visit the Microsoft Connect Web site (http://connect.microsoft.com).

2) Click Invitations on the Connect menu.

3) Sign in using a valid Windows Live ID to continue to the Invitations page.

4) Enter your Invitation ID in the box. Your invitation ID is: IPDM-QX6H-7TTV

5) Click Go.

If you have not previously registered with Microsoft Connect, you might be required to register before continuing with the invitation process.

If the link in step 1 does not work for you, copy the full link and paste it into the Web browser address bar.

Recently published knowledge base articles:

·         942372  When you try to create a template from a Windows Server 2003 Service Pack 2-based virtual machine in System Center Virtual Machine Manager 2007, the job fails

http://support.microsoft.com/default.aspx?scid=kb;EN-US;942372

·         942983  Error message when you try to use the Physical-to-Virtual (P2V) Wizard in System Center Virtual Machine Manager 2007 to start a P2V process: "Not enough memory available"

http://support.microsoft.com/default.aspx?scid=kb;EN-US;942983

·         942984  Error message when you try to use the "Physical to Virtual" (P2V) wizard in Microsoft System Center Virtual Machine Manager 2007: "ID: 3224"

http://support.microsoft.com/default.aspx?scid=kb;EN-US;942984

·         942985  Error message when you try to install a System Center Virtual Machine Manager 2007 server: "The Virtual Machine Manager installation was not completed successfully."

http://support.microsoft.com/default.aspx?scid=kb;EN-US;942985

·         942986  Error ID 3210 occurs when you perform a physical to virtual (P2V) migration in System Center Virtual Machine Manager 2007 on a Windows XP-based system or on a Windows Server 2003-based system

http://support.microsoft.com/default.aspx?scid=kb;EN-US;942986

·         942987  An unattended installation of the System Center Virtual Machine Manager service prompts you for the product key

My colleague put the following together to answer a customer question, passing it on to you.

VMM Help, which is posted in the VMM TechNet Library (http://technet.microsoft.com/en-us/library/bb740766.aspx), contains several good sources of information for administering virtual machine self-service:

About Virtual Machine Self-Service: http://technet.microsoft.com/en-us/library/bb740785.aspx - Provides a conceptual overview.

About Self-Service Policies: http://technet.microsoft.com/en-us/library/bb740909.aspx - Gives a detailed description of the components of a self-service policy.

How to Set Up Virtual Machine Self-Service: http://technet.microsoft.com/en-us/library/bb740803.aspx - Provides an overview of all tasks involved in setting up virtual machine self-service and links to a detailed procedure for configuring self-service policies.

How to Troubleshoot a User Session on the VMM Self-Service Portal: http://technet.microsoft.com/en-us/library/bb740815.aspx - Tells how to access the Self-Service Portal as an administrator in order to see and manage the virtual machines as a specific self-service user would view them.

You can't get closer to the bone for information on the next version of VMM than reading the new blog here.

Enjoy!