Jump to content


wickedang3l

SCCM 2012 R2 Build & Capture issues

Recommended Posts

Greetings All,

 

I started a dialog with anyweb in PM about an issue I'm facing in my environment and the notion that this could be helpful to someone else escaped me. As per his recommendation, I'm opening the question to the forum.

 

I am currently managing two SCCM environments: SCCM 2007 R3 and SCCM 2012 R2. As it stands, the 2012 environment is doing all the relatively straightforward things that one would expect (Application/Package deployment, Baseline Configuration, OSD, Windows Update management, and so forth). The functionality I'm having problems with now is the Build & Capture.

The B&C process inexplicably drops out at random during the "Install Package" steps I've added for getting our standard software into the image. I initially thought this was related to one piece of software and disabled the package for further evaluation. As I tested more and more, I found that the same error would pop up at random places during the "Install Package" area. Windows loads in an incomplete configuration state and the task sequence never continues.

Miscellaneous details: The same behavior can be observed across Windows 7/Windows 8/Windows 8.1 Build & Capture attempts. I'm initiating the task sequence via boot media as the 2007 environment as the network helpers are still pointing to the 2007 PXE server. The software packages that I'm attempting to utilize are configured to allow for installations during the task sequence without being deployed.

The first recommendation to me was as follows:

 

make sure you've specified the SLP/MP property in the setup windows and configmgr step (SMSMP=fqdn)

AND

make sure that the machine in question falls into a boundary that is already defined, lastly please do post questions like this on the forums, you'd be surprised about how many people PM me thinking that they are the only person asking me for advice

cheers

niall

The setup string I was using was as follows:

CCMSetup.exe /noservice /mp:SERVER90.ad.organization SMSSITECODE=GS2 FSP=SERVER91.ad.organization

It was changed to:

CCMSetup.exe /mp:SERVER90.ad.organization SMSSITECODE=GS2 FSP=SERVER91.ad.organization SMSMP=SERVER90.ad.organization

The task sequence properties are as follows:

SMSCACHESIZE=30000 PATCH="%_SMSTSMDataPath%\OSD\GS20003D\Hotfix\KB2905002\Client\x64\configmgr2012ac-r2-kb2905002-x64.msp"

I double-checked the boundaries and the subnet range that the virtual machine falls under is within one of the boundaries of my site's boundary group.

The SMSTS.log looks relatively benign with the exception of the following error, which presents itself numerous times:

Failed to query CCM_SoftwareDistribution

I've attached the SMSTS.log to this post. I changed the suffixes to something a bit more generic so as to maintain anonymity.

Any help would be appreciated and a preemptive, public thanks to anyweb for already offering some ideas.

smsts-20140226-093900 - Copy.log

Share this post


Link to post
Share on other sites

It occurred to me that I hadn't updated my boot images since I updated to R2 so I did that.

 

The problem is still occurring but there are new errors. Client WMI corrupt in the middle of a Task Sequence?

 

Failed to open key Software\Microsoft\SMS\47006C006F00620061006C005C007B00350031004100300031003600420036002D0046003000440045002D0034003700350032002D0042003900370043002D003500340045003600460033003800360041003900310032007D00\SMSTS

smsts-20140226-164625 - Copy.log

Share this post


Link to post
Share on other sites

that's not the full smsts.log, you can see it's installing apps just fine but at the end we are missing content, what's in your normal SMSTs.log file (the one you attached is the one it creates when the previous one has rolled over), the last app it lists installing is flash

 

<![LOG[start executing an instruction. Instruction name: Install Flash Player. Instruction pointer: 17]LOG]!><time="16:46:25.643+300" date="02-26-2014" component="TSManager" context="" type="1" thread="260" file="engine.cxx:116">

 

I would not be worried about these entries

 

<![LOG[Failed to open key Software\Microsoft\SMS\47006C006F00620061006C005C007B00350031004100300031003600420036002D0046003000440045002D0034003700350032002D0042003900370043002D003500340045003600460033003800360041003900310032007D00\SMSTS]LOG]!><time="16:46:28.097+300" date="02-26-2014" component="InstallSoftware" context="" type="3" thread="3428" file="environmentscope.cpp:311">
<![LOG[GetKeyFromRegistry (m_sScopeRegKey.c_str(), Key), HRESULT=80070013 (e:\qfe\nts\sms\framework\tscore\environmentscope.cpp,764)]LOG]!><time="16:46:28.097+300" date="02-26-2014" component="InstallSoftware" context="" type="0" thread="3428" file="environmentscope.cpp:764">
<

 

 

also you state

 

CCMSetup.exe /mp:SERVER90.ad.organization SMSSITECODE=GS2 FSP=SERVER91.ad.organization SMSMP=SERVER90.ad.organization

 

 

are you not using the built in Setup windows and configmgr step ?

Share this post


Link to post
Share on other sites

I am using the Setup & Configure step. The properties of that are as follows:

 

 

SMSMP=server90.ad.organization SMSCACHESIZE=30000 PATCH="%_SMSTSMDataPath%\OSD\GS20003D\Hotfix\KB2905002\Client\x64\configmgr2012ac-r2-kb2905002-x64.msp"

 

I've attached all the smsts logs that I'm aware of at the point where it fails: one in C:\_SMSTaskSequence\Logs and the other in C:\Windows\CCM\Logs (Along with the rollover file).

 

 

smsts - _SMSTaskSequence.log

smsts - CCM-Logs.log

smsts-20140227-191749 - CCM-Logs.log

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

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.