Jump to content

Recommended Posts

Posted

Hi Guys,

 

I am running a development Environment (before moving to my live system) with SCCM 2012R2 for OSD. We are using MDT to deploy Windows 8.1. After every deployment the computer is unable to boot saying it can't find the boot drive. We have a single Windows 8.1 Enterprise Image ready for install that we have captured. We have set the Task Sequence up to install the OS Image (2-2) onto Disk 0 partition 2.

 

A few things that I have noticed:

1) In the OS Selection section of the OS Deployment it says 'Windows 7 RTM' is this correct?

2) If I try and apply the 1-1 image to Disk 0 Part 1 the Computer boots but it says there was an error and to run Start Up Repair (I haven't tried this as yet).

 

Does anyone have any suggestion as to why this might be happening?

 

Kind Regards,

Posted

This is ringing a bell with me, but it's been a long day and I can't remember exactly why. There are two possibilities floating around in the back of my mind:

 

1) This could be something to do with the 100Mb "system" partition Windows likes to create itself when you let it do its own thing as part of setup. I know we had problems with that very early on in our Windows 7 deployment but can't remember what as it's years back - now we force Windows (even 8.1) to install into a single partition when we build master images prior to sysprep/recapture.

 

 

2) Are you using the correct SCCM capture process? We used to use the WDS capture boot image after sysprepping our images for redeployment as the thought was it would give us more control over the process but I know we had issues with that too, something about it not generalising an image built using a SCCM 2012 task sequence correctly. We now run the inbuilt SCCM capture image task sequence, using the SCCM capture boot image, and that works fine for us.

 

 

I can't remember if the issues we had deploying images we'd built ourselves were as a result of one or the other (or both, or neither!) of the points above, but we haven't seen that sort of problem for a long time since so I hope my ramblings prove some help!

Posted
We had a similar problem with uefi bios but due to time constraints ended up putting all our computers on legacy rather than fixing the problem.
Posted

Hi,

We are currently testing the Deployment in Hyper-V so not sure about UEFI but will check. The 3 Partitions are all still there I haven't deleted them.

 

TheCrust - I am using the built in Capture Image process using a Bootable ISO image on a VM.

 

I have Managed to download the Log File to one of our Servers so will upload it while I am looking through it later tonight.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...