k3v1nr055

What was the fix?

Thanks for that idea. Just to clarify, I was installing Windows 7 SP1 from the volume license ISO and not as an update to be provided during the "install updates" step. As I stated above what I ended up doing is simply deploying the vanilla version of W7 SP1 and then I created a "capture media" iso and used it to kick off the capture sequence. Once I had the captured image I simply replaced the original W7 captured image with the new SP1 image in a task sequence that had been working very well and, SO FAR at least, both the 32 bit and 64 bit versions seem to be fine. As I also said above, I will almost certainly revisit this again but for the number of base images that I will need to create the "capture media" scenario works fine. Eventually I will probably build a master image that includes all apps that all users here need and have it around for emergency purposes but the ideal that I am working toward is to have just one basic image and use software distribution and software virtualization to provide users and students with just the software they need.

What I have done to workaround this issue is simply use capture media to grab the Win 7 sp1 images. I really only need one each of 32 and 64 bit at this time so I think I am in good shape. I will revisit the Build And Capture scenario later but at this moment I just needed to be able to get the SP1 image prepared to plug into my other working task sequences. Thanks for your help on this.

smsts.log

OK, here is where I am now. Several months ago I had to completely rebuild SCCM 07 after a server crash and failed backup. Before that I was working with a partially working SCCM implementation that I inherited. OSD was working since the consultant who set it up captured the basic image that I was using to deploy from. At this time other OSD tasks ARE working fine (at least as of a few days ago)and we are able to deploy an image with a custom task sequence that installs Win 7 x64, SCCM client, runs updates and installs numerous applications including Office 2010, Flash Player, Quicktime, Adobe Reader, and other apps needed by the staff and students here. I have also set up and deployed Forefront Endpoint Protection successfully and set up some Windows Update packages which also work fine. So basically everything else seems to be OK. I have lots to learn about SCCM but until this problem nothing else has taken more than a day or so to overcome. To answer some of the above questions more thoroughly, I suppose that since my rebuild I have not captured any images. I am attempting to accomplish this via VM Player and Windows Virtual PC (I have tried both with the same results). We use KMS for the license. I have created boot images that work fine and I have attempted this operation via both PXE and with an .iso that I capture with the VM Player's Virtual DVD drive. I am joining a workgroup for this reference image. In yesterday's attempts I created VMs that had the default settings (1 GB RAM, 40 GB Virtual HDD). The operation failed yesterday at the "Install Updates" step and the last two status messages referenced "not enough space" kind of errors. I am not sure if the problem was on the server (which is getting low on space with about 20 GB free out of 256GB on the partition where most of the SCCM files reside and the install is based there also. So then I create VM with 100 GB hdd and 4 GB of ram. The TS still failed but the specific reference to "not enough space" was not there. This morning I tried again but I disabled the "install updates" step and ran the TS again booting initially from the iso. In all the recent examples Window 7 SP1 completely installs and even goes out and begins grabbing updates. However, with the "install updates" disabled the TS fails at the "setup Windows and configmgr step. On the actual VM I will see the progress indicator open up for a second or two and then it disappears and nothing else happens. All I need at this time is one vanilla wim of Win 7 SP1(x86) and one vanilla wim of Win 7 SP1(x64). I am probably missing something that is very simple. In the end though any way of capturing these two .wim files that allows the new image to be used in other SCCM 2007 OSD task sequences will work. I am hoping that once I attain these wims I can just make copies of my working TS and point the task to the new reference SP1, update my DPs and run with it. Is this correct? I am attaching the latest smsts.log from the last attempt. Thanks, Kevin smsts.log

Thanks for your input on this. I am back from vacation and have made some progress. Right now it seems the Win 7 SP1 (x86) is installing in a VM. It seems that my next problem is that the "install updates" is timing out. Then the capture seems to fail (there is no captured wim on the destination server or locally. I have the smsts.log file attached. Again. Thanks for your help and thanks for this site. smsts-20110517-222054.log

I found a post that led me to the setupact.log file that pointed to the drivers and the line "Windows could not install on or more boot-critical drivers". Setup blows up soon after that statement. It seems to be in the "setup Windows and Config Manager" step in the TS. PnPIBS: Installing driver X:\WINDOWS\INF\lsi_sas.inf ... PnPIBS: Installing driver X:\WINDOWS\INF\oem1.inf ... [0x0640ae] IBSLIB PublishMessage: Publishing message [Windows Setup could not install one or more boot-critical drivers. To install Windows, make sure that the drivers are valid, and restart the installation.] I just ran an MDT based task and with a new MDT boot disk image. In the SCCM messages I saw this: The task sequence execution engine failed executing the action (Setup Windows and ConfigMgr) in the group (PostInstall) with the error code 2147500037 Action output: ce\unattend.xml Successfully initialized driver information Command line for extension .EXE is "%1" %* Set command line: "C:\_SMSTaskSequence\Packages\SDS000E3\SOURCES\SETUP.EXE" "/unattend:C:\_SMSTaskSequence\unattend.xml" /noreboot Executing commandline: "C:\_SMSTaskSequence\Packages\SDS000E3\SOURCES\SETUP.EXE" "/unattend:C:\_SMSTaskSequence\unattend.xml" /noreboot Process completed with exit code 31 Windows Setup completed with exit code 31 Entering ReleaseSource() for C:\_SMSTaskSequence\Packages\SDS000E3 reference count 1 for the source C:\_SMSTaskSequence\Packages\SDS000E3 before releasing Delete source directory C:\_SMSTaskSequence\Packages\SDS000E3 Released the resolved source C:\_SMSTaskSequence\Packages\SDS000E3 exitCode == 0, HRESULT=80004005 (e:\nts_sms_fre\sms\client\osdeployment\setupwindows\setupwindows.cpp,440) setup.run(), HRESULT=80004005 (e:\nts_sms_fre\sms\client\osdeployment\setupwindows\setupwindows.cpp,1707) Exiting with code 0x80004005 Windows setup failed, code 31. The operating system reported error 2147500037: Unspecified error

Hi, I am fairly new to SCCM07 (less than 6 month in it) and suddenly I am not able to successfully perform Build And Capture tasks. I am trying to create new Reference_Win_7_SP1.wim file (one each in x86 and x64 versions). My tasks keep failing with a 80004005 error) I suspect this is a driver problem but I was able to build and capture several months ago. The smsts.log is not telling me much but the setupact.log from the x: drive seems to indicate that there are lots of unsigned drivers that are causing windows setup to fail. Any help will be appreciated. I am attaching both logs. BTW: other tasks are still working. I am able to deploy an image with applications. I am using the same boot images generally for both scenarios although I did create and test a new clean winPE boot image today and I received the same result. I will be on vacation all of the next week so if I cannot respond to any replies that is the reason. I will try to look at this board as much as possible though I might have to go several days without access (that's not so bad really! ;-) Again, thanks so much for this site. It has been invaluable to me as I have had to set up and master SCCM07 on my own and pretty much all alone! K smsts.log setupact.log