pxe boot isue

[bbunjevac]

Thanks to this forum I've taken big steps in OS deploys...so thank you to everybody who's guides I've used and to everybody who's responded to my cries for help-I appreciate it a lot!

 

My current issue is this: (the error I get is attached)

windows PE cannot start because the actual systemroot directory (X:\Windows) is different form the configuired one...

I will also attach the smsts.log and the smspxe.log files. Hopefully these things will help you!

 

Let me know if you rather have me post the logs in my message so that you dont have to download it if you have issues...

 

Thank you!Hopefully I'll find whatever is wrong with this myself!

CHeers

smsts.log

smspxe.log

[bbunjevac]

Thanks to this forum I've taken big steps in OS deploys...so thank you to everybody who's guides I've used and to everybody who's responded to my cries for help-I appreciate it a lot!

 

My current issue is this: (the error I get is attached)

windows PE cannot start because the actual systemroot directory (X:\Windows) is different form the configuired one...

I will also attach the smsts.log and the smspxe.log files. Hopefully these things will help you!

 

Let me know if you rather have me post the logs in my message so that you dont have to download it if you have issues...

 

Thank you!Hopefully I'll find whatever is wrong with this myself!

CHeers

Also, do I need specific drivers injected into the boot.wim file for the OS to be deployed? I assume its the network and storage drivers for the specific motherboards?

[anyweb]

first of all what version of sccm are you running ?

secondly the only drivers you should add to your boot.wim files are Network drivers (sometimes storage too, but rarely) and the network drivers are based on the version of SCCM and not on the os you are deploying

 

eg:

 

if you are running SCCM 2007 sp1, use Windows vista based network drivers

if you are running SCCM 2007 sp2, use Windows 7 based network drivers

 

the drivers used by the os you are deploying (windows 7 or windows xp or whatever) are applied during the Apply Driver Package stage of the Task Sequence,

 

your failure, baseed on the logs provided seems to be here

 

<![LOG[Failed to locate the local data path. The files needed to resume the task sequence are missing. This could be because the task sequence finished while in Windows PE. Please check the largest available partition for SMSTSLog\smsts.log file for more information.

The system cannot find the file specified. (Error: 80070002; Source: Windows)]LOG]!><time="11:17:02.912+240" date="08-30-2010" component="TSManager" context="" type="3" thread="7444" file="tsmanager.cpp:1106">

<![LOG[Task Sequence Manager could not initialize Task Sequence Environment. code 80070002]

 

so can you tell me a bit about how you set up your task sequence, how are you executing it etc..

 

cheers

niall

[bbunjevac]

I have solved the issue I get with the WinPE crapping out, the issue was that I had to re-create the WINPE image, I think this is because the img I was using did not have the 3 windows components that SCCM2007 requires to use (scripting, wmi, and xml)(xml is included in all base winpe images nowadays)...SO now I got to the part where the client actually downloads the .wim image and applies it, it got through about half of the application and then crapped out to this error code

0x80070032

 

the smsts.log is located in C:\Program Files\SMS_CCM\Logs for me but it has not updated since early yesterday morning but since you said that i should check my largest partition I assume that its not the one you want me to check:

I found the 1 on my D partition(largest)

this one has not ben updated since 6/24/2009!

 

Any suggestions?

 

----------------------------------------------

 

I am using sccm2007 SP2 so I assume I have to get the windows 7 drivers for it-where can I get my hands on the generic ones?

Also this is my imaging process...I'll explain it to the best of my ability!

 

I have a custom collection in which I added my lab box to using the computer association feature and I refresh the clients ability to get an OS deployed to it by clearing the last pxe advertisement and using the query feature available in the collections settings.

I use the WInPE x64bit image as the lab box is of 64bit architecture (quad-core).

I created a package under operating system images in which its a base 32bit Windows 7 one (already been captured manually by me using the imagex cmd from WinPE)

I created a task sequence for it and made sure to use the 64bit WinPE boot image.

 

Em assuming that the info I just gave you isn't the most descriptive or enough-please let me know what other information I should provide.

[bbunjevac]

you can close this thread!

my issue was that i was using a 64bit winpe image to deploy a 32 win7 OS