• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1735
  • Last Modified:

Windows 2008 Sysprep Change Hal

Hi all:

I recently had to migrate my Windows 2008 32-bit (Non-R2) vmware guest image to ESXi 4.1u1 from VMWare Server 1.0.10

Unfortunately the image is not booting on the ESXi box and keep blue-screening. As far as I'm aware it is because of dissimilar hardware, which is why I decided that a sysprep would fix the issue... The odd thing is, I cannot seem to execute sysprep?!

I tried using the installation CD, and in the command prompt I typed sysprep, nothing happened.
I booted off of MS-DaRT v6.5, and used its command prompt, and got an error about ActionQueue.dll missing

How does one go about sysprep'ing a windows server 2008 system after the fact, where you don't have access to the running/working environment to sysprep and shut it down properly.

Any help is much appreciated. I do NOT want to be quoted a bagillion KB articles, a simple: "go here, and do this" would earn you the 500 points!
  • 5
  • 4
1 Solution
Subhashish LahaCommented:
Please go through below, it has the link for downloading "Windows Automated Installation Kit" which includes Sysprep and the screenshots to configure Sysprep.

ovpritAuthor Commented:

I would appreciate it if you could please read my question before giving suggestions. As my question indicates, if I could BOOT the server in the first place, I'd be able to do a sysprep and wouldn't be asking questions here.

Can you pass us the blue screen top row error please? usually it states a file or error code. 0x0000DE or similar

Check if previous count of cpus is still the same for this VM. (changing from 1 cpu to 2 cpus can cause bluescreens/boot problems)
in VM settings for the guest, check that the type of disc-controller is same or similar.
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Subhashish LahaCommented:
Sorry for above comments.

If you are sure that the issue occurred due to different Hal, you can follow below steps

- You can boot the machine with WIndows 7 / Windows 2008 ISO / CD
- Click Repair your computer.
- Click the operating system that you want to repair, and then click Next.
- In the System Recovery Options dialog box, click Command Prompt.
- Run below commandline
    bcdedit /store C:\Boot\bcd /set detecthal Yes

Or, you can rebuild BCD store using Bootrec.exe

-  Type Bootrec.exe on commandline and press ENTER.

Please let me know if that helps
ovpritAuthor Commented:
c:\> bcdedit /store C:\Boot\bcd /set detecthal Yes
An error ocurred while attempting to reference the specified entry.
The system cannot find the file specified

c:\> bootrec

Repairs critical dis structures. The following commands (...) gives me 4 options: /FixMbr, /FixBoot, /ScanOS and /RebuildBcd

c:\> bootrec /rebuildbcd
Scanning all disks for Windows installations.

Please wait since this may take a while...

Successfully scanned Windows installation.
Total identified Windows installations: 0
The operation completed successfully.


Next? ;)
Subhashish LahaCommented:
As per the output of Bootrec.exe commandline, it is not able to find any windows installation

"Total identified Windows installations: 0"

When you selected "Repair your computer", did it showed any OS details?

You can open command prompt and change to C drive then run "DIR". Check is it showing any relevant data.

As you earlier mentioned, you migrated the VM from ESXi 4.1u1 from VMWare Server 1.0.10.
VM disk are configured previously on IDE controller or on LSI controller. Now, after migrating, what is the Storage controller configred for disk?

ovpritAuthor Commented:
@subhashishlaha & @warddhooghe:

I didn't realize that the default controller picked is the SAS one, I switched it back to Parallel and it seems to be booting the image now. I will try to sysprep as soon as the system comes up, then do the changes.

Will report back with updates shortly.
ovpritAuthor Commented:
Hey guys... So I am a little upset as sysprep took away ALL the settings, and literally blew it back to "fresh install" status.

How would I go about increasing the CPU count and switching from Parallel to SAS without going into the BSOD issue? The bcdedit method didn't seem to work and yes @subhashishlaha C: drive did contain the c:\Boot\BCD file and was visible.

Is there a way to set it to detecthal while it's booted with the old settings, then I set that somehow, and shutdown, do the changes the boot it up?
Subhashish LahaCommented:
You can run below command to change HAL settings for supporting multiple CPUs while Windows is booted.

- Open command prompt as Administrator
- bcdedit /set {default} detecthal yes
- bcdedit /set {current} detecthal yes

After running above commands, shutdown the machine and then increase CPU count and boot.

For changing Storage controller:

- First add additional Disk as SAS disk to VM and boot.
- Install SAS controller driver and check that additional disk is detected in VM.
- Then remove the additional Disk and change the Boot disk from Parallel to SAS controller.

ovpritAuthor Commented:

We got off on a rocky start there partner, but you pulled thru! Thank you so much for all the assist, and you more than deserve the points!

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Upgrade your Question Security!

Your question, your audience. Choose who sees your identity—and your question—with question security.

  • 5
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now