Jump to content


mqh7

build & capture cm2012

Recommended Posts

NO MATTER WHAT I DO THE OS INSTALLS TO D:\WINDOWS

windows-Noob web page http://www.windows-noob.com/forums/index.php?/topic/6353-using-system-center-2012-configuration-manager-part-7-build-and-capture-windows-7-x64-sp1/ I've done this and it does not work.

I have watched YouTube video's and nothing I do works.

All I want to do is create a .WIM image that I can then Deploy via MDT/UDI to our environment. If the INSTALL.WIM that ships with Windows 7 defaults to D:\ then why even put it in there? What use is it?

When I create my CM2012 Build & Capture Task Sequence I only have 1 option which is to Use "IMAGE PACKAGE" Which only allows you to use a .WIM file and from what I've read you are supposed to grab the .WIM from the Windows 7 soruce CD. But that does not work since it defaults to D:\Windows. So how do you do this?

I need to have a WIM image that I can then deploy using MDT/UDI but it seems impossible to create a build and capture WIM.

I did all of this in SCCM 2007 no probably, in fact it took about 4 hours to get it all done and working. What is so secret about CM2012?

Share this post


Link to post
Share on other sites


I read another thread and the answer was.

 

Hi,

If you already have a properly configured reference machine, then yes, you could/should skip this step. This Build phase is there to help you create and configure the reference machine in a guided, automated way. If for any reason you never have to make this first step (let's say you receive the image 'ready' from another team), then of course, you would skip it.

I tried this. I have a generic Windows 7 install that is on a VM. I created a new Task Sequence that only has the following steps.

Restart in Windows PE

Prepare Configuration Manager client

Prepare OS

Capture the Reference Computer

this fails with the following errors.

Expand a string: FullOS TSManager 3/28/2014 2:25:13 PM 1384 (0x0568)
!bInWinPE, HRESULT=80070032 (e:\nts_sccm_release\sms\client\tasksequence\executionengine\instruction.cxx,518) TSManager 3/28/2014 2:25:13 PM 1384 (0x0568)
The step (Prepare Configuration Manager Client) must be running in full OS TSManager 3/28/2014 2:25:13 PM 1384 (0x0568)
!--------------------------------------------------------------------------------------------! TSManager 3/28/2014 2:25:13 PM 1384 (0x0568)
Failed to run the action: Prepare Configuration Manager Client.
The request is not supported. (Error: 80070032; Source: Windows) TSManager 3/28/2014 2:25:13 PM 1384 (0x0568)
MP server http://MGH-SCCM12-01.OurCompany.org. Ports 80,443. CRL=false. TSManager 3/28/2014 2:25:13 PM 1384 (0x0568)
Setting authenticator TSManager 3/28/2014 2:25:13 PM 1384 (0x0568)
Set authenticator in transport TSManager 3/28/2014 2:25:13 PM 1384 (0x0568)
Sending StatusMessage TSManager 3/28/2014 2:25:13 PM 1384 (0x0568)
Setting message signatures. TSManager 3/28/2014 2:25:13 PM 1384 (0x0568)
Setting the authenticator. TSManager 3/28/2014 2:25:13 PM 1384 (0x0568)
CLibSMSMessageWinHttpTransport::Send: URL: MGH-SCCM12-01.OurCompany.org:80 CCM_POST /ccm_system/request TSManager 3/28/2014 2:25:13 PM 1384 (0x0568)
Request was successful. TSManager 3/28/2014 2:25:13 PM 1384 (0x0568)
Set a global environment variable _SMSTSLastActionRetCode=50 TSManager 3/28/2014 2:25:13 PM 1384 (0x0568)
Set a global environment variable _SMSTSLastActionSucceeded=false TSManager 3/28/2014 2:25:13 PM 1384 (0x0568)
Clear local default environment TSManager 3/28/2014 2:25:13 PM 1384 (0x0568)
Let the parent group (Capture the Reference Machine) decides whether to continue execution TSManager 3/28/2014 2:25:13 PM 1384 (0x0568)
The execution of the group (Capture the Reference Machine) has failed and the execution has been aborted. An action failed.
Operation aborted (Error: 80004004; Source: Windows) TSManager 3/28/2014 2:25:13 PM 1384 (0x0568)
Failed to run the last action: Prepare Configuration Manager Client. Execution of task sequence failed.
The request is not supported. (Error: 00000032; Source: Windows) TSManager 3/28/2014 2:25:13 PM 1384 (0x0568)
MP server http://MGH-SCCM12-01.OurCompany.org. Ports 80,443. CRL=false. TSManager 3/28/2014 2:25:13 PM 1384 (0x0568)
Setting authenticator TSManager 3/28/2014 2:25:13 PM 1384 (0x0568)
Set authenticator in transport TSManager 3/28/2014 2:25:13 PM 1384 (0x0568)
Sending StatusMessage TSManager 3/28/2014 2:25:13 PM 1384 (0x0568)
Setting message signatures. TSManager 3/28/2014 2:25:13 PM 1384 (0x0568)
Setting the authenticator. TSManager 3/28/2014 2:25:13 PM 1384 (0x0568)
CLibSMSMessageWinHttpTransport::Send: URL: MGH-SCCM12-01.OurCompany.org:80 CCM_POST /ccm_system/request TSManager 3/28/2014 2:25:13 PM 1384 (0x0568)
Request was successful. TSManager 3/28/2014 2:25:13 PM 1384 (0x0568)
Executing command line: X:\WINDOWS\system32\cmd.exe /k TSBootShell 3/28/2014 2:25:17 PM 612 (0x0264)
The command completed successfully. TSBootShell 3/28/2014 2:25:17 PM 612 (0x0264)
Successfully launched command shell. TSBootShell 3/28/2014 2:25:17 PM 612 (0x0264)

Share this post


Link to post
Share on other sites

 

I tried this. I have a generic Windows 7 install that is on a VM. I created a new Task Sequence that only has the following steps.

Restart in Windows PE

Prepare Configuration Manager client

Prepare OS

Capture the Reference Computer

 

 

If you want to capture a reference machine you do it through capture media or B&C.

Right click create Task sequence Media (not Task sequence)

Select Capture media and go through the process and save your capture media.

 

On the VM you are trying to capture simply attach the capture ISO in Hyper-V or whatever Virtual platform you are using and run it.

This will sysprep the VM and capture the wim file to a share.

This will then be able to be deployed out as an image to any machine and will install on the C drive.

Share this post


Link to post
Share on other sites

so basically you are having issues with Windows on D: after build and capture ? that's a well known problem solved with Set OSDPreserveDriveLetter to False before the Apply Operating System step in your build and capture task sequence, this variable wasn't present until SP1 but i'll update the guide to reflect this.

 

update: i've updated the original guide and added Step 8a. hope this helps.

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...