Build and Capture - Windows 2012 no longer possible

Dear all
We are using SCCM SP1 and facing since May 2013 the following problem:
Our - until May 2013 working - Task Sequence to build and capture our Windows 2012 Datacenter Image does not capture when we install updates during this sequence.
The following steps are working:
- Restart in Windows PE
- Partition Disk 0
- Apply Operating System
- Apply Windows Settings
- Apply Network Settings
- Setup Windows and Configuration Manager
If the next step is Install Updates, it installs the updates, reboot twice, shows again the status of the task sequence and then we can see the login screen from Windows 2012 instead of starting the step "Prepare Configuration Manager
Client".
As soon as we disable the Install Updates step, the task sequence can go to "Prepare Configuration Manager Client" and can successfully capture a new wim.
What could be the problem? Thanks for any hints.
best
JBAB

check your windowsupdate.log and see what updates it's installing, one or more of them is causing a reboot which the task sequence does not expect or like and that is probably your issue, remove that update(s) from the deployment and start again
Step by Step Configuration Manager Guides >
2012 Guides |
2007 Guides | I'm on Twitter > ncbrady

Similar Messages

  • SCCM 2012 R2: Build and Capture - Windows 8.1 prompting for network

    I have upgraded my SCCM 2012 SP1 (CU2) to SCCM 2012 R2 and I am attempting to Build and Capture Windows 8.1 Enterprise. Everything is perfect except for the OS prompting for a network selection during the process, if I click "next" on that screen
    the Capture finishes without incident. The same is true of the Deploy as well...
    Is this a bug from my upgrade?
    Portland Public Schools / Systems Administrator II

    Hi LillonelC
    Can you point out how and where to do this?
    When capturing with MDT 2013 on VMware I do not see this, naturaly, since the "machine" only has one network adapter.
    But when deploying to a Laptop I get the wireless Setup screen...
    On beforehand Thank You!
    With kind regards
    We aren't using MDT but what we did was create a package called Windows 8.1 - Compnents. In it  placed a file named "32Bit-Unattend.xml" and 1 named "64Bit-Unattend.xml". 
    During the capture in the "Apply Operating System Image" I put a check in the box "Use an unattended or Sysprep answer file for a custom installation". The package was Windows 8.1 - Compnents the File name was "32Bit-Unattend.xml".
    I did the same for 64-bit and used the 64-bit version.
    Here is content of the 32-bit file:
    <?xml version="1.0" encoding="utf-8"?>
    <unattend xmlns="urn:schemas-microsoft-com:unattend">
        <settings pass="oobeSystem">
            <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                <OOBE>
                    <HideEULAPage>true</HideEULAPage>
                    <HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE>
                    <NetworkLocation>Work</NetworkLocation>
                    <HideOnlineAccountScreens>true</HideOnlineAccountScreens>
                    <HideOEMRegistrationScreen>true</HideOEMRegistrationScreen>
                    <HideLocalAccountScreen>true</HideLocalAccountScreen>
                </OOBE>
            </component>
        </settings>
        <cpi:offlineImage cpi:source="wim://SERVERNAME/e$/osimages/win_8.1_x86/sources/install.wim#Windows 8.1 Enterprise" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
    </unattend>
    Here is the content of the 64-bit file:
    <?xml version="1.0" encoding="utf-8"?>
    <unattend xmlns="urn:schemas-microsoft-com:unattend">
        <settings pass="oobeSystem">
            <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                <OOBE>
                    <HideEULAPage>true</HideEULAPage>
                    <HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE>
                    <NetworkLocation>Work</NetworkLocation>
                    <HideOnlineAccountScreens>true</HideOnlineAccountScreens>
                    <HideOEMRegistrationScreen>true</HideOEMRegistrationScreen>
                    <HideLocalAccountScreen>true</HideLocalAccountScreen>
                </OOBE>
            </component>
        </settings>
        <cpi:offlineImage cpi:source="wim://SERVERNAME/e$/osimages/win_8.1_x64/sources/install.wim#Windows 8.1 Enterprise" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
    </unattend>
    If that doesn't help I can try to clarify it a bit further.
    PS You won't need to do this for the deploy, only the capture.
    Portland Public Schools / Systems Administrator II

  • Workgroup Installing Client Fails (Build and Capture) - Windows 7 x64

    Hi, I'm trying to configure a Build and Capture TS for Windows 7 x64 but the client always fails to find my site during installation, which means I can't install updates and applications. I'm running SCCM 2012 SP1 and the ConfigMgr2012-SP1-KB2801987-X64-ENU
    hotfix has already been installed.
    I'm using the SMSMP=XX.XX (and SMSSITECODE=XXX) options but the log always says "No MPs were specified from commandline..."
    I've done a huge amount of searching and it seems like it should be possible to end up with a client installed on a workgroup computer with the correct side code (and displaying "Currently Internet"), which should allow updates to be installed
    during the TS, but I can't get it to work! Any help would be greatly appreciated.
    Here's part of my ccmsetup.log file :
    ==========[ ccmsetup started in process 2332 ]========== ccmsetup 6/06/2014 10:58:01 AM 2336 (0x0920)
    Running on platform X64 ccmsetup 6/06/2014 10:58:01 AM 2336 (0x0920)
    Launch from folder D:\_SMSTaskSequence\OSD\XXX00034\ ccmsetup 6/06/2014 10:58:01 AM 2336 (0x0920)
    CcmSetup version: 5.0.7804.1500 ccmsetup 6/06/2014 10:58:01 AM 2336 (0x0920)
    Running on OS (6.1.7600). Service Pack (0.0). SuiteMask = 256. Product Type = 1 ccmsetup 6/06/2014 10:58:01 AM 2336 (0x0920)
    Ccmsetup command line: "D:\_SMSTaskSequence\OSD\XXX00034\ccmsetup.exe" /useronly /source:D:\_SMSTaskSequence\OSD\XXX00034 /config:MobileClient.TCF /status:572 ccmsetup 6/06/2014 10:58:01 AM 2336 (0x0920)
    Command line parameters for ccmsetup have been specified. No registry lookup for command line parameters is required. ccmsetup 6/06/2014 10:58:01 AM 2336 (0x0920)
    Command line: "D:\_SMSTaskSequence\OSD\XXX00034\ccmsetup.exe" /useronly /source:D:\_SMSTaskSequence\OSD\XXX00034 /config:MobileClient.TCF /status:572 ccmsetup 6/06/2014 10:58:01 AM 2336 (0x0920)
    Copying config file from D:\_SMSTaskSequence\OSD\XXX00034\MobileClient.TCF to folder D:\WINDOWS\ccmsetup\. Return result: 0x0 ccmsetup 6/06/2014 10:58:01 AM 2336 (0x0920)
    SslState value: 224 ccmsetup 6/06/2014 10:58:01 AM 2336 (0x0920)
    CCMHTTPPORT: 80 ccmsetup 6/06/2014 10:58:01 AM 2336 (0x0920)
    CCMHTTPSPORT: 443 ccmsetup 6/06/2014 10:58:01 AM 2336 (0x0920)
    CCMHTTPSSTATE: 0 ccmsetup 6/06/2014 10:58:01 AM 2336 (0x0920)
    CCMHTTPSCERTNAME: ccmsetup 6/06/2014 10:58:01 AM 2336 (0x0920)
    FSP: ccmsetup 6/06/2014 10:58:01 AM 2336 (0x0920)
    CCMFIRSTCERT: 1 ccmsetup 6/06/2014 10:58:01 AM 2336 (0x0920)
    Config file: D:\WINDOWS\ccmsetup\MobileClientUnicode.tcf ccmsetup 6/06/2014 10:58:01 AM 2336 (0x0920)
    Retry time: 10 minute(s) ccmsetup 6/06/2014 10:58:01 AM 2336 (0x0920)
    MSI log file: D:\WINDOWS\ccmsetup\Logs\client.msi.log ccmsetup 6/06/2014 10:58:01 AM 2336 (0x0920)
    MSI properties: INSTALL="ALL" SMSPROVISIONINGMODE="1" SMSSITECODE="XXX" CCMHTTPPORT="80" CCMHTTPSPORT="443" CCMHTTPSSTATE="0" CCMFIRSTCERT="1" ccmsetup 6/06/2014 10:58:01 AM 2336 (0x0920)
    Source List: ccmsetup 6/06/2014 10:58:01 AM 2336 (0x0920)
    D:\_SMSTaskSequence\OSD\XXX00034 ccmsetup 6/06/2014 10:58:01 AM 2336 (0x0920)
    MPs: ccmsetup 6/06/2014 10:58:01 AM 2336 (0x0920)
    None ccmsetup 6/06/2014 10:58:01 AM 2336 (0x0920)
    No version of the client is currently detected. ccmsetup 6/06/2014 10:58:02 AM 2336 (0x0920)
    Updated security on object D:\WINDOWS\ccmsetup\. ccmsetup 6/06/2014 10:58:02 AM 2336 (0x0920)
    A Fallback Status Point has not been specified. Message with STATEID='100' will not be sent. ccmsetup 6/06/2014 10:58:02 AM 2336 (0x0920)
    Downloading file D:\_SMSTaskSequence\OSD\XXX00034\ccmsetup.exe ccmsetup 6/06/2014 10:58:03 AM 2336 (0x0920)
    Downloading D:\_SMSTaskSequence\OSD\XXX00034\ccmsetup.exe to D:\WINDOWS\ccmsetup\ccmsetup.exe ccmsetup 6/06/2014 10:58:03 AM 2336 (0x0920)
    File download 17% complete (262144 of 1457840 bytes). ccmsetup 6/06/2014 10:58:03 AM 2336 (0x0920)
    File download 35% complete (524288 of 1457840 bytes). ccmsetup 6/06/2014 10:58:03 AM 2336 (0x0920)
    File download 53% complete (786432 of 1457840 bytes). ccmsetup 6/06/2014 10:58:03 AM 2336 (0x0920)
    File download 71% complete (1048576 of 1457840 bytes). ccmsetup 6/06/2014 10:58:03 AM 2336 (0x0920)
    File download 89% complete (1310720 of 1457840 bytes). ccmsetup 6/06/2014 10:58:03 AM 2336 (0x0920)
    File download 100% complete (1457840 of 1457840 bytes). ccmsetup 6/06/2014 10:58:03 AM 2336 (0x0920)
    Download complete. ccmsetup 6/06/2014 10:58:03 AM 2336 (0x0920)
    Running as user "SYSTEM" ccmsetup 6/06/2014 10:58:05 AM 2336 (0x0920)
    Detected 928475 MB free disk space on system drive. ccmsetup 6/06/2014 10:58:05 AM 2336 (0x0920)
    Checking Write Filter Status. ccmsetup 6/06/2014 10:58:05 AM 2336 (0x0920)
    This is not a supported write filter device. We are not in a write filter maintenance mode. ccmsetup 6/06/2014 10:58:05 AM 2336 (0x0920)
    Unexpected row count (0) retrieved from AD. ccmsetup 6/06/2014 10:58:05 AM 2336 (0x0920)
    Failed to get site version from AD with error 0x80004005 ccmsetup 6/06/2014 10:58:05 AM 2336 (0x0920)
    SiteCode: XXX ccmsetup 6/06/2014 10:58:05 AM 2336 (0x0920)
    SiteVersion: ccmsetup 6/06/2014 10:58:05 AM 2336 (0x0920)
    No MPs were specified from commandline or the mobileclient.tcf. ccmsetup 6/06/2014 10:58:05 AM 2336 (0x0920)
    Downloading file ccmsetup.cab ccmsetup 6/06/2014 10:58:05 AM 2336 (0x0920)
    Determining source location... ccmsetup 6/06/2014 10:58:05 AM 2336 (0x0920)
    Found accessible source: D:\_SMSTaskSequence\OSD\XXX00034 ccmsetup 6/06/2014 10:58:05 AM 2336 (0x0920)
    Found available source D:\_SMSTaskSequence\OSD\XXX00034\ ccmsetup 6/06/2014 10:58:05 AM 2336 (0x0920)
    Downloading D:\_SMSTaskSequence\OSD\XXX00034\ccmsetup.cab to D:\WINDOWS\ccmsetup\ccmsetup.cab ccmsetup 6/06/2014 10:58:05 AM 2336 (0x0920)
    File download 100% complete (9613 of 9613 bytes). ccmsetup 6/06/2014 10:58:05 AM 2336 (0x0920)
    Download complete. ccmsetup 6/06/2014 10:58:05 AM 2336 (0x0920)

    Thanks for the reply. You're right, I'm setting the SMSMP and SMSSITECODE in the command line of the package itself, not the TS properties box. I have tried both ways, in fact every combination I could think of and nothing seems to produce an installed client
    which knows its site (and both ways produce almost identical logs, which makes me think the properties are being ignored from either location).
    The log doesn't actually contain any error messages which seem relevant at all, but here's some chunks with all of the errors (the log was too big to post in its entirety) :
    Download complete. ccmsetup 6/06/2014 10:58:03 AM 2336 (0x0920)
    Running as user "SYSTEM" ccmsetup 6/06/2014 10:58:05 AM 2336 (0x0920)
    Detected 928475 MB free disk space on system drive. ccmsetup 6/06/2014 10:58:05 AM 2336 (0x0920)
    Checking Write Filter Status. ccmsetup 6/06/2014 10:58:05 AM 2336 (0x0920)
    This is not a supported write filter device. We are not in a write filter maintenance mode. ccmsetup 6/06/2014 10:58:05 AM 2336 (0x0920)
    Unexpected row count (0) retrieved from AD. ccmsetup 6/06/2014 10:58:05 AM 2336 (0x0920)
    Failed to get site version from AD with error 0x80004005 ccmsetup 6/06/2014 10:58:05 AM 2336 (0x0920)
    SiteCode: XXX ccmsetup 6/06/2014 10:58:05 AM 2336 (0x0920)
    SiteVersion: ccmsetup 6/06/2014 10:58:05 AM 2336 (0x0920)
    No MPs were specified from commandline or the mobileclient.tcf. ccmsetup 6/06/2014 10:58:05 AM 2336 (0x0920)
    Downloading file ccmsetup.cab ccmsetup 6/06/2014 10:58:05 AM 2336 (0x0920)
    Determining source location... ccmsetup 6/06/2014 10:58:05 AM 2336 (0x0920)
    Found accessible source: D:\_SMSTaskSequence\OSD\XXX00034 ccmsetup 6/06/2014 10:58:05 AM 2336 (0x0920)
    Found available source D:\_SMSTaskSequence\OSD\XXX00034\ ccmsetup 6/06/2014 10:58:05 AM 2336 (0x0920)
    Discovering whether item 'x64/MicrosoftPolicyPlatformSetup.msi' exists. ccmsetup 6/06/2014 10:58:11 AM 2336 (0x0920)
    Couldn't find a product with MSI upgrade code '{19B9818B-7432-49E9-BC02-B126025EE235}' in the MSI database. ccmsetup 6/06/2014 10:58:11 AM 2336 (0x0920)
    Item x64/MicrosoftPolicyPlatformSetup.msi has not been installed yet. Put to pending install list. ccmsetup 6/06/2014 10:58:11 AM 2336 (0x0920)
    Discovering whether item 'x64/WindowsFirewallConfigurationProvider.msi' exists. ccmsetup 6/06/2014 10:58:11 AM 2336 (0x0920)
    File 'D:\WINDOWS\ccmsetup\WindowsFirewallConfigurationProvider.msi' does not exist. Discovery failed. ccmsetup 6/06/2014 10:58:11 AM 2336 (0x0920)
    Item x64/WindowsFirewallConfigurationProvider.msi has not been installed yet. Put to pending install list. ccmsetup 6/06/2014 10:58:11 AM 2336 (0x0920)
    Discovering whether item 'i386/Silverlight.exe' exists. ccmsetup 6/06/2014 10:58:11 AM 2336 (0x0920)
    32-bit Hive selected ccmsetup 6/06/2014 10:58:11 AM 2336 (0x0920)
    Item i386/Silverlight.exe has not been installed yet. Put to pending install list. ccmsetup 6/06/2014 10:58:11 AM 2336 (0x0920)
    Discovering whether item 'i386/dotNetFx40_Client_x86_x64.exe' exists. ccmsetup 6/06/2014 10:58:11 AM 2336 (0x0920)
    Detected item 'i386/dotNetFx40_Client_x86_x64.exe' ccmsetup 6/06/2014 10:58:11 AM 2336 (0x0920)
    Discovering whether item 'SCEPInstall.exe' exists. ccmsetup 6/06/2014 10:58:11 AM 2336 (0x0920)
    Couldn't determine site version for site 'XXX'. Let client deployment continue. ccmsetup 6/06/2014 10:58:16 AM 2336 (0x0920)
    MSI: Action 11:01:01: CcmRegisterHostedApplications. Register hosted out-of-proc DCOM applications running inside of Configuration Manager Client. ccmsetup 6/06/2014 11:01:01 AM 2336 (0x0920)
    MSI: Action 11:01:01: CcmRegisterEndpointsInit. Gathers information such as log file name on each endpoint to be registered on the system. ccmsetup 6/06/2014 11:01:01 AM 2336 (0x0920)
    MSI: Action 11:01:01: CcmRegisterEndpointRollback. In the event of a failed installation, this action rolls back the changes from CcmRegisterEndpoint. ccmsetup 6/06/2014 11:01:01 AM 2336 (0x0920)
    MSI: Action 11:01:01: CcmRegisterEndpoint. Registers endpoint gathered in the action CcmRegisterEndpointsInit with WMI. ccmsetup 6/06/2014 11:01:01 AM 2336 (0x0920)
    MSI: Action 11:01:01: CcmRegisterSystemTasksInit. Processes the CcmSystemTask table and passes this information to CcmRegisterSystemTask. ccmsetup 6/06/2014 11:01:01 AM 2336 (0x0920)
    MSI: Action 11:01:01: CcmRegisterSystemTaskRollback. Rolls back the changes made by CcmRegisterSystemTask. ccmsetup 6/06/2014 11:01:01 AM 2336 (0x0920)
    MSI: Action 11:01:01: CcmRegisterSystemTask. Registers a System Task with WMI. ccmsetup 6/06/2014 11:01:01 AM 2336 (0x0920)
    MSI: Action 11:01:02: CcmRegisterPerfCounters. Registers performance counters gathered in the CcmRegisterPerfCountersInit action ccmsetup 6/06/2014 11:01:02 AM 2336 (0x0920)
    MSI: Action 11:01:02: CcmRegisterComponentsInit. Generates the list of components for CcmRegisterComponets action to register. ccmsetup 6/06/2014 11:01:02 AM 2336 (0x0920)
    MSI: Action 11:01:03: CcmRegisterComponentsRollback. In the event of a failed installation, this action rolls back the changes from CcmRegisterComponents. ccmsetup 6/06/2014 11:01:03 AM 2336 (0x0920)
    MSI: Action 11:01:03: CcmRegisterComponents. Registers components passed in from CcmRegisterComponentsInit ccmsetup 6/06/2014 11:01:03 AM 2336 (0x0920)
    MSI: Action 11:01:03: SmsMigrateSwDistHistory. Migrate software distribution history. ccmsetup 6/06/2014 11:01:03 AM 2336 (0x0920)
    MSI: Action 11:01:03: CcmInstallUtilInit. Initializing InstallUtil.exe to register .net WMI provider ccmsetup 6/06/2014 11:01:03 AM 2336 (0x0920)
    MSI: Action 11:01:04: CcmStopService. Stops the ccmexec service. ccmsetup 6/06/2014 11:01:04 AM 2336 (0x0920)
    MSI: Action 11:01:04: StopServices. Stopping services ccmsetup 6/06/2014 11:01:04 AM 2336 (0x0920)
    MSI: Action 11:01:04: SmsUninstallPrepDrvr. Uninstalling Software Metering PREP Driver ccmsetup 6/06/2014 11:01:04 AM 2336 (0x0920)
    MSI: Warning 25702. Failed to uninstall PrepDrvr.Sys for Software Metering Agent. ccmsetup 6/06/2014 11:01:04 AM 2336 (0x0920)
    MSI: Action 11:01:04: SmsStopUIComponents. This custom action forces all open client UI components to stop and exit. ccmsetup 6/06/2014 11:01:04 AM 2336 (0x0920)
    MSI: Action 11:01:04: SmsStopUserComponents. This custom action forces all open client UI and SCNotification components to stop and exit. ccmsetup 6/06/2014 11:01:04 AM 2336 (0x0920)
    MSI: Action 11:01:04: CcmUnloadWmiProviders. Enumerates all providers and unloads them, verifies they are unloaded, and then reloads them. ccmsetup 6/06/2014 11:01:04 AM 2336 (0x0920)
    MSI: Action 11:01:22: CcmRegisterHostedApplicationsRollback. Rollback the registration of hosted out-of-proc DCOM applications running inside of Configuration Manager Client. ccmsetup 6/06/2014 11:01:22 AM 2336 (0x0920)
    MSI: Action 11:01:22: CcmRegisterHostedApplications. Register hosted out-of-proc DCOM applications running inside of Configuration Manager Client. ccmsetup 6/06/2014 11:01:22 AM 2336 (0x0920)
    MSI: Action 11:01:22: CcmRegisterEndpointRollback. In the event of a failed installation, this action rolls back the changes from CcmRegisterEndpoint. ccmsetup 6/06/2014 11:01:22 AM 2336 (0x0920)
    MSI: Action 11:01:22: CcmRegisterEndpoint. Registers endpoint gathered in the action CcmRegisterEndpointsInit with WMI. ccmsetup 6/06/2014 11:01:22 AM 2336 (0x0920)
    MSI: Action 11:01:22: CcmRegisterSystemTaskRollback. Rolls back the changes made by CcmRegisterSystemTask. ccmsetup 6/06/2014 11:01:22 AM 2336 (0x0920)
    MSI: Action 11:01:22: CcmRegisterSystemTask. Registers a System Task with WMI. ccmsetup 6/06/2014 11:01:22 AM 2336 (0x0920)
    MSI: Action 11:01:26: CcmRegisterPerfCountersRollback. Rolls back any changes made by CcmRegisterPerfCounters if install fails. ccmsetup 6/06/2014 11:01:26 AM 2336 (0x0920)
    MSI: Action 11:01:26: CcmRegisterPerfCounters. Registers performance counters gathered in the CcmRegisterPerfCountersInit action ccmsetup 6/06/2014 11:01:26 AM 2336 (0x0920)
    MSI: Action 11:01:26: CcmRegisterComponentsRollback. In the event of a failed installation, this action rolls back the changes from CcmRegisterComponents. ccmsetup 6/06/2014 11:01:26 AM 2336 (0x0920)
    MSI: Action 11:01:26: CcmRegisterComponents. Registers components passed in from CcmRegisterComponentsInit ccmsetup 6/06/2014 11:01:26 AM 2336 (0x0920)
    MSI: Action 11:01:26: CcmInstallUtil. Calling InstallUtil.exe to register .net WMI provider ccmsetup 6/06/2014 11:01:26 AM 2336 (0x0920)
    MSI: Action 11:01:33: SmsSetLUAAccessPermissions. >Gets permission for evelation on Vista and grants each COM object permission. ccmsetup 6/06/2014 11:01:33 AM 2336 (0x0920)

  • Build and Capture Windows 8.1

    Hi,
    Am simply building and capturing a Windows 8.1 reference image with associated task sequence but get the error below.
    Using F8, it appears to have installed but get this message and the process halts.
    'windows could not parse the unattend answer file for pass specialize windows shell setup'.
    I have verified the product key as suggested in other posts and this is a simple build and capture, there is no unattend.xml in the task sequence.
    thanks in advance.

    Which version of ConfigMgr?
    Have you already tried using no product key?
    Torsten Meringer | http://www.mssccmfaq.de

  • MDT 2013 supports build and capture win 7 SP1

    Hi,
    Just want to have a check if MDT 2013 supports Build and capture windows 7 as image (wim)?
    I know it is supporting windows 7 as supported OS for deployment.
    Regards,

    Yes it does:
    http://technet.microsoft.com/en-US/windows/dn475741.aspx
    Good luck!

  • Install Software Updates in a WIndows 7 build and capture shooses wrong SUP

    Hi,
    My environment is the following.
    One SCCM 2012 R2 Primary site server in a trusted domain, MP, DP and SUP. This site is reachable from the clients on the internal  network.
    One SCCM 2012 R2 server in an untrusted forest, MP, DP and SUP. This server is NOT reachable from clients on the internal nrowotk.
    I am doing a build and capture of Windows 7 using a SCCM TS on a VM on the internal network.
    When the Install Updates task Is running the SCCM client is trying to use the SUP in the untrusted forest instead of the one in the local trusted forest.
    How do I force the SCCM client to use the local SUP instead of the one in the untrusted forest.
    According to
    http://blogs.technet.com/b/configmgrteam/archive/2013/03/27/software-update-points-in-cm2012sp1.aspx it should prioritize the one in the local forest, but the build and capture PC is not member of the AD so it looks like it just uses the SUP that is
    first in the list from the MP.
    The blog also states that the SUP will not be shifted to the next one in the list before 4 failed scans at 30 minutes intervals so it will take more than 4 hours before the SCCM client will try the next SUP. At that time the TS has long finished the
    Software Update task.
    I thought about creating an entry in the hosts file on the capture PC with the name of the untrusted SUP and the IP of the trusted SUP to redirect the client to use the trusted SUP. I solution that might work but that I find very ugly.
    What can I do to force the SCCM client on the build and capture PC to us the internal trusted SUP?
    Thomas Forsmark Soerensen

    The SUP info cannot be got from the Internal MP. Please review the Smsts.log file.
    Juke Chou
    TechNet Community Support

  • Steps to create MDT based Build and capture TS in SCCM 2012 R2

    Hi ,
    I have MDT2012 update 1 with Config manager 2012 R2 integrated. If I try to create MDT task sequence in config manager console, I don't see and template for build and capture. Anyone using the build and capture, pls. share steps with me . Any help will be
    appreciated. Preferably UDI based if possible. Thanks in advance.
    Regards,

    MDT 2012 Update 1 is for SCCM 2012 SP1
    MDT 2013 is for SCCM 2012 R2
    So you need to upgrade your MDT installation. After that, make sure to install the ConfigMgr integration from the start screen (menu)
    http://technet.microsoft.com/en-US/windows/dn475741.aspx
    Tim Nilimaa | Blog: http://infoworks.tv | Twitter: @timnilimaa

  • Install Updates task not working during Build and Capture in SCCM 2012

    Working with a new SCCM 2012 installation.
    We are trying to get a Build and Capture TS to install all updates for Win7SP1.
    All packages are deployed to DP, build and cap machine is in a collection with all updates deployed to it. Agent installation parameters include "SMSMP" "SMSSLP" parameters. Machine is not being attached to the domain during OS install. 
    Updates can be pushed to existing domain machines, so obviously the updates themselves are working.
    The task sequence works correctly to install the image, but "Install Updates" task just sits there and eventually times out. (No indication of updates being installed.) If this task is working, shouldn't I see a Downloading Updates progress bar, or was that
    eliminated from 2012?

    Same issue for me except I'm running 2012 R2 my B&C runs forever on Install Software Updates, eventually just rebooting and coming back to the login screen of Windows 7 without ever finishing the Install Updates.
    Been working on it litteraly for weeks.
    1- Tried adding .Net 4.52 as an application installation thinking maybe it would resolve the issue
    2- Tried installing via Run Command Line + DISM all hotfixes that require 2 reboots as per (https://support.microsoft.com/en-us/kb/2894518)
    3- Tried to simply REMOVE the same hotfixes from my Software Update Groups alltogether.
    4- Injected all applicable software updates through Offline Servicing in the SCCM Console (Schedule Updates) on the Windows 7 DVD wim file. That way my logic was that once it would hit the Software Updates, there would be a lot less to install.
    I'm at the point where I had to open a case with Microsoft Premier Support as of yesterday. So, nothing new to report yet. But yes, this is a true pain in the ***.
    For the sake of comparison, I am running 4 Update Groups: one containing patches up to 2012. Another one for 2013, 2014 and 2015. I have patches for Windows 7 + Office of all categories except Service Packs.
    If someone has any ideas, feel free to chime in. 

  • SCCM 2012 SP1 - Build and Capture - ReCapture impossible

    Hi all
    i upgrade my SCCM 2012 RTM to SCCM 2012 SP1 yesterday. Today i started a recapture of my Windows 7 and Windows 2008 R2 Base Image.
    For that i have 2 VMs located in different SCCM Collections. And a Build and Capture Task Sequence is deployed to the collections.
    Before SP1 the behavior was:
    - Reset Required PXE Deployment in SCCM for the VMs
    - Start VM
    - VM boots with PXE
    - VM installs and capture the Installation
    And that i could do all the time so often as i want.
    Now with SP1 it is the same procedure but just for one time. After one success Build and Capture Task, the vm is unable to do the task sequence again. The VM is booting into the PXE and then i can see in the smsts log:
    There are no task sequences available to this computer
    But there are. The Task Sequence is set to "Always rerun".
    The only "fix" is to completely recreate the computer item in sccm.
    What is here wrong? Is this a known bug?
    best
    JBAB

    Hi, your problem is that when you deploy the task over the collation you only specified "media and PXE" was available to and probably the machines that you try to capture already had the sccm client. You can try to deploy the sequence task to a collation
    including the the option "configuration manager, media and PXE", or you can also deploy the task sequence to de "unknown devices" collation and delete the objects of the two virtual machines in configuration manager

  • Build and capture task sequence stops after apply windows updates

    Hi
    SCCM 2012 SP1 CU4. Deploying Windows 7 SP1.
    Pulling my hair out over this one. I successfully performed a build and capture installing some applications. When I choose to install Windows updates, the updates install, the system reboots then doesn't continue. Applications don't install, image isn't captured.
    I've tired using the default B&C TS and receive the same results. I've amended the TS to as follows, as suggested in a technet forum post: https://social.technet.microsoft.com/Forums/en-US/a535e509-fc6a-483c-bf24-7e2aa064e5b7/deploying-100-of-available-software-updates-during-a-task-sequence?forum=configmanagerosd
    Looking at smsts.log there's errors relating to not accepting the license agreement, but I didn't think this would stop the TS. 
    Can someone point out why the deployment stops?
    https://dl.dropboxusercontent.com/u/23479177/smsts-20141113-182413.log 
    Cheers

    This is very common scenario you´re having! :)
    For OSD and for Capture I always create myown Software Update Group, which lets me totally control, what updates goes to the image and which doesn´t. I then edit membership of update and tag or un-tag update to the group.
    I suggest you do the following:
    1. Create manual Computer record and add it to OSD Capture collection.
    2. Create SUG for OSD Capture and un-tag updates which are listed in KB2894518. But that might not be enough.
    3. Deploy TS to the OSD Capture collection.
    4. Create/modify virtual machine with MAC matching the computer record.
    5. Run PXE and hook Capture TS.

  • Windows 7 64bit Build and Capture Task Sequence keeps failing. Need to Offline Patch

    Hi All,
    I have been having problems running my SCCM 2007 R3 Build and Capture Task Sequence for Windows 7 64bit since MS released the October 2014 patches. (Having problems described in KB2894518, but can't get workaround to work)
    So my next step is to try to apply the patches directly to the install.wim file using dism and "Offline Servicing". I'm hoping this will allow my TS to finish, and also adds the benifit of making my TS much faster to run every month. So I followed
    the steps in
    this post, and injected 165 updates into the install.wim file (extracted from Win7 ISO). Now, I've copied the updated WIM into my Operating System install package and updated the distribution point. But the Install Software Updates step still installs 160
    updates (same as before the Offline patch injection). The only thing that seems faster is that the download of the updates is instantaneous. So it seems like the Offline patch injection just copied the patch installer files to the WIM, but did not actually
    install them.
    I remember reading a post by Niall C. Brady or Jason Sandys about exactly how they inject patches into a WIM, but have been unable to re-locate the post. Does anybody out there have a tried and true method for offline injection of patches into install.wim
    for use with SCCM Build and Capture task sequence? thanks!

    My recommendation would be to use MDT to build your images instead:
    http://technet.microsoft.com/en-us/library/dn744290.aspx
    This will make your life much easier with the patching of the image :)
    You can use Nickolaj's great MDT Factory tool to set up an MDT Build machine from scratch:
    https://gallery.technet.microsoft.com/MDT-Factory-Tool-100-8e68123b
    Blog: www.danielclasson.com/blog |
    LinkedIn:
    Daniel Classon | Twitter: @danielclasson

  • Is it possible to resize the log and capture window?

    Hi,
    Using Final cut pro, I would like to make my capture window a bit bigger while capturing. I am capturing footage via my Blackmagic Infinity card and get the input through an HDMI cable. I'm capturing in Apple Pro ress on 720p, 59,59 fps.
    For a good overview of what I'm capturing at the moment, I would love to have a bigger capture window. For all I know, FC pro doesn't support the resizing of the log and capture window. Anyone an idea on how to solve this?
    Thank you.

    In my case, the capture window is adjustable if I am capturing SD (DVCAM) video. I can also use the scopes in this case. (Good if you are recording to disk, or using a laptop for monitoring.)
    However, both features (adjustable capture window and scopes) are not available if capturing HD (HDV in my case) video.
    Message was edited by: amarasme

  • Build and Capture task sequence fails at 'Prepare ConfigMgr Client for Capture' step

    The scenario is as follows:
    Task Sequence is a Build and Capture of Windows 7 SP1 x64 Enterprise
    There are 17 Applications installed split into 2 'Install Application' steps due to the 9 item limit
    129 Software Updates are installed
    SCCM 2012 RTM
    I have built and captured on this system previously however there were no 'applications', just traditional SCCM 'packages'
    All task sequence steps run successfully until it gets to the 'Prepare ConfigMgr Client for Capture' step and it fails here. Here are the relevant parts of the SMSTS.log file:
    <![LOG[No certificates to delete]LOG]!><time="15:30:12.531-660" date="11-13-2012" component="PrepareSMSClient" context="" type="1" thread="2880" file="preparesmsclient.cpp:1013">
    <![LOG[Deleting Client properties from file C:\Windows\SMSCFG.INI succeeded.]LOG]!><time="15:30:12.531-660" date="11-13-2012" component="PrepareSMSClient" context="" type="1" thread="2880" file="preparesmsclient.cpp:922">
    <![LOG[Reseting the Trusted Root Key successful]LOG]!><time="15:30:12.531-660" date="11-13-2012" component="PrepareSMSClient" context="" type="1" thread="2880" file="preparesmsclient.cpp:1088">
    <![LOG[Deleting instance of 'CCM_Client' successful]LOG]!><time="15:30:12.531-660" date="11-13-2012" component="PrepareSMSClient" context="" type="1" thread="2880" file="preparesmsclient.cpp:170">
    <![LOG[Successfully reset Registration status flag to "not registered"]LOG]!><time="15:30:12.531-660" date="11-13-2012" component="PrepareSMSClient" context="" type="1" thread="2880" file="preparesmsclient.cpp:309">
    <![LOG[Successfully disabled provisioning mode.]LOG]!><time="15:30:12.546-660" date="11-13-2012" component="PrepareSMSClient" context="" type="1" thread="2880" file="preparesmsclient.cpp:1273">
    <![LOG[Start to cleanup TS policy]LOG]!><time="15:30:12.546-660" date="11-13-2012" component="PrepareSMSClient" context="" type="0" thread="2880" file="utils.cpp:2773">
    <![LOG[getPointer()->ExecQuery( BString(L"WQL"), BString(pszQuery), lFlags, pContext, ppEnum ), HRESULT=ffffffff (e:\nts_sccm_release\sms\framework\core\ccmcore\wminamespace.cpp,389)]LOG]!><time="15:35:21.000-660" date="11-13-2012" component="PrepareSMSClient"
    context="" type="0" thread="2880" file="wminamespace.cpp:389">
    <![LOG[ns.Query(sQuery, &spEnum), HRESULT=ffffffff (e:\nts_sccm_release\sms\framework\tscore\utils.cpp,2800)]LOG]!><time="15:35:21.000-660" date="11-13-2012" component="PrepareSMSClient" context="" type="0" thread="2880" file="utils.cpp:2800">
    <![LOG[Wmi query 'select * from CCM_Policy where PolicySource = 'CcmTaskSequence'' failed, hr=0xffffffff]LOG]!><time="15:35:21.000-660" date="11-13-2012" component="PrepareSMSClient" context="" type="3" thread="2880" file="utils.cpp:2800">
    <![LOG[End TS policy cleanup]LOG]!><time="15:35:21.000-660" date="11-13-2012" component="PrepareSMSClient" context="" type="0" thread="2880" file="utils.cpp:2821">
    <![LOG[TS::Utility::CleanupPolicyEx(false), HRESULT=ffffffff (e:\nts_sccm_release\sms\client\osdeployment\preparesmsclient\preparesmsclient.cpp,457)]LOG]!><time="15:35:21.000-660" date="11-13-2012" component="PrepareSMSClient" context="" type="0" thread="2880"
    file="preparesmsclient.cpp:457">
    <![LOG[Failed to delete policies compiled by TaskSequence (0xffffffff)]LOG]!><time="15:35:21.000-660" date="11-13-2012" component="PrepareSMSClient" context="" type="3" thread="2880" file="preparesmsclient.cpp:457">
    <![LOG[Failed to prepare SMS Client for capture, hr=ffffffff]LOG]!><time="15:35:21.000-660" date="11-13-2012" component="PrepareSMSClient" context="" type="3" thread="2880" file="preparesmsclient.cpp:472">
    <![LOG[pCmd->Execute(), HRESULT=ffffffff (e:\nts_sccm_release\sms\client\osdeployment\preparesmsclient\main.cpp,136)]LOG]!><time="15:35:21.000-660" date="11-13-2012" component="PrepareSMSClient" context="" type="0" thread="2880" file="main.cpp:136">
    <![LOG[Failed to prepare SMS Client for capture, hr=ffffffff]LOG]!><time="15:35:21.000-660" date="11-13-2012" component="PrepareSMSClient" context="" type="3" thread="2880" file="main.cpp:136">
    <![LOG[Process completed with exit code 4294967295]LOG]!><time="15:35:21.015-660" date="11-13-2012" component="TSManager" context="" type="1" thread="2152" file="commandline.cpp:1098">
    <![LOG[!--------------------------------------------------------------------------------------------!]LOG]!><time="15:35:21.015-660" date="11-13-2012" component="TSManager" context="" type="1" thread="2152" file="instruction.cxx:3011">
    <![LOG[Failed to run the action: Prepare ConfigMgr Client for Capture. 
    Unknown error (Error: FFFFFFFF; Source: Unknown)]LOG]!><time="15:35:21.046-660" date="11-13-2012" component="TSManager" context="" type="3" thread="2152" file="instruction.cxx:3102">
    It looks like there is a similar issue over here (http://www.windows-noob.com/forums/index.php?/topic/5906-task-sequence-error-0xffffffff/) that was resolved by removing the Application Installations one by one until a problematic one was found
    and removed - however I would rather avoid this very time consuming process if possible.
    I have also testing this using 'capture media' in the full OS and that also fails at the same step with the same errors in the smsts.log
    The only workaround I have for now is to let the task sequence fail at the 'Prepare ConfigMgr Client for Capture' step, then I uninstall the SCCM client using 'ccmsetup.exe /uninstall' and use the 'capture media' method - obviously with no SCCM client installed,
    it skips the 'Prepare ConfigMgr Client for Capture' step and goes straight to the 'Prepare OS' step and then to the actual capture to the WIM step.
    Anybody else seeing this or have any suggestions?
    My Microsoft Core Infrastructure & Systems Management blog -
    blog.danovich.com.au

    It looks like there is a similar issue over here (http://www.windows-noob.com/forums/index.php?/topic/5906-task-sequence-error-0xffffffff/) that was resolved by removing the Application Installations one by one until a problematic one was found
    and removed - however I would rather avoid this very time consuming process if possible.
    You dont have to test it 18 times....
    Just test with 50% of the applications first, if it fails, test with 25% and then on of the time...
    You should be able to find the application, within 4-5 tests...
    Ronni Pedersen | Microsoft MVP - ConfigMgr | Blogs:
    http://www.ronnipedersen.com/ and SCUG.dk/ | Twitter
    @ronnipedersen

  • Install Updates step fails in Build and Capture (error code 87D00272)

    Hello,
    I was really hoping someone could help me with this.
    Background information:
    - We have a CM07 server in a production environment.
    - I've set up a CM12 RTM server, following the guides in this forum, with the hopes of migrating soon.
    - I wanted to do OSD from scratch to learn more and to take advantage of new features in CM12.
    - I have a few virtual machines running for testing OSD/apps (these are the only clients managed by my CM12 server).
    - Since it's not possible to have two WDS servers running at the same time AFAIK (without using registry tweaks, the F11 trick, that by the
    way doesn't work for me) I have created a bootable TS media that I mount on the virtual machines whenever I want to test OSD.
    Now, to my problem:
    I can't figure out why my Build and Capture TS is failing on the Install Software Updates step. smsts.log file says: Failed
    to RefreshUpdates, hr=087d00272, followed by: Failed to run the action: Install Software Updates. Component is disabled (Error: 87D00272; Source: CCM).
    I have read about similar issues occurring in CM07 capture task sequences since the machine is joined to a Workgroup. The proposed solution was adding SMSSLP=FQDN to the client installation properties, but since that functionality is moved to the MP in CM12,
    it should be enough to specify SMSMP=FQDN in my case. It's not working anyway. Tried it to a Deploy TS also, where the machine is domain joined, but I got the same error.
    The error code 87D00272 returns no results on Google. This stumps me, as someone surely has had the same problem? Here are the relevant portions
    of the smsts.log file
    If someone had the chance to look at this, I would greatly appreciate it. Thank you!
    Refreshing Updates InstallSWUpdate 2012-06-13 10:15:33 228 (0x00E4)
    spInstall->RefreshTargetedUpdates( spCallback, &bAlreadyCompleted ),
    HRESULT=87d00272 (e:\nts_sccm_release\sms\client\osdeployment\installswupdate
    \installswupdate.cpp,467) InstallSWUpdate 2012-06-13 10:15:34 228 (0x00E4)
    Failed to RefreshUpdates, hr=0x87d00272 InstallSWUpdate 2012-06-13 10:15:34 228
    (0x00E4)
    RefreshTargetedUpdates(spInstall, spCallback, bAlreadyCompleted), HRESULT=87d00272
    (e:\nts_sccm_release\sms\client\osdeployment\installswupdate
    \installswupdate.cpp,1295) InstallSWUpdate 2012-06-13 10:15:34 228 (0x00E4)
    RefreshUpdates(), HRESULT=87d00272 (e:\nts_sccm_release\sms\client\osdeployment
    \installswupdate\installswupdate.cpp,906) InstallSWUpdate 2012-06-13 10:15:34
    228 (0x00E4)
    InstallUpdates(pInstallUpdate, tType, sJobID, sActiveRequestHandle),
    HRESULT=87d00272 (e:\nts_sccm_release\sms\client\osdeployment\installswupdate
    \main.cpp,248) InstallSWUpdate 2012-06-13 10:15:34 228 (0x00E4)
    Setting TSEnv variable SMSTSInstallUpdateJobGUID= InstallSWUpdate 2012-06-13
    10:15:34 228 (0x00E4)
    Process(pInstallUpdate, tType), HRESULT=87d00272 (e:\nts_sccm_release\sms\client
    \osdeployment\installswupdate\main.cpp,304) InstallSWUpdate 2012-06-13 10:15:34
    228 (0x00E4)
    Process completed with exit code 2278556274 TSManager 2012-06-13 10:15:34
    912 (0x0390)
    ---------! TSManager 2012-06-13 10:15:34 912 (0x0390)
    Failed to run the action: Install Software Updates.
    Component is disabled (Error: 87D00272; Source: CCM) TSManager 2012-06-13
    10:15:34 912 (0x0390)
    MP server http://CFGMGR-SRV.zenit.brummer.se. Ports 80,443. CRL=false. TSManager
    2012-06-13 10:15:34 912 (0x0390)
    Setting authenticator TSManager 2012-06-13 10:15:35 912 (0x0390)
    Set authenticator in transport TSManager 2012-06-13 10:15:35 912 (0x0390)
    Sending StatusMessage TSManager 2012-06-13 10:15:35 912 (0x0390)
    Setting message signatures. TSManager 2012-06-13 10:15:35 912 (0x0390)
    Setting the authenticator. TSManager 2012-06-13 10:15:35 912 (0x0390)
    CLibSMSMessageWinHttpTransport::Send: URL: CFGMGR-SRV.zenit.brummer.se:80  CCM_POST
    /ccm_system/request TSManager 2012-06-13 10:15:35 912 (0x0390)
    Request was succesful. TSManager 2012-06-13 10:15:35 912 (0x0390)
    Set a global environment variable _SMSTSLastActionRetCode=-2016411022 TSManager
    2012-06-13 10:15:35 912 (0x0390)
    Set a global environment variable _SMSTSLastActionSucceeded=false TSManager
    2012-06-13 10:15:35 912 (0x0390)
    Clear local default environment TSManager 2012-06-13 10:15:35 912 (0x0390)
    Let the parent group (Setup Operating System) decides whether to continue execution
    TSManager 2012-06-13 10:15:35 912 (0x0390)
    The execution of the group (Setup Operating System) has failed and the execution has
    been aborted. An action failed.
    Operation aborted (Error: 80004004; Source: Windows) TSManager 2012-06-13
    10:15:35 912 (0x0390)
    Failed to run the last action: Install Software Updates. Execution of task sequence
    failed.
    Component is disabled (Error: 87D00272; Source: CCM) TSManager 2012-06-13
    10:15:35 912 (0x0390)
    MP server http://CFGMGR-SRV.zenit.brummer.se. Ports 80,443. CRL=false. TSManager
    2012-06-13 10:15:35 912 (0x0390)
    Setting authenticator TSManager 2012-06-13 10:15:35 912 (0x0390)
    Set authenticator in transport TSManager 2012-06-13 10:15:35 912 (0x0390)
    Sending StatusMessage TSManager 2012-06-13 10:15:35 912 (0x0390)
    Setting message signatures. TSManager 2012-06-13 10:15:35 912 (0x0390)
    Setting the authenticator. TSManager 2012-06-13 10:15:35 912 (0x0390)
    CLibSMSMessageWinHttpTransport::Send: URL: CFGMGR-SRV.zenit.brummer.se:80  CCM_POST
    /ccm_system/request TSManager 2012-06-13 10:15:35 912 (0x0390)
    Request was succesful. TSManager 2012-06-13 10:15:35 912 (0x0390)
    Launching command shell. OSDSetupHook 2012-06-13 10:15:45 1932
    (0x078C)
    executing command: C:\WINDOWS\system32\cmd.exe /k OSDSetupHook 2012-06-13
    10:15:45 1932 (0x078C)
    executed command: C:\WINDOWS\system32\cmd.exe /k OSDSetupHook 2012-06-13
    10:15:45 1932 (0x078C)
    Execution::enExecutionFail != m_eExecutionResult, HRESULT=80004005 (e:
    \nts_sccm_release\sms\client    asksequence    smanager    smanager.cpp,756) TSManager
    2012-06-13 10:16:57 912 (0x0390)
    Task Sequence Engine failed! Code: enExecutionFail TSManager 2012-06-13
    10:16:57 912 (0x0390)
    TSManager 2012-06-13 10:16:57 912 (0x0390)
    Task sequence execution failed with error code 80004005 TSManager 2012-06-13
    10:16:57 912 (0x0390)

    I can add that I've looked at the Site Status in the Monitoring tab, and everything looks green apart from some Warnings about User and System Discovery. In Component Status, I have a warning about the Distribution Point on C$. I thought placing a NO_SMS_ON_DRIVE.SMS
    file in the root of C: would mean no stuff was placed there? I can't see anything SCCM related, but it seems that it has placed a DP on C:?
    The error message about DP is: 
    Distribution Manager has not tried to install IIS component of operating system to distribution point "["Display=\\CFGMGR-SRV.zenit.brummer.se\"]MSWNET:["SMS_SITE=PS1"]\\CFGMGR-SRV.zenit.brummer.se\". You should install and configure IIS manually. Please
    ensure RDC is also enabled.

  • Install Software Updates Step fails during Build and Capture

    I have run into a problem while attempting to use the Install Software Update task during a build and capture task sequence.  I have MDT 2012U1 integrated into SCCM 2012.
    The Install Software steps find and use the Deployment Points fine and the Use Toolkit steps similarly are able to download their source files from the distribution points using the Network Access account.  The Install Software Updates step, however
    fails with an access denied error in the CAS.log.
    I have found that I can work around this problem by setting the DP to allow anonymous access.  After checking this box, the software updates install during the build and capture task sequence.  Unchecking the Allow anoymous makes the problem recur.
    I would like to not have to have the "allow anonymous access" enabled on the DPs for obvious reasons.  Other packages download correctly from the DP with anonymous access disabled - they use the network access account.  Install Software Updates
    is the only step that seems unable to use that account to talk with the DP.
    Is this a known issue?  Is there a work around?

    Thanks for the information. I will give that a try.  I do have the SMSMP & SMSSLP (not sure I need this one in 2012) filled in in the Configmgr client install settings.  Before I did that, it couldn't even find the SUP.
    I am a little skeptical that the hotfix will fix my problem since most packages are downloading from the DP fine - it is only Software Updates that are failing to download.  On the other hand, it is clearly a permissions issue since allowing anonymous
    on the DP resolves the issue, all be it in a way I am uncomfortable maintaining in the long run.
    That KB replaces a lot of key Windows system files.  Hopefully, it won't cause more problems than it solves.
    ---additional thought
    I wonder, could it be that Packages that work without this KB have package share settings with "Copy the content in this package to a packages share on Distribution Points" cleared/unchecked?  This setting is not available for patch packages
    - so I wonder if it is enabled by default behind the scenes.  That could explain why the patch packages are affected and not the other regular application packages I have are not.  All my regular packages so far do not have the
    "Copy the content" box checked. Clients would be accessing the packages differently I suppose based on whether it was through a packages share or through the new SCCM 2012 package storage thing with the hashing.

Maybe you are looking for