Windows Deployment Server and Multi/Uniprocessor

I have recently loaded a couple of XP images to our WDS server that were built on a uniprocessor machine. I have noticed that when trying to load these images to a multiprocessor machine they do not show up as an option. I think this microsoft article kind of explains what is going on. 

My question is, short of rebuiding these images from scratch on a multicore, how can I trick WDS to install these on those particular systems? I have already tried changing the processor in the BIOS temporarily but it throws up some kind of DHCP error when loading WDS. A complete and simplistic solution is key. Please help!!! Thanks in advance!
Who is Participating?
jbyrd1981Connect With a Mentor Author Commented:
I think I found my answer and I will post so that others may find it easier than I have. If I load the single core images to a multicore machine and apply the following procedure it will bring the other processor back. I have tested it and it works!! I should then be able reseal and load this image up the WDS and then the multicore machines should be able to see it and use it. I have not tested the second part out but I do not see any possibility of failure. I will post back with the results as soon as I complete the procedure. Here is my find available on this link and I have posted the relvant part.

Option #1 - Hal / NToskrnl replacement
a. Make a directory called DUO on C:\
b. Copy halmacpi.dll (search your C:\ drive for this) to C:\DUO then rename it to hal.dll
c. Copy ntkrnlmp.exe (search your C:\ drive for this) to C:\DUO then rename it to ntoskrnl.exe
d. Make a batch file called go2core.cmd and put this in the file.

REN hal.dll hal.old
copy C:\Duo\hal.dll C:\windows\system32
REN ntoskrnl.exe ntoskrnl.old
copy C:\Duo\ntoskrnl.exe c:\windows\system32

e. Run Go2Core.cmd from C:\duo directory.
f. Reboot and you should now see two processors in Task manager
BrianIT ManagerCommented:
This isn't going to be possible because the HAL is different for multiprocessor systems.  Its more than just a few registery changes.

jbyrd1981Author Commented:
What if I loaded the image on the multiprocessor machine a different way and then did a non-destructive reinstall using the XP disks? Would this reset the HAL to multiprocessor?
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

BrianIT ManagerCommented:
Never tried that.  I'm really not sure if it would work or not.

James HaywoodCommented:
You could try loading the image onto a machine with very similar hardware (except the processor type) then transfer the harddrive into the multi-processor machine. When it boots windows will recognize the new type processor and load the necessary files.
Like i said this will only work if the hardware is similar.
James HaywoodCommented:
Oh and then you can re-image the machine
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.

All Courses

From novice to tech pro — start learning today.