Good Afternoon All - Got a big issue going on. For at least the past 2-3 weeks, my Build & Captures have been failing. It doesn't matter what OS I'm deploying, what Image I'm using, etc - they all fail at the same point. Here's some background info: My company has 4 sites - Tennessee, San Diego, Mexico, & Ireland. - Tennessee - Primary SCCM Server with all roles, but DP & MP which are on seperate, local server. - San Diego - Secondary Site which holds DP & couple other roles - Mexico - - Secondary Site which holds DP & couple other roles - Ireland - - Secondary Site which holds DP & couple other roles Here's an example of a B&C TS that fails. This B&C has the following configuration: - Uses the default x86 boot image - Restarts in PE - Partitions NTFS (Quick) - Applies OS (Win 7 SP1 x86 Enterprise - same image proven to work previously) - Applies Windows Settings - No Product Key - Specifies Local Admin Password - Specific Timezone - Applies Network Settings - Join WORKGROUP - Setup windows and ConfigMgr -Standard ConfigMGR Package Chosen - SMSCACHESIZE=8000 - SMSSLP=TNSCCM01.abc.com - SMSMP=TNDP01.abc.com - FSP=TNDP01.abc.com - Install Updates - All Updates - Install Software - Installs 7 packages which work when deployed individually - nothing special - Capture the Reference Machine - Prepare ConfigMgr Client - Capture the Reference Machine - Captures to a local share with tested credentials Advertisement 1. Advertise the TS to a New, empty collection 2. Make avaliable to boot media 3. Mandatory to run as soon as possible 4. Ignore maint windows & Allow restarts 5. Access content directly, user remote DP if no local avaliable 6. Use unprotected if protected no avaliable How the TS goes... 1. I boot to USB media that I created. I use the same USB for OSD deployments as everything's on one DP so it's proven 2. It boots up and I click Next - it finds B&C TS and starts 3. It partitions and formats - 1-2 minutes - Reboots 4. "Running Action: Setup Windows and ConfigMGR" - 5-10 minutes - Reboots 5. "Completing installation" is in bold at end of Win7 install list - 5 minutes - Reboot 6. Starting Windows /w logo - 1 minute 7. "Checking Video Performance" - 1 minute 8. "Running Action: Setup Windows and ConfigMGR" - Installs Client - Deinstalls SMS Legacy Client or SMS 2.0 Client - Initializing ConfigMGR Client.................................................................................................. After waiting a LONG time, the power management takes over and eventually the screen goes to only the SCCM wallpaper. The log files are here. I'm sure it's related, but also, I cannot inject drivers / update dist points for my boot images. I ran into this a couple of moths ago and ended up reinstalling WAIK which fixed it for a little while. I haven't tried that yet, but have run a repair on it from the WAIK installation files. Any ideas? Thank you very much for your help! - Ben Ben K.

hi Ben looking at the start of smsts.log it looks network related, possibly dropping the ip address or DNS issues, <![LOG[unknown host (gethostbyname failed)]LOG]!><time="18:27:48.251+300" date="06-21-2011" component="TSManager" context="" type="3" thread="2004" file="libsmsmessaging.cpp:624"> <![LOG[hr, HRESULT=80072ee7 (e:\nts_sms_fre\sms\framework\osdmessaging\libsmsmessaging.cpp,7714)]LOG]!><time="18:27:48.251+300" date="06-21-2011" component="TSManager" context="" type="0" thread="2004" file="libsmsmessaging.cpp:7714"> <![LOG[sending with winhttp failed; 80072ee7]LOG]!><time="18:27:48.251+300" date="06-21-2011" component="TSManager" context="" type="3" thread="2004" file="libsmsmessaging.cpp:7714"> <![LOG[Will retry in 5 second(s)]LOG]!><time="18:27:48.251+300" date="06-21-2011" component="TSManager" context="" type="2" thread="2004" file="libsmsmessaging.cpp:1937"> <![LOG[Retrying...]LOG]!><time="18:27:53.430+300" date="06-21-2011" component="TSManager" context="" type="2" thread="2004" file="libsmsmessaging.cpp:1941"> <![LOG[CLibSMSMessageWinHttpTransport::Send: URL: TNSCCM01.PENS.COM:80 CCM_POST /ccm_system/request]LOG]!><time="18:27:53.430+300" date="06-21-2011" component="TSManager" context="" type="1" thread="2004" file="libsmsmessaging.cpp:7446"> <![LOG[Error. Received 0x80072ee7 from WinHttpSendRequest.]LOG]!><time="18:27:53.430+300" date="06-21-2011" component="TSManager" context="" type="1" thread="2004" file="libsmsmessaging.cpp:7665"> <![LOG[unknown host (gethostbyname failed)]LOG]!><time="18:27:53.430+300" date="06-21-2011" component="TSManager" context="" type="3" thread="2004" file="libsmsmessaging.cpp:624"> however, things seem to fix themseleves after this, and it all goes fine until Setup windows and configmgr, (as you state above, and the log seems fine..) the setup windows part seems to work fine which means it's probably failing to install the client, can you post the ccmsetup.log please and client.msi.log <![LOG[Start executing an instruciton. Instruction name: Setup windows and ConfigMgr. Instruction pointer: 6]LOG]!><time="21:34:53.790+300" date="06-21-2011" component="TSManager" context="" type="1" thread="1964" file="engine.cxx:117">.... ... <![LOG[Executing command line: "C:\_SMSTaskSequence\OSD\PEN00009\ccmsetup.exe" /useronly /config:MobileClient.TCF /status:616]LOG]!><time="21:46:45.935+300" date="06-21-2011" component="OSDSetupHook" context="" type="1" thread="1480" file="commandline.cpp:805"> <![LOG[Process completed with exit code 0]LOG]!><time="21:48:20.456+300" date="06-21-2011" component="OSDSetupHook" context="" type="1" thread="1480" file="commandline.cpp:1102"> <![LOG[Install succeeded. Blocking other instances of ccmsetup.] if you reboot one of these machines after logging in does anything happen ? My step by step SCCM Guides I'm on Twitter > ncbrady

Good Afternoon - Thanks for your reply. I worked on this again all morning with no results. I don't have the ccmsetup.log amd client.msi.log from the same deployment as the files I orginally posted, but do have them from a B&C I ran this morning (which failed wqith the exact same error as they all do) Here they are - ccmsetup.log client.msi.log Thanks!!! Ben K.

Ohh - forgot to answer your other question. If I reboot the machine after this "freeze", it loads Windows just fine and goes to Ctrl-Alt-Del. I do check, though, and my share which it's supposed to capture the WIM into is empty. Thanks -Ben K.

One more thing I also forgot to mention... (sorry :)) It does go to Windows normally like I said in the previous post - however - none of the software from the TS is installed nor (seemingly) updates. It seems to have the issue during/after "Setup windows and ConfigMgr" and "Install Updates". Thanks - Ben K.

New Information... Just to see what happened, I took one of the B&C Task Sequences and created Standalone Media with it. I figured that perhaps it would work or at least give clues as it could possibly tell me if it was network issues or not. Well, I copied it to a bootable USB and started it. Unfortunatly, it "froze" at the exact same part as when the TS is deployed as normal. Any ideas? Thanks!Ben K.

well the sccm client is getting installed fine - see here > <![LOG[Installation succeeded.] which must mean that something else is failing in or around this point, so you will have to search one of these completed/failed installs for all logs to see if there's any smsts.log files (it does come with names based on date/time also) hiding somewhere that reveal the true failure, it's mostly likely failing on the actual Capture task, but we need to prove it so please check your smsts.log files again (look on the entire drive please) cheers niall My step by step SCCM Guides I'm on Twitter > ncbrady

Thanks Niall - I tried another B&C today seeing if a new boot image would help, but got same results. After it timed out on Initializing ConfigMGR Client as usualy (like 45 minutes w.o change), I turned off the PC and booted directly to a Linux flash. I then scanned the entire drive for .log files. I found one smsts.log file as well as 141 more files that at least had log somewhere in the extension. Here's the smsts.log from this run. In it, you can clearly see where it Times Out. I just don't know why. Also, if it makes any different, my ConfigMgr package is PEN00009. Thanks! - BenBen K.

thanks Ben, that log does indeed show the failure, but i'm at odds to tell why it's happening, here's the actual failures... "<![LOG[Waiting for CcmExec service to be fully operational]LOG]!><time="19:36:51.438+300" date="06-24-2011" component="TSManager" context="" type="1" thread="2532" file="utils.cpp:4129"> <![LOG[Succeeded loading resource DLL 'C:\Windows\system32\CCM\1033\TSRES.DLL']LOG]!><time="19:36:52.452+300" date="06-24-2011" component="TSManager" context="" type="1" thread="2532" file="util.cpp:869"> <![LOG[Launching command shell.]LOG]!><time="17:02:39.840+300" date="06-24-2011" component="OSDSetupHook" context="" type="1" thread="624" file="debugwindow.cpp:202"> <![LOG[Windows station: WinSta0]LOG]!><time="17:02:39.840+300" date="06-24-2011" component="OSDSetupHook" context="" type="1" thread="624" file="utils.cpp:43"> <![LOG[Desktop: Default]LOG]!><time="17:02:39.840+300" date="06-24-2011" component="OSDSetupHook" context="" type="1" thread="624" file="utils.cpp:62"> <![LOG[executing command: C:\Windows\system32\cmd.exe /k]LOG]!><time="17:02:39.840+300" date="06-24-2011" component="OSDSetupHook" context="" type="1" thread="624" file="debugwindow.cpp:63"> <![LOG[executed command: C:\Windows\system32\cmd.exe /k]LOG]!><time="17:02:39.856+300" date="06-24-2011" component="OSDSetupHook" context="" type="1" thread="624" file="debugwindow.cpp:80"> <![LOG[Timed out waiting for ccmexec service to be fully operational]LOG]!>"LOG]!><time="17:07:18.924+300" date="06-24-2011" component="TSManager" context="" type="3" thread="2532" file="utils.cpp:4191"> can you please do the following actions to test.. 1. recreate the Configmgr Package from definition and redistribute the package to your dp's once done 2. recreate your USB media and test this process again also, are you doing these build and captures on real hardware ? if so, have you tried different physical machines ? the best way (and recommended best practise) is not to use hardware but to use Virtual machines instead like hyperV or vmware My step by step SCCM Guides I'm on Twitter > ncbrady

Thanks Niall - I really appreciate you sticking with this. I've tried that already, but am trying again now. The method I have tried before consisted of creating the package from definition I believe. What I'm trying now is below: 1. New Package 2. Source is \\sccmserver\SMS_SITE\Client 3. All defaults to Close 4. Create new Program - ccmsetup.exe 5. Run whether or not user logged in - all rest defaults 6. New DPs & then update them 7. Replacing the client package I was using in B7C with the one I created above. The above instructions were from: http://www.kozeniauskas.com/itblog/2008/03/20/sccm-how-to-create-sccm-client-package-and-program-for-osd/ Starting TS now so will let you know ASAP. Thanks!Ben K.

I really need to start making sure I answer all questions before submitting my replies... sorry. Yes, I have tried them in VMs (newest VirtualBox) and have even imported the guest drivers into SCCM. I have tried a couple of different pieces of hardware, but have been able to do TS on them before. I'mm go ahead and install and try VMWare Workstation too as well as different hardware which B&C is proven on (even though I think I've done so already. I've not only recreated my media, but created a new, local DP on a temp machine, distributed my packages to it, then created new boot media to use with it with same results. All let you know how all this goes. Thanks Again - I really do appreciate your time!Ben K.

NoGo on rebuilding the ConfigMGR client with the method above. Trying VMWare and new hardware next... ThanksBen K.

Okay - both VMWare Workstation test and new hardware test gave the same results. I'm totally stuck. Any more ideas? Thanks!Ben K.

BTW - Found this and am going to try out. http://support.microsoft.com/kb/2509007 I checked my ConfigMGR client and it's only 4.00.6487.2000. Strange, though, because my SCCM is up to date...Ben K.

here's how to add it to your task sequence Ben, so are you saying that if you disable the Install software updates step everything works fine ? Adding a hotfix to the Setup Windows and Configmgr step in a task sequence How can I add a hotfix (or hotfixes) to my ConfigMgr Client during OSD My step by step SCCM Guides I'm on Twitter > ncbrady

Thanks - Just ran patch, updated DPs, and added patch string to one of the B&C TSs I've been having issues with. Testing now...Ben K.

That was it!!! Finally! Thank you for your assitance again. I really appreciate it.Ben K.

great stuff Ben, glad it's working now My step by step SCCM Guides I'm on Twitter > ncbrady