Jump to content


Recommended Posts

I am trying to build and capture a Windows 7 Ent x64 System (SCCM 2007 R3)

 

I have created the OS image etc and the TS using the SCCM wizard.

 

When my system reboots at the end of the TS I am greeted with the message:

 

BOOTMGR is missing

Press Ctrl+Alt+Del to restart

 

The system I am trying to image needs additional mass storage device drivers that I have added to the boot image and are working (I can hit F8 and see the hard drive in DISKPART).

 

I have also tried adding them to the TS (Apply Driver Package) but still the same error.

 

Please help me troubleshoot this.

 

I have read that using the RTM installation is not recommended but others say it will work?

 

Thanks

 

Andy

Share this post


Link to post
Share on other sites

Thank you for your reply, although I am not sure what you mean by my 'OS Installer'.

 

The source files I am using are the MS W7 x64 RTM files.

 

Is your OS installer valid??

Have you tried new installer files?

Share this post


Link to post
Share on other sites

If it is a build and capture then you have to set up an OS installer and point it to the full source files...with an OS image setup you just need the wim file without all other files......

 

You say that after the TS finishes(at what stage does it finish?) it produces this error.....but does it not try and capture it after it has built the OS?

Share this post


Link to post
Share on other sites

Ok, you mean an 'Operating System Install Package' ?

 

Yes, I have created one and it's data source is pointing at the W7 x64 Ent RTM install files.

 

My TS currently has the capture steps disabled as I want to get the build process working first, then customize the image build steps before moving on to capture.

 

I couldnt figure out how to add a screen shot here so will type the steps in my TS .... (Mostly as created by the TS wizard)

 

Build Reference Machine

Restart in Windows PE

Partition Disk 0

Apply Operating System

Mass Storage Device Drivers (Do I need to do this?)

Apply Windows Settings

Apply Network Settings

Apply Device Drivers

Setup Windows and ConfigMgr

Restart Computer

 

 

Upon restart at the end is where I get the BOOTMGR is missing error....

Share this post


Link to post
Share on other sites

OK this is where you are going wrong......The build and capture with all source files is specifically for BUILD&CAPTURE and not just build.......... disabling capture steps will not work thus your missing BOOTMgr...if you want to just build a machine then create an OS image out of just the install.wim from the sources folder and create a new TS this time using an existing image and not the B&C task sequence....the wim file is all that is needed to achieve this...once you have created the OS image.

 

When you get your B&C working properly and you have your captured custom wim file then you can create a new OS image from this wim file...but for now you could use a standard RTM wim file and see how you get on!!

  • Like 1

Share this post


Link to post
Share on other sites

EDIT: Also just to warn you by just deploying the install.wim from the RTM media will install the OS to the D:\ drive on any machine (this is a major flaw with windows7, apparently windows 8 has overcome this!?)....to get it to install on the C:/ drive of any machine you will have to eventually get a capture TS successfully done...either by the B&C or by a standalone capture media...either way works.

 

But just for testing carry on for now with the RTM install.wim....then you could install all your custom software and then simply use a capture media TS to capture your custom wim..

 

OR

 

If you have all your software packaged then just roll out the install wim(if you cannot get your B&C to work) and then do whatever mods you have to do and capture it.

 

It is also reccommended that all this is done on a Virtual environment as it will have minimum drivers etc.....thats if you do intend to package model specific drivers?

  • Like 1

Share this post


Link to post
Share on other sites

Thanks for the update, some very useful advice there.

 

I will set up a VM envirnment (don't have one as yet) and use that for this work.

 

For now I need to work with this particular system (HP Z620 Workstation) to create an image for it.

 

I am very close now (after followign your advice) but now am coming accross the age old mass storage device driver issue.

 

Where in my TS should these be installed ?

 

Thanks

 

Andy

Share this post


Link to post
Share on other sites

macdat

 

How did you get the sccm imaging to work with your HP z620?

 

I am still unable to get the applying operating system step to work.

 

All drivers are there, but still no luck.

 

Thanks,

JD

Share this post


Link to post
Share on other sites

I feel i should reply to some inaccuracies in your comments Rocketman

 

OK this is where you are going wrong......The build and capture with all source files is specifically for BUILD&CAPTURE and not just build.......... disabling capture steps will not work thus your missing BOOTMgr...

 

This is not correct. We have a number of build and capture task sequences which are effectively split into two - One builds and the second just runs the Capture phase (syspre/prep the SCCM client, captures the WIM). This is to allow for any tweaks or customisations which cannot be easily scripted in the TS. For example, with the XP TS it allows for customising the appearance of the default user profile. You would then push out the second TS as a SD task whcih performce the prep and capture. Its a good method, works well and is supported.

 

As long as you perform all the steps in the Capture group from the B&C TS, then the WIM you create will be valid to use in an OSD TS

 

EDIT: Also just to warn you by just deploying the install.wim from the RTM media will install the OS to the D:\ drive on any machine (this is a major flaw with windows7, apparently windows 8 has overcome this!?)....to get it to install on the C:/ drive of any machine you will have to eventually get a capture TS successfully done...either by the B&C or by a standalone capture media...either way works.

 

This is also not correct - The excellent Hydration kit from Johan Arwidmark, a Microsoft MVP (google Hydration kit if you havent seen it before, it is excellent) simply uses the install.wim from a Windows setup disk without any problems. The OP's problem sounds to me like its due to the OS not being applied to the partition he has designated as the active boot partition. I suspect that making sure the boot partition is active, and using a task sequence variable for the created boot partition which is then referenced in applying the WIM would resolve the boot problem. Additionally, if you ahve a USB pen drive plugged in can cause problems! In fact with XP it will cause all manner of problems trying to use an OSD TS with a pen drive connected.....

 

Hope this helps.

Share this post


Link to post
Share on other sites

Hi Mickey

 

The excellent Hydration kit from Johan Arwidmark, a Microsoft MVP (google Hydration kit if you havent seen it before, it is excellent) simply uses the install.wim from a Windows setup disk without any problems

 

This sounds good..but what I gather from a quick research is that this installs a fully operational test lab of SCCM/ DCs and MDT? Am I correct in this?

If this is the case what about labs/production environments already with SCCM implemented?? Does this KIT not require to be setup alongside the initial setup of SCCM?

 

Have you ever just used a standard RTM install.wim from the media and deployed it? I am quite positive you will end up with an OS installed on a D:\ partition! There are numerous bloggs reporting this problem all over the web...and the fix is to B&C or a standard media capture of a previously deployed OS and then deploy the new wim and it will install on the C:\ partition.....SP1 I think resolves this...well for windows 8 deployment..not sure about windows 7 as i have not installed SP1 as of yet..as it is BETA and I have demolished my testing lab(must try this Hydration kit to get a test lab up and going again) :)

 

Cheers

Share this post


Link to post
Share on other sites

Hi Mickey

 

 

 

This sounds good..but what I gather from a quick research is that this installs a fully operational test lab of SCCM/ DCs and MDT? Am I correct in this?

If this is the case what about labs/production environments already with SCCM implemented?? Does this KIT not require to be setup alongside the initial setup of SCCM?

 

Have you ever just used a standard RTM install.wim from the media and deployed it? I am quite positive you will end up with an OS installed on a D:\ partition! There are numerous bloggs reporting this problem all over the web...and the fix is to B&C or a standard media capture of a previously deployed OS and then deploy the new wim and it will install on the C:\ partition.....SP1 I think resolves this...well for windows 8 deployment..not sure about windows 7 as i have not installed SP1 as of yet..as it is BETA and I have demolished my testing lab(must try this Hydration kit to get a test lab up and going again) :)

 

Cheers

 

I referenced the Hydration kits, not as a solution for this post, but an example of thousands of people using a standard rtm Install.wim to successfully deploy an OS to the correct destination partition (which i presume you mean by "installed on a D: partition").

 

If the client hard disk only contains a single partition, then windows would not assign a drive letter D when installing. I think you are getting confused with installing an OS through the UI without manually create the destination partition using shift+F10, in that circumstance the OS installer automatically creates a hidden partition 0 of 100 mb (or more if you are using an EFI device) and then installs the OS to partition 1. In that case, all the boot files are on partition 0 and if you only capture partition 1 then you obviously are going to be missing all the boot files and the resulting OSD TS will not boot.

 

However, simply applying an install.wim to a drive with only 1 partition causes no problems at all, and does not create any additional partitions (unless your task sequence does) and will boot fine.

 

Hope this helps/clarifies

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

×
×
  • Create New...