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>

Patching is one of those tasks you want to bundle up with some other critical work that you can kick off on the side while you dig into the pizza you expensed for dinner. It is necessary work but never exciting.

So imagine my surprise when I applied ISA 2006 Service Pack 1 and got new features, it was like XP Service Pack 2 all over again :)

New to the ISA Management console is Change Tracking, and once enable will keep detailed records on what really changed after the new guy has implemented an RFC.

This feature is fantastic! Even if you have processes out the wazoo this information will be invaluable when you really want to know why the website really went down.

Change management isn’t the only new feature to ISA 2006; there is also rule testing and traffic simulators (just to name a few). Check out http://technet.microsoft.com/en-us/library/cc707230.aspx for the full story.

I came across this problem the other day, where I wanted to determine if a Virtual Machine was running on Hyper-V or Virtual Server 2005 host system.

WMI exposes the Win32_ComputerSystem class which contains information about the Manufacturer and Model of a particular system (this is very hand if you want to check type of system before installing an application, e.g. Virtual Machine Additions). The unfortunate news is that Win32_ComputerSystem returns the following on both Hyper-V and Virtual Server hosts:

So how to determine what it is I am looking at? Well there is another WMI class, Win32_BIOS, which can help. Here you can see a difference in the Version between products.

Hyper-V

Virtual Server 2005 SP1

So far this seems to work for me; I am interested if anyone has alternate suggestions on how to solve my little problem, especially if there are cases where this will break (for example limiting the CPU functionality to run NT 4.0?)

Not long now till I tie the knot and if you are in the same boat, you may not have realised how many geek wedding accessories are out there.

With a little help for Leon we have found a few things to make that special day that bit more geeky!