Scripted XP install on a ESX VM machine

ldekens · 12-21-2005, 09:29 AM

Did anyone succeed in using the Scripted OS installation to install XP Pro SP2 on a virtual machine on a VMware ESX server ?

I know that the SCSI vmxbuslogic driver is not included in XP Pro.

To avoid that problem I downloaded the vmscsi-1.2.0.2.flp file and used the method described in the XP Pro resource kit (see http://www.microsoft.com/resources/d...asp?frame=true).

To start I used the DOS managed automation but that always comes back with a Stop 0x7B (no hard disk). So apparently the SCSI controller driver was not taken.

Then I tried with the WinPE managed automation but there the message "The file txtsetup.oem could not be found ...." came immediatly after the winnt32.exe command.

If anyone got this working with either of the automation agents would you mind sharing the procedure ?
Regards,
Luc.

PS: does anyone know why the WinPE automation tries to start the smartdrv.exe with the following command line:
f:\bootwiz\platfo~1\dos\MSDos\OS\smartdrv.exe ? See the attached BAT file.

ldekens · 12-21-2005, 09:58 AM

Correction, the error message from the WinPE automation agent spoke of the unattend.txt file not the txtsetup.oem. See the attached screenshot.
Luc.

ldekens · 01-16-2006, 08:20 AM

After my Xmas leave I now have a partial success.

The problem with the WinPE Managed method was caused by the fact that the SFCDllCacheDir (in [SystemFileProtection]) variable needed quotes around the value string.

The scripted OS installation with the option WinPE Managed now works.

The scripted OS installation with the option DOS Managed keeps giving the Stop 0x7B when the GUI setup mode start (first boot to production).

Anyone already suceeded in running the Scripted OS installation for Windows XP Pro with the DOS Managed option ?
Luc.

Nick · 01-16-2006, 09:31 AM

Luc,

I've been running a Scripted OS Install (SOSI) of Windows XP Pro (with SP2 installed) for the past couple of weeks using DOS Managed.

It is working great for me.

ldekens · 01-16-2006, 09:46 AM

And was that on VM machine under VMware ESX 2.5.2 ?

Would you mind sharing the unattend.txt and the layout of the $OEM$ folder ?

Nick · 01-16-2006, 10:11 AM

Luc,

Unfortunately is wasn't on a VM session. It was on physical machines (C600 and GX110).

The $OEM$ structure is vanilla with just the cmdlines.txt inside and it only has the install of the aclient.

I have attached my unattend.txt file as well for your review. The product ID has been cleared for obvious reasons.

My setup was only done to test out using another patching tool via the DS, which turned out quite impressive.

Let me know if you I can help.

ldekens · 01-16-2006, 02:46 PM

Nick,

Success at last.
The problem came from the type of SCSI controller I selected for the VMware machine.
In short, under ESX you can select from 2 types of SCSI controllers (buslogic or LSIlogic).
On the VM machine where I was testing the DOS Managed unattended XP installation I had unknowingly selected the LSIlogic controller while my unattended setup only contained the drivers for the buslogic controller.

Once changed it all worked as a dream.
Thanks for the help.

If someone would be interested I could produce a short document with all the required steps.
Luc.

PS: would you mind telling which PMS alternative you have been testing ?

Nick · 01-16-2006, 05:47 PM

Outstanding Luc! Glad to hear that you got it figured out and I would love to see any document outlining your steps. I'm sure that someone will find it useful.

As for the other patching alternative. I have been testing AutoPatcherXP which can be found at AutoPatcher.com. It is freeware and what I have done is setup the configuration file to install with just a progress bar after the OS has been installed.

This lets me run a Scripted OS Install, have XP SP2 installed then another job that copies the AutoPatcher files down which is a couple hundred megs in size. The AutoPatcher then starts and installs every patch that you tell it to, in this case I had it do all Critical and Recommended. The install went smooth and easy. The only thing is that I had to use a script to launch the installer. Other than that it was start the job, walk away, come back to a completely installed OS with SP2 and all the latest patches.

On a side note Autopatcher will also let you install WMP 10, the latest flash and shockwave. Definitely worth looking at if something like this is what you have been trying to do.

JAustgen · 01-16-2006, 08:50 PM

I would love to see a short doc! It may lead to a solution for my GSX-based VMs being unable to boot to WinPE.

ldekens · 01-17-2006, 05:57 AM

Attached the in the end not-so-short document about the unattended XP Pro installation on ESX-based virtual machines.

Officially ESX does not support PXE.
For me it works but I suspect VMware will give no support for this way of working.

For the question about WinPE on a VMware GSX server note that ESX does not have a builtin DHCP server (like GSX). I was forced to use a virtual Cisco router and with this setup DHCP, PXE and WinPE work fine.
Luc.

Nick · 01-17-2006, 08:06 AM

Luc,

Thank you for sharing your information! I'm sure others will find it useful.