SCCM 2012 SP1 Boot Image

Hi Guys,
We upgraded to SCCM 2012 SP1 from the RTM yesterday and now our OS Deployment has stopped working. I have tried to update the DP's with the boot images and it keep failing to add drivers. I have also tried to add a Boot Image but this failing.
Any suggestion on what might be going wrong? Our upgrade processed completed successfully.
Kind Regards
TPark IT Technician

Hi,
I have removed all the drivers and I am now getting the following error.
Error: Boot image to update:
Microsoft Windows PE (x86)
 Error: Actions to perform:
Add ConfigMgr binaries
Add custom background
Enable Windows PE command line support
Optional components:
Scripting (WinPE-Scripting)
Startup (WinPE-SecureStartup)
Network (WinPE-WDS-Tools)
Scripting (WinPE-WMI)
 Error: The wizard detected the following problems when updating the boot image.
The SMS Provider reported an error.: ConfigMgr Error Object:
instance of SMS_ExtendedStatus
Description = "Failed to insert OSD binaries into the WIM file";
ErrorCode = 2152205056;
File = "e:\\qfe\\nts\\sms\\siteserver\\sdk_provider\\smsprov\\sspbootimagepackage.cpp";
Line = 4630;
ObjectInfo = "CSspBootImagePackage::PreRefreshPkgSrcHook";
Operation = "ExecMethod";
ParameterInfo = "SMS_BootImagePackage.PackageID=\"ASH00001\"";
ProviderName = "WinMgmt";
StatusCode = 2147749889;
I am only trying to Deploy Windows 7 images currently but we are looking to upgrade to Windows 8 at Christmas. Can I import a boot image from a Windows 7 or Windows 8 cd?

Similar Messages

  • SCCM 2012 R2 Boot Image won't load in Windows XP

    I'm using ADK 8.1, MDT 2013, x86 Boot image w/ PE 5. Deployed a TS to Windows XP SP3 computer with a single task: Reboot Computer to PE
    Getting this: Executing command line: "C:_SMSTaskSequence\WinPE\SMS\bin\i386\bootsect.exe" /NT60 SYS /MBR TSManager 10/31/2013 9:49:27 AM 3000 (0x0BB8)
    Failed to install boot image. is not a valid Win32 application. (Error: 800700C1; Source: Windows)
    More detailed smsts.log below:
    <![LOG[Captured settings for adapter 1]LOG]!><time="09:33:52.197+420" date="10-31-2013" component="OSDNetSettings" context="" type="1" thread="5368" file="netsettings.cpp:99">
    <![LOG[OSDNetSettings finished: 0x00000000]LOG]!><time="09:33:52.197+420" date="10-31-2013" component="OSDNetSettings" context="" type="1" thread="5368" file="main.cpp:192">
    <![LOG[Process completed with exit code 0]LOG]!><time="09:33:52.307+420" date="10-31-2013" component="TSManager" context="" type="1" thread="4856" file="commandline.cpp:1123">
    <![LOG[Installing boot image to hard drive]LOG]!><time="09:33:52.353+420" date="10-31-2013" component="TSManager" context="" type="1" thread="4856" file="bootimage.cpp:621">
    <![LOG[Backing up existing boot system before trying to set up new boot system]LOG]!><time="09:33:52.353+420" date="10-31-2013" component="TSManager" context="" type="1" thread="4856"
    file="bootimage.cpp:644">
    <![LOG[BootLoader::backup: C:\, C:\_SMSTaskSequence\backup]LOG]!><time="09:33:53.213+420" date="10-31-2013" component="TSManager" context="" type="1" thread="4856" file="bootloader.cpp:85">
    <![LOG[BootLoader::restore: C:\_SMSTaskSequence\WinPE, C:\]LOG]!><time="09:33:54.479+420" date="10-31-2013" component="TSManager" context="" type="1" thread="4856" file="bootloader.cpp:382">
    <![LOG[Saving bcd store to C:\_SMSTaskSequence\WinPE\boot\BCD]LOG]!><time="09:33:57.057+420" date="10-31-2013" component="TSManager" context="" type="1" thread="4856" file="bootconfigimplbcd.cpp:703">
    <![LOG[Executing command line: "C:\_SMSTaskSequence\WinPE\SMS\bin\i386\bootsect.exe" /NT60 SYS /MBR]LOG]!><time="09:33:57.166+420" date="10-31-2013" component="TSManager" context="" type="1"
    thread="4856" file="commandline.cpp:827">
    <![LOG[CreateProcess failed. Code(0x800700C1)]LOG]!><time="09:33:57.182+420" date="10-31-2013" component="TSManager" context="" type="3" thread="4856" file="commandline.cpp:1018">
    <![LOG[Command line execution failed (800700C1)]LOG]!><time="09:33:57.182+420" date="10-31-2013" component="TSManager" context="" type="3" thread="4856" file="commandline.cpp:1245">
    <![LOG[Failed to install boot image. 
     is not a valid Win32 application. (Error: 800700C1; Source: Windows)]LOG]!><time="09:33:57.182+420" date="10-31-2013" component="TSManager" context="" type="3" thread="4856" file="bootimage.cpp:681">
    <![LOG[Failed to install boot image UCI00073. 
     is not a valid Win32 application. (Error: 800700C1; Source: Windows)]LOG]!><time="09:33:57.198+420" date="10-31-2013" component="TSManager" context="" type="3" thread="4856" file="engine.cxx:840">
    <![LOG[Failed to reboot the system. Error 0x(800700c1)]LOG]!><time="09:33:57.198+420" date="10-31-2013" component="TSManager" context="" type="3" thread="4856" file="engine.cxx:953">
    <![LOG[Failed to initialize a system reboot. 
     is not a valid Win32 application. (Error: 800700C1; Source: Windows)]LOG]!><time="09:33:57.198+420" date="10-31-2013" component="TSManager" context="" type="3" thread="4856" file="engine.cxx:577">
    <![LOG[Fatal error is returned in check for reboot request of the action (Restart in Windows PE). 
     is not a valid Win32 application. (Error: 800700C1; Source: Windows)]LOG]!><time="09:33:57.198+420" date="10-31-2013" component="TSManager" context="" type="3" thread="4856" file="engine.cxx:273">
    <![LOG[An error (0x800700c1) is encountered in execution of the task sequence]LOG]!><time="09:33:57.198+420" date="10-31-2013" component="TSManager" context="" type="3" thread="4856" file="engine.cxx:348">
    <![LOG[Set authenticator in transport]LOG]!><time="09:33:57.198+420" date="10-31-2013" component="TSManager" context="" type="0" thread="4856" file="libsmsmessaging.cpp:7734">
    <![LOG[Task Sequence Engine failed! Code: 800700C1]LOG]!><time="09:34:45.920+420" date="10-31-2013" component="TSManager" context="" type="3" thread="4856" file="tsmanager.cpp:919">
    <![LOG[****************************************************************************]LOG]!><time="09:34:45.920+420" date="10-31-2013" component="TSManager" context="" type="1" thread="4856"
    file="tsmanager.cpp:953">
    <![LOG[Task sequence execution failed with error code 800700C1]LOG]!><time="09:34:45.920+420" date="10-31-2013" component="TSManager" context="" type="3" thread="4856" file="tsmanager.cpp:954">
    <![LOG[Cleaning Up.]LOG]!><time="09:34:45.920+420" date="10-31-2013" component="TSManager" context="" type="1" thread="4856" file="tsmanager.cpp:675">
    <![LOG[Removing Authenticator]LOG]!><time="09:34:45.920+420" date="10-31-2013" component="TSManager" context="" type="1" thread="4856" file="tsmanager.cpp:686">

    See the "Workaround" section of this post for an example of downgrading bootsect.exe:
    http://social.technet.microsoft.com/Forums/en-US/6e934990-999a-4367-860a-3ce4e5eda956/sccm-2012-r2-error-0x800700c1?forum=configmanagerosd
    It is not the version of WinPE that is the problem here, but the version of bootsect.exe that gets injected into the boot media.
    Nash Pherson, Senior Systems Consultant
    Now Micro -
    My Blog Posts
    <-- If this post was helpful, please click "Vote as Helpful".
    This workaround worked in my environment.  Fixed my in-place upgrades from XP to Windows 7, and as a bonus, fixed imaging XP as well. yeah, I have to keep XP for awhile. :-(

  • Deployed Windows 7 Image failing to start -SCCM 2012 SP1

    Hello, I am deploying windows 7 image using SCCM 2012 SP1, the installation goes thru fine but when it is in the process of restart, a blue screen is displayed for a split second and then it tries to reboot again with same results. Are there any logs on
    the SCCM server I can check to see where the problem may be?

    This generally means inaccessible boot device. How are you partitioning the drive and applying the image?
    This is one way to do it
    http://www.gerryhampsoncm.blogspot.ie/2013/02/sccm-2012-sp1-step-by-step-guide-part_18.html
    Gerry Hampson | Blog:
    www.gerryhampsoncm.blogspot.ie | LinkedIn:
    Gerry Hampson | Twitter:
    @gerryhampson

  • SCCM 2012 SP1 - Offline Servicing failure - Failed to find or access the update binaries to be applied on the image

    Hi there
    Trying to patch a new Windows 7 SP1 image within SCCM 2012 SP1, but it's failing.
    I've searched for information on the failure messages I am seeing, but although there is a LOT of information online concerning Offline Servicing failures, I can't find anything on the errors I am seeing.
    I've tried injecting a single update, five updates and ten updates, no difference, same messages.
    We have McAfee Access Protection disabled, as we know Offline Servicing simply won't work if this is running.
    In the console, in Schedule Update Status for the image I am trying to update, the following message is shown:
    "Failed to find or access the update binaries to be applied on the image."
    That sounds as if the process can't find the actual .cab file for any update I've tried to inject, but I don't know why it wouldn't be able to do that, we have Software Updates configured and the .cab files are on the same server.
    When I looked at the OfflineServicingMgr.log file, I see the following entries:
    Processing image at index 1        SMS_OFFLINE_SERVICING_MANAGER        14/06/2014 14:52:49        8272 (0x2050)
    Mounting image at index 1. Image file='D:\ConfigMgr_OfflineImageServicing\PackageID\W7_Image.wim', MountDirectory='D:\ConfigMgr_OfflineImageServicing\PackageID\ImageMountDir', ImageFileType='WIM', Mode='ReadWrite'        SMS_OFFLINE_SERVICING_MANAGER       
    14/06/2014 14:52:49        8272 (0x2050)
    Image OS information : MajorVersionMS = 6, MinorVersionMS = 1, MajorVersionLS = 7601, MinorVersionLS = 17514        SMS_OFFLINE_SERVICING_MANAGER        14/06/2014 14:53:31       
    8272 (0x2050)
    Failed to find properties of file 4        SMS_OFFLINE_SERVICING_MANAGER        14/06/2014 14:53:31        8272 (0x2050)
    UnMounting Image (Commit Changes = 0) ...        SMS_OFFLINE_SERVICING_MANAGER        14/06/2014 14:53:31        8272 (0x2050)
    Completed processing image package PackageID. Status = Failed        SMS_OFFLINE_SERVICING_MANAGER        14/06/2014 14:54:04        8272 (0x2050)
    Updated history for image package PackageID in the database        SMS_OFFLINE_SERVICING_MANAGER        14/06/2014 14:54:04        8272 (0x2050)
    Schedule processing failed        SMS_OFFLINE_SERVICING_MANAGER        14/06/2014 14:54:04        8272 (0x2050)
    Processing completed for Schedule with ID 16777237        SMS_OFFLINE_SERVICING_MANAGER        14/06/2014 14:54:04        8272 (0x2050)
    STATMSG: ID=7910 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_OFFLINE_SERVICING_MANAGER" SYS=SCCMServer.domain SITE=Site_Code PID=8560 TID=8272 GMTDATE=Sat Jun 14 13:54:04.964 2014 ISTR0="16777237" ISTR1="" ISTR2=""
    ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0        SMS_OFFLINE_SERVICING_MANAGER       
    14/06/2014 14:54:04        8272 (0x2050)
    Schedule processing thread stopped        SMS_OFFLINE_SERVICING_MANAGER        14/06/2014 14:54:05        8272 (0x2050)
    I'm not sure what file "Failed to find properties of file 4" is referring to, whether dism.exe, an update or the image itself, but immediately after this message appears the image is unmounted. After that this message shows:
    "Completed processing image package PackageID. Status = Failed"
    As I say, there's a lot of information available re Offline Servicing but I haven't found anything with these particular messages.
    If anyone has encountered this before, I'd appreciate any information you have.
    Regards,
    John.

    Hi,
    I think file named 'NO_SMS_ON_DRIVE.SMS’ might be causing this issue. If this file is present in logical drives, then please give it a shot one more time after deleting this file from the logical drives.
    Due to this file, it might be preventing 'smsexec' service to skip the drive when looking for content. So worth a try!
    After deleting this file, you also need to restart 'smsexec' service to reflect the changes. You can also verify from below registry value & ensure that all of your logical drives (specially where SCCMContentLib directory resides) should be listed
    over there 
    'HKLM\Software\Microsoft\SMS\DP\ContentLibUsableDrives'
    Hope this will help!
    Cheers | Navdeep Sidhu

  • SCCM 2012 SP1 fails to install OSD of Captured Image

    I installed Windows Server 2012, Visual Studio Pro 2008, 2010, 2012 and SQL Server 2012 onto a machine. Configured the settings on Windows Server 2012 and SQL 2012 to how the Developers requested to be configured. Ran the Capture Media from SCCM 2012 SP1,
    saved to the designated network share. Capture was successful.
    I create a TS to deploy the image to the other Dev Servers but it reboots to say no valid operating system found. I checked Monitoring for the Deployment I see the Task sequence but has the following error: Device - Unknown, MessageID - 11170, Description
    - The task sequence manager could not successfully complete execution of the task sequence.
    I see in the Apply Operation System from a captured image shows 1-1, 2-2, or 3-3. Does it matter which one I select and if so what does the numbers mean?
    Any help is greatly appreciated, thanks!!

    Hi Blacksuit,
    Those numbers of the captured image stand for the indexes that are part of your WIM.  And yes, it does matter which one you select.  In the ConfigMgr console, go to your Software Library > Operating Systems > Operating System Images and select
    the image you imported into ConfigMgr.  Then at the bottom, click the Details tab to display your indexes.  The index that contains your OS will have an OS Version and a description.  The other indexes will be data images and not contain any
    information in the Details tab.  You'll need to choose the index (number) that contains the OS for the Apply OS step.  To apply the data image indexes, use the Apply Data Image task sequence step and specify the partitions to apply the images
    too before the Apply OS step.
    Good luck!
    -Matt 

  • SCCM 2012 SP1 MDT task sequence fails on reboot does not retain ip

    we are having a sccm 2012 sp1 server that used for installation of win 8.1 Enterprise , the task sequence works perfectly fine but when we  run the same task on HP Elite 8300 system having Intel 82579LM Adapter from Windows XP , after the reboot the
    task fails as no ip address is assigned the NIC , We did download the WInPE Adapter drivers from HP site and injecting to the x86 Boot Image (6.2.9200) however the task still fails ,
    Our environment uses all static ip address , the same task as mentioned earlier has worked fine with Different brands of HP elite 8200/8100 , infact the elite 8200 also uses the same NIC card
    Find below the smsts.log file
    Main error in the log file is
    No physical network adapters found    OSDNetSettings    2/12/2014 1:02:38 AM    2064 (0x0810)
    Found network adapter "Intel(R) 82579LM Gigabit Network Connection" with IP Address 169.254.181.151.    TSMBootstrap    2/12/2014 1:05:41 PM    1984 (0x07C0)
    Xtract from LOG
    SMSTSRebootDelay=60    Reboot    2/12/2014 1:01:56 AM    3496 (0x0DA8)
    SMSTSRebootMessage=A new Microsoft Windows operating system is being installed. The computer must restart to continue.    Reboot    2/12/2014 1:01:56 AM    3496 (0x0DA8)
    SMSTSRebootRequested=WinPE    Reboot    2/12/2014 1:01:56 AM    3496 (0x0DA8)
    Process completed with exit code 0    TSManager    2/12/2014 1:01:56 AM    1876 (0x0754)
    !--------------------------------------------------------------------------------------------!    TSManager    2/12/2014 1:01:56 AM    1876 (0x0754)
    Successfully completed the action (Restart to Windows PE) with the exit win32 code 0    TSManager    2/12/2014 1:01:56 AM    1876 (0x0754)
    Set authenticator in transport    TSManager    2/12/2014 1:01:56 AM    1876 (0x0754)
    Set a global environment variable _SMSTSLastActionRetCode=0    TSManager    2/12/2014 1:01:57 AM    1876 (0x0754)
    Set a global environment variable _SMSTSLastActionSucceeded=true    TSManager    2/12/2014 1:01:57 AM    1876 (0x0754)
    Clear local default environment    TSManager    2/12/2014 1:01:57 AM    1876 (0x0754)
    Updated security on object E:\_SMSTaskSequence.    TSManager    2/12/2014 1:01:57 AM    1876 (0x0754)
    Set a global environment variable _SMSTSNextInstructionPointer=59    TSManager    2/12/2014 1:01:57 AM    1876 (0x0754)
    Set a TS execution environment variable _SMSTSNextInstructionPointer=59    TSManager    2/12/2014 1:01:57 AM    1876 (0x0754)
    Set a global environment variable _SMSTSInstructionStackString=0 41 57    TSManager    2/12/2014 1:01:57 AM    1876 (0x0754)
    Set a TS execution environment variable _SMSTSInstructionStackString=0 41 57    TSManager    2/12/2014 1:01:57 AM    1876 (0x0754)
    Save the current environment block    TSManager    2/12/2014 1:01:57 AM    1876 (0x0754)
    Executing command line: "bcdedit.exe"    TSManager    2/12/2014 1:01:57 AM    1876 (0x0754)
    CreateProcess failed. Code(0x80070002)    TSManager    2/12/2014 1:01:57 AM    1876 (0x0754)
    Command line execution failed (80070002)    TSManager    2/12/2014 1:01:57 AM    1876 (0x0754)
    Staging boot image UNB0003A    TSManager    2/12/2014 1:01:57 AM    1876 (0x0754)
    ResolveSource flags: 0x00000000    TSManager    2/12/2014 1:01:59 AM    1876 (0x0754)
    SMSTSPersistContent: . The content for package UNB0003A will be persisted    TSManager    2/12/2014 1:01:59 AM    1876 (0x0754)
    Set authenticator in transport    TSManager    2/12/2014 1:01:59 AM    1876 (0x0754)
    WinHttp credentials set    TSManager    2/12/2014 1:01:59 AM    1876 (0x0754)
    List of files to be downloaded    TSManager    2/12/2014 1:01:59 AM    1876 (0x0754)
    Downloaded file from http://unb-ho-sccmdb.exch1.mas.unb.com:80/SMS_DP_SMSPKG$/UNB0003A/sccm?/WinPE.UNB0003A.wim to E:\_SMSTaskSequence\Packages\UNB0003A\WinPE.UNB0003A.wim     TSManager    2/12/2014 1:02:22 AM    1876
    (0x0754)
    VerifyContentHash: Hash algorithm is 32780    TSManager    2/12/2014 1:02:22 AM    1876 (0x0754)
    Found boot image E:\_SMSTaskSequence\Packages\UNB0003A\WinPE.UNB0003A.wim    TSManager    2/12/2014 1:02:25 AM    1876 (0x0754)
    Copying boot image locally...    TSManager    2/12/2014 1:02:25 AM    1876 (0x0754)
    Failed to find ADK installation root registry key    TSManager    2/12/2014 1:02:32 AM    1876 (0x0754)
    Opening image file E:\_SMSTaskSequence\WinPE\sources\boot.wim    TSManager    2/12/2014 1:02:32 AM    1876 (0x0754)
    Applying image 1 to volume E:\_SMSTaskSequence\WinPE    TSManager    2/12/2014 1:02:32 AM    1876 (0x0754)
    Closing image file E:\_SMSTaskSequence\WinPE\sources\boot.wim    TSManager    2/12/2014 1:02:35 AM    1876 (0x0754)
    Capturing WinPE bootstrap settings    TSManager    2/12/2014 1:02:35 AM    1876 (0x0754)
    Environment scope successfully created: Global\{E7E5BB69-6198-4555-B5CA-6C46A2B5EB78}    TSManager    2/12/2014 1:02:35 AM    1876 (0x0754)
    Executing command line: "osdnetsettings.exe" capture adapters:true scope:Global\{E7E5BB69-6198-4555-B5CA-6C46A2B5EB78}    TSManager    2/12/2014 1:02:35 AM    1876 (0x0754)
    ==============================[ OSDNetSettings.exe ]===========================    OSDNetSettings    2/12/2014 1:02:36 AM    2064 (0x0810)
    Command line: "osdnetsettings.exe" capture adapters:true scope:Global\{E7E5BB69-6198-4555-B5CA-6C46A2B5EB78}    OSDNetSettings    2/12/2014 1:02:36 AM    2064 (0x0810)
    No adapters found with non-empty DNSDomainSuffixSearchOrder    OSDNetSettings    2/12/2014 1:02:36 AM    2064 (0x0810)
    Adapter "ROOT\SYMC_TEEFER2MP\0000" not found    OSDNetSettings    2/12/2014 1:02:38 AM    2064 (0x0810)
    No physical network adapters found    OSDNetSettings    2/12/2014 1:02:38 AM    2064 (0x0810)
    OSDNetSettings finished: 0x00000000    OSDNetSettings    2/12/2014 1:02:38 AM    2064 (0x0810)
    Process completed with exit code 0    TSManager    2/12/2014 1:02:38 AM    1876 (0x0754)
    Installing boot image to hard drive    TSManager    2/12/2014 1:02:38 AM    1876 (0x0754)
    Backing up existing boot system before trying to set up new boot system    TSManager    2/12/2014 1:02:38 AM    1876 (0x0754)
    BootLoader::backup: C:\, E:\_SMSTaskSequence\backup    TSManager    2/12/2014 1:02:39 AM    1876 (0x0754)
    BootLoader::restore: E:\_SMSTaskSequence\WinPE, C:\    TSManager    2/12/2014 1:02:43 AM    1876 (0x0754)
    Saving bcd store to E:\_SMSTaskSequence\WinPE\boot\BCD    TSManager    2/12/2014 1:02:43 AM    1876 (0x0754)
    Executing command line: "E:\_SMSTaskSequence\WinPE\SMS\bin\i386\bootsect.exe" /NT60 SYS /MBR    TSManager    2/12/2014 1:02:45 AM    1876 (0x0754)
    Process completed with exit code 0    TSManager    2/12/2014 1:02:46 AM    1876 (0x0754)
    Updated security on object E:\_SMSTaskSequence.    TSManager    2/12/2014 1:02:47 AM    1876 (0x0754)
    Set a global environment variable _SMSTSNextInstructionPointer=59    TSManager    2/12/2014 1:02:47 AM    1876 (0x0754)
    Set a TS execution environment variable _SMSTSNextInstructionPointer=59    TSManager    2/12/2014 1:02:47 AM    1876 (0x0754)
    Set a global environment variable _SMSTSInstructionStackString=0 41 57    TSManager    2/12/2014 1:02:47 AM    1876 (0x0754)
    Set a TS execution environment variable _SMSTSInstructionStackString=0 41 57    TSManager    2/12/2014 1:02:47 AM    1876 (0x0754)
    Save the current environment block    TSManager    2/12/2014 1:02:47 AM    1876 (0x0754)
    Updated security on object C:\_SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca.    TSManager    2/12/2014 1:02:47 AM    1876 (0x0754)
    Updated security on object D:\_SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca.    TSManager    2/12/2014 1:02:47 AM    1876 (0x0754)
    Updated security on object E:\_SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca.    TSManager    2/12/2014 1:02:47 AM    1876 (0x0754)
    Updated security on object E:\_SMSTaskSequence.    TSManager    2/12/2014 1:02:47 AM    1876 (0x0754)
    Set a global environment variable _SMSTSNextInstructionPointer=59    TSManager    2/12/2014 1:02:47 AM    1876 (0x0754)
    Set a TS execution environment variable _SMSTSNextInstructionPointer=59    TSManager    2/12/2014 1:02:47 AM    1876 (0x0754)
    Set a global environment variable _SMSTSInstructionStackString=0 41 57    TSManager    2/12/2014 1:02:47 AM    1876 (0x0754)
    Set a TS execution environment variable _SMSTSInstructionStackString=0 41 57    TSManager    2/12/2014 1:02:47 AM    1876 (0x0754)
    Save the current environment block    TSManager    2/12/2014 1:02:47 AM    1876 (0x0754)
    Expand a string: %_SMSTSMDataPath%\Logs    TSManager    2/12/2014 1:02:47 AM    1876 (0x0754)
    <![LOG[LOGGING: Finalize process ID set to 780]LOG]!><time="01:04:01.537+480" date="02-12-2014" component="TSBootShell" context="" type="1" thread="784" file="tslogging.cpp:1495">  
          1/1/1601 12:00:00 AM    1995266923 (0x76ED5B6B)
    ==============================[ TSBootShell.exe ]==============================    TSBootShell    2/12/2014 1:04:01 AM    784 (0x0310)
    Succeeded loading resource DLL 'X:\sms\bin\i386\1033\TSRES.DLL'    TSBootShell    2/12/2014 1:04:01 AM    784 (0x0310)
    Debug shell is enabled    TSBootShell    2/12/2014 1:04:01 AM    784 (0x0310)
    Waiting for PNP initialization...    TSBootShell    2/12/2014 1:04:01 AM    796 (0x031C)
    RAM Disk Boot Path: MULTI(0)DISK(0)RDISK(0)PARTITION(3)\_SMSTASKSEQUENCE\WINPE\SOURCES\BOOT.WIM    TSBootShell    2/12/2014 1:04:01 AM    796 (0x031C)
    WinPE boot path: E:\_SMSTASKSEQUENCE\WINPE\SOURCES\BOOT.WIM    TSBootShell    2/12/2014 1:04:01 AM    796 (0x031C)
    Booted from fixed disk    TSBootShell    2/12/2014 1:04:01 AM    796 (0x031C)
    Found config path E:\_SMSTaskSequence    TSBootShell    2/12/2014 1:04:01 AM    796 (0x031C)
    hMap != 0, HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentscope.cpp,515)    TSBootShell    2/12/2014 1:04:01 AM    796 (0x031C)
    m_pGlobalScope->open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,337)    TSBootShell    2/12/2014 1:04:01 AM    796 (0x031C)
    this->open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,549)    TSBootShell    2/12/2014 1:04:01 AM    796 (0x031C)
    hMap != 0, HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentscope.cpp,515)    TSBootShell    2/12/2014 1:04:01 AM    796 (0x031C)
    m_pGlobalScope->open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,337)    TSBootShell    2/12/2014 1:04:01 AM    796 (0x031C)
    this->open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,549)    TSBootShell    2/12/2014 1:04:01 AM    796 (0x031C)
    hMap != 0, HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentscope.cpp,515)    TSBootShell    2/12/2014 1:04:01 AM    796 (0x031C)
    m_pGlobalScope->open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,337)    TSBootShell    2/12/2014 1:04:01 AM    796 (0x031C)
    open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,430)    TSBootShell    2/12/2014 1:04:01 AM    796 (0x031C)
    Can not find DeploymentType in file TsmBootstrap.ini or the file doesn't exist. This is not running on Windows To Go.    TSBootShell    2/12/2014 1:04:01 AM    796 (0x031C)
    hMap != 0, HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentscope.cpp,515)    TSBootShell    2/12/2014 1:04:01 AM    796 (0x031C)
    m_pGlobalScope->open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,337)    TSBootShell    2/12/2014 1:04:01 AM    796 (0x031C)
    open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,430)    TSBootShell    2/12/2014 1:04:01 AM    796 (0x031C)
    Restoring boot system from E:\_SMSTaskSequence\backup    TSBootShell    2/12/2014 1:04:01 AM    796 (0x031C)
    Successfully loaded the BCD boot system    TSBootShell    2/12/2014 1:04:05 AM    796 (0x031C)
    Successfully loaded an exported NTLDR boot system    TSBootShell    2/12/2014 1:04:05 AM    796 (0x031C)
    BootLoader::restore: E:\_SMSTaskSequence\backup, C:\    TSBootShell    2/12/2014 1:04:05 AM    796 (0x031C)
    Successfully merged logs from cache.    TSBootShell    2/12/2014 1:04:06 AM    796 (0x031C)
    hMap != 0, HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentscope.cpp,515)    TSBootShell    2/12/2014 1:04:06 AM    796 (0x031C)
    m_pGlobalScope->open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,337)    TSBootShell    2/12/2014 1:04:06 AM    796 (0x031C)
    open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,430)    TSBootShell    2/12/2014 1:04:06 AM    796 (0x031C)
    Loading bootstrap settings from E:\_SMSTaskSequence\WinPE    TSBootShell    2/12/2014 1:04:06 AM    796 (0x031C)
    Loading saved WinPE settings    TSBootShell    2/12/2014 1:04:06 AM    796 (0x031C)
    Creating key 'Software\Microsoft\SMS\47006C006F00620061006C005C007B00450037004500350042004200360039002D0036003100390038002D0034003500350035002D0042003500430041002D003600430034003600410032004200350045004200370038007D00'    TSBootShell  
     2/12/2014 1:04:06 AM    796 (0x031C)
    Environment scope successfully created: Global\{E7E5BB69-6198-4555-B5CA-6C46A2B5EB78}    TSBootShell    2/12/2014 1:04:06 AM    796 (0x031C)
    Configuring WinPE bootstrap settings    TSBootShell    2/12/2014 1:04:06 AM    796 (0x031C)
    Creating WinPE answer file    TSBootShell    2/12/2014 1:04:06 AM    796 (0x031C)
    Setting hive location to "X:\windows\system32"    TSBootShell    2/12/2014 1:04:06 AM    796 (0x031C)
    Getting namespace "Microsoft-Windows-Setup" for architecture "x86"    TSBootShell    2/12/2014 1:04:06 AM    796 (0x031C)
    Configuring global network settings    TSBootShell    2/12/2014 1:04:06 AM    796 (0x031C)
    Join type:     TSBootShell    2/12/2014 1:04:06 AM    796 (0x031C)
    DNS domain: exch1.mas.unb.com    TSBootShell    2/12/2014 1:04:06 AM    796 (0x031C)
    DNS domain search order:     TSBootShell    2/12/2014 1:04:06 AM    796 (0x031C)
    IP filter sec enabled: false    TSBootShell    2/12/2014 1:04:06 AM    796 (0x031C)
    No adapters found in environment.  Performing global configuration only.    TSBootShell    2/12/2014 1:04:06 AM    796 (0x031C)
    Writing configuration information to E:\_SMSTaskSequence\WinPE\WinPeUnattend.xml    TSBootShell    2/12/2014 1:04:06 AM    796 (0x031C)
    Successfully saved configuration information to E:\_SMSTaskSequence\WinPE\WinPeUnattend.xml    TSBootShell    2/12/2014 1:04:06 AM    796 (0x031C)
    Executing command line: wpeinit.exe -winpe    TSBootShell    2/12/2014 1:04:06 AM    796 (0x031C)
    The command completed successfully.    TSBootShell    2/12/2014 1:05:40 AM    796 (0x031C)
    Starting DNS client service.    TSBootShell    2/12/2014 1:05:40 AM    796 (0x031C)
    Finalizing network settings    TSBootShell    2/12/2014 1:05:40 AM    796 (0x031C)
    No adapters found in environment.  Performing global finalization only.    TSBootShell    2/12/2014 1:05:40 AM    796 (0x031C)
    Finalizing global network settings    TSBootShell    2/12/2014 1:05:40 AM    796 (0x031C)
    DNS domain: exch1.mas.unb.com    TSBootShell    2/12/2014 1:05:40 AM    796 (0x031C)
    DNS domain search order:     TSBootShell    2/12/2014 1:05:40 AM    796 (0x031C)
    DNS for WINS enabled: false    TSBootShell    2/12/2014 1:05:40 AM    796 (0x031C)
    LMHosts file enabled: true    TSBootShell    2/12/2014 1:05:40 AM    796 (0x031C)
    Host lookup file:     TSBootShell    2/12/2014 1:05:40 AM    796 (0x031C)
    WINS scope ID:     TSBootShell    2/12/2014 1:05:40 AM    796 (0x031C)
    Executing command line: X:\sms\bin\i386\TsmBootstrap.exe /env:WinPE /configpath:E:\_SMSTaskSequence    TSBootShell    2/12/2014 1:05:40 AM    796 (0x031C)
    The command completed successfully.    TSBootShell    2/12/2014 1:05:40 AM    796 (0x031C)
    ==============================[ TSMBootStrap.exe ]==============================    TSMBootstrap    2/12/2014 1:05:40 AM    1984 (0x07C0)
    Command line: X:\sms\bin\i386\TsmBootstrap.exe /env:WinPE /configpath:E:\_SMSTaskSequence    TSMBootstrap    2/12/2014 1:05:40 AM    1984 (0x07C0)
    Succeeded loading resource DLL 'X:\sms\bin\i386\1033\TSRES.DLL'    TSMBootstrap    2/12/2014 1:05:40 AM    1984 (0x07C0)
    Succeeded loading resource DLL 'X:\sms\bin\i386\TSRESNLC.DLL'    TSMBootstrap    2/12/2014 1:05:40 AM    1984 (0x07C0)
    Adding SMS bin folder "X:\sms\bin\i386" to the system environment PATH    TSMBootstrap    2/12/2014 1:05:40 AM    1984 (0x07C0)
    Failed to open PXE registry key. Not a PXE boot.    TSMBootstrap    2/12/2014 1:05:40 AM    1984 (0x07C0)
    Resuming Task Sequence in WinPE    TSMBootstrap    2/12/2014 1:05:40 AM    1984 (0x07C0)
    Creating key 'Software\Microsoft\SMS\47006C006F00620061006C005C007B00350031004100300031003600420036002D0046003000440045002D0034003700350032002D0042003900370043002D003500340045003600460033003800360041003900310032007D00'    TSMBootstrap  
     2/12/2014 1:05:40 AM    1984 (0x07C0)
    Environment scope successfully created: Global\{51A016B6-F0DE-4752-B97C-54E6F386A912}    TSMBootstrap    2/12/2014 1:05:40 AM    1984 (0x07C0)
    Creating key 'Software\Microsoft\SMS\47006C006F00620061006C005C007B00420041003300410033003900300030002D0043004100360044002D0034006100630031002D0038004300320038002D003500300037003300410046004300320032004200300033007D00'    TSMBootstrap  
     2/12/2014 1:05:40 AM    1984 (0x07C0)
    Environment scope successfully created: Global\{BA3A3900-CA6D-4ac1-8C28-5073AFC22B03}    TSMBootstrap    2/12/2014 1:05:40 AM    1984 (0x07C0)
    Loading the Task Sequencing Environment from "E:\_SMSTaskSequence\TSEnv.dat".    TSMBootstrap    2/12/2014 1:05:41 AM    1984 (0x07C0)
    Updating the local data path in the Task Sequencing Environment.    TSMBootstrap    2/12/2014 1:05:41 AM    1984 (0x07C0)
    Setting LogMaxSize to 1000000    TSMBootstrap    2/12/2014 1:05:41 AM    1984 (0x07C0)
    Setting LogMaxHistory to 1    TSMBootstrap    2/12/2014 1:05:41 AM    1984 (0x07C0)
    Setting LogLevel to 0    TSMBootstrap    2/12/2014 1:05:41 AM    1984 (0x07C0)
    Setting LogEnabled to 1    TSMBootstrap    2/12/2014 1:05:41 AM    1984 (0x07C0)
    Setting LogDebug to 1    TSMBootstrap    2/12/2014 1:05:41 AM    1984 (0x07C0)
    Command line for extension .exe is "%1" %*    TSMBootstrap    2/12/2014 1:05:41 AM    1984 (0x07C0)
    Set command line: "X:\sms\bin\i386\TsProgressUI.exe" /Register:WinPE    TSMBootstrap    2/12/2014 1:05:41 AM    1984 (0x07C0)
    Executing command line: "X:\sms\bin\i386\TsProgressUI.exe" /Register:WinPE    TSMBootstrap    2/12/2014 1:05:41 AM    1984 (0x07C0)
    ==========[ TsProgressUI started in process 2004 ]==========    TsProgressUI    2/12/2014 1:05:41 AM    2008 (0x07D8)
    Command line: "X:\sms\bin\i386\TsProgressUI.exe" /Register:W
    In dire need of help,
    I have already gone through the below articles on the NET
    http://social.technet.microsoft.com/Forums/systemcenter/en-US/0fe5cded-51cf-487a-97e3-837fb3426a3e/install-software-updates-in-osd-reboots-leaves-clients-in-provisioning-mode?forum=configmgrosd
    http://social.technet.microsoft.com/Forums/systemcenter/en-US/c590e486-d3ca-423f-8953-e596160f3567/updates-hang-during-osd-kb2509007-not-working-for-me?forum=configmgrosd
    Awating response,
    Hasan Reza

    Well Finally I sorted my issue ,
    Just want to share the solution, may be it would be helpful to some one else and save some times
    The problem was that the Xp images has lot of hidden NIC installed , this would not allow the system to work with the correct NIC card and Ip address (System -> View Hidden Devices) , what I did 2 things
    1) Copied the OSD Script folder from the SCCM Server to the Client pc and ran that ztigather.wsf and captured the output , it was evident that it showed capturing multiple adapters , (There are some blogs that pointed out that OSD can capture only one nic
    due to the only one Adapter0 section being defined in the ZTIgather.xml file,)
    2) I open the registry at the xp pc navigated to HKLM-> System ->Current Control Set-> Services-> TCPIP -> Parameters-> Interfaces ->
    Expect for the NIC card that had the Ip address assigned I deleted all other nic card's guid,
    As then post running deleting the old scanstate (USMTUTIL /rd c:\statestore) , reran the task and VOILA..
    All worked fine , below are the two post I followed , though notvery relevant but they were helpful and help me reached the conclusion.
    Thanks,
    Hasan Reza.
    http://systemscenter.ru/mdt2012.en/ztigatherwsf.htm
    http://social.technet.microsoft.com/Forums/windowsserver/en-US/8acb7cd1-7028-4ffe-86c9-eb43041cf8b3/how-do-i-get-rid-of-second-169254xx-ipv4-address-on-windows-server-2008-sp2-x86?forum=winservergen

  • Can I have an SCCM 2012 R2 server and a SCCM 2012 SP1 server in the same site?

    We are currently using SCCM 2012 SP1/MDT 2012 Update 1 to deploy Windows 7, and to migrate existing XP installs to Windows 7 (using the offline USMT functionality in MDT).  We are moving forward with Windows 8.1, and understand that
    we need to upgrade our SCCM infrastructure to SCCM 2012 R2/MDT 2013.  We also understand that this will cause us to lose the ability to migrate XP machines, since MDT 2013 uses a newer version of USMT that doesn’t support XP.
    What do we need to do to continue to support our XP migrations, and enable deployments of Windows 8.1?
    Can we have two SCCM servers in the same Site running different versions of SCCM? Do we need a separate site? 

    You don't explicitly need ConfigMgr 2012 R2 to support Win 8.1. SP1 CU3 will suffice although managing a few things like boot images is a little more difficult: http://blogs.technet.com/b/configmgrteam/archive/2013/10/21/how-to-enable-windows-8.1-deployment-in-sc-2012-configmgr-sp1-cu3.aspx
    You could create two separate site hierarchies, but that would be painful and involve tons of duplication. There would be other issues also if the systems are located on the same subnets and in the same AD forest.
    The best option is to get rid of XP. EOL is in less than 30 days!
    Next best is to stay on SP1 CU3 until you get rid of XP. I know that sucks, but keeping XP around is the root cause of this and many other coming issues in any organization wanting to keep it around.
    Jason | http://blog.configmgrftw.com

  • Deploy Windows 8 To Go through SCCM 2012 SP1

    First a little backgroud:
    I have SCCM 2012 SP1 with MDT 2012 Update 1 integrated. I am using an MDT UDI task sequence to deploy windows 8 and it works perfectly. My Windows 8 image is fairly thin (only containing OS updates and C++ runtimes), and I am using the MDT database
    and an MDT task sequence in SCCM 2012  to dynamically set a list of SCCM Applications to install as well as settings based on location. 
    Now I want to get Windows To Go provisioning working in SCCM 2012 SP1. I had a powershell script that preparied the drive and applied a thick image (including office and other apps) to it then updated unattend.xml with a computer name and the domain join
    info.  That worked for me however I'd like to levarage the dynamic task sequence that I described above to build these To Go sticks the same as my other Windows 8 machines without having to keep updating the thick image evertime something changes. 
    There isn't much info out there that Iv'e found on setting up SCCM 2012 SP1 to provision windows to go here are the two that I have found 
    http://ixrv.blogspot.com/2012/10/provisioning-windows-8-to-go-with.html
    http://technet.microsoft.com/en-us/library/jj651035.aspx
    I followed the instructions in the first link and was able to run the Windows to Go Creator program and apply the prestaged wim to the USB stick. I rebooted from the USB stick Windows PE started and started to run my task sequence then it errored out on
    the apply image step. At this point it occured to me that the MDT SCCM task sequence was probably not setup for prestaged media and or Windows To Go. 
    So my question is am I on the right track? Do I just need to examine each step in my task sequence and make sure that it will work properly with my Prestaged/Windows To Go stick? If so has anyone actually gotten this to work that could give me some advice?
    Or is it asking too much to have a dynamic Windows To Go task sequence and I should just be building a thick image and using a second task sequence specifically for Windows to go? 
    are there any other resources for Windows To Go with SCCM that I'm missing? 
    Thanks, 
    Tony

    First of all sorry I missed your last three posts I have to check my email notifications. I'll try to answer all of them even though I think the last part is the only one where you are still stuck. 
    When I created my prestaged media I didn't put anything into it except for the the OS image and my PE image. On the Select Application and Select Package screen in the prestaged media wizard remove any application or packages that are added automatically.
    The task sequence is supposed to be smart enough to know if the version of the package that is on the prestaged media is out of date and go to a DP to get it but that didnt work for me. The only way I was able to get it to work was to remove all the packages
    from the prestaged media even the Customsettings package, the MDT toolkit package, USMT, etc.. 
    http://social.technet.microsoft.com/Forums/en-US/configmgrosd/thread/d729d0ff-829f-4af8-91af-2131b3355fd0/
    This thread which is about prestaged media in SCCM 2007 helped me to understand how prestaged media is supposed to work. Basically what I learned is that once the computer is rebooted from the ToGo stick into PE the task sequence will run the same as any
    other task sequence installing any applications and setting up your ToGo stick just like any other computer that runs the task sequence they dont need to be in your prestaged media for this to happen. 
    You shouldn't need to worry about partitioning WTGCreator.exe will partition the ToGo stick for you I'm just using the standard MDT Integrated partitioning in my task sequence. The one thing that I did was set the Windows To Go Creator package to "run from
    distribution point" which speed things up because then it didnt download the prestaged wim then apply it to the USB drive. 
    Is it booting into PE then rebooting? Did you check the "Allow unattend operating system deployment" check box when you made your prestaged media? If so it wants you to have set the task sequence to run in a task sequence variable SMSTSPreferredAdvertID
    to the task sequence ID you want to run. I'd just remake the media and leave that box unchecked. 
    Good luck and let me know how it works for you. I'll check back sooner this time I promise. 

  • 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

  • Multicast not working SCCM 2012 SP1

    Hi,
    Am having issues getting multicast working with SCCM 2012 SP1 / Server 2008 R2.
    We have followed all the guidelines in this forum but still no joy
    - Multicast setting enabled on DP
    - Multicast Enabled on OS Image
    - Task Sequence set to down content when needed
    - SCCM DP and Client are on same VLAN to rule out routing issues
    - Network team confirm all ok there end anyway
    - Boot images / WDS and PXE are all healthy
    The PC Boots via PXE ok and runs our windows 7 task sequence, when the task sequence starts it says "Opening multicast session" for about 5 seconds and then disappears. Its as though it tries but then fails. Unicast works fine.
    I then set the OS image to "Only use Multicast" which produces the following error in the client SMSTS.log
    reply has no message header marker
    Failed to open session request (Code 0x80004005)
    ApplyOperatingSystem 28/01/2014 12:53:25
    1944 (0x0798)
    ClientRequestToMCS::DoRequest failed. error = (0x80004005).
    ApplyOperatingSystem 28/01/2014 12:53:25
    1944 (0x0798)
    Request to MCS 'SererName' failed with error (Code 0x80004005).
    ApplyOperatingSystem 28/01/2014 12:53:25
    1944 (0x0798)
    Multicast OpenSessionRequest failed (0x80004005).
    ApplyOperatingSystem 28/01/2014 12:53:25
    1944 (0x0798)
    Sending status message: SMS_OSDeployment_PackageDownloadMulticastStatusFail
    ApplyOperatingSystem 28/01/2014 12:53:25
    1944 (0x0798)
    Any idea on how we get this working ?
    Thanks

    The logs related to multicast that you'll see on the site server are:
    mcsisapi.log
    Records information for multicast package transfer and client request responses.
    Site system server
    mcsprv.log
    Records multicast provider interaction with Windows Deployment Services (WDS).
    Site system server
    MCSSetup.log
    Records details about multicast server role installation.
    Site system server
    MCSMSI.log
    Records details about multicast server role installation.
    Site system server
    Mcsperf.log
    Records details about multicast performance counter updates.
    Site system server
    http://technet.microsoft.com/en-us/library/hh427342.aspx
    >>  Network team confirm all ok there
    end anyway
    This is something to double and triple check.  If Multicast is not enabled on the routers/switches properly, this will not work.  If there is a firewall between the client and the distribution point that doesn't have the Multicast ports open, this
    will not work.
    Client -- > Distribution Point Configured for Multicast
    Description
    UDP
    TCP
    Server Message Block (SMB)
    445
    Multicast Protocol
    63000-64000
    http://technet.microsoft.com/en-us/library/hh427328.aspx
    I hope that helps,
    Nash
    Nash Pherson, Senior Systems Consultant
    Now Micro -
    My Blog Posts
    If you've found a bug or want the product worked differently,
    share your feedback.
    <-- If this post was helpful, please click "Vote as Helpful".

  • SCCM 2012 SP1 - Software Center appears twice in Start Menu

    Hi guys,
    i just finished implementing a fresh SCCM 2012 SP1 Installation for a customer. The whole OSD works like a charm (except some issues with the latest Windows updates breaking the whole OSD, will open a separate thread for this soon), but after the deployment
    the Software Center is appearing twice in the Start Menu (We're using Win7 Enterprise SP1 x86 English with 5 integrated language packs). I first thought this has something to do with the integrated language packs, but both Start Menu entries
    are always in the same language.
    The strange Thing is, that one entry for the SCCM Software Center is called "Software Center" and the other one "SoftwareCenter" (without a space). We configured 2 Client policies, one with EP-enabled and one without EP. We
    deployed the Client Settings to different collections so i don't think that this is causing the Problem?Do you guys have any idea why this is Happening?
    Has anyone ever seen this? See a screenshot below:
    Thank you.
    Cheers
    Stefan

    Thanks for your Response Thomas.
    I don't think it is related to the upgrade to SP1.I think it might be a General issue in SP1. I started with a fresh SCCM 2012 SP1 Installation and i also have 2 Software Center entries in my start menu. If i check the shortcut i can see that one shortcut
    was created when i captured my base Image, the other one was created during the Install OS Task Sequence.

  • SCCM 2012 SP1 - OS Deployment - hash could not be matched for the downloded content

    I've got a newly deployed SCCM 2012 SP1 running on Windows Server 2012. The W2K12 runs as vm on ESX 5.1. I'm having very odd issues with OS deployment. The TS keeps failing when processing SCCM client installation - it downloads the package but then it fails
    straight away with the 80091007 - hash values couldn't be matched error - some extract from smsts.log attached below. It's very consistent, it happens every time - it downloads and applies the image fine straight after that it bombs out.
    What is very interesting is that it works perfectly fine when I deploy vms (on the same or different host) - the issue seems to be be only affecting physical machines (laptops desktops). This might suggest some network issues (vSwitch with Cisco switches) but
    the config on the switch is very simple and this shouldn't be the case.
    I had a few virtualised SCCM 2007 installations (ESX 5 and 4) and it always worked with no problems.
    I tried to recreate the package (changing source directory), turn binary differential replication on and off, copy the content of the package to the dist point or not copy. Push client installation (or other package deployments) work fine
    When I tried to deploy with no download - sometimes it works but most of the time I'd get the files/folder corrupt error (can't remember the No)
    This is starting to drive me crazy - There are some significant changes in the way SCCM 2012 is validating package integrity (like Content Lib folder) but the consistency of this problem is just very odd.
    Anyone has any clues?
    thanks
     - Downloaded file from http://GTKVMGMT05.GTK.LOC...m?/x64/wic_x64_enu.exe to C:\_SMSTaskSequence\Packages\GTK0000C\x64/wic_x64_enu.exe 
     - Download done setting progress bar to 100
    VerifyContentHash: Hash algorithm is 32780
    c:\_smstasksequence\packages\GTK0000c\i386 is a directory. Setting directory security
    c:\_smstasksequence\packages\GTK0000c\x64 is a directory. Setting directory security
     - Hash could not be matched for the downloded content. Original ContentHash = 5EF3A189C48F3469440A83026EC8ECD36EAD6EAF3B5D35663F8201BDE175413C, Downloaded ContentHash = FA4516EDD2D7907F8FA472A3E1B717DF2DD4A0976CD4CEAE11045EE62EC8C661
    0L == TS::Utility::VerifyPackageHash(pszContentID, sDestination), HRESULT=80091007 (e:\nts_sccm_release\sms\framework\tscore\resolvesource.cpp,2999)
     - DownloadContentAndVerifyHash(pszPackageID, L"SMSPackage", saHttpContentSources, saSMBContentSources, saMulticastContentSources, sDestination, dwFlags, L"", 0, dwPackageFlags, pszUserName, pszUserPassword ), HRESULT=80091007 (e:\nts_sccm_release\sms\framework\tscore\resolvesource.cpp,3106)
     - DownloadContentLocally(pszSource, sSourceDirectory, dwFlags, hUserToken, pszUserName, pszUserPassword), HRESULT=80091007 (e:\nts_sccm_release\sms\framework\tscore\resolvesource.cpp,3331)
    ResolveSource(pszSource, sSourceDirectory, dwFlags, 0, 0, 0), HRESULT=80091007 (e:\nts_sccm_release\sms\framework\tscore\resolvesource.cpp,3221)
    TS::Utility::ResolveSource(sClientPackageID, sClientPackagePath), HRESULT=80091007 (e:\nts_sccm_release\sms\client\osdeployment\osdgina\basesetuphook.cpp,1655)
     - Failed to resolve package source "GTK0000C"
     - Exiting ConfigureEx: 0x80091007
     - BaseSetupHook::configure(sWindowsDir), HRESULT=80091007 (e:\nts_sccm_release\sms\client\osdeployment\osdgina\osdsetuphook.cpp,292)
     - Failed to configure OSD setup hook (0x80091007)
     - Failed to configure OSD setup hook (0x80091007)

    is this the only indication of a problem in your smsts.log file ? did you apply the
    authenticode hotfix or have you
    downloaded the SP1 media after that hotfix was applied ?
    Step by Step Configuration Manager Guides >
    2012 Guides |
    2007 Guides | I'm on Twitter > ncbrady

  • Prestaged OSD using SCCM 2012 SP1 windows Partition variable is not being set

    Hello All  I need some assistance with a workaround.
    I am using a presaged task sequence created from a working network / PXE deployment TS for windows 7.
    This TS sets a variable for the OS partition called "Windows" and the value is set in the Partition Disk task.
    Problem is this value is not being read from a prestaged due to the OEMMedia condition skipping this partition and format task.
    Question is how do I get it to read and or set the value for that partition?
    From what I have found on Google this was an issue in beta of MDT but was fixed in RTM.  I am not using MDT TS but I do have it installed. Any idea if this is a known issue with SCCM 2012 sp1 TS? 
    Edit: also noticed that the variable's case is different and will not let me change it.
    Variable under format is "windows"  variable under Apply OS is "Windows"  when I change them to be the same then close and reopen they revert back to the above.  Are these variables case sensitive?
    Edit: for now I have changed it from variable to next available partition.  I tested it twice so far it seems to be using the correct partition and it remains to be called the C drive.  For now this will be my solution.

    When you say "presaged task sequence created from a working network / PXE deployment TS" are you saying this is still a network boot process? Or have you done "Create Task Sequence Media"?
    Dustin Estes - MCP
    yes when i say prestaged that is using the create task sequence media then selecting prestaged.

  • SCCM 2012 Sp1 CU3 support Windows 2012 R2 deployment?

    Hi,
    Sorry for so basic question, but I have read few docuemnts, blogs and official materials and I'm a bit confused. 
    In our organization we have SCCM Sp1 CU3. We are planning create and next deploy Windows 2012R2 Server images. On some documentations there is CU3 supports only application managment, inventory and so on. but there is nothing about image deployment. 
    So, my question is - I have to upgrade SCCM 2012 Sp1 CU3 to SCCM2012R2 to capture, build and deploy Windows 2012R2 system?
    Thank you.

    Yes, you do. See what's new with ConfigMgr 2012 R2
    http://technet.microsoft.com/en-us/library/dn236351.aspx
    Gerry Hampson | Blog:
    www.gerryhampsoncm.blogspot.ie | LinkedIn:
    Gerry Hampson | Twitter:
    @gerryhampson

  • SCCM 2012 SP1 errors when downloading updates

    Currently using SCCM 2012 SP1 with CU2 and I am having some update download issue with Automatic Deployment Rules.
    The Environment is:
      Server 2008 R2
      SCCM 2012 SP1 CU2 (Upgraded from SCCM 2012 CU2)
    I created an Automatic Deployment Rule for Adobe Flash. Since I was having the same issue with Adobe Reader, when I published via SCUP to WSUS I chose not to sign the updates.
    After publishing to WSUS I then sync SCCM, I see the updates and then in the ADR I had it download the updates and I see this error:
    Authentication of file C:\Windows\TEMP\CABDEC5.tmp failed, error 0x800b0004 Software Updates Patch Downloader 8/15/2013 6:49:43 PM 3712 (0x0E80)
    ERROR: DownloadContentFiles() failed with hr=0x80073633 Software Updates Patch Downloader 8/15/2013 6:49:43 PM 6876 (0x1ADC)
    Failed to download the update from internet. Error = 13875 SMS_RULE_ENGINE 8/15/2013 6:49:43 PM 6876 (0x1ADC)
    Failed to download ContentID 16845337 for UpdateID 16841530. Error code = 13875 SMS_RULE_ENGINE 8/15/2013 6:49:43 PM 6876 (0x1ADC)
    Now the funny thing is if I go to the update itself within update group that Flash is a member I can right click it and choose download and the error doesn't occur.
    I observed that the UNC path for ADR Adobe flash, when the rule is ran, is populated with folders that have a name something like 44738297895427890.1 or 423154325378u867234789.1. I have come to realize that those are failed downloads. So for the
    heck of it I then right clicked the update itself and chose download and it downloaded without issue. Now I'm guessing that when I chose to download directly from the update maybe the system is getting the update from adobe and not from wherever the rule was
    trying to get it from.  I then see the .1 removed from the directory name and there are updates within them.
    Just for clarity here are the steps I go through from SCUP to Syncing...
    Log in to WSUS server
    Run SCUP as administrator
    Get notified there are updates from Adobe and let SCUP download updates
    Find the updates the specify the following publishing options
    Full Content
    Sign all software updates with a new publishing certificate .... (Is this necessary by the way?)
    Then click Next
    After that's done I then go to SCCM Manager Console and go to Software Updates and right click to Synchronize them.
    After that's done then I run the ADR for Adobe Flash and when it goes to download the updates that's when the error occurs.
    What am I missing?
    Also, while I wait for help I just recently added the WSUS SCUP certificate to the SCCM server to see if by chance that fixes stuff. If it does then I'll post the results of adding the certificate to the SCCM server.
    One other thing, is there a way to delete updates? When I was having this issue in the past, I went in to SCUP I marked the updates as expired and then deleted the updates. Went to SCCM and synchronized the updates and they went from not expired to expired
    then I waited, maybe 30 days or so before I could add the updates back in.
    Thanks for the help!

    Yes, I know this is an old post, but I’m trying to clean them up. Did you solve this problem, if so what was the solution?
    Have you seen the note at the bottom of this page about this error?
    http://technet.microsoft.com/en-us/library/bb932193.aspx
    Garth Jones | My blogs: Enhansoft and
    Old Blog site | Twitter:
    @GarthMJ

Maybe you are looking for