Issues with PXE on client computer

[Cyrius]

Hi everyone,

This is my first post here so go easy, I couldn't find this exact info :-)

I have set up WDS on a 32-bit Windows Server 2008 Standard box. I was following the quick start guide for using it, then attempted to use a guide to capture a client image.

The original install and boot images pulled off the disc fine, and I was able to create a capture image through the MMC snapin. The capture image is Win 7 64bit.

Then, I ran sysprep /oobe /generalize /reboot and this works all fine and dandy. By this I mean I have a generalized OOBE once PXE fails!

Once the system reboots and I go to PXE it goes through "Loading Windows Files" then ends with the following error (Had to copy it from somewhere, mine says dism and not peimg):

Windows PE cannot start because the actual SYSTEMROOT directory(X:\Windows) is different from the configured one (x:\Windows~BT\Windows). This can be configured with the peimg /targetpath command. Please consult the documentation for more details. Press the OK button or close this message to reboot.

Could someone help me out here? I am not very familiar with DISM OR WDS, and none of this stuff was talked about in the guide. Since my familiarity with these deployments is minimal, please keep it so I can understand it

If you need any more info from me let me know please.

Thank you very much!

[Tripredacus]

What media did you use to create the capture image?

Try creating a 32bit capture image instead.

[Cyrius]

It was a Windows 7 Professional x64 disc.

I really want to avoid having x86 on my network because we have already run into issues with printer shares coming from x64 to x86 systems.

Can you create a x64 image from a x86 capture?

[Tripredacus]

An x86 boot image can install both x86 and x64 using Setup for both Vista and Windows 7. You can also use an x86 WinPE to capture and deploy x64 images using Imagex.

Anyways, just try a 32bit one. The only reason I ask is because of your server. I don't know if it has anything to do with it.

[Cyrius]

I will give it a shot. I will let you know whether or not this works.

Thanks!

[Cyrius]

By the way, is this the correct forum area? Should I have posted this elsewhere?

[Tripredacus]

By the way, is this the correct forum area? Should I have posted this elsewhere?

This is a fine place. If the troubleshooting moves into another direction and moving the topic to another area provides better visibility, it will be considered.

[Cyrius]

K thanks

[Cyrius]

x86 image did not work

Since it looks like I will have to dig in to dism I have a quick question.

In your opinion would this error would be referencing the capture boot image I created or some problem within the host I am using to create the custom image?

Edited October 14, 2011 by Cyrius

[iamtheky]

i believe it's referencing the boot.wim

in case you havent tried going back to the beginning, open your deployment tools cmd window

1) ' COPYPE X86 C:\WinPEx86'

2) 'mkdir c:\winpex86\export'

3) imagex.exe /export C:\winpex86\winpe.wim 1 C:\winpex86\export\x86boot.wim

replace your boot.wim in WDS with that x86boot.wim in your export folder and see if the issue persists...

Edited October 14, 2011 by iamtheky

[Cyrius]

i believe it's referencing the boot.wim

in case you havent tried going back to the beginning, open your deployment tools cmd window

1) ' COPYPE X86 C:\WinPEx86'

2) 'mkdir c:\winpex86\export'

3) imagex.exe /export C:\winpex86\winpe.wim 1 C:\winpex86\export\x86boot.wim

replace your boot.wim in WDS with that x86boot.wim in your export folder and see if the issue persists...

I will do this, but where do I run this from??? I just used WDS and I cant find a command window for it.

Maybe I am just being dumb here, give me hints? haha

[iamtheky]

its a shortcut created by WAIK, you can also just run

C:\WINDOWS\system32\cmd.exe /k "C:\Program Files\Windows AIK 3\Tools\PETools\pesetenv.cmd"

Your argument path might be different depending on your system architecture and version of WAIK. Just search for pesetenv.cmd and use that path, if its not there, go install WAIK.

[Cyrius]

Alright thanks!