If you missed the Brisbane Infrastructure Group last night you can checkout the Live Meeting recording (https://www112.livemeeting.com/cc/microsoft/viewRecordings, recording id BDT4KQ) and see the my presentation on "Managing Virtual Environments using System Centre Virtual Machine Manager".

And lastly thank you to everyone who provided words of wisdom and the BIG team for the presentation spot.

Enjoy :)

An private update has been released for users experiencing the following issues:

You cannot connect to a virtual machine when the Windows Server 2008 Hyper-V VMMS certificate has expired

Cannot connect to the virtual machine because the authentication certificate is expired or invalid. Would you like to try connecting again?

'VMName' failed to initialize.
Could not initialize machine remoting system. Error: ‘Unspecified error’ (0x80004005).
Could not find a usable certificate. Error: ‘Unspecified error’ (0x80004005).

And then today I noticed this posted on Ben Armstrong's blog:

Management Operating System

This is a new term that we are introducing in Windows Server 2008 R2.  We have been struggling without a good term here – as with Virtual PC / Virtual Server we had a nice set of terms where we could talk about the physical computer / virtual machine and the host operating system / guest operating system.  However this became muddier with Hyper-V – because we no longer really have a host operating system, and all operating systems run on top of the hypervisor.  Most people have been just using the term “Parent” or “Parent partition” to refer to what we used to call the host operating system – but this is not really architecturally correct.  Unfortunately the architecturally correct terms are – frankly – hideous; they are the “parent partition guest operating system” and the “child partition guest operating system”.  Yuck.  So after a lot of thought we decided to call the “parent partition guest operating system” the “Management operating system” as this is the operating system you use to manage your virtual machines, and “guest operating system” will be reserved to mean the operating system running inside virtual machines.

If you are interested in learning about managing a virtual environment with System Center Virtual Machine Manager 2008 come along to the Brisbane Infrastructure Group meeting Tuesday (10th of March) to see Mark Rhodes and myself speak.

It is a free event and you can register over at there Events page.

Hope to see you there.

If you are performing a migration to a new deployment suite, or if you just like to have every disk imaging tool in a WinPE WIM ready at a moment's notice, you might want to consider adding the Microsoft Automated Deployment Services (ADS) for legacy image support.

First off you will need to get a copy of the tools and the easiest way is to run the setup wizard for ADS and perform a custom installation. Be careful which options you install, multiple PXE agents in an environment could destroy all your hard work, see a screenshot of the installation options I used below.

Once installed you will need to collect the following file and incorporate them into your tools folder for WinPE.

• "%windir%\system32\adssupport.dll"
• "%programfiles%\Microsoft ADS\bin\*.*"

Done, enjoy.

I have been helping Alan Renouf, co-host of the Get-Scripting podcast, with a PowerShell script and he has been nice enough to mention me and my blog on during their latest episode.

If you haven't already checked out the Get-Scripting podcast you can listen and subscribe to it at http://get-scripting.blogspot.com.

The WinPE customisations keep coming, wanting more information about the system you are running WinPE on?

If you are familiar with BGInfo, you already know that it is a great way of displaying information about a system and you probably already use it in your base server build (for those not in the know check out BGInfo on TechNet). But what you may not know is that it works in WinPE and you can draw that same information out and display it on the screen.

Simply add the BGInfo executable and custom layout file to your WinPE scripts directory, modify your unattend.xml to include "X:\BGInfo.exe /accepteula /timer:0 /iqX:\WinPE.bgi /silent" and you are up and running.

To get you started I have added my layout file for download WinPE.zip (.86 KB).

NOTE: BGInfo is a 32-bit executable and since WinPE 2.0 64-bit doesn't support WOW it will only work in a 32-bit WinPE environment.

Something that I have been meaning to write up for some time now...

In nearly every environment I have worked in I have always come across some type of issue with Broadcom NICs.

In my most recent bout, it was determined that the network wasn't always (seemed to swap between having link negotation issues and invalid IP addresses) 100% initialised in WinPE before a task in the unattend.xml started executing. In our particular case we were working with Microsoft Deployment Toolkit which builds a custom WinPE image as part of deployment point synchronising.

Sample boot.bat

@echo off
echo.
echo INFO: Executing Sleep
echo.
cscript //nologo "%systemdrive%\sleep.vbs" 10
echo.
echo INFO: Renewing IP Address
ipconfig /renew
echo.
echo INFO: Executing Sleep
echo.
cscript //nologo "%systemdrive%\sleep.vbs" 10
echo.

Sample sleep.vbs

If Wscript.Arguments.Count = 0 Then
   ' Print Usage then quit
   Wscript.Echo "Usage: cscript sleep.vbs <Number>"
   Wscript.Echo " <Number> - Number of seconds to sleep."
   Wscript.Quit
Else
   ' Print how long we are sleeping for
   Wscript.Echo "INFO: Sleeping for " & Wscript.Arguments.Item(0) & " seconds"
   NumSeconds = Wscript.Arguments.Item(0) * 1000
   'Sleep
   Wscript.Sleep(NumSeconds)
End If

Unattend.xml Extract

<RunSynchronous>
   <RunSynchronousCommand wcm:action="add">
      <Description>CommandBreak WINPE Customisations</Description>
      <Order>1</Order>
      <Path>X:\boot.bat</Path>
   </RunSynchronousCommand>
   <RunSynchronousCommand wcm:action="add">
      <Description>Lite Touch PE</Description>
      <Order>2</Order>
      <Path>wscript.exe X:\Deploy\Scripts\LiteTouch.wsf</Path>
   </RunSynchronousCommand>
</RunSynchronous>