Disk2vhd 1.0

The Microsoft SysInternals team released a new tool called Disk2vhd.  Ben Armstrong talked about it yesterday. 

You can run the tool on a XP SP2, Windows Server 2003 or higher machine to capture the physical disks as VHD files.  VHD is the virtual hard disk used in Microsoft virtualisation.  Think of it as a poor man’s P2V tool.  It does not do any clever HAL or driver stuff – that must be done by you.

System Center Essentials 2010 Beta

The beta (pre release testing) program of SCE 2010 has started.  SCE is the product that includes some of the key features of System Center Configuration Manager and Operations Manager in an integrated package.  Some of the new features included are:

  • Integrated server virtualization management support, built on VMM 2008 R2 technology, including easy template-based creation of new virtual servers and live migration
  • Adjusted licensing limits to allow for management of virtual servers
  • Rewritten setup for an easier, intuitive installation
  • Built-in automatic Microsoft Update subscription maintenance
  • Provided flexible computer grouping
  • Added additional software distribution target criteria

You can read that 1st one as VMM 2008 R2 integration.

VMM 2008 R2 Documentation

Microsoft has published a set of downloadable documentation for System Center Virtual Machine Manager 2008 R2:

  • Virtual Machine Manager Deployment Guide: This guide provides information essential for the successful deployment of VMM 2008 and VMM 2008 R2. The topics in this guide provide detailed information about system requirements, installing VMM, upgrading or migrating from a previous version, and additional deployment and configuration information.
  • Virtual Machine Manager Guide to Operations Manager Integration: This guide provides information essential for the successful integration of System Center Operations Manager 2007 with Service Pack 1 (SP1) or Operations Manager 2007 R2 with System Center Virtual Machine Manager (VMM) 2008 or VMM 2008 R2. The topics in this guide provide system and security requirements, detailed procedures for performing a successful integration, and troubleshooting for integration issues, whether you are a new VMM customer or you previously integrated Operations Manager with VMM 2008 or VMM 2008 R2 Beta. Procedures also are provided for enabling Performance and Resource Optimization (PRO) and configuring reporting in VMM. A successful Operations Manager integration is a prerequisite for both the PRO and reporting configurations.
  • Virtual Machine Manager Security Guide: This guide provides the information needed to successfully configure security for VMM 2008 and VMM 2008 R2. Topics include security basics (role-based security, ports and protocols used by VMM, and account requirements for administrative tasks); instructions for hardening the VMM server, database server, virtual machine hosts, library servers, and self-service Web servers against unauthorized access; domain and account requirements for integrating System Center Operations Manager 2007 with VMM; and security requirements for managing a VMware environment by using VMM.
  • Virtual Machine Manager Operations Guide: This guide provides information essential for the successful configuration of VMM 2008 and VMM 2008 R2. For new customers, this guide explains how to configure the required and optional features of VMM after setup. The guide also provides information about creating, managing, and migrating virtual machines; performing maintenance on virtual machines, their hosts, and the VMM server; and managing a VMware Infrastructure 3 (VI3) environment by using VMM.
  • Virtual Machine Manager Scripting Guide: This guide provides an overview of the Windows PowerShell – Virtual Machine Manager command shell and sample scripts that explain how to use Windows PowerShell scripting to manage your virtual system infrastructure.
  • Virtual Machine Manager Cmdlet Reference: As an alternative to using the VMM Administrator Console to administer your Virtual Machine Manager environment, you can use the cmdlets in the Windows PowerShell – Virtual Machine Manager command shell, which is an administrator-focused command-line shell. This guide provides the Help topics for the VMM 2008 and VMM 2008 R2 cmdlets.
  • Building PRO-Enabled Management Packs: This document gives an overview of creating PRO-enabled management packs and walks you through the steps required to create a simple PRO-enabled management pack.

Some OpsMgr Documentation

Microsoft is busy catching up with some documentation after the release of Operations Manager 2007 R2:

RedHat Support on Hyper-V

This is a big announcement, one we’ve been waiting on for a while.  How big?  I’ve been too busy to keep up with blogging on IT updates.

Microsoft has announced they they have completed a mutual support program with RedHat.  Now we have support for both enterprise Linux platforms on Hyper-V; SUSE being the other one.  And both can be monitored from hardware to service using Operations Manager 2007 R2.  Details on RedHat:

  • Red Hat Enterprise Linux 5.2, 5.3, 5.4 have passed cert tests when running on Windows Server 2008 Hyper-V, Microsoft Hyper-V Server 2008, Windows Server 2008 R2 Hyper-V, Microsoft Hyper-V Server 2008 R2. See more at RedHat’s certified hardware site.
  • Windows Server 2003/ Windows Server 2008 / Windows Server 2008 R2 are validated to run on Red Hat Enterprise Linux 5.4, using their KVM-based hypervisor. See more at Microsoft Server Virtualization Validation Program site.

According to Microsoft “you can now run JBoss Enterprise Middleware within a virtual machine guest on Hyper-V and receive coordinated technical support”. 

Well done to two competitors who’ve worked together to satisfy the needs of their mutual customers!

EDIT #1

Dig a little deeper and we get some more details.  The support for RedHat on Hyper-V does not include synthetic drivers, i.e. the integration components.  Only emulated devices, e.g. legacy NIC, are supported as of now.  Eventually the open source integration components (that were recently signed off by the community) will filter their way into the new RedHat builds.

What Is IT Book Writing Like?

Back when I was in school I hated English classes.  Macbeth, poetry, short stories, etc all bored me to tears.  In the Leaving Cert (set of Irish state exams when you’re finishing secondary/high school) I managed to pull in a D in the lower level English exam when I was getting great grades in things like Construction, Biology and Technical Drawing higher papers.  Ask any of my teachers and they probably thought I would end up in the construction industry as a draftsman or engineer.  So me writing something for a book definitely wasn’t on the forecast.

A while back, I was lucky enough to be asked to contribute to a new book.  Schedules got all messed up and the original publication didn’t happen.  That all got fixed earlier this year and we’re on schedule to be published according to plan.  What was writing this like?

The first thing was the writing style.  The lead author has a very distinct style and like to give real world examples in everything, injected with a little humour here and there.  Lucky for me, I like to write with practical implementations in mind.  I think I surprised the editors by how much I like to use screenshots.  I’m probably using them much more than my co-editors because I think people can relate more to the contents of a book if they can visualise what the author is talking about.  I also hate it when I’m reading page 256 and I’m asked to flip to page 189 to look at a diagram or screenshot so there’s a couple of repeat shots in there.

The time for writing each chapter was around 1 month.  I was given a minimum set of things to cover and after that it was up to me to find relevant materials.  As time went by new facts or solutions might appear and they’d be added to the chapter as I was writing.  The publisher has a formatting tweak for MS Office that we used to format the text, headers, tables, etc.  The bit that continues to mess me up is the screenshots and diagrams.  The publisher doesn’t want them embedded in the word document because that compromises the image quality.  Instead, I’d name the file according to a naming standard.  After the text describing and referring to the screenshot/diagram, I’d put in a “slug”.  That slug describes the image.  It also refers to the file name for the final processing of the document.  Adding and removing images basically meant going through all the filenames to increase/decrease numbers and doing the same in the document.  Very painful!

After the initial writing I thought the bulk of my work was done.  I knew there would be technical reviews, language edits, etc but I had no idea.  The bulk of the work was still to be done.

Each chapter went off to the editors.  One appeared to review the technical side of things to test what I had been writing.  Another did the expected stuff and also enforced the publisher’s standardisations.  The chapter would come back with plenty of stuff marked in red for me to go back through.  I dreaded this.  The first time a chapter came back I was afraid to open the attachment.  But it wasn’t too bad.  The editors have been fair and are just as likely to put in something like “nice paragraph” as they are to request a change.

The biggest surprise for me was the request that I remove any personal references such as “I”, “me”, etc.  I’d used examples from my past to illustrate how to do or not do things.  Examples were great.  But the book is a joint exercise so “I” should be “we” and “me” should be “us”.  That meant I had to change a lot of text.  I usually like to put in a screenshot and then describe it.  The publisher prefers to talk about a subject and reference a following screenshot.  Again, more changes and a lot of time double checking things to make sure everything flowed OK and in the correct order.

After that the document goes off to a copy editor.  According to Wikipedia, this “is the work that an editor does to improve the formatting, style, and accuracy (but not content) of a manuscript”.  A lot of formatting changes went on here.  The Office tweak used for formatting has an unbelievable number of options and it was never obvious to me which ones to use.  Take the Word 2007 ribbon and change them all so each one is used for formatting, not just a little section like in the default Ribbon.  My Irish way of speaking was Americanized and this was where my D-grade English got corrected 🙂

After that comes the layout edit.  I’m halfway between the copy edit and layout stages now.  In the layout a PDF is created to create the manuscript that will be printed.  The images are finally brought in.  Why not use Word?  Because it adjusts everything according to whatever default printer is attached so you might get different results on different machines.  It’s here that the document starts to look like a chapter in a book, e.g. watermarks behind the chapter title.  It’s around now that you get sick of reading your own material.  The PDF still has the occasional mistake which must be highlighted and changed.  In the first one of these I’ve done I also spotted a few things I wanted to tweak, e.g. to make a sentence clearer.

I reckon about 50% of the work goes into doing the labs, trying out the scenarios, edge testing and writing the original content.  Maybe 50% of the work I’ve done has been done after the original submission.  It’s a lot of hard work.  The pay isn’t great but I knew that going in – you certainly can make much more pay doing ordinary work.  It will be great to see my name in print at the end, though, and it’ll always be on my CV/resume.

It won’t be long until the book is out.  The name of the book? Mastering Windows Server 2008 R2.

Upgraded HP BL460 G5 From W2008 to W2008 R2

The first step in our upgrade from Windows Server 2008 Hyper-V to Windows Server 2008 R2 Hyper-V is to upgrade the VMM server.  I decided to upgrade the operating system before upgrading the VMM 2008 R2 installation.  Of course, a Windows Server Backup job was run to start things off.

I mounted the ISO for the OS installer in ILO and ran the upgrade.  That took a while.  When I logged in I found that NIC teaming was broken.  Uh-oh!  I downloaded HP PSP 8.30 and ran that.  Another reboot.  Still no NIC teaming.

I found out which of the EXE’s was the installer for the HP NCU and re-ran it.  It told me this version of the OS was unsupported.  So much for HP support for Window Server 2008 R2 in HP PSP 8.30!

image

Here’s the simplest way to do some application compatibility.  I right-clicked on the installer and selected properties.  I opened the compatibility tab.  In there I ticked “Run this program in compatibility mode for:” and selected “Windows Server 2008 (Service Pack 1)”.  Now I reran the installer.  All was well and I could enable NIC teaming.

I figure that I’ll be waiting a while longer before upgrading our Hyper-V hosts 🙁  Anyway, until then, I’ll upgrade VMM 2008 to VMM 2008 R2.

Logic Bug in MDT 2010 LTIApply Script

During the demo preparation for the Windows 7 launch events I found a bug in the LTIApply script in MDT 2010.  That script is responsible for downloading a Windows PE image during an upgrade deployment and using BCDEDIT to configure the PC to boot from it instead of the onboard OS. 

My upgrade tests on XP were fine.  But when I upgraded from Vista Ultimate I got this: “The Apply PE step (ZTIAPPLY) is failing with a hex error of 0x80070070”.  I thought over it for a weekend.  I suspected an issue with the hidden 100MB partition that you get with Vista and Windows 7.  I posted on the Minasi Forum and Rhonda Layfield (deployment MVP) emailed me with a suggestion.  That sort of error code usually refers to a space availability issue.  Ah!

I dug into the script in question.  I found the issue.  The script determines if the 100MB partition is present or not.  If it is, it downloads the WinPE image into the 100MB partition.  That’s a problem: My unmodified MDT WinPE image with just a handful of drivers was 140MB.  140MB does not fit into 100MB.  There’s a destination location variable in the script that I hacked out and replaced with C:.  My solution was to download the WinPE image to C: instead of the 100MB hidden partition.  I tested it and it works.

I have no idea how this one got past MS and the beta testers.  Maybe they did just like what I did: tested with XP upgrades.  I know that the original Vista build I was given to work with had no 100MB partition and the upgrade worked fine.  But a later Vista Ultimate SP2 image with the 100MB partition messed it up.  Only my hack got it to work.

My suggestion to the MS folks: Make a simple change to the logic of the script so the download does not use the 100MB partition.

Microsoft Windows Virtual PC Blog

The folks behind the Windows Virtual PC Blog asked me to help spread awareness of its existence: so here you go!  On there they talk about the desktop virtualisation product and XP Mode.  I talked about XP Mode in the blog before.  It’s a free XP SP3 VM that you can run on the professional, ultimate and enterprise editions of Windows 7 for application compatibility when things like the ACT 5.5 kit won’t work or aren’t suitable.  You install your legacy application into the XP VM and you run it from your Windows 7 interface.  When the application starts up it runs in a seamless window, hiding the presence of the VM.  A feature added since I talked about it (or I didn’t notice it) is something people have been begging for in Hyper-V but don’t have yet: support for USB devices.  I showed that in action at the MS Ireland comunity launch event in Cork where I plugged in a BitLocker-To-Go protected USB stick into the XP Mode VM and accessed the secure contents.

You still need to treat the VM like a typical hardware machine on you network, e.g. domain membership, antivirus, patching, etc.  Larger organisations with Software Assurance might want to look at the paid for per desktop MDOP which includes MED-V, a way to centrally manage and configure the VM images on the desktop network.