Archive for the ‘Hyper-V’ Category

Bringing Legacy Blog Back to Cover Legacy Products

Just about a year ago, I moved all new posts over to In spite of that, this blog still continues to get much attention due to a lot of the existing content proving to be very useful for users. For that I am extremely happy to help and it recently gave me an idea. I have been mulling over how I should focus my current blog over at Technet with regards to information, guidance, and support tips. While I have a lot of great information coming (a lot of new products/product versions in the pipeline) I also have a wealth of information I’ve been needing to post tat was related to existing products and legacy products (Softgrid/App-V 4.x/MED-V V1, etc.) I also realize there is a strong user community and install base still present who may not be moving off until the products get closer to end of life.

– Steve Thomas

With this said, I decided that I would use this blog on WordPress in the future for legacy product information (App-V 4.x/Softgrid/MED-V V1/VMM 2008/VPC) while keeping my blog over at Technet more related to current and forward technologies (App-V 5.0/UE-V/Hyper-V 2012/Win8/Win2012.)

SCVMM: Checkpoints are great for Reversion but not for Serious Backup

Checkpoints in SCVMM are managed Hyper-V Snapshots. Hyper-V snapshots are block-level at the VHD layer and serve great for development environments that need reversion capabilities but are not recommended in production.

For a good how-to guide for creating and managing checkpoints, you can look at the Technet documentation here:

As I said earlier, this is great for scenarios of testing patches, testing upgrades, or working with App-V/Softgrid sequencers. It does not work if you are trying to attain file-level backup/restoration capabilities.

Checkpoints/Snapshots will not give you file-level restoration capabilities, however. This must come through a solution from the guest operating system. Windows Server 2008 and Server 2008 R2 have built-in VSS-based backup features.

You should use the built-in backup features of the operating system within the guest operating system to do individual file-based backups.

Backup and Recovery Overview for Windows Server 2008

Backup and Recovery Overview for Windows Server 2008 R2

NOTE: If you plan to use checkpoints for virtual machines with SCVMM, you will want to ensure that you have merged or deleted all checkpoints before moving the virtual machines or else you will experience delays when migrating virtual machines over the network (using BITS) or during QSM (Quick Storage Migration.)

Even worse, you could have errors from these timeouts that could also result in potential corruption of the checkpoints\snapshots.

Steve Thomas

SCVMM: Service Principal Names (SPNs) Required for Proper SCVMM 2008 Functionality

April 30, 2011 8 comments

SCVMM 2008, 2008 R2, as well as future versions of SCVMM rely on kerberos and kerberos delegation functionality for its security and authentication model. You may encounter various problems with SCVMM related to authentication and authorization if the underlying platform service principal names (SPNs) are not properly set.

There are all sorts of problems ranging from console authentication, to SQL access, or even host access for the purposes of accessing virtual machines managed by SCVMM. All of these problems cann be caused when delegation is failing possibly due to incorrect or missing SPNs (Service Principal Names.)
The resolution is to verify and correct any configuration issues with kerberos delegation, often correcting problems related to SPNs not being registered – or even duplicate SPNs.
You can use the SETSPN command to check for duplicate SPNs and to create missing ones if needed. Please note not all SPNs may be required as that will vary based on what server roles are installed. SETSPN is a default external command in both Windows Server 2008 and 2008 R2. For Windows Server 2003, I would recommend downloading the SETSPN update for Windows Server 2003. More information and download links are found here:
The following list below lists all of the SPNs that may be required relating to their corresponding components. Since SCVMM is a management interface that sits on top of so many different platform components, incomplete or improper delegation at these component layers will cause problems in SCVMM functionality.
Hyper-V Virtual Consoles:

For Virtual Console Support for Hyper-V Hosts (VMCONNECT.EXE) – This will be required on Hyper-V Hosts. Use the following command to set and verify SPNs.

setspn -s "Microsoft Virtual Console Service/HOSTNAME" computername 
setspn -s "Microsoft Virtual Console Service/hostname.fqdn.etc" computername 

For P2V Support.

Use the following command to set and verify SPNs.

setspn -s "Microsoft Virtual System Migration Service/hostname.fqdn.etc" computername 
setspn -s "Microsoft Virtual System Migration Service/hostname" computername 

 For VS2005 Hosts and the VMRC utility

– This will be required on Virtual Server 2005 Hosts. Use the following command to set and verify SPNs.

setspn -s vmrc/hostname.fqdn.etc:5900 computername 
setspn -s vmrc/hostname:5900 computername 
setspn -s vssrvc/hostname.fqdn.etc computername 
setspn -s vssrvc/hostname computername 

For RDP Support.

Use the following command to set and verify SPNs.

setspn -s TERMSRV/hostname.fqdn.etc computername 
setspn -s TERMSRV/hostname computername 

 For all Hosts.

Use the following command to set and verify SPNs.

 setspn -s HOST/hostname computername 
setspn -s HOST/hostname.fqdn.etc computername 

 HTTP (may needed for authentication on SSP if VMM server is using Remote SQL.)

Use the following command to set and verify SPNs.

setspn -s HTTP/hostname.fqdn.etc computername 
setspn -s HTTP/hostname computername 

 SQL VMM Database

Depends on port and instance type: 

Named Instance.

Use the following command to set and verify SPNs.

 setspn -s MSSQLSvc/hostname.fqdn.etc:Port computername

setspn -s MSSQLSvc/hostname.fqdn.etc:InstanceName computername 

 Default Instance.

Use the following command to set and verify SPNs.

setspn -s MSSQLSvc/hostname:1433 computername 
setspn -s MSSQLSvc/hostname.fqdn.etc:1433 computername 

Here are some links to some excellent articles:

Microsoft Virtualization Engine and Management Updates

Here are a listing of significant Microsoft management and Virtualization engine downloads and updates at all levels of the stack:

Storage Virtualization:

Microsoft iSCSI Target Software:

iSCSI Software Target is an optional Windows Server component that provides centralized, software-based and hardware-independent iSCSI disk subsystems in storage area networks (SANs).


Microsoft App-V 4.6 Service Pack 1


Windows Server 2008 R2 SP1:

Hyper-V Server 2008 R2 SP1:

Updated Hyper-V Management Tools for Windows 7 SP1 now available

Update to the Hyper Best Practices Analyzer:


SCVMM 2008 R2 SP1:

Updated Configuration Analyzer for SCVMM to include 2008, 2008 R2, and 2008 R2 SP1

Remote Desktop Services Connector for System Center Virtual Machine Manager

Planning for a Microsoft VDI Deployment

April 13, 2011 2 comments

In the past, desktop virtualization administrators have used Microsoft for only part of their VDI (virtual desktop infrastructure) while using solutions from VMWare of Citrix as the primary basis.

You may be already familiar with Microsoft’s client-hosted enterprise desktop virtualization solution – MED-V. VDI is Microsoft’s server-based desktop virtualization solution combining all of the following for engine support all the way to complete end-to-end management:

  • Hyper-V
  • Windows 7
  • Windows Server 2008 R2
  • System Center Virtualization Manager
  • Remote Desktop Services
  • RemoteFX

Windows Server 2008 R2 Service Pack 1 adds two new components (RemoteFX and Dynamic Memory) that fill two holes related to management flexibility and user experience that now make Microsoft almost a non-brainer choice for your VDI solution.

Microsoft’s virtualization main page is found here:

First things first,

Licensing Information regarding VDI. One of the first things customers want to know is what are the costs and the potential cost savings:

In terms of how it works, here is Microsoft’s VDI solution at a high level:

The next items of concern are often what infrastructure changes will need to be made. Moving to a VDI environment will require the presence of a Windows 2008 or Windows 2008 R2 domain controller (depending on the Hyper-V/RDS platform being used.) You will also need to update the schema accordingly to support these domain controllers and subsequent services required for the VDI environment.

Here are the outlines of the Windows 2008 and Windows 2008 R2 Schema changes:

Windows 2008:

Windows 2008 R2:

You will need to have Windows 2008 Schema changes minimally however, the minimum AD domain level supported is Windows 200 native. Windows 200 mixed or Windows 2003 interim are not supported.


The following are important considerations about assigning a personal virtual desktop to a user in AD DS:

  • To deploy personal virtual desktops, your schema for the Active Directory forest must be at least Windows Server 2008. To use the added functionality provided by the Personal Virtual Desktop tab in the User Account Properties dialog box in Active Directory Users and Computers, you must run Active Directory Users and Computers from a computer running Windows Server 2008 R2 or a computer running Windows 7 that has Remote Server Administration Tools (RSAT) installed.
  • You must use a domain functional level of at least Windows 2000 Server native mode. The functional levels Windows 2000 Server mixed mode and Windows Server 2003 interim mode are not supported.
  • Ensure that the RDVH-SRV computer meets the Hyper-V installation prerequisites (
  •  The user account and the virtual machine must both be members of an Active Directory domain.
  • Personal virtual desktops can only use Windows client operating systems. You cannot install Windows Server® 2008 R2 on a virtual machine and assign it as a personal virtual desktop.
  • A user can be assigned only one personal virtual desktop at a time.
  • A virtual machine can be assigned as a personal virtual desktop to only one user at a time.
  • The name of the virtual machine in the Hyper-V Manager tool must match the fully qualified domain name (FQDN) of the computer.

 Sizing Concerns:

Alongside of instructure changes and concerns is capacity planning. Here is a good webcast on planning and sizing session virtualization and bandwidth for VDI:

 And a good document as well:

 RD Web Access Information:

 RD gateway Information:

 Why VDI for Hyper-v Whitepaper:

 Windows 2008 R2 SP1’s RemoteFX feature for Hyper-V

 If you have time, also check out the VDI videos on technet Edge:

SCVMM 2008 and 2008 R2: Error when Connecting through VMConnect or RDP: 0x8009030e

January 18, 2011 2 comments

You may notice that you may run into problems with credentials going stale when trying to connect to a Virtual Machine from the SCVMM 2008 or SCVMM 2008 R2 console. When this happens, you get the following error when launching VMConnect.exe to connect to the VM:

An authentication error has occured (Code: 0x8009030e)

Remote computer:

You will also get this error when trying to RDP or connecting through the Hyper-V Management console as well.

The result code 0x8009030e refers to SEC_E_NO_CREDENTIALS in this context or:

“No credentials are available in the security package.”

The security credentials stored by the Hyper-V Host are stale and need to be reset for this particular virtual machines. Other virtual machines may be affected  as well but this setting is actually stored on a per-VM basis.

There is no equivalent way to delete existing stale or missing credentials for Hyper-V hosts in SCVMM. This needs to be corrected on the Hyper-V host.

On the Hyper-V Host, open up the Hyper-V Management Console. Select the host, the select “Hyper-V settings”

In the Hyper-V Settings option, under User Credentials, uncheck “Use default credentials automatically”

Connect to the Virtual Machine again, it will prompt to enter username and password.

Enter credentials, check the box “Remember my credentials”.

VMCONNECT and RDP should be successful. Once verified, return to the Hyper-V Settings option, under User Credentials, check “Use default credentials automatically”

How to Make an MS-DOS Bootable Floppy Disk for Hyper-V or VPC

January 11, 2011 8 comments

If you are stuck trying to do this, you would be surprised at how quickly it can still be done. The Challenge is getting a boot sector – which you can override with a new set of MS-DOS files if require a specific version.

1.) Mount a Blank VFD

2.) Start a Windows XP VM.

3.) Attach a VFD to the XP VM after you have logged on to the XP VM.

4.) Right-click the floppy in the Windows XP Guest OS and select Format.

5.) Check the option to create an MS-DOS System Disk.

Post format you can do whatever you need to copy over the files on the disk if you need an older version such as MS-DOS 6.22. Overwrite files as needed as all you needed from step #5 was the creation of the boot sector.

Categories: Hyper-V, Virtualization, VPC Tags: , , , , , , ,

Microsoft releases source code for Linux Vm ICs (Integrated Components) – formerly called VM Additions

Get the offical story here:

External Article on the Subject

"Microsoft stuns Linux world, submits source code for kernel "

First and foremost, the title is very misleading. We did not release any source code for "our" kernel. We released source code for virtualization support on Hyper-V to be included into the Linux Kernel’s source code.

This is an open source requirement as Linux operates off a more macro kernel and requires kernel re-compilation for  driver support. This is, in essence, driver code, not Windows kernel code.
The next question you may have is: Why? Well, to quote the following article "Microsoft is making a compelling case that it could be the virtualization vendor of choice for consolidation of Windows and Linux applications."

Categories: Hyper-V

Microsoft Mythbusters: Tope 10 VMWare Myths Exposed

Microsoft fights back the FUD regarding Hyper-V vs. VMware in this video exposing the top ten VMWare Myths:
Categories: Hyper-V