Search the Community
Showing results for tags 'build & capture'.
Found 3 results
Long time lurker, first time poster. Niall, your guide has been invaluable and Microsoft is lucky that people like you exist in the community. I'm sure it's a lot of hard work without much thanks - so THANK YOU! I followed your SCCM 2012 guides to setup a fresh install of SCCM 2012R2 Update 1 on a VM running Server 2012 + SQL 2012 + MDT 2013. My goal is to have a Windows 7 64-bit 'fat' image with Office 2013 + all Windows Updates installed that I can then use in a separate Deploy sequence. I am using a standard TS and not a MDT TS for the Build & Capture because I read somewhere that it was easier to use the standard to Build & Capture sequence to capture and then the MDT sequence to deploy. If I follow your Build & Capture guides for Windows 7 (also referencing the Windows 8 one because I'm using the install.wim method) everything APPEARS to go successfully. No errors appear on screen during the Build & Capture sequence and an image file is created. However after the image is created and the Build & Capture machine reboots, I'm asked to enter a computer name, an administrator password, time zone, etc. All things that I thought were spelled out in the Build & Capture task sequence. This makes me nervous that something isn't working properly behind the scenes. Additionally the root of C: still has a SMSTSLog folder. Digging through the SMSTS.log, I can see several failures that usually indicate a problem with DNS. I'm confused at how I have network during 99% of the process but then name resolution fails *right* after the Prepare OS step? I'm using VMware 5.1 and the VM is a standard Windows 7 64-bit template using the e1000 adapter. It's my understanding that the e1000 adapter works in all the recent flavors of WinPE. DHCP is running on a Server 2003 machine in the same subnet as the SCCM server and VM and DNS entries are correct in the scope and in the DHCP Server Options. I'm able to hit F8 during the Build & Capture sequence and I can verify the IP is correct, I can nslookup against the SCCM server, and ping. Things I've tried so far: * Recreated my boot files just in case (with ADK 8.1) and updated my DPs * Deleted all my TSes, and OS Installers * Download a fresh Windows 7 Enterprise with SP1 64-bit from Microsoft's site and imported it again * Created a new Build & Capture task sequence. The only modifications I made to the stock SCCM Build & Capture sequence are: Modify the 'Partition Disk 0 - BIOS' step so it only creates a single primary partition (not using BitLocker) and setting SMSMP=mysccmhost.domain.local * Resetting the SCCMNA password * Creating an SCCMNA2 account and specifying it under the Software Distribution Network Access Account tab (based on other folks' experiences) * Deleted the Build & Capture VM's device out of the collection and re-added it * Recreated the Build & Capture VM from scratch Any ideas at all? I spent the past two days going line by line through your guides again double checking everything I've done. smsts.log smsts.log
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?
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: 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