Windows Server 2003 Build Process

In my current project we're using WinPE to handle the imaging and setup process. This is quite interesting since we can build a basic W2K3 image with Ghost, and then post-process all PNP differences during startup. In terms of time, this saves endless times trying to create HW-specific images, and allows an almost error-free installation.

After the system boots the first time, we use a startup script to continue the post-build processes; including hw patches, firmware upgrades, PNP, and security hotfixes and the like.

From CD boot to a complete and configured domain member server, with completely updated hotfixes and patches is about 20 minutes.

From that point, clicking on a desktop shortcut brings up a 'roles wizard' which allows installation and configuration of additional services; IIS, File & Print, DFS, Shadow Copy, among some others.

I've not seen anything this sophisticated in many years, short of a complete Ghosting of a complete image. Pretty cool stuff.

More on WinPE Development

It appears that CPU counts aren't the only missing pieces in WinPE. There are other API required for a sophisticated installation that Microsoft left out. I'll have a complete list later but one of the more important ones is the ability to use LDAP. Our development has to use some complex code to get information from the AD at this point. Unfortunately I can't post code yet but hope to soon.

Designing a Build with WinPE

After 4 weeks of learning about WinPE, I decided to download the evaluation and try it myself. That appears the only way to get a real idea of how the process works.

In the past few weeks, we have also found some limitations of winPE, which we hope MS will correct. The main limitations are in the area of scripting; the exposed layers don't always return the correct information especially concerning hardware. The number of CPUs is fixed at 1, so designing multi-processor builds require asking the user the number of processors.

There are some others which I'll post later after I receive some feedback from MS.

All in all, WinPE is quite a step up from the previous build processes. It allows for a third-party application to image the drive (we use Ghost), and then syspreps the drive to set up the Registry and SID correctly. In our trials I can test under Virtual PC and then move the build to real hardware.

The amount of time saved is considerable and I suggest those that build systems for several servers to definetely check out WinPE.

Currently we build for both 32-bit and 64-bit systems on 3 hardware types: Dell, HP, and IBM.

More later.

Sitting on the dock of the lake

It's been busy here in CH, so I haven't had time to post anything until now.

On Monday, Jan 3rd, I started consulting at a company in Vevey, located right on the lake. The weather this week (until today) has been sunny and cool (around zero) and I have enjoyed walking to lunch around the lake area.

The project is to create a build for Windows 2003 servers, including W2K3 32-bit and 64-bit. Very, very interesting since we're using WinPE to handle the work.

I'll post more on this process in the future.

Condolences to all the people hit by the earthquake

I know there is nothing I can do but my heart and prayers go out to all.

Merry Christmas and Happy New Year

As it has started to snow here in Switzerland, I feel even more in the holiday spirit. I wish everyone safe holidays wherever they are.

Blogs Changes 101: Corner Move

I'm having problems moving the corners to the right to accept a wider profile block. Have tried a few code changes but to no avail. Emailed support for assistance. Awaiting word.

Second Post - I am not a writer...

Well, thinking about the comment from AC (Anonymous Coward: see Slashdot), I decided to just change the template. Which appears to look better and brings the font size down a bit.

Now, on to checking RSS and email posts.

Cafè time.

First Post

.... and I do what now?