Search the Community

Hi everyone, we are using SCCM 2007 R3. We use Task sequences to deploy the OS in combination with a bootable media (DVD). They told me I had to create a new bootable media everytime I make a change in the Task sequence. Is it really necessary?

I am not too familiar with SCCM 2007. My goal is trying to make a bootable media (with network access), so my local lab guy can deploy Windows ThinPC (WES 7) to machines. I do not want him to use/touch the configuration manager console. I just want him to be able to copy an .iso from me to multiple jump drives, then deploy the new OS to machines. So, in SCCM 2007, I right click on my Task Sequence --> Create Task Sequence Media. I select the 2nd "Bootable media" SCCM made it in .iso then I extracted it to a jump drive. I plugged in the jump drive into my destination computer, and boot from it. Then, I get the following error message: "Unable to read task sequence configuration disk. For more information, please contact your system administrator or help desk operator." I google the error message online and see what's the issue. I found this link. It mentioned about checking and see if the network card driver is running. Sure enough, when I do ipconfig, it is not showing anything. But, if I do PXE boot, same boot image, it will boot just fine. In case I missed anything, I went back to SCCM 2007 and import the LAN drivers into the boot image. After rebuilding the boot image, same error message. So, I researched more, and found this link. It mentioned to run “wpeinti.exe”, it will load the network adapter. Then, run “x:\sms\bin\i386\TsBootShell.exe” to relaunch. Unlike the description in that link, mine did not kick off the build process. Instead, I got another error message: “The instruction at 0x77057a1f referenced memory at 0x00000028. The memory could not be written. Click on OK to terminate the program.” Now, I am stuck. I tried manually inject the network drivers into boot image, no help. I manually put the sleep command into the boot image, no help. I attached my smsts.log if that will help. Please help! Thanks! smsts.log