Hello everyone. I am trying to perform a bare metal deployment to an HP 8530P using Windows 7 Enterprise (x86). I used the basic task sequence for deploying an operating system. I format the drive with quick format and tell it to apply the OS to the first drive and use C:. When I use the "Apply Operating System from captured image option and point it to the OS install package which uses the install.wim from the source, my OS gets installed to teh D: drive instead of C:. I understand that this is because the install.wim is itself tied to the D: drive when it runs, and thus explains that behavoior.The problem comes in when I try to install the OS from its original installation source. I have had this work in the past and now for whatever reason I cannot figure out what is going on. Both log files say that the Apply Operating System step in the task sequence completes successfully, but this is incorrect as when the OS is installed from an image it takes a few minutes to copy and apply the install.wim file to the HDD. When I install it from the source, this step calls itself complete within one to two seconds. The drivers are all in place as again, I am using the installation source in both cases. It succeeds from the install.wim, but I need it on the C: drive and not D:, so I really need it to work from the installation source. I can also get this to work with XP Pro SP3 with no problems.Here is the web report error for the last step in the sequence where it says it fails:"on to C:\_SMSTaskSequence\unattend.xml Successfully saved configuration information to C:\_SMSTaskSequence\unattend.xml Successfully initialized driver information Command line for extension .EXE is ""%1"" %*Set command line: ""\\SERVER\SMSPKGE$\PKGID\SOURCES\SETUP.EXE"" ""/unattend:C:\_SMSTaskSequence\unattend.xml"" /norebootExecuting command line: ""\\SERVER\SMSPKGE$\PKGID\SOURCES\SETUP.EXE"" ""/unattend:C:\_SMSTaskSequence\unattend.xml"" /norebootProcess completed with exit code 31Windows Setup completed with exit code 31Entering ReleaseSource() for \\SERVER\SMSPKGE$\PKGIDreference count 1 for the source \\SERVER\SMSPKGE$\PKGID\ before releasingReleased the resolved source \\SERVER\SMSPKGE$\PKGIDexitCode == 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 0x80004005Windows setup failed, code 31"Thanks for your help in advance!

BTW, no activation key is being used. Using KMS and do not need the key.

You should always use a (re-)captured WIM and not the original install.wim from the installation media for your deployment task sequences; i.e., don't directly import the install.wim as an OS Image. Use an OS Install Package to create your (re-)captured WIM using a build and capture task sequence and then use this WIM for your deployment.Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys

Well, I can't even get that far. Using the build and capture TS (referencing the OS install package) I still get the same results. If I use the OS Image, which points to install.wim, it will work, but create the D: drive issue noted before. The only thing I can think to do is recopy the OS source files and recreate the package.

as Jason says don't use the original WIM, instead do a Build and Capture task sequence documented step by step right here once you have captured that wim, you can use that wim to deploy 7 cheers niall My step by step SCCM Guides windows-noob on Twitter

Not working. Cannot get the orginal build and deploy to work - getting same errors as stated above.

are you using or specifying an unattend.xml file in your task sequence ? My step by step SCCM Guides windows-noob on Twitter

No, it doesn't even get that far. It dies before the first reboot, after applying the driver package, which works when I install it using the install.wim image. When it runs form the source package it completes the OS copying and installation step in one second and then starts applying drivers.So I get the partition and format to work, it says it successfully completes the Apply OS step, but there's no way it does that in one second. I think I am going to delete and re-copy the source files and remake the OS package. I already tried remaking tha package from the current source and there was no change.

As an update - I deleted and replaced all packages and source data and recreated the OS install packages. I still get this problem, which I am positive is caused by the Apply OS step only taking one seond (and I really mean one second) to complete. When I hit F8 and navigate to the C: drive, I type dir and only have a folder for smstslog listed. No other windows directories. But the drivers are all downloading and installing. Almost as if they are installing onto the boot image running on the machine instead of to the C: drive, likely because there is no directory structure to install to... What gives?

How are you creating the OS Install Package (exactly)? Is it actually listed under the OS Install node after you import? Did you copy the source files (all of them; i.e., the entire contents of the DVD) to your source repository and then create the OS Install package from these source files (not referencing install.wim in any way)? Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys

Yes, exactly as you should.

OK, back on this now. I have successfully installed and captured XP in this manner. After watching that process intently I realize I may be off base as to how long it should take the TS to apply the OS image during the "Apply Operating System" step. That part went really fast with XP, but the files weren't copied and installed until the "Setup Windows and ConfigMgr" step, which seems to be the actual step where the installation files are copied to the hard drive and the installer runs. This is where my TS falls apart and I get the HRESULT=80004005 error. I really wish MS would do a better job with these error codes. Here is the message in the report I ran for the TS:I am feverishly searching Google for a resolution and trying everything I can to get this resolved. Thanks for the help everyone! 2147467259 on to C:\_SMSTaskSequence\unattend.xml Successfully saved configuration information to C:\_SMSTaskSequence\unattend.xml Successfully initialized driver information Command line for extension .EXE is "%1" %* Set command line: "\\MMSCCM01\SMSPKGE$\ATL00034\SOURCES\SETUP.EXE" "/unattend:C:\_SMSTaskSequence\unattend.xml" /noreboot Executing command line: "\\MMSCCM01\SMSPKGE$\ATL00034\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 \\MMSCCM01\SMSPKGE$\ATL00034reference count 1 for the source \\MMSCCM01\SMSPKGE$\ATL00034\ before releasing Released the resolved source \\MMSCCM01\SMSPKGE$\ATL00034exitCode == 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

After some more research I came across this:http://verbalprocessor.com/2008/02/27/build-and-capture-task-sequence-failure/which wasn't the issue in my case as I don't use product keys, but it led me to look in the x:\windows\temp\smstslog\WindowsSetupLogs. Once there I noticed the setuperr.log file was empty, and looked in the setupact.log. What do you know, at the bottom there was a line stating that "Setup could not install one or more boot critical drivers." I am trying to deploy an HP 8530P laptop, so anyone that has any input as to what drivers are needed would be greatly appreciated. I have downloaded, extracted, and imported everything I could find for Windows 7 on this model. I am going to attempt an install of of a DVD and see if it works that way.

Resolution found - remove driver packages from TS. I verified that the Windows 7 DVD could complete installation without the addition of any extra drivers, so I removed the packages from the TS. Now it is working fine from the installation source. For the HP 8530p the only drivers missing are the 3D Dataguard and the Ricoh media card reader. Everything else is there and updateable through Windows Update. Thanks!

Sorry to hijack the thread but can you explain You should always use a (re-)captured WIM and not the original install.wim from the installation media for your deployment task sequences; i.e., don't directly import the install.wim as an OS Image. Use an OS Install Package to create your (re-)captured WIM using a build and capture task sequence and then use this WIM for your deployment. if all i want is a 'vanilla' image and want to use the layered approach.. can i not use original install.wim as my original 'vanilla' image, on top of which i will be layering other apps either tyhrough task sequence of software packages sorry to hijak once again.

You can use the original one in theory, but that will end up in being deployed to the D: drive. That's one reason why it's recommended to create a custom wim image.

Not necessarily. If you create the operating system image from the source install.wim you can set the installation and formating options in your task sequneces to the C: drive. I may have it backwards (meaning it may have to be done through OS install packages), but there is a way to use the source and set it to install onto the C: drive. One of them will definitely install it to the D: drive due to the install.wim being based to run from a DVD, commonly D:. But there is a way around it.

Unfortunately, that does not work. Windows setup goes through great pains, or so I've read, to "fix up" the default install.wim so that it can be installed to the C drive; the WIM itself was built with these known limitations. This was rumored to be fixed in Win 7 but is not.Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys

Respectfully, I have pulled this off several times in my setup. I will go back and retrace my steps to see what the difference is, but either the OS Image or the OS Install Package version allows you to install to the C: drive. The option is there for both, but only one of them actually works. I will post back as soon as I can recreate what I did to achieve this.

I have confirmed that if you create an OS install package pointing to the source installation folder and use the Apply operating system from original installation source pointing to the package for Windows 7 and selecting Destination: Specific logical drive letter and Drive Letter: C: options it will install to C:. If you use the captured image it points to the operating system images under \sources\install.wim and that will install it to the D: drive no matter what. I apologize for the run-on sentence. ;-)

That is the expected result. Using an OS Install Package and Apply OS task merely runs Windows setup from the source files, it does not directly apply the install.wim. Windows setup then applies the install.wim and performs its fix-ups.Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys

Sorry guys i still havnt understand what you are trying to imply. I just want 'vanilla' image with nothing at all (i.e. no office, any apps etc) as i will be using a layered approach ! which is using the task sequence i will be installing applications etc. so that i can have different flavours. Now do i need to use 'Build & Capture' process as well to achive this. as i thought install.wim in the source folder would let me do this. and i wont have to captute my .wim. But i was to do this way. What am i achieving i am in essence capturing exactly the same file? am i not? please help me clarify this. Techie.

Yes, you need to use a build and capture to recapture the installation. If you don't, Windows will be installed to the D drive. I recommend that you at least add the current Windows Updates to your image also. The whole point of the image is to speed the process up and include common lengthy tasks so that they don't have to be repeated during deployment. Applications in the image are often debatable, but the same argument goes here, include them in the image to reduce deployment time.Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys

Sorry for bringing this thread from the dead, but I'm having a similar issue. I did a build and capture from source Win 7 64 bit Enterprise SP1. I used the UDI Wizard step by step guide for UDI deployment. I created a reference machine and all the packages that went along with it: mdt update 1 files - reference, reference computer custom settings, etc. I then followed the steps to create the packages and deploy the target machine using the captured reference system. It created software packages similar to the reference, but now they are called Target. I edited the necessary UDI xml file to offer the things I want to offer (domain and OU selection, applications (currently disabled), etc. I deploy that system with my boot up media, it connects, sees the advertised task sequence pulling the OS image from the reference machine (captured image). It's a 100% full format of the system. It loads and joins the domain properly but the OS is on D. I'm not using the install.wim from the raw media, this is a captured image. Some notes: I didn't build and capture on a virtual. I used a physical system for that, same exact hardware. I had some issues with software updates and application installs, so I've disabled the updates in the TS and have made sure not to check any applications to install during the UDI build. I'm trying to resolve one problem at a time.

When you did your build and capture, did you you use an OS Install Package or an OS Image (install.wim)?Jason | http://myitforum.com/myitforumwp/members/jasonsandys/ | Twitter @JasonSandys

I know I created an OS Install Package, but when I go back and look at the reference machine task sequence, it looks like the "apply os" is pointing directly to the original source install.wim. Am I looking in the wrong place or did I select the wrong source when I created the reference machine? I guess I should probably start over with the capture, going step by step through the UDI guide again and make sure I select that OS Install package that I have created instead of possibly just selecting the os install image. Do you recommend building this on a virtual instead of a physical machine? I suppose I could re-do it that way as long as I'm starting over.

Hello, Here is a step by step description on how to go about doing a deployment: http://www.windows-noob.com/forums/index.php?/topic/1182-deploy-windows-7-enterprise/ I want to make sure that you are really doing the "Build and Capture" and not the "Install an existing image" process. Just keep this in mind: 1- Create an "Operating system package" and not Image. it will be asking for the path to the source folder and not to a .wim file 2- When you start creating your TS, on the first screen wizard make sure you choose the second option to "Build and Capture a reference operating system image". After this scenario to build the OS and then capture the image (.wim), you then can use the resulting osd image (.wim file) to deploy to other machine. At this point with your new Task sequence choose the first option when creating you TS on the first wizard and specify the .wim file you captured during your first scneario. Good luck, Mahmoud MS-SCCM test team

Using a VM is generally considered a best practice because VMs are easy to reproduce, don't tie up actual resources, are portable, can be easily accessed from a remote location, require fewer (if any) drivers not already included on the Windows media, and generally represent common/least-common denominator hardware.Jason | http://myitforum.com/myitforumwp/members/jasonsandys/ | Twitter @JasonSandys

Thanks for the updates, I've gone through the initial process again using the UDI Wizard step by step guide for creating the reference image, recreating all the packages as outlined within except for the config mgr install and USMT (I'm using the existing packages for those). I'm waiting for my OS System Install Package to distribute and then I will create the TS and Media and test the build and capture on a virtual. Any issues with using a Windows Virtual PC virtual? I'm not sure how I missed the OS Install Package step, I have one created, but somehow it wasn't being utilized in that initial build and capture. I must have missed that in one of my many attempts to get this to build properly. I'll report back after I've done the build and capture and then attempt to deploy to a physical target pc using the rest of the UDI Wizard guide.

Found one issue with using Windows Virtual PC to build my reference... it only supports 32 bit... I'm doing all my Windows 7 work in 64 bit. I don't have a hyper-v sand box to play with.

I would never actually recommend Virtual PC, the product is like 5 years old. If you don't have Hyper-V or ESX available, then use VMWare Workstation or Sun VirtualBox (free). Or, load Hyper-V server (the free version) on a desktop system.Jason | http://myitforum.com/myitforumwp/members/jasonsandys/ | Twitter @JasonSandys

Added Hyper-V role to a server... testing the new build and capture, I'll deploy to target once it's done and report back next week. Thanks for your help.

hyperV works great, only thing you need to remember when deploying to your vm's is to set the network card to Legacy Network Adapter (for PXE boot), I use hyperV all the time for my lab work, love it ! cheers niall My Step by Step ConfigMgr Guides I'm on Twitter > ncbrady